- ripe-list - mailman.ripe.net

RIPE DNS Hostcount August 1993
by Marten Terpstra 02 Sep '93

02 Sep '93

Folks, Please find below the RIPE DNS hostcount for August 1993. - we are currently analyzing all the DNS output for some statistics on the 2nd and 3rd level domains inside each of the top levels. Once we get some results we will post them as well. - output again on ftp.ripe.net:ripe/hostcount, also available in the gopher server on gopher.ripe.net under "RIPE Archive"/"ripe"/"hostcount" - UK makes a big jump in their race with Germany towards 100,000 - total increase of almost 25,000 to over 451,000. - history again appended, I have included deltas this time, which shows the growth compared to the previous count. I plan to continue doing this. - everyone who uses "host" for similar purposes as this should pick up a new version from either ftp.ripe.net:tools/dns/host.tar.Z or ftp.nikhef.nl:pub/network/host.tar.Z, because some modifications have been made that make the output somewhat more friendly, and the hostcount much faster (thanks to Eric Wassenaar, NIKHEF) Enoy, -Marten ------- RIPE DNS Hostcount Previous Count : Wed Jul 31 1993 This Count : Tue Aug 31 1993 CY SOA COUNTED DUPL REAL CHANGE ============================================================ al 1 0 0 0 0 at 296 12986 94 12892 + 272 be 57 5134 92 5042 + 806 bg 3 21 5 16 + 16 by 0 0 0 0 0 ch 171 32476 712 31764 + 1283 cs 74 2810 57 2753 + 3 cy 5 30 0 30 0 cz 69 3439 85 3354 + 170 de 1395 95375 3355 92020 + 2506 dk 113 6823 93 6730 + 222 dz 0 0 0 0 0 ee 17 210 2 208 + 16 eg 1 0 0 0 0 es 238 10485 127 10358 + 358 fi 271 28244 748 27496 + 1521 fo 1 0 0 0 0 fr 539 44242 604 43638 + 5287 gb 1 15 0 15 + 1 ge 1 0 0 0 0 gr 86 1337 225 1112 + 12 hr 26 419 1 418 + 91 hu 32 1679 7 1672 + 265 ie 44 1937 48 1889 + 222 is 36 1302 10 1292 + 65 it 353 14058 215 13843 - 338 il 84 5671 64 5607 + 152 li 2 17 0 17 0 lt 1 0 0 0 0 lu 11 229 0 229 + 23 lv 1 15 0 15 + 1 mt 1 0 0 0 0 nl 379 36634 400 36234 + 949 no 404 25871 226 25645 + 958 pl 62 1216 9 1207 + 91 pt 85 2692 45 2647 - 75 ro 2 14 0 14 0 se 457 35535 313 35222 + 2873 si 11 468 3 465 + 9 sk 24 469 8 461 + 162 su 143 757 44 713 + 219 tn 1 0 0 0 - 11 tr 18 449 2 447 + 259 ua 34 140 11 129 + 110 uk 654 95794 10274 85520 + 5791 va 0 0 0 0 0 yu 2 2 0 2 0 ============================================================ 6206 468995 17879 451116 +24289 History Count Delta 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% Apr 1992 170050 + 2111 + 1.3% May 1992 182528 + 12478 + 7.3% Jun 1992 196758 + 14230 + 7.8% Jul 1992 213017 + 16259 + 8.3% Aug 1992 221951 + 8934 + 4.2% Sep 1992 232522 + 10571 + 4.8% Oct 1992 254585 + 22063 + 9.5% Nov 1992 271795 + 17210 + 6.8% Dec 1992 284374 + 12579 + 4.6% Jan 1993 303828 + 19454 + 6.8% Feb 1993 322902 + 19074 + 6.3% Mar 1993 355140 + 32238 + 10.0% Apr 1993 366164 + 11024 + 3.1% May 1993 385522 + 19358 + 5.3% Jun 1993 404930 + 19408 + 5.0% Jul 1993 426827 + 21897 + 5.4% Aug 1993 451116 + 24289 + 5.7%

1 0

Guidelines on how to report on european connectivity
by Milan Sterba 01 Sep '93

01 Sep '93

Dear colleagues, it has been agreed at the last RIPE meeting that a new more general scheme of reporting on european connectivity shall be adopted in RIPE. The reporting scheme will be open for whole Europe and will cease to be restricted only to Central and Eastern European countries. Connectivity issues will not be pulished in form of a periodical report but will rather be maintained in the form of an indexed archive at the RIPE repository. We have agreed that there should be some editing board which would unify the look and style the presentations of different countries. We also agreed on producing guidelines to the contributors on how the connectivity report of a country should be organized. These guidelines are now published as a RIPE draft document ripe/docs/ripe-drafts/connectivity-report-plan.txt and will be proposed to be accepted as a ripe document at the next RIPE meeting in September. Please have a look at this proposal. I will be gratefull for any comments you might have to this proposal in order to work out a viable scheme which would result in improved quality of reporting on european connectivity. Thanks and see you in Amsterdam Best regards Milan Sterba -- BEWARE - MY TELEPHONE NUMBER HAS CHANGED !!!! ====================================================================== Prague University of Economics e-mail : Milan.Sterba(a)vse.cz Computing Center tel : +42 2 24 21 79 00 nam. W. Churchilla 4 home: +42 2 823 78 59 130 67 Praha 3 fax : +42 2 236 46 24 Czech republic =======================================================================

1 0

RIPE 16 - Draft Agenda v.1
by k13＠nikhef.nl 01 Sep '93

01 Sep '93

Dear all, please find below the first draft of the agenda for the coming RIPE meeting. Comments/addition are welcomed. As usual, the second day is reserved for the working group meetings. Agenda's for the working group meetings will be distributed in a week from now. See you all, Rob Blokzijl R I P E 1 6 ------------- draft Agenda - version 1 1. Opening 2. Minutes previous meeting 3. Action items 4. RIPE NCC report (Daniel Karrenberg) 5. Network Resource Discovery - GARR on-line network resource guide (Giuseppe Romano) - Guide To Network Resource Tools (Daniele Bovio) 6. Update on the new JIPS services (Phil Jones) 7. RIPE Network Operations Coordination (Bernhard Stockman) 8. Introduction of DANTE (Howard Davies) 9. Joint Projects progress (Tony Bates) - RS - GISS - PRIDE 10. RIPE & RARE (Rob Blokzijl) 11. RIPE NCC Review (Rob Blokzijl) 12. RIPE NCC Activity Plan (Rob Blokzijl) 13. Update on networking with Russia (Rob Blokzijl) 14. Next meetings 15. A.O.B. 16. Closing

1 0

Re: RARE Call for Tender for MS-Windows X.500 DUA using LDAP
by Brian Call 30 Aug '93

30 Aug '93

>I believe Wollongongs pathworks(pathways) product commercially available >for a few months has a windows based dua, I believe it does use ldap. > >If you are already aware of this information, I apologize for wasting your >time. >If anyone has any information which enhances or disputes the contents of >this message, I look forward to hearing from you. The current release of Wollongong's PathWay Messaging Services includes a X Windows based dua. The current release of PathWay Messenger (mail client program for X Windows, MS-Windows, and Macintosh) inlcudes X.500 searching capabilities. Neither of these uses LDAP yet. The protocol is RFC 1202 based. We plan on supporting LDAP in a future release. Brian Call brian(a)twg.com

1 0

control problems in communication networks
by RIPE NCC Staff 19 Aug '93

19 Aug '93

Can anyone assist Mario with his query below? ------- Forwarded Message Date: Thu, 19 Aug 93 16:29:40 +0200 From: bleich(a)epo.iitb.fhg.de To: ncc(a)ripe.net Subject: control problems in communication networks Dear Anne, let me explain what I want. In our lab we deal with machine learning algorithms , i.e. decision tree algorithms. The generic problem to machine learning is as follows. From samples of data (exapmles) described by a vector of attributes and a class, derive a function which predicts the class of the samples from the same population. The general scheme is to present the algorithm with "training data", from which it "learns" a classification function, then apply this function to some unseen "test data" to predict their class. One example for this is the recognition of handwritten digits. The handwritten digits were digitised onto images with 16*16 pixels and 256 grey levels. So each example consists of 16*16=256 attributes and 1 class (the digit). The resulting decision tree does not need all attributes to predict the class, only those which are relevant for the classification. Other application problems are in medicine, banking, etc. The question is now, is such an algorithm applicable on problems in communication engineering? One of the problems for example is the routing and flow control in networks. Perhaps it is possible to simulate such control algorithms. Mr. Kaehler told me, that you have made some experiments with the IBORN. It would be nice, to hear more about that. May be, you have data to another classification problem (like error recognition), too. Regards Mario Bleich ------- End of Forwarded Message

1 0

Re: RARE Call for Tender for MS-Windows X.500 DUA using LDAP
by Mike Newell 12 Aug '93

12 Aug '93

> RARE solicits tenders for the provision of a Directory User Agent > employing the Lightweight Directory Access Protocol (LDAP/RFC1487) for > the MS-Windows operating system. Please direct all enquiries to the > RARE Secretariat (raresec(a)rare.nl, mail address below). > > Analysis of products available for personal/desktop computer systems has > indicated that no LDAP solution is available for the MS-Windows > platform. RARE has therefore decided to encourage the provision of such > a solution by offering to assist with the development costs. A full > specification of the requirements is attached to this solicitation. > This has really surprised me. I wrote one for NASA Headquarters this weekend; it was designed to be REALLY simple and return the basic information we need at Headquarters. All told it took me about 60 hours to learn Visual C++, LDAP, and WINSOCK enough to generate a simple interface. Surely there are others out there willing to share their projects???? Mike Newell NASA Advanced Network Applications

1 0

RARE Call for Tender for MS-Windows X.500 DUA using LDAP
by dixon＠rare.nl 11 Aug '93

11 Aug '93

RARE solicits tenders for the provision of a Directory User Agent employing the Lightweight Directory Access Protocol (LDAP/RFC1487) for the MS-Windows operating system. Please direct all enquiries to the RARE Secretariat (raresec(a)rare.nl, mail address below). Analysis of products available for personal/desktop computer systems has indicated that no LDAP solution is available for the MS-Windows platform. RARE has therefore decided to encourage the provision of such a solution by offering to assist with the development costs. A full specification of the requirements is attached to this solicitation. Basic requirements, however, can be summarised as follows: o Support for MS-Windows 3.0 and higher and a commonly-available lower-layers protocol stack, preferably the WinSocket library. o A "user-friendly point-and-click" interface conformant to the "look and feel" of MS-windows, customisable for different language environments o The ability at least to search and browsethe directory and display entries. The ability to update and create new entries is to be preferred, but not essential. o Customisable schemas including basic provision of at least the "PilotPerson" Object Class defined in RFC1274. Within the schema, it should be possible to customise the default DUA display to show only a chosen subset of objects and/or attributes. o Available funding is limited, therefore a successful proposal is likely to be based on porting an existing DUA or on an offer for collaborative funding o The application should be freely distributable to the academic and research community represented by RARE for non-commercial use. Tenders should sent to the RARE Secretariat at the address below by 17th September 1993. Further information can be obtained from the same address. In addition to the information requested in the Requirements section of this call for tender, tenders should include: o The cost to RARE of the development work o The estimated start and end dates of the development phase of the project o The length of time for which support will be provided following the development phase, and the extent of that support o The name of an administrative contact for contract negotiation o The name of a technical contact o Telephone numbers, addresses and e-mail addresses of the named contacts Where the proposals are based on modifications to existing products, tenderers are encouraged to offer access to demonstration versions of the existing products so that there features may be compared. Specification ============= Hardware, Operating System and Communications Software ------------------------------------------------------ The DUA application should be supplied in binary form for execution under MS-Windows 3.0 + MS-DOS v5.0 or appropriate later releases of this software. The software should support a TCP/IP communication stack commonly available within the European academic community, preferably the WinSocket library. Tenders should indicate specific hardware and software requirements. Proposals should not rely on the availability of colour displays, but may require the provision of at least VGA-resolution monitors. Human Interface --------------- The application should provide an intuitive human interface which provides access to the major functions using the WIMP paradigm in a fashion compatible with the "look and feel" of other Windows applications. The application should be delivered with textual information provided in the English language, but should be developed in such a way that translation to other language environments is straightforward. Protocol Elements ----------------- The DUA should implement the protocol specified in RFC1487, although BIND requests may be restricted to "simple" authentication. Encoding rules for attribute values are as defined in RFC1488. Functionality ------------- The DUA is required to provide at least search, browse and display operations (i.e. it should be possible to look for an entry without knowing the exact RDN or position within the DIT and to display its contents in a meaningful way). It should be possible to navigate the directory structure without the need to enter either attribute names or values, although the entry of attribute values may be used to direct attention to a chosen part of the tree. The sorting scheme which determines the order in which entries are returned for selection should be customisable by the user (i.e. the attributes used to determine the order should be selectable). It should be possible by means of configuration (possibly by a system manager) to restrict the default DUA display to a subset of object classes, or attribute types meaningful in a particular application. The DUA may additionally provide for the updating of existing directory entries and for the creation of new entries. This provision will be balanced against the proposal cost: tenderers who wish to offer this functionality may benefit from quoting separate prices for the basic (search/display) and extended implementations. DSA Interworking ---------------- It should be possible to demonstrate interworking with at least two different DSA implementations. Dependency on a particular DSA will not be acceptable. Schema ------ The basic reference for the schema to be supported is RFC1274 (The COSINE and Internet X.500 Schema). The DUA must be pre-configured to be able to recognise the PilotPerson Object Class defined in this document. However, the DUA must also be configurable to support a variety of different classes of data object for all supported operations. Tenders should specify any restrictions on the data types or combinations of data types that may be used in configuring new classes of object. Intellectual Property, Support and Maintenance ============================================== Licensing --------- The application should be distributable freely or at nominal cost to the international academic and research community for non-commercial use. The supplier may make additional charges for the provision of support and/or documentation beyond that described below. It is not a requirement that the source code of the application be made freely available. Furthermore, the supplier shall not be inhibited from commercial exploitation of the product outside of this community. Installation, Support & Documentation ------------------------------------- Sufficient documentation should be provided (preferably in electronic form) to permit the installation of the application by an averagely-experienced network manager. The installation should contain a test procedure to enable its success to be determined. Following completion of the development phase of the project, the tenderer will be expected to fix significant defects in the application which are reported during the initial period of its use. Monitoring and Acceptance ========================= Intermim versions of the application should be made available for evaluation by a review group nominated by RARE. Payments will normally be staged, payment being dependent on the acceptance of each phase of the development by the nominated group. Addresses ========= Tenders to be sent to: RARE Secretariat Singel 466-468 NL - 1017 AW Amsterdam. Phone: +31 20 639 1131 E-mail: raresec(a)rare.nl

1 0

REGISTRATION FORM - 16th RIPE meeting
by Anne Lord 10 Aug '93

10 Aug '93

********************************************************************** If you are interested in participating in the 16th RIPE Meeting in Amsterdam, would you kindly fill in the attached form and mail it to meeting(a)ripe.net as soon as possible. ---------------------------------------------------------------------- 16th RIPE meeting Registration reservation form Amsterdam, September 15th-17th 1993 a) Registration ( ) I would like take part in the RIPE meeting. ( ) I already have a RIPE badge from a previous meeting. ( ) I need a RIPE badge making up for me (please provide your details below). These will be printed on your badge. Name: Organisation/affiliation: Country: b) Personal details Please give your name and contact details below. If you have a person entry in the RIPE database, you do not need to fill this in. Name: Address: Address: Country: E-Mail Address: ------------------------------------------------------------------- Please send this form to: <meeting(a)ripe.net> or +31 20 592 5090 fax For further information please send mail to the above e-mail address. -------------------------end----------------------------------------

1 0

ANNOUNCEMENT - 16th RIPE meeting
by Anne Lord 10 Aug '93

10 Aug '93

R I P E meeting announcement ============================ This is to announce that the 16th RIPE meeting will take place: Dates: 15 September 14:00h - 18:00h 16 September 09:00h - 18:00h 17 September 09:00h - 16:00h Venue: CWI Kruislaan 413 1098 SJ Amsterdam The Netherlands Host: NIKHEF Registration: Please use the registration form (which will follow in a separate mail) to give notice of your coming as soon as possible. General Information: -------------------- Currency: 1 UK pound = Hfl 3.- 1 ECU = Hfl 2.2 1 US$ = Hfl 1.90 Appended to this announcement: ------------------------------ - directions to the meeting place Documents to follow (separate mail messages): --------------------------------------------- <> details of hotels in Amsterdam close to meeting venue <> registration form for attendance at the meeting ================================================================== CWI - The RIPE meeting venue: How do I get there? ------------------------------------------------------------------ To ease any possible confusion, two postscript maps can be found in the RIPE document store. One shows the bus and tram stops around the meeting site and the other is a more general map of the area. Both maps are available by ftp: /ripe/docs/Next-Meeting/area-map.ps /ripe/docs/Next-Meeting/area-map.ps.Z /ripe/docs/Next-Meeting/local.transport-map.ps /ripe/docs/Next-Meeting/local.transport-map.ps.Z *PLEASE NOTE: The number 69 and 169 now end at Amstel station rather than Muiderpoort station. The number 15 now connects the Amstel station with Muiderpoort station. a) From Amsterdam Schipol airport: <> Take the train from the airport railway station to the Central Railway station (Amsterdam CS). Then from Amsterdam Central Station : <> Take tram number 9 till the stop at the intersection of Middenweg and Kruislaan (15 min ride). The stop is just before the intersection. <> Walk down the Kruislaan in the direction of the railway bridge. Cross under the bridge and continue. Take the 2nd entrance left and follow the signs to the meeting (15 min walk all together). Instead of walking down Kruislaan you can take the shuttlebus for 2 stops. Turn into Kruislaan and the bustop is a little way down on the right hand side of the road. or from Central Station you can: <> Take bus 22 in the direction 'Indische Buurt' to the stop at the 'Muiderpoort Station' and take shuttlebus 66 which stops outside CWI. b) Alternatively from Amsterdam Schipol <> Take the train from the airport railway station to the RAI station in Amsterdam, which is at the end of this line (10 min ride). NOTE: Amsterdam Central Station (CS) is on another line. Then from the RAI station: <> From the RAI station take the city bus number 69 or CN bus number 169 in the direction `Amstel Station'. From the Amstel Railway Station <> From the Amstel station take the city bus number 15 the direction `Muiderpoort Station' to the stop on the corner of Kruislaan and Linnaeusparkweg (15 min ride, ask the driver where to get off) or proceed to 'Muiderpoort Station' and take shuttlebus 66. You can also take the shuttlebus 66 from the Kruislaan and Linnaeusparkweg intersection as described above. d) Taxi from the airport <> Takes 15 mins and will cost approximately Hfl. 60.00 e) Connections away <> Tram 6 will take you to Leidseplein Tram 10 also Leidseplein Tram 14 To and from Dam Square Tram 9 Rembrandtplein f) Bus 66 Timetable <> From Muiderpoort Station (Monday - Friday) 7.20 7.40 8.00 8.20 8.40 9.00 9.20 9.40 10.10 10.40 11.10 11.40 12.21 12.51 13.21 13.51 14.21 14.51 15.21 15.51 16.11 16.31 16.51 17.11 17.31 17.51 18.11 <> From CWI to Muiderpoortsation (Monday - Friday) 7.28 7.48 8.08 8.28 8.48 9.08 9.28 9.48 10.18 10.48 11.18 11.48 12.28 12.58 13.28 13.58 14.28 14.58 15.28 15.58 16.18 16.38 16.58 17.18 17.38 17.58 18.18 <> This bus is a shuttle bus that operates from Muiderpoort station in a large circle around the CWI and NIKHEF campus. ==================================================================== Public Transport - how much does it cost and where can I get tickets? -------------------------------------------------------------------- Tickets of 15 strips (`Strippenkaart' costing Hfl. 10.75) can be bought in Post Offices, railway stations and cigarette shops. Tickets of 2 and 3 strips can be bought on the bus or the tram but they are much more expensive. You have to validate the ticket yourself in the metro stations and in the trams (except on lines 4 and 13). In the buses the driver will validate the ticket. Amsterdam is divided into zones: the old city is in zone `Centrum' whereas CWI is in zone `Oost'. You need to count how many zones you will be travelling through (from the centre - CWI is 2 zones) and count up that number of strips on your ticket + 1 extra. So in the above example you will need to stamp the 3rd strip. In case of overflow you stamp the last strip of the first ticket and start counting the remaining strips on the next ticket. Confused? Warning: BEWARE of pickpockets in crowded places.

1 0

Re: RIPE DNS Hostcount July 1993
by Joseph Michl 05 Aug '93

05 Aug '93

Christian Huiteme is right. The x.25 is a well spreaded, well understood, well working and calculable network infrastructure in germany. It is right that for an IP dominated network you can think for an better infrastructure. But the point is not to have the best infrastructure, but to have at least one good. And with the x.25 network (WIN) we have one. So I think it is more right to say: because of this x.25 infrastructure there are so many IP Hosts connected in germany, and not in spite of. Concerning "trouble enhancement layer": There are problems with x.25, but they are resolvable. With every other protocol you have some problems. The way should therefore be to work at the problems and not to condemn a whole protocol. Regards, Joseph

2 1