October 1994 - ripe-list - mailman.ripe.net

mailing list on trouble tickets
by Stephan.Biesbroeck＠belnet.be 27 Oct '94

27 Oct '94

Hello, At the last RIPE meeting in Lisbon we had a BOF on Trouble Tickets and one of the decisions was to have a mailing list to discuss further a common format for Trouble Tickets and to review ripe-063 (I hope to have the number right). This mailing-list is now created : tts-people(a)ripe.net So anyone who wants to join the discussion on Trouble Ticket (Systems) can join this list by sending a mail to majordomo(a)ripe.net with "subscribe tts-people" in the body. Regards, Stephan -- 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

1 0

RIPE meeting DRAFT minutes: ripe-m-19.{txt,ps}
by RIPE NCC Document Annoucement Service 20 Oct '94

20 Oct '94

Short content description ------------------------- These are the draft minutes from the 19th RIPE meeting in Lisbon. Sincere aplogies for the late issue of this document. Thanks to everyone who helped with supplying draft text. As usual, comments are very welcome and can be sent to me at <anne(a)ripe.net>. thanks, Anne 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/minutes/" followed by the command "get filename". The relevant filenames for this document are: ripe-m-19.txt for the ASCII version ripe-m-19.ps for the PostScript version 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 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". MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the RIPE document by FTP or mail server. SEND ripe/minutes/ripe-m-19.txt

1 0

PRIDE Courses in November
by Daniel Karrenberg 17 Oct '94

17 Oct '94

There are stll a few places left for the Amsterdam and London courses! Announcing the PRIDE courses November 1995 ------------------------------------------ This is a preliminary announcement for the forthcoming one-day PRIDE courses in November 1995. The course will be based around the second edition of the PRIDE guide. The courses are aimed at Internet Service Providers with the following benefits: o Gain a better understanding of routing policy techniques. o Understanding of the concept of a Routing Registry. o Learn how to use/maintain routing policy information in the routing registry. o Learn how to use the PRIDE tools to diagnose and check routing policy problems. o Give Service Providers a chance to feedback ideas on the Routing Registry and the tools that are needed now and in the future. This course will be based on the revised RIPE Routing Registry (ripe-118). It will also give participants a firsthand look at newest developments around the routing registry and associated tools. Participant feedback will be appreciated. For a rough overview about the material covered, please refer to ftp://ftp.ripe.net/pride/docs/guide-1.0.ps.tar.Z. Note that this document refers to the old style RR (ripe-81). The course will be based on the new style RR (ripe-181). This course will be offered at the following locations and dates: Amsterdam November 7th Monday London November 14th Monday The course will be funded by the PRIDE project and thus be free of charge. We might even throw in a free lunch ;-). Space is limited to a maximum of 12 participants per course and reservations will be taken on a first-come-first-served basis. The definite details will be announced to those who have reserved by October 14th. Attendees from or sponsored by the PRIDE funding organisations will be given preference. If you plan to attend this course please fill in the form below and return to "pride-rsvp(a)ripe.net". %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL (remember this is on list and badge) e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Organisation/Institution # ORG [ ] 3) Your e-mail address # EMAIL [ ] 4) Country code of organisation e.g. IT FR # CTRY [ ] 5) Location you wish to attend at e.g. Amsterdam London Pisa Vienna Washington # LOC [ ] 6) Are you sponsored by a PRIDE funding partner Y yes N no (if in doubt you are probably not) # SPONS [ ] %END

1 0

Opening: RIPE NCC SENIOR TECHNICAL STAFF (DEPUTY MANAGER)
by Daniel Karrenberg 13 Oct '94

13 Oct '94

Dear colleagues, please give this appropriate distribution. Thank you Regards Daniel Karrenberg RIPE NCC Manager ----- There currently is an opening at the RIPE NCC for a SENIOR TECHNICAL STAFF (DEPUTY MANAGER) The position provides an excellent opportunity to work at the very heart of the European Internet industry. The person filling this position will report directly to the NCC manager and be in charge of a substantial number of NCC activities. He or she will also be acting manager of the NCC in the absence of the NCC manager. Since the NCC is quite small, he or she will also execute a part of the actual work. Duties The general duties of the RIPE NCC senior technical staff: - to execute some of the NCC activities - take responsibility for part of the activities - to supervise the technical and administrative staff - propose new activities, where needed, to the RIPE NCC Manager - represent the NCC to other organisations The specific duties of this position are: - perform Internet Registry related tasks, in particular those requiring in-depth technical review and difficult decisions - support the NCC manager in generating NCC reports - support the NCC manager in generating the yearly Activity Plans - participate proactively in planning the NCC infrastructure The other specific NCC activities which the senior technical staff member will have to execute and/or take responsibility for will be determined according to her preferences and the need at the time. Please refer to the RIPE NCC Activity Plan (ripe-110). Qualifications Essential - management experience - good communication skills - solid background in Internet technology - good knowledge of written and spoken English - experience with Internet service provision - familiarity with the Unix and X-Windows environments Desirable - work experience in an international environment - experience in the RIPE community - knowledge of spoken Dutch Time Frame The position is open immediately and will be filled as soon as possible but no later than January 1995. R I P E N C C The RIPE Network Coordination Centre is funded by all European Internet service providers. Its task is to ensure the necessary administrative and technical coordination to allow the operation of a pan-European IP network. RIPE does not operate a network of its own. A detailed description of these activities can be found in the RIPE NCC Activity Plan ftp://ftp.ripe.net/ripe/docs/ripe-110.txt. The latest report on those activities can be found in ftp://ftp.ripe.net/ripe/docs/ripe-116.txt. The RIPE NCC is currently staffed by 4 full time employees: one NCC manager two NCC technical staff one NCC administrative staff Another engineer (technical staff) is expected to join in November. Further growth is expected in 1995. The RARE association provides the legal and financial framework for the NCC. NCC staff are employed by RARE. Further information about the RIPE and the RIPE NCC can be found at: http://www.ripe.net/ or gopher://gopher.ripe.net/ or ftp://ftp.ripe.net/ or telnet://telnet.ripe.net/ Conditions RIPE NCC personnel will be employed under the standard RARE association employment conditions. The salary will depend on qualifications and experience. Costs of relocation to the Netherlands will be met. The appointment will be for one year with possible extension. Location The RIPE NCC is currently located at the Scientific Center Watergraafsmeer (WCW) in Amsterdam. Relocation of the office to the center of Amsterdam is currently under consideration. Further Information For further information about this position please contact: Daniel Karrenberg RIPE NCC Manager Kruislaan 409 NL-1098 SJ Amsterdam Netherlands Tel.: +31 20 592 5065 <Daniel.Karrenberg(a)ripe.net> How to Apply Applications, including a curriculum vitae and references should be submitted in confidence to: Dr. T. Kalin RARE Secretary General Ref: NCC Staff Application Singel 466 - 468 NL-1017 AW Amsterdam Netherlands <kalin(a)rare.nl> Applications have to be received before November 1st 1994.

1 0

New Document available: ripe-124
by RIPE NCC Document Annoucement Service 07 Oct '94

07 Oct '94

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-124 Title: European Internet Network Number Application Form Title: and Supporting Notes Author: RIPE NCC Date: 7 October 1994 Format: PS=76937 TXT=34471 bytes Obsoletes: ripe-115 Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- Update of ripe-115 document. Following changes made: - stressed "last resort" only function of these registries - please consider rfc1597 if not connecting in foreseeable future - send in network plans if first time applying for more than 2 netnumbers and also if applying for more space in addition to that already held. 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/" followed by the command "get filename". The relevant filenames for this document are: ripe-124.txt for the ASCII version ripe-124.ps for the PostScript version 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 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 RIPE document by FTP or mail server. SEND ripe/docs/ripe-124.txt

1 0

New Document available: ripe-182
by RIPE NCC Document Annoucement Service 06 Oct '94

06 Oct '94

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-182 Title: Experimental Objects and attributes for the Routing Registry Author: Elise Gerich, Laurent Joncheray Date: 3 October 1994 Format: PS=8865 TXT=2153 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This short document acts a place-holder for future extensions to the routing registry representation language as detailed in ripe-181. It gives some detail of a couple of extensions already proposed. It is expected that this document will be updated over time. 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/" followed by the command "get filename". The relevant filenames for this document are: ripe-182.txt for the ASCII version ripe-182.ps for the PostScript version 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 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 RIPE document by FTP or mail server. SEND ripe/docs/ripe-182.txt

1 0

New Document available: ripe-181
by RIPE NCC Document Annoucement Service 06 Oct '94

06 Oct '94

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-181 Title: Representation of IP Routing Policies in a Routing Registry Author: Tony Bates, Elise Gerich, Laurent Joncheray, Jean-Michel Jouanigot, Daniel Karrenberg, Marten Terpstra, Jessica Yu Date: 3 October 1994 Format: PS=217237 TXT=124919 Obsoletes: ripe-081 Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This document is an update to ripe-081 and is also known as ripe-81++. This details a number of changes to the routing registry syntax and objects. 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/" followed by the command "get filename". The relevant filenames for this document are: ripe-181.txt for the ASCII version ripe-181.ps for the PostScript version 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 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 RIPE document by FTP or mail server. SEND ripe/docs/ripe-181.txt

1 0

New Document available: ripe-123
by RIPE NCC Document Annoucement Service 06 Oct '94

06 Oct '94

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-123 Title: RIPE Database Transition Plan Author: Tony Bates, Daniel Karrenberg, Marten Terpstra Date: 3 October 1994 Format: PS=70350 TXT=35083 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This document guves full details of the transition plan for the new proposed RIPE database and routing registry objects. Please make sure you are aware of the details in the document including the actual dates. 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/" followed by the command "get filename". The relevant filenames for this document are: ripe-123.txt for the ASCII version ripe-123.ps for the PostScript version 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 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 RIPE document by FTP or mail server. SEND ripe/docs/ripe-123.txt

1 0

New Document available: ripe-122
by RIPE NCC Document Annoucement Service 06 Oct '94

06 Oct '94

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-122 Title: Specifying an `Internet Router' in the Routing Registry Author: Tony Bates Date: 3 October 1994 Format: PS=37970 TXT=14242 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This document specifies a simple object for detailing Internet routers with the RIPE routing registry. 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/" followed by the command "get filename". The relevant filenames for this document are: ripe-122.txt for the ASCII version ripe-122.ps for the PostScript version 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 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 RIPE document by FTP or mail server. SEND ripe/docs/ripe-122.txt

1 0

New Document available: ripe-121
by RIPE NCC Document Annoucement Service 06 Oct '94

06 Oct '94

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-121 Title: Support for Classless Internet Addresses in the RIPE Database Author: Tony Bates, Daniel Karrenberg, Marten Terpstra Date: 3 October 1994 Format: PS=36698 TXT=14177 Obsoletes: Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This document details the added support for classless Internet addresses in the RIPE database. It details the change in representation and handling of database objects. 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/" followed by the command "get filename". The relevant filenames for this document are: ripe-121.txt for the ASCII version ripe-121.ps for the PostScript version 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 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 RIPE document by FTP or mail server. SEND ripe/docs/ripe-121.txt

1 0