- ripe-list - mailman.ripe.net

OPS-NM Interim meeting (Oct 1-2) at RIPE-40 in Prague
by Wijnen, Bert (Bert) 17 Sep '01

17 Sep '01

All, I have only a short list of "registered" participants right now. I do not see enough IETF OPS-NM folk, and I do not see enough European (or better non-USA) operators. I understand and respect that the events of last week may have made you wait to register. However, if we do not get a longer list of participants, then one should wonder if it makes sense to have this meeting at all. If it is caused by last weeks events, then we can consider to move it out to the next RIPE meeting which I believe is in January in Amsterdam. But I wonder if this is really the reason, specifically for the European operators, and after all, we want to speak with these European operators. I think we all seriously hope that things will calm down over the next 2 weeks, and that in October we can more or less assume we can travel again. If that turns out to be false hope, we can cancel the meeting at the last minute. But assuming everything gets better from now on, pls let me know if you plan to attend (see below). To do so,please send me (bwijnen(a)lucent.com) a short email to let us know. Pls add a few lines as to why you want to participate. Bert details about the meeting times, venue, agenda, see below -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] Sent: maandag 3 september 2001 20:31 To: ops-area(a)ops.ietf.org Subject: OPS-NM Interim meeting (Oct 1-2) All, At the last two IETF OPS Area Open meetings, we had some good discussion between the OPS NM folk and some operators. We also have had a so called OPS-NM Interim in the USA that was co-located with NANOG in May of this year. We also called it something like: Net Management Protocol Folk & Net Operators - Reality Check #2 We will have another IETF Interim Meeting for the OPS-AREA Network Management people, this time in Europe, co-located with the next RIPE-NCC meeting. The idea is to meet with another set of operators to try and understand their needs and to explain to them how we think that our NM related work in the IETF can help them to manage their networks. In other words: Net Management Protocol Folk & Net Operators - Reality Check #3 We probably will have similar sessions in the future to meet with people who operate enterprise networks, because their requirements may be different. We are still working on the agenda, however below you will find a prelimenary agenda proposal. Any suggestions should be sent to Randy (randy(a)psg.com) and Bert (bwijnen(a)lucent.com) We have limited space for this meeting. Those who plan to attend, pls send a short email to Bert Wijnen <bwijnen(a)lucent.com> to let us know. Pls add a few lines as to why you want to participate. Bert and Randy -------------- OPS-NM Interim Meeting details ------------------ The plan is to have this meeting co-located with the next RIPE NCC meeting, namely RIPE 40. That means: Oct 1st OPS-NM Interim from 2-5pm Oct 2nd OPS-NM Interim from 9am-noon Oct 2-5 RIPE 40. Starts at 1:30pm on oct 2nd. RIPE 40 and OPS-NM Interim will be in the Prague Congress Centre in Prague, Czech Republic. For RIPE 40 and hotel registration, pls visit: http://www.ripe.net/ripe/meetings/current/ripe-40/ There is a whole range of hotels to choose from, but it is very hard to book, so do it now. Those only participating in the OPS-NM meeting are not required to pay the RIPE meeting fee. Of course, if you want to take the opportunity to participate in the RIPE-NCC meeting, then you should register for that meeting via the web page listed above. Those who plan to attend the OPS-NM Interim should send an email to Bert Wijnen <bwijnen(a)lucent.com> because we only have limited room, and if too many people want to show up we may have to tell some that there is no more space. Prelimenary Agenda ------------------ - Agenda bashing and intro - Summary of the current set of OPS requirements draft-ops-operator-req-mgmt-00.txt Please read this document to prepare for the meeting. If this one no longer exists, then pls check for a possible revision 01.txt. It is important to try and figure out if this also represents needs of European operators, or do they have different/new/additional requirements? - Discussion of the above. - Discussion of SNMP, MIBs, COPS, POLICY and such - how do the developers of these protocols/specs think that they can address operator NM requirments. - what do operators think about that - what kind of positive or negative expoerience do operators have - Operator requirements - what are the real hot issues to be solved this year - what are the constraints within which the tools have to work - Next steps - Wrapup/Summary -30-

1 0

"IP Tutorial" during the RIPE 40 meeting
by Ferenc Csorba 14 Sep '01

14 Sep '01

Dear colleagues, During the RIPE 40 Meeting in Prague, an "IP Request Tutorial" will be held on Friday, 5th October, 14:00-17:30. The "IP Request Tutorial" contains selected sections of the LIR Training course that RIPE NCC provides to its members: - How to Request Address Space - Completing the Request Form - Evaluation of Address Space Requests - Registering Address Space in the RIPE Database - How to Request New Allocation Registration for this tutorial is not necessary. All RIPE meeting participants are more than welcome to attend this tutorial. The slides of this tutorial are available at: http://www.ripe.net/ripe/meetings/archive/ripe-40/presentations/ip-tutorial/ Kind regards, Ferenc Csorba RIPE NCC Trainer

1 0

Reminder: Removal of selected sets of contact information from the RIPE Database
by Joao Luis Silva Damas 13 Sep '01

13 Sep '01

Dear all, (apologies for duplicates) This message is a reminder of the ongoing process of removal of unreferenced contact information from the RIPE Database. We have updated the web page http://www.ripe.net/ripencc/pub-services/db/orphaned.html with a more up to date list of maintainer objects relevant to this process. I would like to use the opportunity to clarify an apparently confusing aspect of previous notes: If your person/role object already has a mnt-by attribute that references a maintainer object not contained in the list provided in the above mentioned web page, there is no need to add a reference to RIPE-NCC-PN-NONE-MNT. This maintainer has been created by the RIPE NCC with the sole purpose of facilitating a mechanism for people without maintainer objects to tag their person/role objects to avoid deletion. If you already have a proper maintainer object, DO NOT include RIPE-NCC-PN-NONE-MNT as this would lower your protection level. Best regards, Joao Damas RIPE NCC

2 1

ipv6 tutorial
by David Kessens 11 Sep '01

11 Sep '01

In case you haven't noticed yet, we will have an ipv6 tutorial on: Monday 1 October : 10 am - 5 pm. The tutorial will be given by Florent Parent. Florent Parent is currently working at Viaginie inc. as a consultant in network architecture and security. He is involved in the architecture and deployment of IPv6 in the CA*net network. IPv6 Tutorial outline: Rationale Features Header Addressing ICMPv6, Neighbor Discovery, Autoconfiguration DNS Routing protocols Transition mechanisms Host and Router configurations Internet deployment I hope this helps, David K. ---

1 0

Removal of selected sets of contact information from the RIPE Database
by Joao Luis Silva Damas 03 Sep '01

03 Sep '01

Dear all, (apologies for duplicates) This is a reminder notice regarding the process of removal of selected sets of contact information from the RIPE Database as initially announced in my mail of 21-8-2001. This phase of the process will affect all person and role objects that are either: - both un-maintained and unreferenced - unreferenced and maintained by maintainers related to registration of domain names in .de For further details about this process, visit the RIPE NCC's web site at http://www.ripe.net/ripencc/pub-services/db/orphaned.html or the "RIPE NCC Annoucements" section at http://www.ripe.net Best regards, Joao Damas Chief Technical Officer RIPE NCC

1 0

Announcement RIPE NCC Annual General Meeting 2001
by AGM role account 03 Sep '01

03 Sep '01

Dear RIPE NCC member, The Executive Board of the RIPE NCC Association is pleased to invite you to the Annual General Meeting(AGM) of the RIPE NCC membership to be held on 30 October 2001 in Amsterdam, The Netherlands. Meeting Venue: Radisson SAS Hotel, Boeing Avenue 2, Amsterdam Schiphol Airport Start Time: 10:30 am According to article [16.2] of the RIPE NCC Articles of Association, those members wishing to attend the Annual General Meeting must register before 15 October 2001. The AGM 2001 meeting registration form can be found at: http://www.ripe.net/cgi-bin/agmreg If you cannot use the form, please e-mail to <agm(a)ripe.net> or send a fax to: +31 20 535 4445. A list of registered attendees will be published regularly on the RIPE NCC Website. You will receive confirmation containing your membership status and number of votes upon your arrival to the meeting. Please note that candidate members are welcome to attend the meeting, but are not permitted to vote according to article [16.3] of the RIPE NCC Articles of Association. Proxy voting for members is possible as per article [16.4]. Please also note that the meeting can only pass resolutions that have been submitted and published according to article [15.2]. The RIPE NCC Articles of Association can be found at : http://www.ripe.net/ripe/docs/articles-association.html With kind regards, Asha Raghoebarsing AGM Coordination

1 0

RIPE 40 reminder
by RIPE NCC Meeting Registration 03 Sep '01

03 Sep '01

Dear Colleagues, This is a reminder for the RIPE 40 meeting, to be held from 1 October - 5 October 2001 at the Prague Congress Center, Czech Republic. More information about this meeting and accommodations can be found on this page: http://www.ripe.net/ripe/meetings/current/ripe-40/ Online registration is open till 21 September 2001. On-site registration will open on Monday 1 October 2001. Please note the following: To avoid waiting queues at the registration desk on-site we encourage pre-payment by credit card. The registration fee for this meeting is EUR 350.00 (this includes refreshments and lunches) and the dinner fee is EUR 65.00. However, if payment is received before 21 September 2001, the pre-payment cut-off date, you will receive a pre-registration discount of EUR 50.00. Therefore, the fee for attendees paying before the cut-off date is EUR 300.00 for the meeting and 65.00 EUR for the RIPE dinner event. If you have any questions, please do not hesitate to contact us at <meeting(a)ripe.net>. With kind regards, Asha Raghoebarsing Meeting Coordinator

2 1

Call for Nominations for Representatives to the ASO Address Council - RIPE region
by Hans Petter Holen 23 Aug '01

23 Aug '01

Dear colleagues, This is a call for nominations of individuals from the RIPE region to serve on the ASO Address Council. During October 2001, one RIPE region Address Council seat will become vacant and will be filled for the next three years by an individual nominated through this open call. This document describes the functions of the ASO and the Address Council, as well as the nomination and selection processes. If you are interested in nominating an individual, or if you are interested in being nominated as a member of the Address Council, please read this document carefully. 1. The Address Supporting Organisation - -------------------------------------- The ASO was formed in August 1999 as a consensus-based advisory body within the ICANN Framework, though a Memorandum of Understanding (MoU) signed by the current Regional Internet Registries and ICANN. The ICANN Bylaws (http://www.icann.org/general/bylaws.htm#VI-A) assign to the ASO the responsibility for the development of global policies relating to the distribution and registration of Internet address space, inter-domain routing identifiers and that part of the DNS name space that is used to name these addresses and identifiers. More information about the ASO is available at: http://www.aso.icann.org 2. The Address Council - ---------------------- The ASO Address Council co-ordinates the process of policy development in areas within the responsibility of the ASO, according to procedures defined within the MoU and by the AC itself. Specifically, these include the hosting of an annual open General Assembly meeting, and attending regular meetings by teleconference or in person at which policy issues and submissions may be considered. The other major responsibility of the Address Council is the appointment of individuals to fill ASO seats on the ICANN Board of Directors, according to procedures defined within the MoU. More information on the Address Council is available at: http://www.aso.icann.org/ac 3. The Role of Members of the Address Council - --------------------------------------------- Members of the Address Council do not represent any RIR, nor do they act as representatives of any other body. They are appointed in their individual capacity, and their membership cannot be proxied by any other individual or organisation. No member of the Address Council is entitled to any compensation from the ASO. No member can be indemnified by the ASO, nor can the ASO obtain insurance coverage relating to the liability of the actions of members of the Address Council. 4. Address Council Nominations Process - -------------------------------------- Through this nomination process, one individual from the RIPE region will be selected to serve on the Address Council for three years, replacing Hans Petter Holen who has served as an initial AC member for the past 2 years. The selection will be made though an open election from the set of individuals who have been nominated within this process. Any individual may be nominated, with the exception of any staff member of any Regional Internet Registry. Self-nominations are permitted. Nominations should be sent by email to <nominations(a)ripe.net>, by midnight UTC on 5 September 2001. The information included with the nomination is to be in English and should include: Name of Nominee: Country of residence: Organisation: Email Address: Postal Address: Biographical information: Motivation for nomination: Name of nominating individual: Organisation: Email Address: All nominees will be contacted via email to confirm their willingness to serve on the Address Council. If a nominee is not contactable via email, or does not respond, then their nomination will not be confirmed and they will not be eligible for election to the Address Council. All confirmed nominations will be listed on the RIPE web site after they are confirmed. All nominees will have the opportunity to submit a written statement in support of their nomination, for publication on the web site. In addition, others may express support for nominated individuals simply by completing and submitting the nomination form provided above. 5. Address Council Selection Process - ------------------------------------ The process for selection of the nominee to serve on the Address Council will involve an open election to be held during the plenary session of the RIPE 40 Meeting, in Prague, Czech Republic, on 5 October 2001. See the following URL for details about the selection procedure: http://www.ripe.net/ripe/wg/lir/adress_council-election.html More information about RIPE 40 will be available shortly at: http://www.ripe.net/ripe/meetings http://www.ripe.net/ripe/meetings/current/ripe-40/ Important Dates: 5 September 2001 - deadline for Address Council nominations Regards, Hans Petter Holen Local IR WG chair

1 1

Re: Removal of selected sets of contact information from the RIPE Database
by Joao Luis Silva Damas 21 Aug '01

21 Aug '01

Dear Hank, I can think of a couple of reasons for requesting this but bear in mind: -We are talking about the deletion of around 2.8 million objects -The only potential link between a person and a country is the address field, which does not necessarily contain a country - Exposing such a list would make a spammers dream. We have tried to protect personal information in the RIPE Database by preventing buld download of personal information and controlling the rate of queries. If we now expose a list of all this information we will doing precisely what we want to avoid Could you put forward some arguments for having this data exposed so we can all weight pros and cons? Thanks, Joao Damas RIPE NCC On Tue, 21 Aug 2001, Hank Nussbacher wrote: > On Tue, 21 Aug 2001, Joao Luis Silva Damas wrote: > > Can a list of "to be deleted" objects per country be posted or if not, how > about after the fact, as to which objects have been deleted per country? > > Thanks, > Hank

1 0

RIPE Region Hostcount for July 2001
by RIPE Hostcount Maintainer 21 Aug '01

21 Aug '01

Dear All, below is the hostcount for July 2001. The table shows an increase since last month of over 98,000 (or 0,6%) to a total of almost 15,310,000 hosts in the DNS in Europe and surrounding areas. The se domain shows the highest increase for July with approximately 78,522 hosts more than in June. Background information and more statistics are available at http://www.ripe.net/hostcount/ - Brief Notes on this Hostcount - - The June, 2001 data had to be reused for es because no new data was available from the remote collector. - The June, 2001 data had to be reused for fr because the data collected wasn't complete. - Credits - I would like to thank all people who help me to create the hostcount every month by running a local count: ad Joan Marc Lauga am Hrant Dadivanyan at Gerhard Winkler be DNS-BE Registration Office ch Marcel Schneider cy Vasoula Papapetrou cz Jiri Orsag de Peter Koch dk Morten Christensen eg EUN Hostcount Admin es Fco. Sanchez Benavides fr Annie Renard ie Mike Norris is Marius Olafsson it Maurizio Martinelli Daniele Vannozzi li Marcel Schneider lt Daiva Tamulioniene lu Alain Frieden mk Goran Muratovski mt Robert Sultana no Havard Eidnes pl Mirek Luc pt Joao Pagaime ro Eugenie Staicut ru Andrey Dobrotsvetov sm Maurizio Martinelli Daniele Vannozzi If you have any questions, please don't hesitate to contact me. Kind regards, Paul Vlaar RIPE NCC RIPE DNS Hostcount Previous Count : Thu Jul 26 2001 This Count : Tue Aug 21 2001 CY SOA COUNTED DUPL REAL CHANGE ============================================================== ad 605 2531 874 1657 5 ae 3386 53599 3284 50315 10442 al 100 228 36 192 20 am 1307 3588 1330 2258 78 at 152440 755938 239593 516345 -3573 az 1230 2133 820 1313 9 ba 507 4346 1202 3144 19 be 57628 402268 73383 328885 -7772 bf 42 675 36 639 1 bg 1502 27623 3548 24075 72 bh 60 2265 555 1710 96 bj 24 513 9 504 0 by 510 4047 1020 3027 271 cf 234 811 351 460 73 ch 181548 829924 283353 546571 56172 ci 360 3452 463 2989 0 cm 55 383 42 341 2 cv 24 140 112 28 1 cy 876 8535 877 7658 341 cz 105659 299547 114181 185366 262 de 2801506 10696193 8335121 2361072 66435 dj 31 40 31 9 0 dk 213630 750238 283689 466549 15885 dz 101 747 100 647 30 ee 7748 61630 16757 44873 234 eg 1491 3726 1044 2682 647 er 43 263 24 239 0 es 18687 518534 31596 486938 0 fi 29695 848656 63223 785433 5224 fr 96586 1078056 172229 905827 0 ga 38 74 24 50 0 gb 2 24 0 24 0 ge 632 3458 1585 1873 132 gg 1716 2598 1148 1450 9 gh 40 427 25 402 -62 gi 626 1391 183 1208 -12 gl 902 3025 484 2541 4 gm 452 299 198 101 1 gn 31 359 140 219 12 gq 4 4 2 2 0 gr 25863 163962 27546 136416 -16622 gw 2 21 1 20 0 hr 5338 36872 16273 20599 -6150 hu 40463 215486 77502 137984 6430 ie 18561 141449 25679 115770 -500 il 25045 193569 63875 129694 -5034 im 556 963 405 558 8 ir 339 3115 712 2403 -1 is 6910 55760 8842 46918 209 it 463701 1456188 577497 878691 -57411 je 1780 2734 1214 1520 16 jo 631 2884 935 1949 154 ke 1401 5835 962 4873 -254 kg 1093 6260 1720 4540 290 kz 2501 12993 3109 9884 1134 lb 1284 8022 1542 6480 -60 li 1352 2748 1812 936 -2408 lr 14 13 3 10 0 lt 7520 36005 6917 29088 246 lu 5551 18230 4670 13560 1161 lv 6323 33173 10258 22915 494 ma 1770 4918 2826 2092 27 mc 429 1008 572 436 1 mk 705 2488 496 1992 6 mt 1081 8626 1836 6790 25 ne 18 152 10 142 40 ng 290 2789 1420 1369 28 nl 450739 3607541 1057369 2550172 -31282 no 60679 473611 69222 404389 -67516 om 111 5911 2989 2922 2 pl 88593 749930 214970 534960 9789 pt 15851 191716 34602 157114 -35227 qa 38 335 234 101 1 ro 9715 64787 17203 47584 4857 ru 109873 656253 310805 345448 2010 sa 2271 13627 2458 11169 -83 se 68537 740999 70530 670469 78522 si 7952 36548 7840 28708 429 sj 1 0 0 0 0 sk 34624 138051 75080 62971 9268 sl 7 271 1 270 -8 sm 379 1680 342 1338 9 so 1 10 6 4 0 su 1073 29064 3563 25501 1048 sy 4 18 9 9 0 td 1 6 5 1 0 tj 120 981 686 295 3 tm 1275 3009 1411 1598 20 tn 28 348 162 186 3 tr 16981 126360 26206 100154 9975 ua 31561 145140 95551 49589 2220 ug 240 467 203 264 18 uk 1445399 5038315 3057723 1980592 47101 va 2 9 0 9 0 yu 9238 22781 7372 15409 366 ============================================================== 95 6657872 30836319 15527848 15308471 +98412

1 0