January 2000 - ripe-list - mailman.ripe.net

LIR.34.6 Define final Address council selection procedure
by hph＠infostream.no 18 Jan '00

18 Jan '00

Dear Local IR WG & RIPE community at large, At the last RIPE meeting we selected 3 representatives to the ICANN ASO address council by an interim mechanism that was defined at the meeting. This was indeed an interim solution and we need to agree on a more formal method before the first term of an AC member expires. The selection procedure itself must be open and transparent. By extension, the process by which this procedure is defined should also be open and transparent. In this sense, the whole RIPE community should be involved. The correct forum is, I believe, the LIR WG, but it is worth broadening the participation to allow anyone to take part in the discussion on the list and at RIPE meetings. This matter will be one of the most important discussions at the upcoming RIPE 35 an I will urge you all to contribute, both to the mailinglist and at the meeting. The discussions will take place in the lir-wg or in a separate meeting for this topic only, if the meeting schedule permits The framework these selections must operate within is by the ASO MoU and, ultimately, by the ICANN bylaws. http://www.aso.icann.org/docs/aso-mou.html The most relevant points being: 2a Selection. Each RIR signatory of the MOU will select three [3] individuals to the Address Council using the following process: (i) Each RIR will annually 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 any RIR. (b) Term. The term of Address Council members will be 3 years. The initial Address Council members selected within each region will have staggered terms of 1, 2 and 3 years. The process by which these initial members are selected must also determine in an open and transparent manner, the assignment of terms to each of the initial members. --- So if the next selection is to be performed at RIPE 37 in September the open call needs to be before June, or practically best at RIPE 36 in Budapest. We should best case define the selection procedure at RIPE 35 but it could be concluded at RIPE 36 at latest. Since the MOU describes the nomination process in broad terms and not to specific details like whether the nominations should be done publicly or not, and whether one should have the opportunity to express support to individual candidates or not. This may need to be refined. In particular we need to address - Can an individual nominate themselves? - Does the nomination need to come from more than one person? To the selection procedure in particular at least the following needs to be defined: - Who performs the selection - In what way is the selection performed We should bear in mind that the process should be open and transparent, and it is likely to be some sort of election but that is not strictly necessary. - We need to consider whether to do the election at a meeting - or electronically I would like to see a small task force formed that will summarise the discussion on the mailinglist into at least one proposal to be presented at the next RIPE meeting. Tentative plan: 18/1 Start of discussion 31/1 End of discussion 7/2 Proposal circulated on list 21/2 Week of RIPE 35 Sincerely, Hans Petter Holen LIR-WG chair

1 0

RIPE Region Hostcount for December 1999
by RIPE Hostcount Maintainer 18 Jan '00

18 Jan '00

Dear All, below is the hostcount for December 1999. The table shows an increase since last month of over 60,000 (or 0.6%) to a total of over 10,275,000 hosts in the DNS in Europe and surrounding areas. The 'no' domain shows the highest increase for December with approximately 64,000 hosts more than in November. Background information and more statistics are available at http://www.ripe.net/pub-services/stats/hostcount/ - Brief Notes on this Hostcount - The excessive drop for ru was caused by a change in IP address for the counting machine. This resulted in many more AXFR refusals than previously. The de and it numbers are copied from the November 1999 count, since no new data was available due to technical difficulties. - Credits - I would like to thank all people who help me to create the hostcount every month by running the hostcount 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 Netvision 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 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 : Mon Dec 13 1999 This Count : Tue Jan 18 1999 CY SOA COUNTED DUPL REAL CHANGE ============================================================== ad 372 1225 536 689 + 47 ae 940 24370 518 23852 + 548 al 36 233 18 215 + 6 am 374 3001 688 2313 + 100 at 54425 371095 108463 262632 + 4371 az 155 682 79 603 + 22 ba 119 2419 187 2232 + 95 be 22658 377569 38212 339357 + 7406 bg 907 18877 2045 16832 + 898 bh 39 1725 230 1495 + 6 bj 15 131 9 122 + 6 by 95 1082 199 883 - 24 ch 89903 385861 116049 269812 - 24184 ci 142 418 142 276 + 13 cm 10 242 9 233 - 2 cv 7 67 50 17 0 cy 555 6819 594 6225 + 1 cz 46224 159919 37666 122253 + 2117 de 697088 3669941 2034874 1635067 0 dj 10 49 10 39 0 dk 103493 450173 111934 338239 - 4898 dz 21 210 10 200 - 2 ee 3983 34299 4196 30103 + 1429 eg 1319 3085 730 2355 + 232 er 1 4 0 4 + 1 es 17643 497593 28006 469587 + 27114 fi 14744 498989 37229 461760 - 13849 fo 310 774 52 722 - 1 fr 57587 1354019 120948 1233071 + 25254 ga 17 42 20 22 + 5 gb 2 27 0 27 0 ge 79 942 44 898 - 81 gg 337 1502 251 1251 - 44 gh 23 403 50 353 + 1 gi 218 1045 596 449 + 1 gl 373 2981 574 2407 + 71 gn 8 393 166 227 + 3 gq 5 11 6 5 0 gr 11492 85968 10880 75088 - 570 gw 2 21 1 20 0 hr 2928 19050 4515 14535 - 329 hu 11833 151108 31466 119642 + 7391 ie 9650 73723 9810 63913 - 2035 il 14433 201696 52206 149490 + 1205 im 263 1472 185 1287 - 25 iq 1 0 0 0 0 ir 99 1285 118 1167 + 17 is 2966 33638 3766 29872 + 1084 it 44153 347216 45688 301528 0 je 344 1501 203 1298 - 30 jo 565 1572 594 978 - 4 ke 422 3824 459 3365 - 13 kg 185 3887 352 3535 + 201 kz 798 6658 943 5715 - 434 lb 1215 5532 1643 3889 - 12 li 2082 5291 1922 3369 + 3 lr 1 0 0 0 0 lt 2715 15660 1467 14193 + 49 lu 2939 11683 2069 9614 - 39 lv 1907 24329 5452 18877 + 166 ma 651 2997 963 2034 - 405 mc 229 581 245 336 - 2 mk 519 1804 317 1487 + 102 ml 29 243 19 224 + 2 mt 555 6879 874 6005 + 351 ng 257 1390 793 597 + 244 nl 124124 1131625 172542 959083 + 62837 no 30452 467253 28292 438961 + 63749 om 34 2923 57 2866 - 4 pl 33550 256178 84961 171217 - 2935 pt 5784 87550 9789 77761 + 13152 qa 32 1084 15 1069 - 2 ro 4085 41942 5648 36294 + 1508 ru 7752 80887 16902 63985 -121572 sa 1130 5423 1263 4160 + 223 se 37799 571964 49076 522888 + 10891 si 3230 27262 3663 23599 + 1185 sj 1 0 0 0 0 sk 10995 39494 11311 28183 + 632 sl 7 77 0 77 0 sm 105 526 47 479 - 15 sn 170 1181 237 944 + 37 su 1463 29370 1925 27445 + 69 sy 7 15 9 6 0 tj 219 1412 901 511 + 62 tm 1367 2479 1627 852 - 90 tn 1 103 70 33 - 1 tr 10089 91212 12334 78878 - 415 ua 5096 50597 21624 28973 + 1275 ug 35 208 28 180 - 1 uk 433251 2485027 745976 1739051 - 2649 va 2 9 0 9 + 1 ye 41 58 28 30 + 2 yu 3626 12765 2221 10544 + 138 ============================================================== 94 1941917 14269849 3992886 10276963 + 61656

1 0

Reminder RIPE 35
by RIPE NCC Meeting Registration 12 Jan '00

12 Jan '00

Dear Colleagues, [ Apologies for duplicate mails ] We would like to remind you that the registration for RIPE 35 in Amsterdam: 22 - 25 February 2000, has been opened. More information about this meeting can be found on this page: http://www.ripe.net/ripe/meetings/current/ripe-35/index.html On-site registration will open on Tuesday 22nd February. Please note the following: - 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 280.00 (this includes refreshments and lunches) and the dinner fee is EUR 65.00. However, if payment is received before 11th February 2000 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 230.00 for the meeting and 65.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/ripe/meetings/current/form35.html (encrypted form) http://www.ripe.net/ripe/meetings/current/nsform35.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. 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/ripe/meetings/current/form35.html http://www.ripe.net/ripe/meetings/current/nsform35.html %START Do not change the following field %MTG [ ripe35 ] 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? (please delete one option so your choice is in the form) %EOF [ 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 230 / RIPE Meeting only excl. reduction; EUR 280 / RIPE Meeting plus RIPE dinner incl. reduction; EUR 295 / RIPE Meeting plus RIPE dinner excl. reduction; EUR 345 ] Payment details sent online cannot be processed after February 11th, 2000 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 February 22nd, 23rd, and 24th 2000. ( again: please choose reduction ONLY when paying in advance ) %END

1 0

Draft Plenary Minutes RIPE 34
by RIPE NCC Meeting Registration 11 Jan '00

11 Jan '00

Dear Colleagues, Please find included below the draft version of the minutes of the plenary session which took place at RIPE meeting 34. They can also be found on our website: http://www.ripe.net/ripe/meetings/archive/ripe-34/plenary-minutes.html Kind regards, Naomi de Bruyn RIPE NCC --- 34th RIPE Meeting Plenary Minutes - DRAFT RIPE 34 Amsterdam, 21st - 24th September 1999 Plenary Session Chair: Rob Blokzijl Scribe: Naomi de Bruyn 1. Opening 2. Agenda 3. Minutes RIPE 33 4. From the Chair 5. Reports from the RIPE NCC (Mirjam Kuehne) 6. ICANN/ASO a - Current Status of ICANN and the ASO (Mirjam Kuehne) b - Selection of 3 Address Council Members (Note: a document describing the relevant procedures will be circulated separately.) 7. 10 Years of RIPE: a special 8. Reports from the working groups 9. Next meetings 10. AOB 11. Close --------------------------------------------------------------------------- - 1. - Opening RIPE chair Rob Blokzijl welcomed the participants to the 34th RIPE meeting. - 2. - Agenda Rob proposed to change the order of agenda items 5 & 6. Agenda item 6 was discussed first followed by item 5. The RIPE 34 meeting participants approved the agenda. - 3. - Minutes RIPE 33 The RIPE 33 plenary session minutes were approved. - 4. - From the chair Rob announced that a candidate was found for the RIPE NCC Managing Director function. The candidate was found by the RIPE NCC Executive Board with support from the RIPE NCC workers council. The current state of affairs was that the final details of a contract were being discussed. The new Managing Director would be announced and introduced at the RIPE NCC Annual General Meeting on 19 October 1999. - 5. - RIPE NCC Status Report http://www.ripe.net/ripe/meetings/archive/ripe-34/presentations/ ncc-status/index.html Statistics ---------- New LIRs: Mirjam reported that at in Q1 of 1999 the RIPE NCC registered two new members per calendar day, twice as many as were expected and forecasted. It has slowed down in Q2 but the RIPE NCC was still registering approximately one and a half new member per day. The new members tend to be small or grow slower than members in the past therefore the overall workload is not increasing in proportion to the growth of members. The RIPE NCC reported that some LIRs had been closed. This has happened for a number of reasons such as an LIR going out of business or LIRs that have not paid their membership fees. The RIPE NCC has closed down 136 members to date and they have been removed from the RIPE NCC accounting system. These LIRs no longer receive services from the RIPE NCC. A long process is undertaken by the RIPE NCC before the decision is made to close down a registry. The present process of collecting outstanding payments has proven successful in decreasing the outstanding payments. The RIPE database receives on average 5 queries per second and 10 updates per minute. During the DB-WG bulk updates which slow down the updating process enormously was discussed. This problem needs to be tackled and is a topical issues in the DB-WG. The number of objects in the RIPE database has exceeded two and a half million. The RIPE NCC has began allocating addresses from 213 address space. 62/8 addresses are also being assigned. Allocations from 62/8 had slowed down somewhat at the beginning of the year but has increased in Q2 with larger members requesting address space from this range for larger contiguous blocks. Overall the RIPE NCC has allocated approx. 70 million addresses. This figure would align with the allocations made by the other RIRs when comparing the ratio of members to the amount of allocated addresses in each region. Services -------- Mirjam reported that the RIPE community is crucial to the development of services provided by the RIPE NCC. The feedback more or less determines the yearly Activity Plan of the organisation. The RIPE NCC has produced the Activities & Expenditure Plan (document ripe-197) for the operating year 2000. The Executive Board has reviewed the document and will present it to the membership at the upcoming AGM meeting. Mirjam outlined the main activities of the Activities & Expenditure Plan. In summary, the main structural change proposed in the Activity Plan is introduction of Membership Services. The Membership Services are comprised of Registration Services and the Test Traffic measurements which are only available to RIPE NCC members. Co-ordination Activities are open to the Internet community at large; such as the maintenance of the RIPE Database and the organisation of the RIPE meetings. Two new activities have been listed: Routing Information Services and Routing Registry Consistency. These projects were initially started in 1999 however more resources will be spent on them in 2000. Details: Paula Caslav has left the RIPE NCC. Nurani Nimpuno has been employed by the RIPE NCC as Registration Services Manager. The average response time for address space and AS number requests has been 2 to 3 days. The RIPE NCC has worked on automating procedures in Registration Services. Therefore a increase of hostmaster staff is not foreseen, even though the membership and number of requests have increased. The RIPE NCC has began allocating IPv6 address space. This was achieved through extremely good co-operation among the RIRs. The RIRs have worked together evaluating requests, exchanging experiences, information and opinions to ensure the same assignment and evaluation criteria is used in all regions. The RIRs also have good co-operation with 6bone. No major failures or major open policy issues were reported. 13 LIR Training Courses were delivered since the last RIPE meeting in May 1999. Mirjam explained the training course policy to the people attending the plenary session. She asked that members notify the RIPE NCC in advance if any persons registered for the course will not attend. This way the RIPe NCC can offer the place to individuals which could not attend the course for reasons of capacity. The RIPE NCC has been working on the current course material to improve the presentation and reference material. The presentation material has revised and a more detailed reference handout is planned for the attendees. The revised courses will be delivered starting January 2000. The database department has been working mainly on re-implementation, but also concentrated on keeping the existing code running. The RIPE NCC has a fully redundant server configuration on one machine and also another server which is running a near real-timer, so that a swap over can be made if necessary. DB/MRTG have done everything to improve the database software for sending in updates. Good results and positive feedback were reported for the database consistency project. The consistency within the database has improved. The RIPE NCC has improved the syntax checks and suggested automated changes where possible. The RIPE NCC is still working on setting up redundant servers with other Regional Internet Registries. Mirjam explained that the RIPE NCC had commenced work on the Routing Information Services project outlined in the Activity and Expenditures Plan. The RIPE NCC will collect and store routing data, current and past/historical, to allow network operators to locate possible problems within the network or within a specific AS at a certain time. The RIPE NCC has started testing and a published document on the design is planned after the RIPE meeting. It was reported that the Routing Registry Consistency project will receive more attention. Initially the RIPE NCC wil concentrate on route/origin authentication and not on the policies in the autnum object. The RIPE community has made it clear to the RIPE NCC that this is the most pressing issue at the moment. Mirjam explicitly mentioned the good co-operation experienced with the other Regional Internet Registries. On a daily basis operational information and support is exchanged between the RIRs as much as possible. This ensures consistency in criteria applied in the regions. Co-operation has mainly taken place in 3 topics: IPv6, ICANN/ASO and database consistency. The RIRs plan to transfer data that is currently registered in the ARIN database (for historical reasons) to the regions that the networks are operated in. Mirjam welcomed Kyoko and Fabrina, the APNIC staff that visited the RIPE meeting. Q: Enzo Valente asked a question with regards to the database. He stated that there is a difference between the ARIN and RIPE database and that the RIPE NCC had made a lot of work on the RIPE database. If Europe succeeds with this database why not offer it for free use with regards to other databases. A: the RIPE database it is there for free. Everyone can use/grep the code and implement it. It mainly is a matter of history. The communities are used to certain different formats. We have tried over the years to work together to improve that situation. The code has always been free has been offered to other RIRs. - 6. - ICANN/ASO Rob explained that ICANN/ASO had been on the RIPE meeting agenda for at least two years but that developments have reached a new phase. Mirjam Kuehne provided a short introduction regarding the current status of ICANN/ASO and the selection of Address Council members which was to take place during the plenary session. She reported that ICANN had reviewed and accepted the proposal for a MoU-based Address Supporting Organisation submitted by the 3 RIRs at the ICANN Board meeting on 26 August 1999 in Santiago, Chile. The RIRs are now working on a MoU that the RIRs and ICANN could hopefully sign in October. Other resolutions that ICANN made at their Santiago meeting include the continued support in the set-up of new registries for Africa and Latin America. They recommended and suggested that the ASO involve representatives in the ICANN structure as observers in the ASO. Another resolution was passed based on information that certain parties did not fully agree with the ASO proposal as such and that certain issues were not properly addressed. ICANN tried to find a compromise and move forward to approve the proposal but at the same time tried to address the concerns of these organisations. This lead to the formation of an Ad Hoc Group. It is not quite clear yet what the exact terms of reference will be but the Ad Hoc Group will look into future numbering schemes to make them consistent specifically with regards to telephony and IP. It was felt that this would fall in between the PSO and ASO. Their work is expected to finish after one year and a report will be delivered to ICANN. This report could possibly suggest a change in structure of the ASO. The group will include representatives of businesses, including telecom operators and Internet service providers and trade organisations, the ASO Council, the ICANN Board, and other legitimately interested parties. During the plenary session a discussion took place on how to select members for Address Council. Following the discussion the AC members would be selected as outlined in the following document published to the RIPE NCC members http://www.ripe.net/ripencc/about/regional/docs/asonomin.html Mirjam reiterated some essential features of the proposed ASO structure: - The structure must be open and transparent. - The functions have to be separated - It should be built on existing structures currently in place (bottom-up, industry self regulatory) The structure of ASO includes having an annual General Assembly meeting and an Address Council. The different tasks and responsibilities for these different groups have been discussed in the LIR-WG. The meeting participants strongly agreed the need for open and transparent structures. Mirjam stated that the communications (announcements, minutes, agendas) will be made public and that open mailing-lists will be created to get input from as many people as possible about the specific IP policy issues. Mirjam reported that the LIR-WG discussed how policies are actually developed in the 3 regions, how everyone could participate and how new policies or changes could be suggested. It was reported that this is the role of the community and the RIRs to ensure policies are realistic and fair. The individuals selected for the Address Council and ICANN Board must not be staff members of any RIR. The proposal also states quite clearly that no ASO-appointed Director may serve simultaneously on the Address Council. In the process of writing this proposal the RIRs tried to recognise and use the structures currently in place and make sure the structures were not duplicated. Existing open structures are proposed to build policy. This includes input from organisations that need to work with IP address space and that are affected by the policies. Mirjam pointed out that participation is possible within the ICANN framework in addition to the proposed structure. Proposals for policy changes can also be submitted directly to the ASO if it is felt that the existing structures are not working or are not appropriate. With regards to regional diversity, the ASO is asked to schedule their General Assembly meetings in different regions and hopefully hold them in conjunction with other meetings in order to minimise travel for the participants. The function of the General Assembly is that it is an open forum which mainly works electronically, but will also physically meet once every year. It is like a members meeting but open to all interested parties. It reviews Address Council operations and gives input to the ASO. In short, Mirjam summarised the function of the Address Council as existing to oversee the whole policy developing process. They are there to make sure the process is open and transparent, fair and consistent and uses the criteria as set by ICANN and the Internet community. Mirjam stated that the Address Council and their duties are outlined in the Memorandum of Understanding that can be found on the RIPE NCC website at: http://www.ripe.net/ripencc/about/regional/docs/icann-mou-oct99.html There had been an open call for nominations for the AC. And we were working to have a fair and open selection process for these candidates. Mirjam clarified that the policy within the ASO is the same as it works now. We have to make sure that we integrate people that are part of the IP address world. This was discussed in the LIR-WG and that more activity is needed to make existing structures known. She also stated that many organisations were not aware that RIPE meetings were where these issues were discussed and where they should be if they want to participate. It was reported that the ASO role is restricted to IP policies and that the registries are the organisations that continue to maintain the resources. The ASO is not there to tell the RIR staff how to do their work, but mainly to oversee the policy development and to report and provide advice to ICANN. Address Council Selection ------------------------- The Address Council selection procedure was discussed in the LIR-WG, which is the open forum that discusses and defines policies in the RIPE NCC service region. The RIPE NCC chose to use the existing open processes for the selection of Address Council members. Therefore, the RIPE meeting plenary session was selected as it is the largest forum and everyone interested in this selection could participate. Mirjam and Rob stressed that it is an interim procedure. Within the ASO proposal and the draft MOU it specifies quite a long time frame and certain deadlines that are to be followed within the nomination and selection process. Due to time constraints set by the ICANN Board, the RIRs modified the procedure to select the initial Address Council. ICANN requested to have the directors from each region selected by November which called for the modification in the initial AC selection process. The procedure will be discussed in further detail in the LIR-WG and the formal procedure for the future can be outlined by the next RIPE meeting in February 2000. Selection of 3 Address Council Members. The Call for Nominations for the AC produced 8 nominees: - Jan Czmok, Gigabell AG - Amar Andersson, Telia AB/Telia Net - Hans Petter Holen, SOL System AS - Wilfried Woeber, Vienna University - Daniele Bovio, America Online Inc. - Sabine Jaume, RENATER - Dave Morton, Cybernet AG - Mark R. Measday - Josmarian SA Rob started the selection procedure with a word of wisdom. He stated that RIPE exists for 10 years now and the RIPE NCC has existed for 7 years. All policy making has been done on a consensus basis. Votes have never been taken, therefore we have no well established 'election' procedure. In light of this, Rob thought it best to replace the word election with selection. Rob pointed out a few conclusions that were reached during the LIR-WG meeting on Wednesday, 22 September 1999. A Memorandum of Understanding exists and one of the requirements is to have an open and transparent regional forum for policy making in the IP address area. The conclusion was that the LIR-WG has played that role for 10 years already. He reported that 100% of the current consumers of IPv4 and IPv6 address space are covered. However, there may be other interest groups that have not been reached that have an interest in the future development of address policy but are not necessarily consumers of IP address space to date. The conclusion was that we need a better out-reach programme to make sure that people are aware that this is the open and transparent forum as mentioned in the ICANN MOU with regards to ASO. This ad-hoc selection procedure is based on the MOU draft version which describes that the policy making organisation i.e. the LIR-WG, puts a selection procedure in place. A small problem arose this year: the MOU has detailed timelines on how that should be done for example that a call for nominations should be at least 90 days before the selection procedure). The MOU had provisions for that, an article stated that a modified procedure could be followed to select the initial Address Council members. It was up to the LIR-WG to come up with a different, but open and transparent procedure. The LIR Working Group should producer two results: - come up with a proper selection procedure for the election (elections are held once a year). - have in place a first draft of a selection procedure by the next RIPE meeting in February 2000. At the RIPE meeting in May 2000 an agreed selection procedure should be in place. This will allow us to have proper elections for the next year. The LIR Working Group could not conclude on a single process at such short notice to have during the plenary session. It discussed whether to conduct an election process by ballot or via the usual method: consensus building. The LIR-WG discussed the terms the initial members should have: 1, 2 and 3 years. Some participants thought this would not be a well balanced procedure and proposed to give the members all a 1 year term. It was decided however not to do this as the first year is such an important year, and weakness could already emerge from day 1. Rob personally thought this was a good argument. Consensus was reached during the plenary session that although the procedure was not perfect the candidates were good enough to be trusted for 3 years. One specific requirement for selecting the Address Council members was that all 3 candidates should have a solid knowledge of IP addressing. Another valid argument proposed was that the 3 members should come from different industry backgrounds, at least one person from a commercial company and someone with an academic background. Four candidates from the list of 8 were present during the plenary session. With regards to the profile criteria all 4 nominees attended RIPE meetings regularly. Rob proposed to shorten the list of 8 nominees to the 4 people present at the RIPE Meeting plenary session. Following some discussion during the plenary session, consensus was reached: the 3 Address Council members were to be selected from the 4 candidates that were present that day. Hans Petter Holen, Sabine Jaume, Daniele Bovio and Wilfried Woeber all gave a short introduction about themselves to the attendees and informed the attendees of their involvement with ICANN in the past. Consensus was reached that the council members would run for a one year, two year and three year seat. It was agreed to hold the selection via a secret ballot. All people present at the plenary session were eligible to vote except for RIPE NCC staff. The 3 chosen Address Council members were to decide amongst themselves the terms of office (1, 2 or 3 years). 150 votes were counted. Sabine Jaume, Wilfried Woeber and Hans Petter Holen were elected to the ASO Address Council. Congratulations were extended to the 3 new Address Council members. - 8. - Reports from the working groups Routing WG ---------- Chair: Joachim Schmitz Attendees: 84 Scribe: Els Willems/Ambrose Magee Report from the RIPE NCC (JLS Damas) Database development - statistics - re-implementation (finished around end of year) RPSL transition - after re-implementation, RIPE35 - issues discussed in transition doc to be prepared Updates to RIPE 178 (C. Panigl) Multicast Routing Projects Backbones Exchange Points - project at the LINX (G. Besch) Proposed focus during RIPE35 !input welcome! Routing between Europe and Asia - An Issue? (J. Schmitz) Routing Information Service RIS (A. Antony) RIPE project(to be published as RIPE-200) Collect Internet routing table including different views Store for "historical" analysis, statistics, ... Work together with US groups Reality Checking of the IRR (JLS Damas) RIPE project (to be published as RIPE document) Use RIS data, compare to IRR data Detect "illegal" things, e.g. - nonallocated announcements - hijacked routes Improve Internet routing and stability Actions 29.R1 on G. Winters, J. Schmitz, RIPE NCC Definition of the IRR and an AUP - draft written, in progress - 31.R1 on RIPE NCC, D. Kessens, J. Schmitz Basic design for an IPv6 IRR - postponed - 32.R1 on RIPE NCC, JLS Damas Prepare draft document on issues of RIPE-181 to RPSL transition - in progress - 32.R2 on J. Schmitz Write project definition for Routing Registry reality checking - done - Q: Bernard Tuy stressed that he thought it was very important resurrect the MBone WG. A: Joachim replied that he is not an MBone expert, he tried to find someone to give a short overview, but couldn't find anyone. During the next RIPE meeting an overview will definitely be given. Database WG ----------- Chair: Wilfried woeber Attendees: 87 Scribe: Ambrose Magee Summary not available yet. Joachim said that when Wilfried develops a Task Force to make this transition to RPSL, he has the support of the Routing Working Group and himself as chair. Ipv6 is obviously for many people not yet an issue, but it should definitely be delt with as well. Wilfried stated that in the beginning it starts with the WG chairs, collaboration between the various working groups. However the chairs themselves cannont do all the legwork. They should therefore identify a set of individuals to become vocal point for some kind of interaction. TLD WG ------ Chair: Niall O'Reilly Scribe: Vesna Manojlovic Attendees: 33 CcTLD Registries represented: 13 This short summary of the TLD-WG session was presented at the closing plenary session of RIPE 34. Please see the RIPE 34 TLD-WG Minutes (when available) for more detail. ---------------------------------------------------------------- Future of TLD WG The WG was closed. Now that CENTR is established, it appears to be the organisation which should best deal with most of the work areas belonging to the TLD WG. It is hoped that a CENTR working group will begin functioning soon and that it will meet at RIPE 35. Some work areas appear to fall more naturally to the continuing RIPE DNS WG. Work areas from the TLD-WG workplan were identified to be entrusted to DNS-WG and to CENTR, as shown below. DNS-WG: Stability of the DNS Root DNS Infrastructure Resources CENTR: IANA and ICANN Documentation and alignment of practices Emerging Registries Tools and Techniques ---------------------------------------------------------------- Input from other RIPE WG's DB-WG Input needed on specification of domain object for next revision of code. Operational difficulties around domain objects. Need decision on migration of domain objects -- CENTR to respond urgently. Specification input deferred until migration path decided. ---------------------------------------------------------------- CENTR Update Presentation by Fay Howard. CENTR has incorporated, is recruiting a Technical Project Officer, and is expected to have a technical programme, with its own working groups. CENTR is aware of problems wrt domain objects in RIPE DB and is in active dialogue with RIPE NCC. CENTR has had to concentrate on global ICANN and DNSO issues, and now expects to have a more "European" focus. Seven DNSO constituencies provisionally recognised, among which ccTLD constituency. ccTLD's have elected 3 NC members. Elections for ICANN Board follow in October. See http://www.centr.org. ---------------------------------------------------------------- Current Actions TLD-33.1 [Chair] Provide minutes for RIPE 32 TLD WG Draft ready; kept open; to be reviewed on list. TLD-33.2 [Chair] Initiate discussion of issues arising around domain objects in RIPE database. Some discussion has taken place between interested parties, especially RIPE-NCC, CENTR and certain registries. Transferred to CENTR, for decision during next week (beginning 27 September 1999). TLD-33.3 [Chair] Request information from registries on whether they are prepared to make their data available for pilot project using HARMONIC interface. NIC-FR is making contact directly. OBE; closed. TLD-33.4 [Chair] Place Future Direction of TLD-WG on Agenda for RIPE-34 and stimulate preparatory discussion on mailing list. Done; closed. TLD-33.5 [All] Contribute to workplan discussion on mailing list. OBE; closed. ---------------------------------------------------------------- New Actions TLD-34.1 [Chair] Ensure loose ends are tidied up, in particular by alerting inheritors of work areas and action items, and by taking care of minutes. Niall thanked everyone who supported the TLD Working Group in any way; wether by participation or taking the minutes at the meetings. And he thanked the RIPE NCC staff for the background suppport that were always provided. Christopher Wilkinson stated that we all owe Niall a heart devoted thanks. 2 years ago we were in desparate need for a vocal point for policy for TLD issues and we didn't have one, Niall volunteered. It is not often that a RIPE BoF results in the creation of a new international organization within 2 years. Christopher also wanted to draw attention to the membership and election in the ICANN structure and organization. The next stage is the creation of an open at large individual membership for the ICANN organization. ICANN is looking for at least 5000 initial individual members from day one. He wanted to urge the RIPE membership to join the ICANN at large membership as individuals. That is where they're responsibilities now lie. Rob noted that when CENTR starts a new Working Group, we have offered them to have regular meetings at the same time and at same facilities as the RIPE meeting. This in order to be as open and transparant as possible. This is an action item for Rob, he will follow this personally in the next few months. LIR WG ------ Chair: Hans Petter Holen Attendees: 89 Scribe: Eamonn McGuinness Local IR Working Group; the open forum where policy is made. Not just for Local Internet Registries but for all of you. AOB - IPv6 policy matters -> LIR WG? - How to handle PI allocations vs setting up new LIRS? - Reverse delegation process-> discussion on LIR WG to fully understand all implications - DB support for multiple domain objects New Actions (1/2) - Chair: Suggest clarification of WG charter - Chair: Form a task force for documenting the existing policy process - Chair: Form a task force to define final Address council selection procedure - NCC: clarify LIR-RIR expectations in the audit process - RB: suggest a selection procedure for the plenary - DONE New actions (2) - JA: additional value for the inetnum "status" field - WG: Reverse delegation process -> discussion on LIR WG to fully understand all implications - NCC: Multiple domains in domain objects - NCC: Proceed with plans to implement PGP as an option for hostmaster communication - NCC: Release source code to rtt due to demand - WG: Discuss moving IPv6 policy matters to LIR WG Charter The LIR WG deals with issues that concern LIRs for example, Local IR operation, and the local implementation of RIPE policies and procedures are discussed here. http://www.ripe.net/ripe/wg/lir/index.html How do we establish policy? - In the LIR WG - Open to anyone to attend not just to LIRs - By concensus There was consencus that the proc. Described was open enough and didn't need to be changed in any major way. Task force for documenting the existing policy process - announce the charter of the task force to the mailinglist - interested parties may volunteer - a draft will be posted to LIR WG for discussion - a second draft will be based on that discussion - the document will be endorsed by consensus at RIPE 35 Task Force: - Aaron Hamilton, Cable & Wireless - Sam Critchley, UUNET - Tim Dimons, IS Products, UK - Barbara Roseman, Frontier Globalcenter - Hans van der Veer, Lucent tech - Gordon Lennox, European Commission Task force to define final Address council selection procedure - announce the charter of the taskforce to the mailinglist - interested parties may volunteer - a draft will be posted for discussion - a second draft will be based on that discussion - The document will be endorsed by consensus at RIPE 35 Remember: it's your forum, be there! Special thanks to RIPE NCC, keep up the good work! Rob added this was a reminder for himself: a couple of actions which have to be done by our new address council delegates. The first one is that we should announce to the world that we have 3 council members. The 3 elected members should figure out among themselves how the 1,2 and 3 year seats will be distributed. A small discussion was to be held that day on how the address council members will be reporting to the RIPE community at large. The 3 council members had (within the next days after the RIPE 34 meeting) to think about a procedure for having a call for nominations for 1 ICANN board director. This action would be closed during the ICANN meeting at 2nd November. DNS WG ------ Chair: Ruediger Volk Attendees: 39 Scribe: Bernard Tuy 1 sda recommendation 2 Dummy guide 6 Extended best practise 7 Fernando Garcia draft 4 ietf dnsops report (Lars Johan Liman) 5 swedish dnssec workshop report (Lars johan Liman) 3 yet another dns dos attack (Peter Koch) 8 potential work areas IPv6 Q: Rob: you working group is planning a workshop around the next RIPE meeting? A: Ruediger: it seems it will be a good idea to push forward a DNSSEC this way. Test Traffic WG --------------- Chair: Matthew Robinson Attendees: 38 Scribe: Rene Wilhelm Presentation by Henk Uijterwaal on current project. Discussed ways of presenting the collected data Discussed publicity available 'overview' of delays - working on draft Netnews WG ---------- Chair: Felix Kugler Attendees: 22 Scribe: Brad Knowles Ongoing business - newsbone satus report - tools: improved traffic statisitics from inn Projects - NHNS - Flowmaps: Administrivia - The future of this Working Group -> wants to continue! - New Working Group chair -> Brad Knowles has volunteered For ayone also interested in becoming chair of Netnews WG: the deadline is 10th October 1999. Brad Knowles wanted to add something about NHNS: not only are we working to try to get the ISC to use NHNS to maintain the hierarchic list for the big 8, we are also working with them to see if we can get the NHNS tools included with the INN distribution as a standard part of the package. If you for example, try to run INN sinc to pick up the big 8 you can automatically work with these tools. We are working to get these tools encorporated within diablo. We will see if we can get in contact with the maintainers of other newspackages and have them do the same. Anti-spam WG ------------ Chair: Rodney Tillotson Attendees: 35 Scribe: Gerry Berthauer - update on spam - code of conduct - assistance to certs - help for owners of open relays Update on spam - little change in amount. - No major techniques. Direct marketing industry. Legislation proposed Opt-out Opt-in ? BCP on operation of mailing lists? Conference in London http://www.euro.cauce.org/lawtel/ Conde of conduct - LINX BCP http://www.linx.net/noncore/bcp/ube-bcp.html Adopt as ripe document depends on good take-up <roland(a)linx.net> Aassistance to certs - reading mail headers - collection of standard advice Help for owners of open relays - simple procedures - target common products http://spam.geht.net/ Hope to come back with draft RIPE document next time. EIX WG ------ Chair: Fearghas McKay Attendees: 65 Scribe: Chris Fletcher LINX - presentation. VIX - presentation. Equinix - presenation. SCOTTIX - presentation. RIPE NCC (Mirjam Kuehne). SubTLA's and IPv6. IX do not want to allocate addresspace, this is a registries' role. AIX - presentation. Y2K - discussion. Bill Norton - Results of paper on interconnection strategies for ISPs. Fearghas also announced that security at IX's will be discussed during the next meeting. Q: Wilfried: with regards to the internet exchange IPv6 address distribution, he was grateful that the EIX WG touched on it. He was also relieved to find out that the recommendation will probably be not do distribute IPv6 addresses in the framework of an exchange point. He wanted to know if EIX WG intends to provid this feedback to the editors of the relevant RFC or do they intend an update to this RFC. It might not be a good idea to have information in an RFC which is contrary to what a regional operations community would recommend these days. A: Fearghas: we will provide feedback to IPv6 WG, they will get that back to RFC's. David: stated that as chairman of IPv6, he will take it up with authors of the aformentioned RFC's, to see what they have to say about it. Keith had a suggestion for Rob, he felt that it is a good idea if we had EIX and IPv6 Working Groups not scheduled in parallel next time. EIX should also not overlap with the Routing WG. IPv6 WG ------- Chair: David Kessens Attendees: 90+ Scribe: Petra Zeidler Summary not available yet. David stated at the end of his summary that sisco is now providing the beta version of their IPv6 implementation for their routers to everybody. EOF Tutorial? ------------- Rob: informed the plenary session that EOF turned out to be completely different from what everyone thought it would be. Rob got some friendly remarks about the presentations that were given instead and stated that we might turn this from a disaster into a surprise feature. Dfk: wanted to propose a new activity related to security issues in operations. We have had some things on various mailinglists about operational coordination in order to track down denial of service attacks and similar things. That has not led to a BoF this time, but Dfk thought it would be a good idea to have a BoF during the next ripe meeting, as some people are getting worried. Perhaps other coordination aspects can be discussed here as well. Dfk suggested that people who are interested in this should organize a BoF for the next meeting. Dfk he stated that if people want to talk to him, send an e-mail. A draft charter will be needed to form this BoF. The draft charter will be discussed on a mailinglist which will be set-up soon by the RIPE NCC. Wilfried mentioned that there was an activity for a while within the framework of the European research network. This was not succesful, he personally really wants the RIPE community to come up with an infrastructure to deal with these issues, such as operational recommendations etc., and then find out if this is something that can stand on its own legs. He stressed that he was really grateful to Dfk for bringing it up. - 9. - Next meetings Offers were made by Daniele Bovio to host the May 2001 RIPE meeting in Paris, France and by GARR/INFN to host the May 2002 meeting in Bologna, Italy. - RIPE 35 21-25 February 2000 Amsterdam - RIPE 36 16-19 May 2000 Budapest - RIPE 37 11-15 September 2000 Amsterdam - RIPE 38 22-26 January 2001 Amsterdam - RIPE 39 May 2001 Paris? - RIPE 40 September 2001 Amsterdam - RIPE 41 January 2002 Amsterdam - RIPE 42 May 2002 Bologna? - 10. - AOB There was no other business to discuss. - 11. - Close Rob thanked everyone for attending and hoped to see everyone again at the next RIPE meeting in Amsterdam, in February 2000.

1 0

New RIPE NCC Website
by RIPE NCC Staff 10 Jan '00

10 Jan '00

Dear Colleagues, The RIPE NCC is happy to announce the launch of its re-structured Website. The aim was to provide users of the site with more structure and ease of use without eliminating the clarity of the pages which have received recognition in the past. With the new structure in place, we hope that you will find it easy to navigate through the site and find all of the information you require. The site also marks the launch of the new RIPE NCC logo. A special thanks to all who have provided input to the new site. Naturally, any errors can be reported to <webmaster(a)ripe.net>. Regards, Paul Rendek Communications Officer

1 0