- ripe-list - mailman.ripe.net

RIPE DNS hostcount November 1994
by Marten Terpstra 06 Dec '94

06 Dec '94

Hi all, Below is the RIPE DNS hostcount for November 1994. Slightly delayed because of the IETF, but still, here it is. - no special comments this time, a nice increase of almost 39,000 to over 973,000. We'll hit 1,000,000 surely in the December hostcount. - France slightly down, reason unknown. All output in the usual places on ftp.ripe.net:/ripe/hostcount, overview again appended. Cheers, -Marten RIPE DNS Hostcount Previous Count : Mon Oct 31 1994 This Count : Wed Nov 30 1994 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 2 0 0 0 0 at 508 27557 939 26618 + 1795 az 3 9 0 9 + 1 be 229 16611 275 16336 + 885 bg 17 158 21 137 + 22 by 1 0 0 0 0 ch 317 49017 329 48688 + 2395 cs 0 0 0 0 0 cy 11 80 4 76 + 14 cz 176 10573 171 10402 + 1119 de 2537 195768 5575 190193 +12920 dk 259 17306 213 17093 + 2560 dz 2 8 0 8 0 ee 49 1198 8 1190 + 137 eg 6 146 1 145 0 es 428 25014 189 24825 + 376 fi 533 65987 1183 64804 + 4831 fo 1 0 0 0 0 fr 1047 74682 1056 73626 - 8246 gb 1 24 0 24 0 ge 1 0 0 0 0 gr 162 3607 208 3399 - 146 hr 58 811 24 787 + 60 hu 105 7519 37 7482 + 679 ie 88 5450 80 5370 + 2204 il 191 12128 111 12017 + 2449 is 74 4253 32 4221 + 243 it 777 30687 904 29783 + 2769 li 4 30 3 27 0 lt 14 101 2 99 + 16 lu 31 539 7 532 + 100 lv 23 453 14 439 + 61 ma 1 0 0 0 0 mk 1 0 0 0 0 mt 1 0 0 0 0 nl 694 83957 2156 81801 + 5391 no 771 45055 872 44183 + 317 pl 388 10057 581 9476 + 880 pt 160 5457 72 5385 + 375 ro 32 500 36 464 + 45 ru 144 1705 155 1550 + 262 se 942 71236 2232 69004 + 1938 si 90 1537 39 1498 + 195 sk 69 1204 21 1183 - 30 su 249 4745 289 4456 + 264 tn 3 59 5 54 + 7 tr 72 1951 39 1912 + 260 ua 65 475 79 396 - 61 uk 2427 234437 21029 213408 +11334 va 0 0 0 0 0 yu 3 0 0 0 0 ============================================================ 13767 1012091 38991 973100 +48421 This is an overview of the History of the RIPE hostcounts. It only contains the totals. The totals for 1990-1991 should be considered rather unstable and unreliable because the program used then was not really tuned, plus the count was not done as regularly as it is now. Count : total hostcount for all European top level domains Delta : delta since previous count Delta % : delta as percentage of previous count Q Delta : delta over the past quarter Q Delta%: delta over last quarter as percentage of end of last quarter count For the Q Deltas I have not calculated those back before 1992, because the figures for 1990-1991 are not too reliable. *) Dec 1991 hostcount estimated at 135,000. Count Delta Delta % Q Delta Q Delta % ------------------------------------------------------------------- Oct 1990 31724 Nov 1990 33665 + 1941 + 6.1% Dec 1990 29230 - 4435 - 13.2% Jan 1991 43832 + 14602 + 50.0% Feb 1991 - Mar 1991 44506 + 674 + 1.5% Apr 1991 46948 + 2442 + 5.5% May 1991 - Jun 1991 63267 + 16319 + 34.8% Jul 1991 - Aug 1991 73069 + 9802 + 15.5% Sep 1991 92834 + 19765 + 27.0% Oct 1991 104824 + 11990 + 12.9% Nov 1991 129652 + 24828 + 23.7% Dec 1991 - Jan 1992 141308 + 11656 + 9.0% Feb 1992 161434 + 20126 + 14.2% Mar 1992 167939 + 6505 + 4.0% + 32939 *) + 24.4% *) Apr 1992 170050 + 2111 + 1.3% May 1992 182528 + 12478 + 7.3% Jun 1992 196758 + 14230 + 7.8% + 28819 + 17.2% Jul 1992 213017 + 16259 + 8.3% Aug 1992 221951 + 8934 + 4.2% Sep 1992 232522 + 10571 + 4.8% + 35764 + 18.2% Oct 1992 254585 + 22063 + 9.5% Nov 1992 271795 + 17210 + 6.8% Dec 1992 284374 + 12579 + 4.6% + 51852 + 22.3% Jan 1993 303828 + 19454 + 6.8% Feb 1993 322902 + 19074 + 6.3% Mar 1993 355140 + 32238 + 10.0% + 70766 + 24.9% Apr 1993 366164 + 11024 + 3.1% May 1993 385522 + 19358 + 5.3% Jun 1993 404930 + 19408 + 5.0% + 49790 + 14.0% Jul 1993 426827 + 21897 + 5.4% Aug 1993 451116 + 24289 + 5.7% Sep 1993 469356 + 18240 + 4.0% + 64424 + 15.9% Oct 1993 500018 + 30662 + 6.5% Nov 1993 533701 + 33683 + 6.7% Dec 1993 553357 + 19656 + 3.7% + 84001 + 17.9% Jan 1994 587135 + 33778 + 6.1% Feb 1994 623158 + 36023 + 6.1% Mar 1994 655164 + 32006 + 5.1% +101807 + 18.4% Apr 1994 693346 + 38182 + 5.8% May 1994 735317 + 41971 + 6.1% Jun 1994 760385 + 25076 + 3.4% +105221 + 16.1% Jul 1994 789747 + 29362 + 3.8% Aug 1994 834945 + 45198 + 5.7% Sep 1994 888398 + 53453 + 6.4% +128013 + 16.8% Oct 1994 924679 + 36281 + 4.1% Nov 1994 973100 + 38991 + 4.2%

1 0

Re: DANTE CERT Service
by Bjorn Eriksen 05 Dec '94

05 Dec '94

>Or (a more positive note) is DANTE the right organization to >do the collection of money and subcontract the actual work >to another organization taht all parties trust to do the >(necessarily sensitive) coordination service right? No, they are absolutely not the right organization for this. --Bjorn

1 0

Re: DANTE CERT Service
by Stephan.Biesbroeck＠belnet.be 03 Dec '94

03 Dec '94

I am very surprised by this announcement. The service announced here in in my opinion NOT a CERT service but a CERT coordination service. I have some questions/remarks with this : - How does this fit into the Concert-in-E proposal ?? - Such a european coordination body can only have success if : - it is supported by all the service providers in Europe. When dealing with security issues, you just can't differentiate between national research networks and commercial providers. - all service providers need to have trust into the provider of this service (sorry but I am afraid that this is not the case for DANTE). - there is only one such coordination service in Europe. You can't have several of such coordination centre. In that case you will miss "the coordination". - I am surprised that some organisation declares one-sided that it will take on this role (even if "some" national networks have asked so). Normally such a coordination task should be set up in cooperation with all the service providers in order to have success. But probably I am just misreading the announcement and it doesn't has anything to do with a CERT coordination Center. Please tell me the difference in that case. Best regards, Stephan Biesbroeck --- Stephan Biesbroeck Tel: +32(0)2-2383470 stephan(a)belnet.be Fax: +32(0)2-2315131 Service Support Team of the Belgian National Research Network, BELNET Howard Davies wrote : > DANTE is pleased to announce that, at the request of a number of > national networks, it proposes to create a European level CERT > service. > The objectives of the DANTE CERT service will be: > - co-ordination of incident handling between member CERTs and > with other incident response teams worldwide > - co-ordination of technical assistance to member CERTs > - maintenance of an information server on operational aspects > of computer security > - assistance for the establishment of new CERTs > - providing backup and support to resolve problems that cannot > be handled by a member CERT. > The DANTE CERT service will build on the expertise and experience > of the national CERTs that are already in place. An important > aspect of the organisational structure will be to minimise the > overlap of activities and to ensure that all available resources > are used in the optimum way. > The DANTE CERT will participate fully in existing international > bodies dealing with incident response and security. Full > membership of FIRST will be applied for. > As is DANTE's normal practice, many of the operational components > of the DANTE CERT activity will be sub-contracted; discussions on > how best to do this are already taking place with organisations > which are interested in carrying out this task. > The DANTE CERT service is expected to be established early in > 1995. Its priority will be to serve the networking organisations > in the European research community but other organisations may > also subscribe. Subscribing organisations will pay an annual fee > which will be set as a function of size of the community that the > organisation represents. > Individuals who wish to be included on the mailing list for the > announcement of further details should send a request in reply to > this message > Howard Davies > HD(94)276

3 2

RIPE 19 actions status report (DECEMBER)
by ncc＠ripe.net 02 Dec '94

02 Dec '94

------- Below is the list of action items from the RIPE meeting (and previously). The actions are grouped into two different categories: "Done" and "Open". If you are on the list with an action against your name, would you please reply confirming the status of that action : ie. whether it has been "Done" or whether it is still "Open", with an expected approx date for completion, if possible. The next reminder will be sent out mid December. David Kessens RIPE NCC ------------- Action List - RIPE 19 ===================== 1. Done Action: 19.9 Marten Terpstra To set up environment to allow objects to be sent to "a test database". Action: 19.16 Stephan Biesbroeck To ask RIPE NCC to create a trouble ticket only mailing list which is maintained by the RIPE NCC. 2. Open Action: 17.1 Glenn Kowack Volunteered to write a paper for discussion which would focus on a funding model for the RIPE NCC. Action: 17.7 Wilfried Woeber, NCC To produce the necessary documentation for the new DB software - ongoing Action: 17.8 NCC To update and re-circulate the RIPE-Handle proposal and then go ahead with the implementation - pending. Action: 17.11 NCC Investigate and propose a syntax-checking facility for the new db software. volunteer needed. Action: 17.20 Oleg Tabarovsky To collect data on external lines and restrictions applying to each line that will form part of the Russian back-bone. Send details to <oleg(a)ussr.eu.net>. Action: 18.3 Geert Jan de Groot Investigate monthly publication of error files on reverse zone files, similar to hostcount error files. Action: 18.5 Wilfried Woeber Post the CEEnet Initiative maps to the RIPE FTP server. Action: 18.16 Everyone in the Mbone group Send in your Mbone maps to Erik-Jan Bos. Action: 19.1 RIPE NCC To survey RIPE community on content of RIPE NCC Quarterly Reports. Action: 19.2 Mike Norris At the 20th meeting to raise the training of local IR's as a topic for discussion. Action: 19.3 Daniel Karrenberg To make an inventory document of the problems associated with charging for address space. Action: 19.4 Daniel Karrenberg To recirculate draft proposal on use of private address space for VSE's not connecting to the Internet. Circulate proposal to the WG mailing list. Action: 19.5 RIPE NCC To organise a meeting between regional registries, with representatives from the RIPE local - IR working group. Action: 19.6 Geert Jan de Groot To document new attribute "status" proposed to describe whether a network is delegated, reserved or assigned. Action: 19.7 RIPE NCC Circulate revised reipe-115 to the local-ir mailing list for comments. Action: 19.8 Daniel Karrenberg To prepare specification for the format of the list of service providers. Action: 19.10 Erik Jan Bos, Wilfried Woeber Written proposal to extend the "inet-rtr" object ready before RIPE 20. Action: 19.11 RIPE NCC To propose new domain object for in-addr.arpa. Action: 19.12 Marten Terpstra To write up the proposed "stored"/"proc essed" attribute. Action: 19.13 Milan Sterba Send e-mail to the prospective contributors to the CDS. Action: 19.14 Erik-Jan Bos Write document describing how to use the rtr-obj to describe location of m-routers. Action: 19.15 Erik-Jan Bos Find out about other vendors' implementations of PIM.

1 0

ns.ripe.net will change IP address
by Geert Jan de Groot 25 Nov '94

25 Nov '94

Hi, Somewhere in the next couple of weeks, ns.ripe.net will change IP address. The new box will have DNS recursion disabled (i.e. you cannot resolve off it), to make chances lower to get infected by bogus resource records without affecting intended operation. This should go unnoticed to you, except: - If you have a DNS glue record for ns.ripe.net, I ask you to remove the glue record. No zone except ripe.net needs it, newer DNS software ignores it but there is a lot of old software around.. - If you resolve off ns.ripe.net (some do, for backup reasons), I ask you to look for another solution. Please get in touch with <ncc(a)ripe.net> if you feel this is too much of a problem. Many thanks to the people that I contacted last week to open up their nameservers to allow the new box to get the zones too. As far as I know, all zones are loaded at the new box. We will maintain a nameserver at the old address for some time after the switch, mainly to detect straggle pointers to the old address. Please refer questions to <ncc(a)ripe.net>. Thanks, Geert Jan

1 0

Ebone press release
by Ebone mailbox 18 Nov '94

18 Nov '94

EBONE is established as an Association and prepares for 34 Mbps =============================================================== The Ebone association --------------------- In the recent past Ebone, a European Network providing Internet IP and ISO CLNS, has gained substantial stability and its prospects for the future are clear. Ebone enjoys a rapidly expanding membership, both in terms of capacity and in terms of new members organizations. Seeing this high demand it is no surprise that Ebone is being upgraded continuously. From 1 July 1994 to the end of January 1995, the overall backbone and trans Atlantic capacity will be increased by a factor of 75 % to 12 Mbps. This proves the strong need for Ebone services, therefore the Ebone Consortium of Contributing Organizations decided to re-model Ebone into an Association to provide further stability also in legal terms. On 2 November 1994 the Ebone Association was formed under French law. Its first Executive Committee officers are: - Christian Michau from Renater, France, President, - Peter Rastl from ACONET, Austria, Vice-President, - Dave Morton from ECRC, Germany, Treasurer and - Dennis Jennings from HEANET, Ireland, Secretary. Technical development --------------------- The global Internet is developing at a speed without parallel, with connected organizations multiplying exponentially. A serious challenge to the Internet infrastructure capacity is the so-called multicast services that have recently found a growing market. Therefore Ebone is configuring multicast using Protocol Independent Multicast (PIM) in its PoPs in order to reduce multiplication of multicast packets. This new development will be operational by the end of January 1995. Ebone configuration planned for January 1995 -------------------------------------------- Vienna 2048 Munich EBS--------ACONET (AT) US (GIX) ------------EBS / CARnet (HR) | / CESNET (CZ) | / Hungarnet (HU) 2048 | /1536 NASK (PL) | / Roman. AC net (RO) | / SANET (SK) 3584 Paris 2048 Geneva US (GIX) -------------EBS-----------EBS -------ILAN (IL) | | RENATER (FR) BELNET (BE) BT (UK) CINECA (IT) DATAnet (FI) ECRC (DE) FCCN (PT) FCRU (EG) FORTH (GR) HEANET (IE) Internetway (FR) Lisbon University (PT) PIPEX (UK) SwipNet (SE) Tipnet (SE) Transpac (FR) Transpac (SE) Plans for 1995 and beyond: 34 Mbps and more. ------------------------------------------- The Ebone Association with its state-of-the art-capabilities in terms of equipment, manpower and routing, is in an excellent position to start piloting 34 Mbps networking for research in Europe in order to provide high speed services, compliant with the Bangemann report. Ebone is looking for participation to its initiative to organize a framework for interconnecting between service providers (peering) at 34 Mbps in Europe. Ebone is also interested in participating in the ACTS programme and sees the interconnection of the ACTS's National Hosts as a highly valuable contribution to coordination of national interconnections in Europe. Ebone will put forward a proposal to the EC in the framework of ACTS. For more information contact: Christian Michau, Ebone chairman, Renater, France, phone +33 14427 4260, fax +33 14427 2613, e-mail christian.michau(a)urec.fr Frode Greisen, Ebone general manager, UNI-C, Denmark, phone +45 3582 8355, fax +45 3183 7949, e-mail frode.greisen(a)uni-c.dk

1 0

RIPE Database Transition T2
by Marten Terpstra 17 Nov '94

17 Nov '94

Dear all, Apologies for this wide distribution but I think it is important enough. This is a reminder that coming Monday the 21st of November, the second and last step of the RIPE database transition will take place. This transition is the transition from network number objects that hold all policy information, to route objects that contain all this information. For more detailed info on what exactly will change and how, please read ripe-123 which is available as: ftp://ftp.ripe.net/ripe/docs/ripe-123.{txt|ps} Especially section 5 explains forthe various RIPE database user groups what is going to change. -Marten

1 0

in-addr.arpa
by Hank Nussbacher 10 Nov '94

10 Nov '94

Up till a week ago I would send in my in-addr.arpa requests to internic.net. They are now telling me they don't handle it anymore. How do other sites handles in-addr.arpa registrations? Thanks, Hank

3 2

Re: in-addr.arpa
by Marko.Kaittola＠dante.org.uk 09 Nov '94

09 Nov '94

This is an automatic reply. Feel free to send additional mail, as only this one notice will be generated. The following is a prerecorded message, sent for -- Thanks for your message. I will deal with it as soon as possible (although this may imply a long delay). My schedule looks roughly like this: Week 42 Travelling in London and Zurich. I may be able to read my mail on Thursday. I may also read my mail on the week-end. Week 43 Holiday - not available for anything Week 44 Holiday - not available for anything Week 45 Holiday - not available for anything Week 46 Return to office. Try to sort out the backlog. End of the week in an EEMA conference. Week 47 Meeting on Monday. Tuesday in office. Wednesday to Friday at Utrecht. Week 48 E-Mail world at Boston Week 49 IETF in California If you really need to get hold of me, DANTE's office should be able to help you. They should also be able to deal with most of the issues you would want to talk to me. Please contact them at dante(a)dante.org.uk S=dante; O=dante; P=dante; A=mailnet; C=fi; Tel +44 223 302 992 Fax +44 223 303 005

2 1

Re: in-addr.arpa
by Hank Nussbacher 09 Nov '94

09 Nov '94

On Tue, 8 Nov 1994 21:43:45 +0100 (MET) you said: >Hank Nussbacher wrote: >> >>Up till a week ago I would send in my in-addr.arpa requests to >>internic.net. They are now telling me they don't handle it anymore. >>How do other sites handles in-addr.arpa registrations? > >Maybe it was just for certain domains such as - for instance - the >193.in-addr.arpa domain which is handled by the RIPE NCC ? No it wasn't: !From: Inaddress Registration Role Account <inaddr(a)internic.net> !Subject: Re: Plz add to in-addr.arpa zone !To: HANK(a)taunivm.TAU.AC.IL (Hank Nussbacher) !Date: Thu, 3 Nov 1994 13:46:58 -0500 (EST) ! !Dear Coordinator: ! ! !Your request is in the block of 192.114.0.0 - 192.118.255.0. 0ur policy is !to delegate the block to the listed Service Provider. It is the Service !Providers responsiblity to provide inaddr service to networks within this !block and to notify potential requestors to contact them instead of the !INTERNIC on server additions, changes, and etc. ! !Please contact your Service Provider to initiate inaddr service. ! !Regards, !Registration Serivce It is from a block I got from nic.mil.net about 4 years ago. > >-- Robert Martin-Legene, = EUnet Denmark = > DKnet, Fruebjergvej 3, DK-2100 Kobenhavn O, +45 39 17 99 00 Hank

2 1