July 1999 - ripe-list - mailman.ripe.net

Final RIR ASO Proposal Submission to ICANN
by Mirjam Kuehne 27 Aug '99

27 Aug '99

Dear Colleagues, Thank you very much for the support received regarding the 'Draft proposal for a MoU-based ASO'. As you know, your support is essential to the process and therefore very much appreciated. Discussions following the announcement of the draft proposal on 8 July 1999, and at the recent open ASO meeting which took place at the IETF in Oslo, modifications to the draft proposal were suggested. Following discussions between the RIR excecutive boards, taking into account the collective interests of our communities, further adjustments were made to the proposal which we believe will enhance the prospect of its adoption by ICANN. A proposal for the formation of an ASO has now been formally submitted to ICANN jointly by the Regional Internet Registries: APNIC, ARIN and RIPE NCC. The 'Proposal for a MoU-based ASO' can be found on the RIPE NCC Web site under the 'Current Issues' section at: http://www.ripe.net/info/ncc/icann.html Below please find the modified sections of the draft text as well as comments supporting the motivation for each of these changes. As the adjustments to this proposal have been made for clarity purposes to ensure fair and open processes in all regions, we hope that we can count on your continued support. Kind Regards, Mirjam Kuehne RIPE NCC 2. The Address Council. a. Members. ----------- [original text:] Each RIR signatory of the MOU will appoint two [2] individuals to the Address Council by means of their own choosing. No individual can serve on the Address Council and be on the staff of a RIR at the same time. [final version:] Each RIR signatory of the MOU will select three [3] individuals to the Address Council using the following process: i Annually the RIR will issue a public call for nominees to the Address Council at least 90 days before the RIR's policy meeting. Any individual can submit a nomination to the RIR. ii The due date for this call shall be 30 days before the meeting. iii The nominees must be individuals. iv A list of all nominees who agree to run for the Address Council must be posted on the RIR's web page at least 15 days before the meeting along with a statement from each nominee who wishes to make one. v Selection of the RIR's members of the Address Council will be made via an open and transparent procedure. The individuals selected for the Address Council must not be staff members of the RIR. COMMENTS: Concerns were raised that having only two [2] Address Council members appointed per region would not allow for sufficient representation. Therefore the number was changed to three [3] per RIR signatory. When additional RIRs sign the MoU this will be revised in order to keep the number of Address Council members at a practical size. Principles for the selection of Address Council members were stated in section 3.b. of the original draft proposal. These methods have been refined and included in this section for further clarification. However, please note that the selection process of the Address Council members will be defined by the regions via an open and transparent procedure. b. Term. -------- [original text:] The term of Address Council members will be 2 years. Removal will be pursuant to procedures established through the MOU. (Initial terms will be 1 and 2 years to provide initial conditions for staggered terms.) [final version:] The term of Address Council members will be 3 years. Removal will be pursuant to procedures established through the MOU. (Initial terms will be 1, 2 and 3 years to provide initial conditions for staggered terms.) COMMENTS: With the increased number of Address Coucil members one additonal term has been defined. c. Powers/Duties of the Address Council. ---------------------------------------- ii Qualifications of ICANN Directors. [original text:] No more than 1 of the ASO-appointed Directors may come from the same geographic region. [final version:] a) No more than 1 ASO-appointed Director may come from the same geographic region. (This proposal assumes the regions defined in the ICANN by-laws.) b) No ASO-appointed Director may serve simultaneously on the Address Council. COMMENTS: The additional sentence under a) is to clarify the word 'region' in this context. Parapraph b) was added as no clear prohibition against Address Council members also serving on the ICANN board was stated. d. Address Policy Development. ------------------------------ [final version:] One paragraph was added to this section: In addition the Address Council may accept, for consideration, proposals for changes to global IP address policy from any interested individual. COMMENT: One may imagine a circumstance where it would be more practical to approach the ASO directly to support the fair and open consideration of a proposal in order to stress equal opportunity for all interested parties. In any case, all proposals received by the ASO will be reviewed by the RIR signaories and the community as described in this section following the above noted addition: In all cases when the Address Council reviews proposals for new global policies or proposed modification to existing policies in this area it will first solicit the opinions of all of the RIR signatories of the MOU and of the public. 3. Annual Open Meeting. (General Assembly) a. Hosting an open meeting. --------------------------- [original text:] The Address Council will periodically host an open meeting ("General Assembly") for promoting discussion and receiving input regarding the work of the ASO. A General Assembly meeting will be held once per year, and will permit open participation by all interested individuals. [final version:] The Address Council will periodically host an open meeting ("General Assembly") for promoting discussion and receiving input regarding the work of the ASO. A General Assembly meeting will be held *at least* once per year, and will permit open participation by all interested individuals. COMMENT: It was felt that the number of meetings should not be restricted in this document. The important point here is that there should be *at least* one meeting per year. b. Selection of Address Council Members. ---------------------------------------- [original text:] Ninety days prior to each General Assembly, ICANN and the Address Council shall make an open call for nominations to any potential vacancies in the Address Council. The results of this call will be forwarded to each RIR signatory to the MOU for their information. Each RIR signatory to the ASO MOU will be entitled to select two [2] members of the Address Council by means of its own choosing. The terms of the appointees will be determined by the appointing RIR. [final version:] Ninety days prior to each annual open meeting, ICANN and the Address Council shall make an open call for nominations to any potential vacancies in the Address Council. The results of this call will be forwarded to each RIR signatory to the MOU for their information. Each RIR signatory to the ASO MOU will be entitled to select three [3] members of the Address Council using the process described in Section 2a. COMMENT: This has been changed in order to make the section consistent with the principles outlined in section 2.a (see above). 4. Open Proceedings and Documents. b. ASO Proceedings ------------------ [original text:] All discussions of ASO business will be conducted on or reported on a publicly-archived mailing list accessible through the ICANN/ASO web site. The schedule for the ASO meetings will be posted 90 days in advance of the meeting date. The agenda for the Address Council and annual open meetings will be posted on the ICANN/ASO web site at least 30 days before the meetings. The minutes from all ASO meetings will be publicly posted on the ICANN/ASO web site within 30 days of the meeting. [final version:] All discussions regarding ASO policy formation will be conducted on or reported on a publicly-archived mailing list accessible through the ASO web site. The schedule for the ASO meetings will be posted 90 days in advance of the meeting date. The agenda for the Address Council and annual open meetings will be posted on the ASO web site at least 30 days before the meetings. The minutes from all ASO meetings will be publicly posted on the ASO web site within 30 days of the meeting. In the unlikely event that the policy formation discussions involve confidential commercial data that was presented in an address allocation process the above disclosures must be done in a way to protect the confidentially of that data. COMMENT: The location of the documentation to be published has been more clearly specified (on the ASO web site). The last sentence has been added in order to explicitly exempt confidential data from publication as defined in the existing RIR operational procedures. 6. Recognition. [original text:] 7) That the introduction of a new RIR must be based on a "Sound Business Plan". The plan must be reviewed by ICANN and by the existing RIRs. The process for creating a new RIR must be included in the MOU. [final version:] 6) That the proposed RIR has clearly defined procedures open to all interested parties regarding ensuring fair representation of constituents within the region of coverage in the policy development process. COMMENT: This paragraph was added in order to ensure open and transparent processes of policy development in all new and existing RIRs. For your information, please note that the order of points in appendix A has slightly changed, resulting in the number change noted above.

3 2

RIPE 34 Meeting Announcement
by RIPE NCC Meeting Registration 23 Jul '99

23 Jul '99

Dear Colleagues, [ Apologies for duplicate mails ] It is our pleasure to open registration for the 34th RIPE meeting, which will be held from 21 - 24 September 1999 at: Krasnapolsky Hotel, Damsquare, in Amsterdam, the Netherlands. On-site registration will open on Tuesday 21st September. Please note: - To avoid wait queues at the registration desk on-site we encourage pre-payment by credit card. The registration fee for this meeting is EUR 170.00 (this includes refreshments and lunches) and the dinner fee is EUR 55.00. However, if payment is received before 10th September 1999 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 120.00 for the meeting and 55.00 EUR for the RIPE dinner event. Confirmation of Registration: For your convenience we have prepared a fax form for sending your credit card number. This form is attached to the acknowledgement of your registration and we encourage you to use it when possible. Alternatively you can register using our secure website at: https://www.ripe.net/meetings/ripe/form34.html (encrypted form) http://www.ripe.net/meetings/ripe/nsform34.html (non-encrypted form) You will receive a second acknowledgement by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. For more details please see: "RIPE Meeting Fees and Refunds" at: http://www.ripe.net/meetings/ripe/meeting-int.html Participants requiring a visa to enter the Netherlands are advised to begin the required procedures as soon as possible. The RIPE Meeting organisers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at <meeting(a)ripe.net>. Kind regards, Naomi de Bruyn RIPE Meeting Registrations ---------------------------------------------------------------------------- Registration is also possible and easier online at: https://www.ripe.net/meetings/ripe/form34.html http://www.ripe.net/meetings/ripe/nsform34.html %START Do not change the following field %MTG [ ripe34 ] Please add a value in the 'box' area marked between the square brackets (i.e. "[" and "]" s). If values are already supplied between the brackets, please delete all values except one. PART 1 - Registration Note this is what will be used for your badge and for the attendee list, so please take care to fill it in correctly. 1) Your name Please enter your first name only. e.g. John , Mary B. %NAME [ ] Please enter your surname next e.g. Doe %SURNAME [ ] 2) Your Organisation/Institution %ORG [ ] 3) Your Organizations Complete Postal Address e.g. Singel 258, 1016 AB Amsterdam, The Netherlands %ORGADDR [ ] 4) The NCC Reg-id of your Organisation %REGID [ ] (Only if you represent a Local Internet Registry) 5) Your e-mail address %EMAIL [ ] 6) Country code of organisation e.g. IT FR DE %CTRY [ ] 7) Do you want to attend the Newcomers Orientation Talk ? (please delete one option so your choice is in the form) %INTRO-MTG [ no / yes ] 8) Do you want to attend the EOF Tutorial ? (please delete one option so your choice is in the form) %EOF-TUTOR [ no / yes ] 9) Do you want to attend the IPv6 Tutorial ? (please delete one option so your choice is in the form) %IPV6-COURSE [ no / yes ] PART 2 - Payment of Registration Fees WARNING!! - Note that sending your credit card information via e-mail is in principle not secure. The payment information will be transmitted in clear via e-mail. If you do not want to do this, please leave your credit card details blank in this form, and send them to us by fax. Please do not forget to mention your name and organisation on the fax, so there will be no risk in us getting confused. Our fax number is: +31 20 535 44 45 1) Method of payment. Payment in advance is greatly preferred. (please delete all choices except one) %PMETH [in advance; credit card / at meeting; credit card / at meeting; cash ] ( *NB: please note aforementioned reduction when paying in advance *) 2) Type of credit card (please delete all choices except one) %CTYPE [ VISA / American Express / Mastercard ] 3) Card number %CCNUM [ ] 4) Expiry date %CCDATE [ ] 5) Card holders name %CCNAME [ ] 6) Card holders address %CCADDR [ ] 7) Amount to be paid %AMT [RIPE Meeting only incl. reduction; EUR 120 / RIPE Meeting only excl. reduction; EUR 170 / RIPE Meeting plus RIPE dinner incl. reduction; EUR 175 / RIPE Meeting plus RIPE dinner excl. reduction; EUR 225] Payment details sent online cannot be processed after September 10th, 1999 with this form. You are welcome to send in your personal data with this form to register, but the actual payment can then only be made at the meeting itself on September 21st, 22nd, 23rd and 24th 1999. ( again: please choose reduction ONLY when paying in advance ) %END

1 0

RIPE NCC office closed on Wednesday 21st July 1999
by RIPE NCC Staff 20 Jul '99

20 Jul '99

Dear Colleagues, Please note that the RIPE NCC office will be closed on: Wednesday 21st July 1999. On this day the RIPE NCC staff will go on their annual staff outing. This means that there will be no one in the office to reply to your e-mails and phonecalls. The office will be open again on Thursday 22nd July 1999. Kind regards, Naomi de Bruyn RIPE NCC

1 0

IMPORTANT: ICANN ASO, Your Expicit Support Required.
by Daniel Karrenberg 18 Jul '99

18 Jul '99

=====> your explicit support is needed, see further below <======= Dear Colleagues, We have recently published the draft proposal for the ICANN Address Supporting Organisation (ASO). The proposal is the result of numerous discussions within the RIPE community and the collective effort of all the Regional Internet Registries: APNIC, ARIN and the RIPE NCC. The proposal reflects the input we have received from the community. In particular it builds on the existing regional structures and proposes to continue using the well established processes we have been using to develop address space related policies over the years. This eliminates the need for you to participate in another, global, process of IP addressing policy development in order to be represented and defend your interests. The Regional Internet Registries plan to collectively submit the ASO proposal to ICANN later this month. This will allow ICANN to consider the proposal at the ICANN meeting to be held on 24-26 August 1999 in Santiago, Chile. The cover letter and draft proposal for a MoU-based ASO document can be found under the current issues section at: http://www.ripe.net/info/ncc/icann.html If you have any comments or discussion points please use the mailing list <aso-discuss(a)ripe.net>. If you can support the draft as is, please register your explicit support on that list too. Since there is at least one other proposal (also referenced from the URL above) it is extremely important that our proposal collects as much explicit support from ISPs as possible. Without this support being explicit, ICANN will not be able to decide on the establishment of the ASO in an expeditious fashion. It will be very useful if your supporting message would include - Organisation Name - RIPE NCC registry ID (if a LIR and if known) - Function (get someone with an impressive job title to send it ;-) Thank you for your support Rob Blokzijl Chairman of RIPE Keith Mitchell Chairman of the RIPE NCC Executive Board Daniel Karrenberg General Manager of the RIPE NCC

3 2

RIPE Region Hostcount for June 1999
by RIPE Hostcount Maintainer 13 Jul '99

13 Jul '99

Dear All, below is the hostcount for June 1999. I once again apologise for the lateness of this report. The 'host' tool needed to be adjusted to handle the large size which is now being reached by some zones, and one of the TLDs had to be rerun as a result. The table shows a *decrease* since last month of over 250,000 (or 2.9%) to a total of around 8,500,000 hosts in the DNS in Europe and surrounding areas. The fr domain shows the highest increase for June with approximately 44,000 hosts more than in May. Background information and more statistics are available at http://www.ripe.net/statistics/hostcount/ - Brief Notes on this Hostcount - The large drop in the number of zones and hosts counted this month is explained by the following: - the collecting machine for de (and the IP address) was changed, resulting in blocked zone transfers for many zones which had previously been accessible. - a major provider for fi accidentally tightened zone transfer restrictions on their main nameservers, resulting in rejection of requests from the RIPE NCC. - large zones in several other TLDs (e.g. it, uk) became restricted as regards zone transfers. Zone transfer restrictions now have an obvious major (detrimental) effect on the hostcount. The RIPE NCC will undertake action over the next weeks to attempt to rectify this situation. The numbers in the hostcount will only ever be useable as a mimimum estimate, but we wouldn't like to see the accuracy continue to decline so severely. - Credits - I would like to thank all people who help me to create the hostcount every month by counting hosts locally: ad Joan Marc Lauga am Edgar D Danielyan at Gerhard Winkler be DNS-BE Registration Office ch Marcel Schneider cy Vasoula Papapetrou cz Jiri Orsag de Peter Koch dk Morten Christensen eg Network Operator es Susana Gayo. CSIC-RedIRIS fr Annie Renard gr Dimitris Zisiadis hr Ivan Maric ie Mike Norris il Shuki Kenan is Marius Olafsson it Maurizio Martinelli Daniele Vannozzi li Marcel Schneider lt Daiva Tamulioniene mk Goran Muratovski mt Robert Sultana no Havard Eidnes pl Mirek Luc pt Armando Domingues ro Eugenie Staicut ru Andrey Dobrotsvetov sk Lubos Elias sm Maurizio Martinelli Daniele Vannozzi tr Hostcount Maintainer uk Robert Stone Kevin Hoadley If you have any questions, please don't hesitate to contact me. Kind regards, Lee Wilmot RIPE NCC RIPE DNS Hostcount Previous Count : Wed Jun 9 1999 This Count : Tue Jul 13 1999 CY SOA COUNTED DUPL REAL CHANGE ============================================================== ad 309 1051 434 617 0 ae 452 18131 478 17653 - 15 al 18 225 15 210 + 9 am 245 1519 278 1241 + 72 at 40197 262694 76346 186348 + 4175 az 115 442 66 376 - 30 ba 109 1572 161 1411 + 488 be 17966 343931 31971 311960 + 2136 bf 12 379 77 302 + 1 bg 807 16502 1332 15170 + 257 bh 27 1556 140 1416 + 10 bj 14 131 13 118 + 35 by 185 1435 300 1135 - 56 cf 2 7 0 7 0 ch 66631 355805 87099 268706 + 15658 ci 100 299 62 237 + 17 cm 7 241 3 238 0 cv 11 64 46 18 - 5 cy 791 5536 351 5185 + 151 cz 33312 125881 23695 102186 - 275 de 419820 2606584 1132060 1474524 -135471 dj 6 44 5 39 0 dk 79628 397278 88124 309154 - 8866 dz 24 194 15 179 + 35 ee 3158 29528 2374 27154 + 67 eg 1062 3017 446 2571 - 33 er 1 2 0 2 + 1 es 15046 384881 22946 361935 + 4827 fi 11247 434488 23054 411434 - 81079 fo 243 903 46 857 + 263 fr 42258 689639 82684 606955 + 44197 ga 17 53 29 24 + 4 gb 2 27 0 27 0 ge 70 989 44 945 + 179 gg 204 263 168 95 + 10 gh 8 8 2 6 - 263 gi 155 678 322 356 + 2 gl 268 2738 525 2213 + 43 gn 2 10 0 10 + 7 gq 5 11 6 5 0 gr 8734 70607 7408 63199 + 1688 gw 2 21 1 20 0 hr 2706 17926 4406 13520 + 664 hu 9504 122710 17246 105464 + 17569 ie 8016 68875 8067 60808 - 360 il 10360 159513 28337 131176 + 1921 im 174 211 90 121 + 6 iq 1 0 0 0 0 ir 89 1178 132 1046 + 146 is 2279 27550 1882 25668 - 293 it 34459 234490 36931 197559 - 93156 je 201 202 87 115 - 10 jo 468 1400 457 943 + 3 ke 349 3172 692 2480 + 2059 kg 79 1224 148 1076 - 429 kz 486 3299 631 2668 + 277 lb 1117 4004 1254 2750 - 157 li 1170 2778 1034 1744 - 85 lr 6 0 0 0 0 lt 1965 13009 1129 11880 + 162 lu 2562 10149 1513 8636 + 222 lv 1354 20099 4119 15980 + 231 ma 463 2992 743 2249 + 72 mc 286 763 235 528 + 11 mk 523 1810 249 1561 + 149 ml 15 158 9 149 + 74 mt 393 5974 542 5432 + 4 ne 16 134 6 128 + 29 ng 220 744 513 231 + 14 nl 76351 834842 109986 724856 - 13803 no 26978 370493 23895 346598 + 5843 om 27 2877 23 2854 - 12 pl 25004 192840 50789 142051 - 20386 pt 8811 77828 11343 66485 + 822 qa 34 1072 8 1064 + 7 ro 3027 33418 4889 28529 - 1575 ru 23483 253883 52305 201578 + 10215 sa 594 4223 777 3446 + 433 se 34650 537856 39529 498327 + 11798 si 4365 26234 3389 22845 + 339 sj 1 0 0 0 0 sk 8477 34140 8048 26092 - 176 sl 1 0 0 0 - 74 sm 95 357 22 335 + 6 sn 97 959 223 736 + 144 su 1657 28054 1844 26210 - 1553 sy 4 1 0 1 0 tj 170 1037 707 330 + 82 tm 1463 2907 1659 1248 + 64 tn 1 72 45 27 0 tr 9094 99276 13923 85353 + 19294 ua 3185 39386 14949 24437 + 917 ug 21 142 8 134 - 4 uk 213490 1872631 376396 1496235 - 45697 uz 233 705 346 359 - 6 va 2 8 0 8 0 ye 34 49 21 28 + 1 yu 2711 9773 1383 8390 - 624 ============================================================== 98 1266591 10888791 2410085 8478706 -256583

1 0

Regional Internet Registries Announce Proposal for an ICANN ASO
by RIPE NCC 08 Jul '99

08 Jul '99

Regional Internet Registries Announce Proposal for an ICANN Address Supporting Organisation (ASO) Amsterdam, The Netherlands -- 8 July 1999 -- The Reseaux IP Europeens Network Coordination Centre (RIPE NCC), the American Registry for Internet Numbers (ARIN), and the Asia Pacific Network Information Centre (APNIC) have published today a collectively developed policy draft describing the Address Supporting Organisation (ASO). The proposal will be submitted to the Internet Corporation for Assigned Names and Numbers (ICANN) later this month. At this stage, the RIPE NCC has distributed the proposal to its membership, the RIPE community and the general public for comment. The current Regional Internet Registries (RIRs) ensure that IP address space is managed in a globally consistent, fair and responsible manner. The primary activity of the RIRs is the allocation of Internet resources required for the stable and reliable operation of the Internet. In addition, the RIRs play a key role in Internet administration directly in keeping with the interests of their membership and the Internet community. The RIPE NCC has carried out these activities in Europe and surrounding areas since 1992. Policies governing these activities are developed in an open process accessible to all interested parties. Global policies have long been established in a bottom-up method whereby the Internet community develops policies that are co-ordinated among the RIRs and the Internet Assigned Numbers Authority (IANA) that were ultimately approved by IANA. These structures are currently established in all regions. The regional processes are open and transparent and have existed for several years in the RIPE NCC service region through RIPE, a collaborative organisation open to all parties. The main purpose of RIPE is to discuss technical and policy issues affecting the Internet Service Providers in the RIPE NCC service region. The ASO is part of the ICANN structure established to formalise activities previously carried out by IANA. The ICANN bylaws call for an ASO to co-ordinate Internet address policy development. As the activities of IANA related to IP address administration will be formally transferred to ICANN, the RIRs are defining the structure of the ASO building on the existing and well established processes. The collective proposal reflects the desire of the Internet community to be represented through the successful regional structures and not be compelled to participate in another global process to defend their interests. Similar to the set-up of the Protocol Supporting Organisation and the Domain Name System Supporting Organisation, the ASO proposal is based on the formation of a Memorandum of Understanding among ICANN and the Regional Internet Registries. The cover letter and draft proposal for a MOU-based ASO document can be found under the current issues section at: http://www.ripe.net/info/ncc/icann.html - About RIPE Network Coordination Centre (RIPE NCC) Established in 1992 and located in Amsterdam, The Netherlands, the Reseaux IP Europeens Network Coordination Centre (RIPE NCC) is one of three Regional Internet Registries providing resources necessary to support the operation of the Internet. The RIPE NCC is a membership based association and is open to anyone using the RIPE NCC services, primarily Internet Service Providers (ISPs). The services provided to its members ensure the fair and impartial distribution of global Internet resources in the RIPE NCC service region. These resources include IP address space and Autonomous System (AS) numbers. The organisation currently provides services for members in over 80 countries. The activities and services are defined, performed, discussed and evaluated in an open manner. In all of its activities, the RIPE NCC observes strict neutrality and impartiality with respect to individual members. For further information please see: http://www.ripe.net/ - About American Registry for Internet Numbers (ARIN) http://www.arin.net/ - About Asia Pacific Network Information Centre (APNIC) http://www.apnic.net - About Internet Corporation for Assigned Names and Numbers (ICANN) http://www.icann.org Press Contact: RIPE NCC Tel: +31 20 535 4444 / Fax +31 20 535 4445 rendek(a)ripe.net

1 0