- ripe-list - mailman.ripe.net

ripe-84: RIPE NCC Funding, Appendix A changed
by Daniel Karrenberg 19 May '93

19 May '93

Appendix A of ripe-84 has been changed to reflect the current status of the funding effort. Since this does not change the content of the document itself it has not been given a new number. We realise this is not good practise. Of course the appendix should have been a seperate document. Since it isn't this is the best way to keep things up to date. Daniel

1 0

Message on evolving directory services (fwd)
by Mr P W Jones 14 May '93

14 May '93

Dear fellow RIPE-ers: This is particularly for those who had enough determiation to stay awake during my 'how can we better exploit the IP Infrastructure talk' at the last RIPE :-) The following seems to me to represent good news, in that it answers the criticisms that I made of the 'white pages' services in trying to get a unified interface to all the available data, plus other points of progress as described below. Best wishes, Phil (p.jones(a)jnt.ac.uk) Forwarded message: > From Directory-Group-administrator(a)uk.ac.jnt Tue May 11 13:37 GMT 1993 > Via: uk.ac.jnt; Tue, 11 May 93 13:37:01 GMT > Via: uk.ac.ucl.cs; Tue, 11 May 1993 14:05:51 +0100 > To: directory-group(a)uk.ac.jnt > Subject: Message on evolving directory services > Date: Tue, 11 May 93 14:05:37 +0100 > From: Paul Barker <P.Barker(a)uk.ac.ucl.cs> > Sender: Directory-Group-administrator(a)uk.ac.jnt > > Greetings, > The following message was posted to an Internet list in the last day or > so. The InterNIC have decided to try a transition strategy of WHOIS -> > X.500. Hope this is of interest. > > Paul > ========================================================== > Towards a Distributed Internet Directory Service > Srinivas R. Sataluri > sri(a)internic.net > InterNIC Directory and Database Services > Draft Dated: 10 May 1993 > > 1. Introduction > > The creation of a Directory Service involves three important steps: > (1) setting the criteria for inclusion in the Directory, (2) collection > and storage of data, and (3) keeping the data valid and up-to-date. > > We observe that a Directory that is essential to the success of a > larger business mission often tends to be up-to-date! For instance, > corporations maintain Directories based on employment status and phone > companies maintain Directories based on subscription to the phone > service. Similarly, the InterNIC Registration Services provider, based > on data supplied at the time of registration, maintains a Directory of > Points Of Contact (POCs) for various network elements crucial to the > smooth operation of the Internet. Thus to ensure currency of a > Directory, the directory service provider should maintain an on-going > contact with the listed entity/person, such as bill payment, entry > verification, etc. > > 2. Internet Directory Evolution > > When there were only a few sites on the ARPANET, SRI established a > central WHOIS Database and requested that "each individual with a > directory on an ARPANET or MILNET host, who is capable of passing > traffic across the DoD Internet, be registered in the NIC WHOIS > Database" [1]. That database now has about 140,000 individual entries > who are not POCs for any network elements crucial to the operation of > the NSFNET. More recently, NSF has asked that those individuals who are > not POCs be excluded from the WHOIS Registration database. However, > there is a wealth of information contained in this database that would > be otherwise valuable if made available to the Internet community. > > The SRI approach if applied today will result in a huge centralized > database that will grow rapidly as the number of Internet users > increases. Such a database will be expensive to maintain, difficult to > replicate, and nearly impossible to keep updated. Moreover, owing to > the large number of potential users, such a service could stress the > server and network resources thus affecting the reliability and quality > of service. > > Several years back the Internet community when faced with a similar but > smaller problem, discarded the centrally maintained "hosts.txt" file in > favor of the distributed Domain Name Server solution. We feel that it > is time to discard the centralized WHOIS directory and create a > Distributed Internet Directory. > > A distributed directory service will allow the data to be moved closer > to the "owner," which in turn increases the likelihood that the > currency and privacy of the data is maintained. Further, replication > will improve performance and reliability. A method of organizing and > managing a Distributed Internet Directory is to allow > organizations/persons responsible for the data to maintain it. > > In addition, to enable people on the Internet to obtain information > about key individuals and to help stay in contact, it is possible, and > may be useful to maintain special secondary directories, such as a list > of authors of RFCs, a list of authors of Internet Standards Documents, > a list of individuals that attended IETF meetings, etc. Such lists can > be created with some diligent effort but are even harder to maintain as > personnel information and organizational affiliation are bound to > change with time. > > 3. Possible Solutions > > Several informal attempts have been made to build an Internet users > list. MIT runs a mailserver (mail-server(a)pit-manager.mit.edu) that > responds to usenet address requests. This database is organized by > collecting information from the electronic mail headers in netnews > postings. There is limited information available on each person - for > instance, the email address. Netfind uses a similar approach but > potentially has a larger name space as it only captures the domain > names from netnews postings and in real-time tries WHOIS and/or finger > queries to obtain information about individuals. In both these cases, > there are no efforts to verify and maintain the accuracy of the > information. There is also no way for individuals to ask to be included > in these directories. > > Several organizations run WHOIS servers and make personnel information > available for Internet access. However, the WHOIS servers are not > interconnected and one has to connect to the WHOIS server that has the > data being sought. To simplify this problem, a list of WHOIS servers > has been assembled by Matt Power of MIT. Gopher gateways into WHOIS > servers have also come up, e.g. University of Minnesota runs a Gopher > server that has a list of 91 WHOIS servers. > > WHOIS++ extends the original WHOIS data model and query protocol and > proposes an extensible, distributed indexing service geared towards > interlinking enhanced WHOIS servers and in developing efficient search > paradigms thus creating a simple distributed directory service. The > WHOIS++ model is under development and it may take some time before > robust implementations are available. > > Of the technologies available today for creating an extensible, > replicated, distributed directory service, X.500 is the most mature. It > requires a hierarchical organization of data and permits a distributed > search based on several attributes. Special purpose/secondary > directories can be easily built by use of alias pointers. Moreover, > attempts are now underway for creating a light-weight directory access > protocol that will enable even personal computers to access the > Directory. > > The Internet community is well aware that no single directory > technology can solve all the needs of the community and clearly X.500 > is not the last word in directory technologies. Several alternate > methods of realizing directories - CSO servers, WAIS based directory > services, WHOIS and WHOIS++ servers - are already in use today. The > Internet community is now concentrating on building gateways between > the different directory systems and information access technologies > rather than converting from one technology to an other. This trend is > bound to continue and mature. Tim Howes of University of Michigan built > a successful Gopher gateway into the X.500 Directory [5]. The Gopher to > X.500 gateway at the University of Michigan currently handles over 5000 > connections per day. Mark Prior of The University of Adelaide, > Australia is building a WHOIS++ to X.500 gateway. > > The Internet community may eventually adopt a Directory system other > than X.500. In that event, the effort involved in creating a X.500 > Directory will not be wasted since other directory systems will be able > to access the X.500 DIT through gateways. > > 4. X.500 Based Solution > > X.500 is designed to build a distributed, global directory service > [4]. It allows organizations to run and maintain their own directory > service while providing a seamless interconnection of different > directory servers. Its main advantage is an extensible hierarchical > namespace called a DIT (Directory Information Tree) eminently suited > for organizing white pages directory information where each entry has a > unique global name. > > PSI is running a X.500 White Pages Pilot Project for the United States > that connects to several International pilots via the European PARADISE > project. The world-wide X.500 Directory is distributed over nearly 500 > DSAs (Directory System Agents) that hold data of about 2800 > organizations. These organizations make their personnel data accessible > to the Internet users. > > All the X.500 Directory pilots structure the personnel information > under organizations placed appropriately in the DIT. The NADF (North > American Directory Forum) - a group of public directory service > providers - is proposing a namespace based on the existing civil naming > infrastructure in Canada and the United States [3]. A NADF pilot is > underway but it is too early to use the NADF structure for implementing > the Distributed Internet Directory. > > As proposed in [2] we envision a distributed Internet Directory where > larger organizations maintain their part of the DIT on their own DSA > (Directory System Agent) and smaller organizations will obtain DSA > space from regional networks or other service providers. Together these > DSAs will form the Internet Directory Service Infrastructure. > > AT&T InterNIC Directory and Database Services will help achieve this > goal through the following action plan: > > * We have already started two X.500 DSAs (a master and a slave) > and joined the PSI White Pages Project. > * We have listed the InterNIC personnel in our DSA. > * We are running a public access DUA and a mailserver that can > search the world-wide X.500 Directory that now has more than a > million entries. > * We are providing technical advice and support to people who > contact us and are interested in Directory Services. > * We are creating a simplified list of instructions to help > organizations bring up their own DSAs. > * We are in the process of creating a starter-kit for > organizations that join the X.500 Directory. > * We are committed to participation in Directory related > educational and outreach activities sponsored by the InterNIC > Information Services provider. > > To expedite the creation of the Distributed Internet Directory, we will > maintain entries of interested organizations in our DSAs. The following > policy will apply to the organizational entries we maintain. > > * Each organization will be allowed a maximum of fifty (50) > directory entries that include one organizational entry, and any > combination of organizational unit or person entries. The > organizational unit and individual entries can be submitted any time > after the organization entry is submitted. > > * Departments and Units of registered/well-known organizations, > however large they may be, do not qualify for an independent > listing. Examples: (1) Department of Computer Science of the > University of Iowa will only be listed under the University entry. > (2) AT&T Data Communication Services does not qualify for a listing. > They can be listed as an organizational unit under the AT&T > organization listing. However, independent organizations such as > college campuses (University of California at Berkeley, State > University of New York at StonyBrook), and subsidiaries of large > corporations (NCR) do qualify for independent listings. > > We reserve the right to change the maximum number of entries allowed > for an organization at any time in the future, in concurrence with the > NSF and other forums suggested by the NSF. Interested organizations > should complete a template - file: > /ftp/pub/internic-info/organization-x500.template available for > anonymous FTP on ds.internic.net - and send the completed form to > request(a)ds.internic.net. > > 5. Transitioning the non-POC Entries in the WHOIS Database > > The WHOIS database maintained by the DDN NIC has valuable information > about individuals active on the Internet. Hence, we propose the > following migration path for the entries in the WHOIS database to the > Distributed Internet Directory. > > * As a temporary measure, we will store the applicable listings > from the nearly 160,000 entries contained in the WHOIS database on > our server through WAIS. No new entries or updates to this data will > be accepted. However, deletion of entries will be permitted. > > We can provide this service within two weeks of obtaining the data. > > * We will contact and encourage organizations whose members are > in the WHOIS database to start their own Directory and list the > appropriate individuals or complete our template and use our facility > to list up to 50 entries. As new organizational listings (DSAs) are > created, the corresponding organizational and personnel listings in > the WHOIS database will be retired. > > This is an ongoing process that involves persuasion, sifting through > the WHOIS database to identify candidate listings, and contacting the > affected individuals. But it is a worthwhile effort since it will > eventually lead to the creation of a fully distributed Directory that > is also accurate. > > * We expect that in due course (2 to 3 years), the WHOIS database > will shrink and many new organizations will join the Distributed > Internet Directory, at which time we can shut down the WHOIS > database. We will attempt to transition every WHOIS entry into the > Distributed Internet Directory. > > A smooth transition consistent with the plan proposed above will > require a dedicated effort from the InterNIC providers, the support of > the NSF, and the cooperation of the Internet community - especially > individuals and organizations listed in the WHOIS Directory. > > * We will develop a user agent that will support the WHOIS > protocol that can search both the WHOIS database and the X.500 > Directory thus providing a uniform user-interface to the evolving > Directory. > > This can be completed within one month after receiving the data. > > REFERENCES > > [1] Harrenstien, K., V. White. "NICNAME/WHOIS," RFC 812, March 1982. > > [2] Kille, S., E. Huizer, V. Cerf, R. Hobby, and S. Kent. "A Strategic > Plan for Deploying an Internet X.500 Directory Service," RFC > 1430,February 1993. > > [3] The North American Directory Forum, "NADF Standing Documents: A > Brief Overview," RFC 1417, February 1993. > > [4] Weider, C., J. Reynolds, and S. Heker. "Technical Overview of > Directory Services Using the X.500 Protocol," FYI 14, March 1992. > > [5] Howes, T. "The Gopher to X.500 Gateway," ConneXions, Volume 7, No. > 4, April 1993. >

2 1

long-awaited NSFNET "re-compete" Solicitation available for FTP
by Steve Goldstein--Ph +1-202-357-9717 12 May '93

12 May '93

Forwarding announcement from Steve Wolff. --SG ------- Forwarded Message To: com-priv(a)psi.com Subject: NSFNET solicitation is out Date: Wed, 12 May 93 09:19:47 EDT From: Stephen Wolff <steve(a)cise.cise.nsf.gov> Anonymous ftp to stis.nsf.gov. Filename is nsf9352. -s ------- End of Forwarded Message

1 0

IETF MAILING 1e: DRAFT AGENDA: 12-16 July 1993/Amsterdam
by Marten Terpstra 12 May '93

12 May '93

Forwarded from Erik Huizer. Apologies for people who already received this. ------- Forwarded Message Date: Tue, 11 May 93 17:50:14 -0400 From: ietf-rsvp(a)cnri.reston.va.us Resent-From: Erik Huizer <Erik.Huizer(a)SURFnet.nl> Sender: ietf-announce-request(a)ietf.cnri.reston.va.us To: IETF-Announce:group list; Resent-To: ripe(a)ripe.net Subject: IETF MAILING 1e: DRAFT AGENDA: 12-16 July 1993/Amsterdam Agenda of the Twenty-Seventh IETF - as of 5/11/93 - 5:30pm (12-16 July 1993) MONDAY, 12 July 1993 0800-0900 IETF Registration and Continental Breakfast 0900-0930 Introductions 0930-1200 Technical Presentations o TBD Breaks Coffee available throughout morning. 1330-1530 Afternoon Sessions I APP OSI Directory Services WG (osids) (Steve Hardcastle-Kille/ISODE) INT IP over ATM WG (atm) (Bob Hinden/Sun) RTG Border Gateway Protocol WG (bgp) (Yakov Rekhter/IBM)* RTG OSI IDRP for IP over IP WG (ipidrp) (Sue Hares/Merit)* OPS Operational Statistics WG (opstat) (Phill Gross/ANS and Bernhard Stockman/SUNET) SEC Security Area Advisory Group (saag) (Steve Crocker/TIS) USV WHOIS and Network Information Lookup Service WG (wnils) (Joan Gargano/UCDavis) 1530-1600 Break (Refreshments provided) 1600-1800 Afternoon Sessions II APP OSI Directory Services WG (osids) (Steve Hardcastle-Kille/ISODE) INT Simple Internet Protocol WG (sip) (Steve Deering/Xerox PARC and Christian Huitema/INRIA) OPS Operational Statistics WG (opstat) (Phill Gross/ANS and Bernhard Stockman/SUNET) USV Uniform Resource Identifiers WG (uri) (Alan Emtage/Bunyip and Jim Fullton/UNC) 1930-2200 Evening Sessions INT IP over Large Public Data Networks WG (iplpdn) (George Clapp/Ameritech) MGT Mail and Directory Management WG (madman) (Steve Hardcastle-Kille/UCL) USV Integration of Internet Information Resources WG (iiir) (Chris Weider/Merit) NOTE: Monday evening's sessions may be moved as the IETF Social has been scheduled at that time. TUESDAY, 13 July 1993 0830-0900 Continental Breakfast 0900-1200 Morning Sessions APP Conferencing Control (mmusic) (Eve Schooler/ISI and Abel Weinrib/Bellcore) INT P. Internet Protocol WG (pip) (Paul Francis/Bellcore) MGT NM Directorate (nmdir) (Marshall Rose/DBC) USV Integrated Directory Services WG (ids) (Tim Howes/UMich and Chris Weider/Merit) USV User Services WG (uswg) (Joyce K. Reynolds/ISI) Breaks Coffee available throughout morning. 1330-1530 Afternoon Sessions I APP MHS-DS WG (mhsds) (Kevin Jordan/CDC and Harald Alvestrand/SINTEF DELAB) INT IP over ATM WG (atm) (Bob Hinden/Sun) INT P. Internet Protocol WG (pip) (Paul Francis/Bellcore) USV Uniform Resource Identifiers WG (uri) (Alan Emtage/Bunyip and Jim Fullton/UNC) 1530-1600 Break (Refreshments provided) 1600-1800 Afternoon Sessions II APP MHS-DS WG (mhsds) (Kevin Jordan/CDC and Harald Alvestrand/SINTEF DELAB) INT IP over Large Public Data Networks WG (iplpdn) (George Clapp/Ameritech) INT Point-to-Point Protocol Extensions WG (pppext) (Fred Baker/ACC) * INT TCP/UDP over CLNP-addressed Networks WG (tuba) (Peter Ford/LANL and Mark Knopper/Merit) RTG Border Gateway Protocol WG (bgp) (Yakov Rekhter/IBM)* RTG OSI IDRP for IP over IP WG (ipidrp) (Sue Hares/Merit)* USV User Documents WG (userdoc2) (Ellen Hoffman/UMich and Lenore Jackson/NASA) 1930-2200 Tuesday, 13 July 1993 - Evening Sessions WEDNESDAY, 14 July 1993 0830-0900 Continental Breakfast 0900-1200 Morning Sessions APP Conferencing Control (mmusic) (Eve Schooler/ISI and Abel Weinrib/Bellcore) APP X.400 Operations WG (x400ops) (Alf Hansen/Sintef and Tony Genovese/LLNL) INT IP over Large Public Data Networks WG (iplpdn) (George Clapp/Ameritech)* INT Point-to-Point Protocol Extensions WG (pppext) (Fred Baker/ACC) * RTG Source Demand Routing Protocol (sdr) (Deborah Estrin/USC and Tony Li/cisco) USV Uniform Resource Identifiers WG (uri) (Alan Emtage/Bunyip and Jim Fullton/UNC) Breaks Coffee available throughout morning. 1330-1530 Afternoon Sessions I APP X.400 Operations WG (x400ops) (Alf Hansen/Sintef and Tony Genovese/LLNL) INT IP over ATM WG (atm) (Bob Hinden/Sun) INT Inter-Domain Multicast Routing BOF (idmr) (Tony Ballardie/UCL) MGT Chassis MIB WG (chassis) (Bob Stewart/Xyplex) SEC Privacy-Enhanced Electronic Mail WG (pem) (Steve Kent/BBN) USV Networked Information Retrieval WG (nir) (Jill Foster/UNewcastle-Upon-Tyne and George Brett/MCNC ) 1530-1600 Break (Refreshments provided) 1600-1800 Afternoon Sessions II MGT IFIP Electronic Mail Management BOF (emailmgt) (Einar Stefferud/NMA and Paul Brusil/MITRE) RTG IP Routing for Wireless/Mobile Hosts WG (mobileip) (Steve Deering/Xerox PARC) SEC Authorization and Access Control BOF (aac) (Cliff Neuman/ISI) USV Network Information Services Infrastructure WG (nisi) (April Marine/SRI and Pat Smith/Merit) 1930-2200 Wednesday, 14 July 1993 - Evening Session INT IPng Decision Process BOF (ipdecide) (Brian Carpenter/CERN and Tim Dixon/RARE) MGT IFIP Electronic Mail Management BOF (emailmgt) (Einar Stefferud/NMA and Paul Brusil/MITRE) * IPLPDN and PPPEXT will be meeting in joint session. THURSDAY, 15 July 1993 0830-0900 Continental Breakfast 0900-0930 Technical Presentations o TBD 0930-1200 Morning Sessions APP Minimal OSI Upper-Layers WG (thinosi) (Peter Furniss/Consultant) APP X.400 Operations WG (x400ops) (Alf Hansen/Sintef and Tony Genovese/LLNL) INT Point-to-Point Protocol Extensions WG (pppext) (Fred Baker/ACC) * RTG IP Routing for Wireless/Mobile Hosts WG (mobileip) (Steve Deering/Xerox PARC) USV Network Training Materials WG (trainmat) (Ellen Hoffman/Merit and Jill Foster/UNewcastle-Upon-Tyne) Breaks Coffee available throughout the morning. 1330-1530 Afternoon Sessions I MGT IFIP Electronic Mail Management BOF (emailmgt) (Einar Stefferud/NMA and Paul Brusil/MITRE) OPS Operational Area Directorate (orad) (Phill Gross/ANS and Bernhard Stockman/SUNET) RTG Multicast Extensions to OSPF WG (mospf) (Steve Deering/Xerox PARC) SEC Security Area Advisory Group (saag) (Steve Crocker/TIS) USV Internet School Networking WG (isn) (John Clement/EDUCOM, Connie Stout/TheNet and Art St. George/UNM) 1530-1600 Break (Refreshments provided) 1600-1800 Technical Presentations o TBD 1930-2200 Open Plenary and IESG NOTE: Plenary may be shifted to Friday. FRIDAY, 16 July 1993 0830-0900 Continental Breakfast 0900-1200 Technical Presentations TBD ------- End of Forwarded Message

1 0

IETF MAILING 1d: DRAFT AT-A-GLANCE: 12-16 July 1993/Amsterdam
by Marten Terpstra 12 May '93

12 May '93

Forwarded from Erik Huizer. Apologies for people who already received this. ------- Forwarded Message Date: Tue, 11 May 93 17:36:38 -0400 From: ietf-rsvp(a)cnri.reston.va.us Resent-From: Erik Huizer <Erik.Huizer(a)SURFnet.nl> Sender: ietf-announce-request(a)ietf.cnri.reston.va.us To: IETF-Announce:group list; Resent-To: ripe(a)ripe.net Subject: IETF MAILING 1d: DRAFT AT-A-GLANCE: 12-16 July 1993/Amsterdam 27th INTERNET ENGINEERING TASK FORCE Mailing Date : 5/10/93 DRAFT AT-A-GLANCE Mailing Number: 1d DATES: July 12-16, 1993 HOST(S): Erik Huizer/SURFnet MEETING SITE: RAI Congress Centre Europaplein NL-1078 GZ Amsterdam Phone: +31.(0) 20.5491212 HOTEL: Refer to IETF MAILING 1b for Hotel information. Also available via ftp: 0mtg-hotel-ams.txt NEWCOMER'S Sunday, 11 July, 1993 ORIENTATION: 16:30pm - 17:30 Location: TBD PRE-REGISTRATION: Sunday, 11 July, 1993 18:00 - 20:00 (reception during) RAI Congress Centre Location: TBD REGISTRATION: Monday - Friday, 12-16, July 1993 08:00 - 18:00 RAI Congress Centre Location: TBD ATTENDANCE FEE: PAYMENT BY: Credit Card or Check $220.00 if registered AFTER 11 June 1993 CAR RENTAL: Don't rent a car. Public transportation is very easy. Cabs work too. AIRPORT: Schiphol Airport ------- End of Forwarded Message

1 0

IETF MAILING 1c: IETF RSVP FORM: 12-16, July 1993/Amsterdam
by Marten Terpstra 12 May '93

12 May '93

Forwarded from Erik Huizer. Apologies for people who already received this. ------- Forwarded Message Date: Tue, 11 May 93 17:20:16 -0400 From: ietf-rsvp(a)cnri.reston.va.us Resent-From: Erik Huizer <Erik.Huizer(a)SURFnet.nl> Sender: ietf-announce-request(a)ietf.cnri.reston.va.us To: IETF-Announce:group list; Resent-To: ripe(a)ripe.net Subject: IETF MAILING 1c: IETF RSVP FORM: 12-16, July 1993/Amsterdam REGISTRATION FORM 27th Internet Engineering Task Force - Page 1 of 2 12-16, July 1993 Amsterdam, The Netherlands Please print or type: Name (Mr/Dr/Ms)__________________________________________________________ Title____________________________________________________________________ Organization_____________________________________________________________ Address__________________________________________________________________ _________________________________________________________________________ City_____________________________State_____________Postal Code___________ Country__________________________________________________________________ Telephone______________________________Fax_______________________________ Email____________________________________________________________________ Do you plan to attend the Sunday, 11 July NEWCOMER'S ORIENTATION at 16:30? YES___ NO___ Do you plan to attend the Sunday, 11 July reception at 18:00? YES___ NO___ $200.00 ($200.00 + $20.00 late fee) Registration postmarked after Friday, 11 June 1993. Method of payment: ___AMEX ___VISA ___MC ___Diners ___Check (U.S. dollars, drawn on a U.S. Bank), payable to: Corporation for National Research Initiatives Account No.____________________________ Expiration Date__________________ Cardholder Name__________________________________________________________ Cardholder Signature_____________________________________________________ Registration Forms can be sent via electronic mail, facsimile, or postal mail: Electronic: ietf-rsvp(a)cnri.reston.va.us Facsimile: +1-703-620-0913 Postal: Corporation for National Research Initiatives Accounting Department - 27th IETF Meeting 1895 Preston White Drive, Suite 100 Reston, VA 22091-5434 USA REGISTRATION FORM 27th Internet Engineering Task Force - Page 2 of 2 12-16, July 1993 Amsterdam, The Netherlands IMPORTANT: 1. Payment MAY, but does NOT have to, accompany the Form. 2. Register ONE person per form. Substitutions are NOT allowed. 3. Include a completed Registration Form with payment. 4. Purchase orders are NOT accepted. 5. DD Form 1556 IS accepted. 6. We CANNOT invoice for payment. 7. Registration Forms will be accepted via electronic mail and facsimile until 13:00 ET on Wednesday, 7 July, 1993. 8. Requests for refunds must be received by Wednesday, 7 July, 1993. 9. Refund policy: Refunds are subject to a $20.00 service charge. Late fees will not be refunded. 10. Your registration fee includes a copy of the Meeting's Proceedings, Sunday evening reception (cash bar), and a daily continental breakfast and coffee breaks. For additional information or assistance, please contact +1-703-620-8990, +1-703-620-0913 (Fax) or ietf-rsvp(a)cnri.reston.va.us. Direct all inquiries to: 27th IETF Meeting - Amsterdam, The Netherlands. ------- End of Forwarded Message

1 0

IETF MAILING 1a: IETF, 12-16, July 1993/Amsterdam
by Marten Terpstra 12 May '93

12 May '93

Forwarded from Erik Huizer. Apologies for people who already received this. ------- Forwarded Message Date: Tue, 11 May 93 17:05:48 -0400 From: ietf-rsvp(a)cnri.reston.va.us Resent-From: Erik Huizer <Erik.Huizer(a)SURFnet.nl> Sender: ietf-announce-request(a)ietf.cnri.reston.va.us To: IETF-Announce:group list; Resent-To: ripe(a)ripe.net Subject: IETF MAILING 1a: IETF, 12-16, July 1993/Amsterdam Dear IETFers: Following this message (1a) you will receive four more, the contents of which follow: IETF MAILING 1b: HOTEL RESERVATION FORM. This form must be returned via fax to the RAI HOTEL SERVICE by May 31st in order to guarantee a room. DO NOT SEND THIS FORM TO THE IETF SECRETARIAT. IETF MAILING 1c: IETF RSVP FORM. Payment DOES NOT need to accompany the RSVP Form, but the Form must be received by June 11th in order to guarantee the lower fee. We strongly encourage you to register immediately, even if you know payment will be delayed for a bit. IETF MAILING 1d: DRAFT AT-A-GLANCE. This is still in draft form. IETF MAILING 1e: DRAFT AGENDA. Please keep in mind that this is only a draft and is subject to frequent changes. The IETF Social is scheduled for Monday evening. The Local Host will be announcing that shortly. NOTE: WE CANNOT STRESS THIS ENOUGH. Though we'd prefer to have payment of the meeting fee as soon as possible, we definitely want immediate notification that you are planning on coming. So even though you know that payment will be delayed for one reason or another, SEND THE RSVP FORM IN ANYWAY. Thank You, Megan ------- End of Forwarded Message

1 0

IETF MAILING 1b: Hotel Reservation Form: 12-16, July 1993/Amsterdam
by Marten Terpstra 12 May '93

12 May '93

Forwarded from Erik Huizer. Apologies for people who already received this. ------- Forwarded Message Date: Tue, 11 May 93 17:17:10 -0400 From: ietf-rsvp(a)cnri.reston.va.us Resent-From: Erik Huizer <Erik.Huizer(a)SURFnet.nl> Sender: ietf-announce-request(a)ietf.cnri.reston.va.us To: IETF-Announce:group list; Resent-To: ripe(a)ripe.net Subject: IETF MAILING 1b: Hotel Reservation Form: 12-16, July 1993/Amsterdam Dear IETF'ers: July 12-16, 1993 is the 27th Internet Engineering Task Force which will be held in Amsterdam at the RAI Congress Centre. The RAI has it's own Hotel Service which was able to negotiate lower Hotel rates than I was able to. To obtain these lower rates you MUST register through the RAI Hotel Service. They have provided the form below, which I have slightly modified. Please fill out the form according to the instructions and fax or mail it to the RAI. DO NOT RETURN YOUR FORM TO THE SECRETARIAT. I have already begun scheduling working groups for the Amsterdam IETF. A Draft Agenda is available in the remote directories under 0mtg-agenda.ams.txt Megan P.S. According to our local host :>> In Europe there are only two sorts of rooms: >> SINGLE - contains one bed of aprox. 3 feet wide >> DOUBLE - contains either two beds of 3 feet each, or 1 bed of min. 6 feet >> >> (We don't do Queens or King Size) HOTEL BOOKING FORM (page 1 of 2) - 29th IETF, 12-16, July 1993 - (Please Print) Return this HOTEL BOOKING FORM before May 31, 1993 to: RAI HOTEL SERVICE Europaplein, NL 1078 GZ AMSTERDAM. Phone: +31 (0) 205491927 Fax : +31 (0) 206462840 ***After May 31st***, hotel accommodation cannot be guaranteed, though requests will still be accepted. Surname_____________________________________________ Initials___________ Organization____________________________________________________________ Address_________________________________________________________________ _________________________________________________________________ Postal Code and City____________________________________________________ Country_________________________________________________________________ Telephone______________________________ Facsimile_______________________ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Date of Arrival in Amsterdam_____________ Date of Departure____________ Single Room_____________ Double Room_____________ Preferred Hotel_________________________________ (see page two) "I prefer the following hotel which is not listed on the HOTEL BOOKING FORM." Hotel Name:_______________________________________ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< DEPOSIT: A guarantee via credit card, a cheque* made out to the RAI HOTEL SERVICE, or a deposit of Dfl. 250 per room is required. After receipt of your payment/credit card details, a voucher will be forwarded to you. Payment must be made in Dutch Guilders. All costs to transmitter's charge (approx. Dfl. 25 per transfer) NO ROOMS CAN BE CONFIRMED UNTIL YOUR HOTEL DEPOSIT/CREDIT CARD GUARANTEE HAS BEEN RECEIVED!!!!! AMEX____ Diners____ Master____ Visa____ Eurocard ____ Access____ Account No._____________________________ Expiration Date_________________ Cardholder Name__________________________________________________________ Cardholder Signature_____________________________________________________ ___Remitted by enclosed cheque payable to RAI HOTEL SERVICE (* personal cheques cannot be accepted.) The deposit paid will be deductible from your hotel bill upon presentation of this voucher at the reception desk of the hotel. ___Remitted to RAI HOTEL SERVICE account No. 54.96.42.528 with the ABN-AMRO Bank at Amsterdam, the Netherlands, IETF93, Mr./Ms.____________________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< HOTEL BOOKING FORM (page 2 of 2) - 29th IETF, 12-16, July 1993 Hotel accommodation at reduced rates can be reserved in the following hotels: Hotel Name Stars Single Double Bkfst Incl. - -------------------------------------------------------- Holiday Inn (1) 5 Dfl. 210 Dfl. 255 No Novotel (1) 4 Dfl. 210 Dfl. 240 Yes Altea (2) 3 Dfl. 220 Dfl. 220 Yes (1) Hotel located within walking distance of the RAI. (2) Hotel located near the RAI. CANCELLATION: Notification of cancellation must be sent in writing, (postal mail or facsimile) no later than 72 hours (three days) prior to originally scheduled arrival time. Notification after this time will automatically result in a charge of Dfl. 250. REFUNDS : Refunds, minus administration costs of Dfl. 50, will be dealt with after the conference. ------- End of Forwarded Message

1 0

Interop Europe Volunteers wanted
by Marten Terpstra 11 May '93

11 May '93

------- Forwarded Message Date: 7 May 1993 19:13:25 +0100 From: "Claude Kiennert" <ckiennert(a)interop.com> Sender: listserv(a)spitfire.interop.com To: noceur93(a)spitfire.interop.com Subject: Volunteers Subject: Time:18:26 OFFICE MEMO Volunteers Date:7/05/93 As I told you during our first meeting, we are looking for volunteers to help us to build the network in the warehouse during the hotstaging and, mainly, in the CNIT to install, tear-down and help us to operate the network during the show. A working knowledge of the English language is necessary. I would appreciate if you could propagate this information around you. You can communicate them my name, phone number (+33 1 46 39 56 71) and email address (ckiennert(a)interop.com) We have a special mailing list for the volunteers. The mail address is: voleur93(a)spitfire.interop.com Thanks for your help Claude. ------- End of Forwarded Message

1 0

Document Announcement: Quarterly Report 4
by Anne Lord 07 May '93

07 May '93

New/Revised RIPE Document Announcement -------------------------------------- A new document below ripe-87 is now available from the RIPE document store. Ref: ripe-87 Title: RIPE NCC Quarterly Report, Issue 4, March 1993 Author: NCC Date: 6 May 1993 Format: PS=697094 TXT=68517 Short content description ------------------------- The fourth Quarterly Report describing the activities of the RIPE NCC from January 1st 1993 until end March 1993. 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-87.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 info.ripe.net". This is a menu driven service which 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 access methods for systems administrators: 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./local/spool/www/default.html 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mail-server(a)ripe.net" Content-Type: text/plain SEND <ripe-87.txt> --OtherAccess Content-Type: Message/External-body; name="<ripe-87.txt"; site="ftp.ripe.net"; access-type="anon-ftp"; directory="ripe-docs/docs" Content-Type: text/plain --OtherAccess-- --NextPart--

1 0