- ripe-list - mailman.ripe.net

Document Announcement
by Tony Bates 03 Sep '93

03 Sep '93

Dear All, A new document is available. This is for use when applying for Autonomous System (AS) numbers. It contains some supporting notes to help with the application. New/Revised RIPE Document Announcement -------------------------------------- A <revised><new> document below ...is available from the RIPE document store. Ref: ripe-091 Title: European Autonomous System Number Application Form Title: & Supporting Notes Author: Tony Bates, Anne Lord Date: 3 Sep 1993 Format: PS=41091 TXT=13759 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- Ripe-091 is the first version of the "European Autonomous System Number Application Form". It contains a guidance section to help in applying for AS numbers. It is split into two parts; an administrative and a technical section. The technical section includes the RIPE-81 attributes used for registering an AS's routing policy. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get <filename>". For example "get ripe-091.txt". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-091.txt

1 0

** RIPE 16 - Dinner Announcement **
by Anne Lord 02 Sep '93

02 Sep '93

* ANNOUNCEMENT * * ANNOUNCEMENT * * ANNOUNCEMENT * * ANNOUNCEMENT * * 16th RIPE Meeting Dinnner Thursday September 16th, Amsterdam Time : 8pm Departure Point: Prins Hendrikkade opposite Central Station For the 16th RIPE meeting dinner we thought it might be nice to have dinner afloat. The dinner will be served aboard a canal boat which will cruise through the canals of Amsterdam. There will be a guide on board the boat to give a guided commentary (as much or as little as you want). The menu for the dinner is as follows (vegetarian and/or special diet meals can be arranged on request) : -00- Creamy Chervil Soup -00- Filet of Salmon in a herb sauce Seasons vegetables Potato-dish -00- Fresh fruit and cream -00- Coffee and digestif -00- The meal will be accompanied by a choice of red or white wine. Cost of the dinner and guide will be Hfl. 70,- inc. drinks Please reply to <meeting(a)ripe.net> if would like to have a place reserved for you at the dinner. Payment from us to them will be on Tuesday 14th, so this is the deadline for reserving a place. The money for the meal will be collected on the second day of the RIPE meeting during lunch. Now I am praying for calm weather and sunny skies :-) Anne - - - - - - - - - - - - -- - - - - - - -- - - - - - - -- - - - - - --

2 1

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