August 2001 - ripe-list - mailman.ripe.net

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

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

21 Aug '01

Dear all, (apologies for duplicates) As you know, the subject of storage of person and role objects in the RIPE Database has been the focus of attention for some time, particularly information being stored in the Database that is not directly related to RIPE NCC activities and/or some of the people whose information is stored in the RIPE Database are not aware of the fact. During the RIPE 39 meeting in Bologna, I reported on increasing concerns about data privacy issues and potential legal implications the RIPE NCC could be involved in due to some of this data. Call it a coincidence,but we have been approached by the Dutch Data Protection Agency a few weeks ago to discuss this matter. The agency's action is taken on behalf of other similar global agencies who have requested their Dutch counterparts to act as the RIPE NCC is based in the Netherlands. As a result of the discussions, the authorities have requested the RIPE NCC to remove all unreferenced data currently stored in the Database. This affects mainly person objects related to domain name registration information stored in the RIPE Database. In order to minimise annoyances to users and the membership we would like to proceed with the process in a timely manner. In order to prevent undue deletions we propose the following process: 1. The following unreferenced person objects will be deleted: - objects referenced only from *.de domains, according to the list provided by DENIC (or list of mntners that define that set); - objects that are un-maintained. 2. Those who want to protect their objects in the database should tag them with a special mntner (RIPE-NCC-PN-NONE-MNT). This procedure is solely meant for personal use by individuals interested in keeping their personal data in the RIPE Database. However, this is subject to change in the future. 3. All of the object deletions will be performed in one step. There will be an outage in updates for ~1 day. We plan to start the process Friday, 21 September 2001 in the evening and finish by the end of Saturday. More concrete details will be provided in the coming weeks. Best regards, Joao Damas RIPE NCC

1 0

New Document available: RIPE-218
by RIPE NCC Document Announcement Service 21 Aug '01

21 Aug '01

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Short content description ------------------------- We are very pleased to present to you the RIPE NCC Annual Report 2000. The RIPE NCC Annual Report is designed to provide the RIPE NCC membership with a short and comprehensive overview of the activities carried out by the RIPE NCC and its achievements in that year. A printed copy of the RIPE NCC annual report has been sent to our membership. Should you wish to obtain an additional copy of the Annual Report then please send an e-mail to: ncc(a)ripe.net Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-218.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-218.pdf PDF version You can also access the RIPE documents in HTML format via WWW. The RIPE NCC Annual Report 2000 is available at the following URL: http://www.ripe.net/docs/ar2000.html

2 1

DNSSEC Course, Prague October 8, 2001
by Olaf Kolkman 15 Aug '01

15 Aug '01

*** DNSSEC Course *** Final Announcement This mail is sent to both the ripe-list and the techsec-wg mailinglist excuse us for possible receipt of duplicates. The RIPE NCC will be organising a DNSSEC course The course will be held in Prague on the Monday after the RIPE Meeting, October 8: 9 am to 5 pm. The goal of the course is familiarise the participants with DNSSEC so they can maintain their own secured zone and to identify current difficulties in deployment and possible future directions. To be able to run the program in a day we expect the participants + being able to administer DNS zone files with bind; + to bring their own dummy zone to experiment with; + to bring a laptop running the latest version of bind; + being able to patch bind software if needed; About a week before the course, you will receive a homework assignment. This will take about an hour to complete and has to be done in advance, so that during the course little time will be wasted on configuration issues. The course will consists of two parts: an introduction to DNSSEC and a hands-on part. The hands-on part will cover: + securing zone transfers using TSIG + generating zone keys and signing zones + securing 'corporate' sites with DNSSEC + establishing a chain of trust + key-exchange and rollover The RIPE NCC does not charge for this course but the amount of participants will be limited to 25 persons. If the interest in the course exceeds the number of available places a selection will be made based on first come first serve basis and by limiting the amount of participants from one affiliation. To register please fill in the form below and mail it to disi-ws(a)ripe.net, use subject header: "[DNSSEC RIPE40] Registration". Please, do not reply to the mailinglists. Finally, the RIPE NCC plans to repeat this course on a regular basis in 2002, so if your application for this event is rejected, there will be ample opportunities to take the course at a later time. --Olaf Kolkman RIPE NCC, DISI project http://www.ripe.net/disi - - - - - - - - - - - - ---cut here--- - - - - - - - - - - - - - - --------------------DNSSEC Course Registration Form.--------------- I hereby register for the DNSSEC course in Prague on October 8, 9am-5pm. Name : E-mail : Affiliation : Job title : Street Address : City : Could you shortly describe why you are interested in participating in this course and what you hope to learn? Your registration will be confirmed within 2 work days after it was received. Since the amount of participants is limited you might be put on a waiting list. ----------------------------------------------------------------------

1 0