- ripe-list - mailman.ripe.net

RIPE Region Hostcount for April 2001
by RIPE Hostcount Maintainer 25 May '01

25 May '01

Dear All, below is the hostcount for April 2001. The table shows an increase since last month of over 180,000 (or 1.3%) to a total of almost 13,860,000 hosts in the DNS in Europe and surrounding areas. The ru domain shows the highest increase for April with approximately 100,000 hosts more than in March. Background information and more statistics are available at http://www.ripe.net/hostcount/ - Brief Notes on this Hostcount - Unfortunately lots of problems this month... - the January, 2000 data had to be reused for uk due to serious interruptions to the collection process - the March, 2001 data had to be reused for eg, es and ro due to fresh data not being available. - the March, 2001 data had to be reused for ci, ma, il, it, tr and fr due to various problems with the data collection. - 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 ES NIC fr Annie Renard gr Dimitris Zisiadis hr Ivan Maric ie Mike Norris il Netvision NOC 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 sk Lubos Elias sm Maurizio Martinelli Daniele Vannozzi tr METU Hostcount Admin 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 : Tue Apr 24 2001 This Count : Fri May 25 2001 CY SOA COUNTED DUPL REAL CHANGE ============================================================== ad 570 2460 814 1646 3 ae 2837 41899 3126 38773 -1607 al 84 194 30 164 1 am 1130 2949 1295 1654 -745 at 142859 752613 220603 532010 -3955 az 691 1708 421 1287 3 ba 393 3801 933 2868 74 be 50220 397631 64820 332811 4298 bg 1404 25401 3281 22120 595 bh 56 609 421 188 132 by 379 3265 682 2583 251 ch 175526 506790 256161 250629 -11862 ci 360 3452 463 2989 0 cm 51 375 35 340 7 cv 20 130 105 25 0 cy 844 8272 857 7415 20 cz 95215 269140 96519 172621 2043 de 2554212 9900004 7520395 2379609 6652 dk 191464 607667 248323 359344 -19075 ee 7049 59395 15734 43661 -62 eg 1533 3392 1036 2356 0 er 39 260 22 238 33 es 29043 503247 53085 450162 0 fi 28195 796611 62532 734079 1366 fr 95219 1333420 172464 1160956 0 ga 31 57 13 44 0 gb 2 24 0 24 0 ge 525 3020 1168 1852 23 gg 1585 2394 965 1429 14 gh 34 502 39 463 2 gi 585 1366 157 1209 23 gl 846 2977 460 2517 20 gn 16 338 135 203 1 gr 22611 164342 23495 140847 278 gw 2 21 1 20 0 hr 4712 33474 13784 19690 473 hu 35441 194768 65238 129530 709 ie 17735 146899 24693 122206 -922 il 20699 166966 58372 108594 17951 ir 274 3020 557 2463 86 is 6376 74695 28288 46407 344 it 426759 1447764 574379 873385 0 je 1634 2514 1027 1487 17 jo 592 1606 734 872 24 ke 1219 5622 809 4813 7 kg 1247 5741 1939 3802 -598 kz 2261 10689 2344 8345 60 lb 1263 8008 1459 6549 2264 li 1265 2358 1353 1005 -2813 lr 12 8 2 6 6 lt 7001 72821 44862 27959 331 lu 5093 16617 4320 12297 -507 lv 5700 29726 8487 21239 79 ma 1483 4413 2420 1993 0 mc 399 956 518 438 0 mk 741 2230 560 1670 69 mt 1015 8611 1698 6913 362 ng 285 2750 1413 1337 253 nl 464430 2794357 908857 1885500 -3744 no 60646 529656 67240 462416 -3156 om 102 5899 2978 2921 0 pl 82206 629276 197845 431431 48986 pt 8781 162317 16323 145994 32565 qa 37 2496 231 2265 43 ro 9753 59786 14855 44931 0 ru 87515 513826 195141 318685 97473 sa 2111 11849 2298 9551 75 se 64010 643840 64848 578992 6527 si 7104 34608 7001 27607 4538 sj 1 0 0 0 0 sk 28961 73528 31123 42405 416 sl 7 278 0 278 64 sm 333 1593 285 1308 5 su 1023 27719 2937 24782 -403 sy 3 18 9 9 0 tj 119 970 684 286 -2 tm 1263 3097 1440 1657 13 tn 27 322 145 177 0 tr 13442 108598 18885 89713 0 ua 24897 123738 79928 43810 2150 ug 211 398 160 238 -8 uk 478844 2502998 825052 1677946 0 va 2 9 0 9 0 yu 8199 20585 6032 14553 145 ============================================================== 84 5292863 25893743 12034143 13859600 182415

1 0

New Document available: RIPE-222
by RIPE NCC Document Announcement Service 23 May '01

23 May '01

New/Revised RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Ref: ripe-222 Title: Smallest RIPE NCC Allocation / Assignment Sizes Author: Joao Luis Silva Damas, Nurani Nimpuno Date: 22 May 2001 Format: PS=9509 TXT=1840 Obsoletes: ripe-211 Obsoleted by: Updates: Updated by: Short content description ------------------------- This document contains the size of the minimum and default allocations made by the RIPE NCC to users from CIDR blocks assigned to the RIPE NCC by the Internet Assigned Numbers Authority (IANA). The document is of special interest to routing engineers and network operators. 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-222.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-222.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-222 is available at the following URL: http://www.ripe.net/docs/smallest-alloc-sizes.html Excuses for duplicate mails

1 0

Minutes DISI BoF @ RIPE39
by Henk Uijterwaal (RIPE-NCC) 15 May '01

15 May '01

Minutes of the DISI BoF - RIPE 39, Bologna, May 2 2001, 9:15 Chair: Henk Uijterwaal (HU) RIPE NCC Scribe: Mark Santcroos Slides are at: http://www.ripe.net/ripencc/pub-services/np/DISI//Talks/0105_DISI HU welcomes everyone. Agenda: 1- What is this BoF about? 2- Administrative matters 3. DISI 4. CSIRS 5. Discussision 6. The future 7. AOB ---- 3. DISI presentation: Olaf Kolkman - RIPE NCC "DISI & DNSSEC on the reverse tree" slides are at: http://www.ripe.net/ripencc/pub-services/np/DISI//Talks/0105_DISI Questions: Q: Why don't you use IPv6? A: Because we want to gain experience first. Q: What about the 192.168.? A: -XXX- Q: What can an end user do to make his ISP secure their zone? A: We want to convince the ISP's to deploy this. Q: What kind of public key system used? A: RSA is recommended, in theory all protocol can be used in parallel. But to get real success we have to choose one. That probably will be RSA. Q: How easily can we go to another encryption protocol, if for example one encryption scheme gets cracked. A: Depending on how long signatures are valid, a change of the protocol can be done within 1 day. But this depends on a lot of parameters. Q: Is there enough experience yet to determine how much effort it is to do actual implementation of this. A: Takes more CPU power for signing. Packet sizes grow. ---- 4. Presentation: Yuri Demchenko - Terena "CSIRS coordination for Europe and extended incident handling standardization" Slides are at: http://www.ripe.net/ripencc/pub-services/np/DISI//Talks/0105_DISI_YD No questions. ------ 6. The future HU asks how to go ahead with this, whether to create a new working group, join an existing working group etc. There are more issues related to security DoS, IPv6, Spam. Q: [chair of Anti-Spam WG] Is a merge going on between the various security-related WG's? A1: Not that we are aware off. A2: We want to keep them seperate. HU asks for a chair. No response. He will setup a mailing list. --- 8. AOB OK offers to give an experimental presentation about DNNSEC. This presentation is still under development and will be given in the future. The attendees welcome that and OK gives his presentation. --- HU thanks all the attendees and closes the WG session. ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(a)ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.5354414 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ As long as you don't tell your friends how I played the hand, then I won't tell my friends how you defended it. (Anonymous)

1 2

New Document available: RIPE-219
by RIPE NCC Document Announcement Service 04 May '01

04 May '01

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE Document Store. Short content description ------------------------- RIPE Document number 219 is the European IP Address Space Request Form. This new document obseletes RIPE-141. 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-219.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-219.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-219 is not available from the WWW at this moment, but will be soon, at the following URL: http://www.ripe.net/ripe/docs/ripe-219.html

2 1

New Document available: RIPE-220
by RIPE NCC Document Announcement Service 04 May '01

04 May '01

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE Document Store. Short content description ------------------------- Supporting Notes for the European IP Address Space Request Form. This document obseletes RIPE-142. 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-220.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-220.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-220 is not available from the WWW at this moment, but will be soon, at the following URL: http://www.ripe.net/ripe/docs/ripe-220.html

2 1

New Document available: RIPE-221
by RIPE NCC Document Announcement Service 04 May '01

04 May '01

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Short content description ------------------------- A new version of the Standard RIPE NCC Service Agreement has been published. This version is an updated version of the RIPE-191 that it refers to all the current documents from 2001 which were already available. 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-221.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-221.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-221 is not available from the WWW at this moment, but will be soon, at the following URL: http://www.ripe.net/docs/ripe-221.html

1 0

Re: RIPE Documents Modified
by RIPE NCC Staff 04 May '01

04 May '01

Dear Colleagues, The RIPE NCC is aware that the changes made to the RIPE documents ripe-141, ripe-142 and ripe-191 were not in keeping with the practices for updating RIPE documents as agreed by the RIPE community. The original versions of the documents in question have been replaced in the RIPE doc. store and new versions of these documents will be published and announced. Again, I apologise for this. Regards, Paul Rendek Communications Manager RIPE NCC

2 1

Re: RIPE Documents Modified
by Nigel Titley 03 May '01

03 May '01

> Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been > modified recently on the RIPE NCC ftp server rather than having new documents > issued with new numbers? It's also interesting to note that the Postscript > versions of these documents seem unchanged. > > And, yes, I realise that there is a requirement to bring database objects > described in the documents in line with the new database implementation but > shouldn't this have been done by issuing new documents? Is it helpful to have > (potentially) different versions of the same document lying around with the > same name? If this has, indeed, happened then I for one would be very disturbed. The only way to modify a RIPE document should to be up-issue it. I recall Rob getting very heated about this at the Budapest RIPE meeting. Nigel

6 5

Re: RIPE Documents Modified
by Nigel Titley 02 May '01

02 May '01

Paul, > Thank you for pointing out the minor changes made to ripe-141, > ripe-142, ripe-191. Apologies are extended and we realise that this > is not the agreed procedure for updating RIPE documents. We assure you > that these changes will not set a precedent for future modifications > made to RIPE documents. A couple of points: 1. It was James who spotted the changes, not Marc 2. Although the changes involved are pretty sensible, one or two at least are not minor. I'm thinking particularly of the change of mnt-by from optional to mandatory. However, apology accepted (by me at any rate), and no doubt Rob will be visiting to make sure that this doesn't happen again :-) Nigel > Regards, > > Paul Rendek > RIPE NCC > > > > Marc Roger <marc(a)belnet.be> writes: > * This message is in MIME format. The first part should be readable text, > * while the remaining parts are likely unreadable without MIME-aware tools. > * Send mail to mime(a)docserver.cac.washington.edu for more info. > * > * ---559023410-341603450-988799134=:8747 > * Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > * Content-ID: <Pine.GSO.4.33.0105021226201.8747@dagesh> > * > * Nigel, > * > * James is right, these documents have changed. I attach the differences > * found for ripe-141, 142 and 191, for info. > * > * On Wed, 2 May 2001, Nigel Titley wrote: > * > * > > Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been > * > > modified recently on the RIPE NCC ftp server rather than having new documents > * > > issued with new numbers? It's also interesting to note that the Postscript > * > > versions of these documents seem unchanged. > * > > > * > > And, yes, I realise that there is a requirement to bring database objects > * > > described in the documents in line with the new database implementation but > * > > shouldn't this have been done by issuing new documents? Is it helpful to have > * > > (potentially) different versions of the same document lying around with the > * > > same name? > * > > * > If this has, indeed, happened then I for one would be very disturbed. > * > The only way to modify a RIPE document should to be up-issue it. I > * > recall Rob getting very heated about this at the Budapest RIPE meeting. > * > * -- > * Marc.Roger(a)belnet.be, BELNET

1 0

Re: RIPE Documents Modified
by Nigel Titley 02 May '01

02 May '01

And the amusing thing is that your diffs show the line "Each revised document will receive a new document number" in RIPE-191 Nigel

1 0