- ripe-list - mailman.ripe.net

New Document available: ripe-113
by RIPE NCC Document Annoucement Service 12 May '94

12 May '94

New/Revised RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Ref: ripe-113 Title: RIPE NCC Annual Report 1993 Author: Daniel Karrenberg, RIPE NCC Date: 1 May 1994 Format: PS=29732, TXT=7653 Obsoleted by: Updates: Updated by: Old: Short content description ------------------------- This is the very short (3 pages) report of RIPE NCC activities in 1993 including an overview of the finalised expenditure accounts. 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-113.txt for the ASCII version ripe-113.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-113.txt

1 0

Re: RIPE 17 actions status report - MAY reminder
by farrache＠ccpnxt5.in2p3.fr 11 May '94

11 May '94

Anne , I am very surprise to see the action 17.26 in the done field !!! >Action: 17.26 Rob Blokzijl, NCC >create new mailing list to enable reorganisation of RIPE discussions to >continue and announce to the ripe-list. I have never seen any announcement . Gilles

1 0

Announcement of new mailing list
by RIPE NCC Staff 11 May '94

11 May '94

A new mailing list has been created to facilitate discussions on the reorganisation of RIPE. This new mailing list is called : <new-ripe(a)ripe.net> To subscribe to the list, send a mail to <majordomo(a)ripe.net> with the body text : subscribe <new-ripe(a)ripe.net> [<your email address>] Due to a minor oversight (hmph ..cough) the announcement mail *was* sent out - just not to the right people..so apologies to everyone who didnt receive the announcement. Anne

1 0

RIPE 18 - Agenda
by k13＠nikhef.nl 11 May '94

11 May '94

18th RIPE Meeting ----------------- Amsterdam, May 16-18 1994 AGENDA ------ (Draft) ----- M O N D A Y 16 M A Y ------ -------------- 14:00 h -------------- 1. Opening 15 min o welcome o apologies o dinner o logistics o agenda 2. Minutes RIPE-17 15 min o approval of the minutes 3. Actions RIPE-17 15 min o review of the Action List 4. RIPE NCC Report 30 min o technical report (D.Karrenberg) o staffing (D.Karrenberg) ----- break 15:30 h - 16:00 h ------------------------------------------- 5. Joint Projects - Status and Progress 15 min o PRIDE (D.Karrenberg) 6. The Merit Routing Registry (E.Gerich) 30 min 7. RIPE NCC: Finance & Management (R.Blokzijl) 15 min 8. RIPE: Restructuring the Organisation 15 min o Introduction (R.Blokzijl) ----- E N D O F D A Y 1 ------------------------ 18:00 h -------------- ----- T U E S D A Y 17 M A Y -------------------- 09:00 h -------------- Parallel Sessions: o RIPE-81++ and related issues ----- break 10:30 h - 11:00 h ------------------------------------------- o RIPE-81++ and related issues (continued) ----- lunch 12:30 h - 14:00 h ------------------------------------------- o Data Base Working Group o European Engineering and Planning Group ----- break 15:30 h - 16:00 h ------------------------------------------- o Domain Name System Working Group o Local Internet Registries Working Group ----- E N D O F D A Y 2 ------------------------ 18:00 h -------------- ----- W E D N E S D A Y 18 ---------------------- 09:00 H -------------- Parallel Sessions: o RIPE Restructuring BOF ----- break 10:30 h - 11:00 h ------------------------------------------- Parallel Sessions o Connectivity Working Group o MBONE ----- lunch 12:30 h - 14:00 h ------------------------------------------- 9. Report on the RARE ATM Working Group (V.Reijs) 30 min 10. Reports from the Working Groups 60 min 11. Next Meetings 15 min o RIPE 19: Lisbon, 12-14 September 1994 o RIPE 20: Somewhere, January 1995 o RIPE 21: Somewhere, Sometime 12. A.o.b. 13. Closing ----- E N D O F D A Y 3 ------------------------ 16:00 h --------------

1 0

RIPE 17 actions status report - MAY reminder
by Anne Lord 11 May '94

11 May '94

Last time you will see this before the meeting ! If anyone has completed an action which is against their name, please let me know. Completed actions that I know about, I have already moved into the "done" column. Thanks, Anne --------- Action List - RIPE 17 ===================== 1. Done Action: 16.21 Milan Sterba, Anne Lord Produce the umbrella document for the CDS. Action: 16.22 Milan Sterba (mid March) Solicit contributions to the CDS. Action: 16.23 Milan Sterba, NCC Create the cds-editor(a)ripe.net alias and establish procedures to integrate new CDS contributions and maps to the CDS. Action: 17.2 Daniel Karrenberg Propose (guarded) RIPE database object representing a local registry, mail to local-ir and db wg. Action: 17.5 Daniel Karrenberg Ask IANA for a default range of AS numbers (65530-65535 or so) in the line of the network-10 proposal. Reply was negative. Action: 17.6 NCC To organise local-ir workshop for the 18th RIPE meeting. Action: 17.9 NCC To update and re-circulate the Guarded Fields proposal and then go ahead with the implementation. Action: 17.10 NCC To investigate and propose facilities for a "template-mode" to support the maintaining database objects. Action: 17.12 Henk Steenman (notified 17.02.94) To update and re-circulate the "dom-prefix:" proposal. Action: 17.13 NCC To implement the CLNS Routing Object. Action: 17.15 NCC Propose and implement a mechanism to check the current state of the database with regard to garbage-collection and merging of guarding values. Comment: overtaken by events - new proposal submitted. Action: 17.16 NCC Propose and implement a mechanism to properly keep track of individual updates of objects and automatic merge/modification operations. Action: 17.17 Bernhard Stockman Draft a new version of the EEPG Terms of Reference and distribute this on the mailing list ASAP. Action: 17.21 NCC Announce "Support of Guarded attributes in the RIPE database" as a RIPE document. Action: 17.22 RIPE NCC To implement the AS macros. Action: 17.23 Daniel Karrenberg Write a proposal on including an "advice" tag in the AS object. Action: 17.26 Rob Blokzijl, NCC create new mailing list to enable reorganisation of RIPE discussions to continue and announce to the ripe-list. 2. Open Action: 15.10 Daniel Karrenberg To propose new tags "created" and "assigned" to the database working group for consideration - pending. Action: 16.6 Daniel Karrenberg Why return unused IP address space and be a good network citizen. Daniel to find volunteer to continue the work. Action: 16.17 Jean-Michel Jouanigot To coordinate the transition from ripe-060 to ripe-081 format for routing description. Action: 16.18 NCC Try to actually get the synchronisation of the various database going, using the recently agreed DB Exchange Format. Action is pending and dependant on the NIC handle. Action:17.1 Glenn Kowack Volunteered to write a paper for discussion which would focus on a future funding model for the RIPE NCC. Action: 17.3 Wilfried Woeber Propose a representation address space assignment/reservation status. Action: 17.4 Wilfried Woeber Propose a graphical representation address space assignment/reservation status. Action: 17.7 Wilfried Woeber, NCC To produce the necessary documentation for the new DB software. Action: 17.8 NCC To update and re-circulate the RIPE-Handle proposal and then go ahead with the implementation. Action: 17.11 NCC Investigate and propose a syntax-checking facility for the new database software. Action: 17.14 Francis Dupont DNS group to review the Domain Object and come up with either a recommendation for retirement or with an updated functionality. Action: 17.18 Bernhard Stockman Draft a new version of the EEPG Workplan and distribute this on the EEPG mailing list ASAP. Action: 17.19 Erik-Jan Bos To coordinate work relating to the new RIPE Mbone working group for the next RIPE meeting. Action: 17.20 Oleg Tabarovsky To collect data on external lines and restrictions applying to each line that will form part of the Russian back- bone. Send details to <oleg(a)ussr.eu.net>. Action: 17.24 Laurent Joncheray To circulate a paper to routing wg on including the AS Path concept in ripe-081. Action: 17.25 NCC, Juliana Tamorri To make FAQ on CIDR by Juliana available in the RIPE document store. Action: 17.27 ripe-chairs Summarise in a paper discussions on RIPE re-org and publish before next meeting.

1 0

Interop Engineers Conference - Announcement
by k13＠nikhef.nl 11 May '94

11 May '94

First Call for Papers ------------------- Engineers Conference at NetWorld+Interop 94 Paris --------------------------------------------------------------------- Interop Company is soliciting technical papers for an Engineers Conference to be held as part of the upcoming NetWorld+Interop 94 Paris event, October 24 - 28, 1994, in Paris. The Engineers Conference, which will be held on Thursday/Friday October 27 - 28, is a two-day focused event offering approaches and solutions to practical systems and software design for networking. All participants in the conference will be able to attend the NetWorld+Interop 94, Paris exhibition, which will run from October 26 - 28. FORMAT The conference will feature the presentation of original papers which will have been selected by a review committee. All accepted papers will be published in Conference Proceedings. Accepted papers must be presented by original authors during the 2-day conference. Conference sessions typically will be 90 minutes long and will present three papers of 20 to 30 minutes duration. The Engineer's Conference will concentrate on engineering design problems in three areas: High Speed Networking, Internetworking, and Multimedia. This conference seeks to bring together research scholars, engineers, and vendors to address pragmatic engineering issues in the field of networking and distributed systems interoperability. It is an excellent forum for Engineers and Researchers to publish papers and to be brought up to date on solutions to today's engineering related problems. Papers are solicited in the following areas: * High Speed Networking: ATM, Fast Ethernet, SDH, FDDI-II, HIPPI, SMDS, Frame Relay, Broadband ISDN, etc. * Internetworking: Addressing Schemes, Routing Protocols, Support of Mobility, Design of Bridges, Routers, and Multiprotocol Brouters, Application Gateways etc. * Multimedia Networking: Multimedia technologies, Multimedia inteoperability, Packet Video and voice, Multimedia Mail and Conferencing, Tele-Presence, Virtual Reality, etc. SUBMISSION GUIDELINES Interested authors are invited to submit an abstract (up to 600 words) clearly describing the problem and the solution offered. All abstracts will be reviewed and authors will be notified for acceptance or rejection of the abstract. Authors of accepted abstracts must submit the paper before the last date. These papers are reviewed by a technical committee for technical merit of the paper before final acceptance. Please note the important dates for abstract and paper submission. All abstracts must contain the authors name, address, telephone number, Fax number and e-mail address (if available). Please send your abstract to: Interop Europe 14 Place Marie-Jeanne Bassot, 92593 Levallois Peret Cedex, Paris, France Attention: Engineer's Conference or e-mail it (in ASCII or PostScript) to: Paris_Engineer(a)interop.com ** E-mail is preferred. ** =================== = Important Dates = =================== Abstracts due: 3 Jun, 1994 Notification to authors: 24 Jun, 1994 Draft paper due: 22 Jul, 1994 Feedback to authors: 5 Aug, 1994 Camera ready copy due: 9 Sep, 1994 Final camera reader papers must not exceed 10 A4 pages.

1 0

IETF Report Abstract
by Jill.Foster＠newcastle.ac.uk 11 May '94

11 May '94

IETF - Seattle: March 28th - April 1st, 1994 ============================================ Trip Report: Jill Foster - Newcastle University, UK RARE Information Services and User Support Project Development Officer and Mailbase Manager Abstract ======== The IETF (Internet Engineering Task Force) met for a week in Seattle. The report deals mainly with the areas of User Support, Networked Information Retrieval and Directory Services, although reports of some of the plenary sessions are also included. Security was a major theme of the meeting. This report is stored on the UK Mailbase Server. file: pub/lists/wg-isus/files/ietf.03.94 It is also available via gopher and WWW from mailbase.ac.uk To retrieve a copy via email, send a message to: Mailbase(a)mailbase.ac.uk with the following command in the body of the message: send wg-isus ietf.03.94 -- Jill Foster

1 0

Some thoughts on the "Restructuring of RIPE"
by Willem van der Scheun 11 May '94

11 May '94

At the last RIPE meeting we had a BOF on the structure of RIPE. It was stated there that further discussions would be held over the mailing list. Up till now this subject has been very quiet and the next meeting is in 1 1/2 week. Therefore I would like to share with you some of my personal thoughts on this subject. Having attended the last IEPG and IETF meeting in Seattle I saw some very nice parrallels with the discussion at the RIPE BOF. I will come to these in thes message. In the oldest RIPE document, ripe-001, "Terms of reference", I see, i.a. the following bullets: - RIPE acts as a forum for the exchange of technical information and the creation of expertise on IP networking. - RIPE promotes and coordinates interconnection of IP networks within Europe and to other continents. - RIPE establishes agreement on common network management practices and the operational management of the interconnected networks. - RIPE serves as a focal point for other common activities of the participants related to IP networking. This document is dated "29 November 1989", so it is 3 1/2 years old, which is ofcourse very, very old in networking land. Never the less these points, especially the first and the last one, seem to me as valid as they were at the time of writing. If I compare this with the recently established IEPG charter, I see a striking resemblance: IEPG CHARTER Internet Engineering and Planning Group Domain of Activity The Internet Engineering and Planning Group (IEPG) is a group principally comprised of Internet Service Operators. Goal The common objective of the group is to promote a technically coordinated operational environment of the Global Internet. Activities The activities of the IEPG will be within the following areas: - To facilitate the operations and management of Global Internet services, - To promote the introduction of new Internet services within the Global Internet, and - Liaison with related Internet Operations groups and liaison with technical development groups. Both documents talk about operations and coordination. Also I think the "feeling" behind both is about the same. This gets me to my first point: RIPE as a body still has the same reason to exist as it had when it started. Perhaps some wording needs to be changed, removing explicit reference to IP. To me the two focal points in the terms of reference and in the work that is being done within RIPE are "coordination" and "information exchange". Another absolutely key word is "technical". RIPE (and I think IEPG and other bodies with about the same goal) are technical fora and not meant for political discussions. This does not preclude "politicians" to attend RIPE meetings and being active in them. I think it is very worthwile they do, as RIPE is the forum to discuss the technical implications and (im)possibilities of the things the politicians come up with. But these discussions should be on a technical level and open minded. Coming back to the focal points I mentioned, "coordination" and "information exchange", I think I am right in presuming "information exchange" is a sine qua non for "coordination". Since RIPE started the European Internet has changed quite dramatically, in the sense that in the old days we had more or less a bunch of international lines owned by the two parties at both ends of the line (some times in collaboration with more parties), that were - slightly exagerated - randomly put all over Europe. Nowadays there are a number of European Internet Service Providers that have brought at least some structure in the chaos. The point I want to make is that the level or type of coordination related to getting a Pan-European Internet Structure has also become different. This means that we'll see a more compex level of interaction at RIPE meetings because we see two types af attendants, one from the "national" or "regional" level, and one from the "european service provider" level. It is the service providers who have to do most of the coordination and ofcourse RIPE is the perfect forum for this because it is here that all the best and brightest in (at least) European networking are assembled. Let me try to define some areas where coordination may be needed. This list is by no means meant to be complete. Some of these items are taken from the Opera BOF at the Seattle IETF (BTW I am very fond of opera!) - routing - CIDR - routing registries - route servers - infrastructure - exchange points - transatlantic connectivity - Central and Eastern European developments - registries - Address allocation - routing - databases - "virtual" networks/systems - Mbone - Information systems like Gopher, WWW - Directory services lik DNS, X.500 - security - CERT - Security issues related to IP - Security issues related to routing - network management - trouble ticket hand-off - reporting The above mentioned areas could be the base for the structure of RIPE. I think "area" is a better wording for these groups than "working group", because the main goal is coordination and information exchange and not so much "work" in the sense that there are clearly defined deliverables. Of course within a area some documents could be needed and for the writing of such a document a working group could be formed. Also other reasons for working groups can be thought off. The point is that working groups are supposed to have a limited TTL and a clear deliverable, where areas are much longer living creatures. At the RIPE restructuring BOF the need was mentioned for a mechanism to start working groups. I think this is indeed needed, and would have to be defined both for areas and working groups in the sense I have defined them. Some of the areas mentoned above already have a working group in the current sense, like routing. Infrastructure could be the subject of the EEPG working group. Where information exchange is at the one hand needed in order to be able to coordinate on the other hand it also is a topic of its own. One of my goals in attending RIPE meetings is to learn things. And one of the means is attending presentations, either by the RIPE NCC people about their wonderfull new tools or by people who want to tell about the things they are doing. This can be on almost any level, f.i. the presentations on the status of Ebone or EUnet or Dante, or the talk Brian Carpenter gave last meeting on IPng. This "information exchange" or "learning" topic also relates to the issue raised at the last RIPE meeting (and one that was also raised at the open plenary at the last IETF) about the size of the meeting (both plenary and working groups). Bigger amounts of people will change the character of a meeting and will get a smaller percentage of the people who are active and participating in the discussion. I do not see this a s a problem, because by listening to discussions that have a fair amount of openness, you can learn quite a lot. Having a discussion by knowledgable people is a way to disseminate this knowledge to relative newcomers. So I should say, the bigger the RIPE meetings are, the better RIPE can fulfill its goals. I hope the points mentioned above can be used to help the discussion about the goal and structure of RIPE along a little. -- Willem

2 2

RIPE Meeting Dinner Announcement
by Anne Lord 10 May '94

10 May '94

18th RIPE Meeting Evening Dinner May 17th, 7.30 pm. Amsterdams Brouwhuis Maximiliaan Kloveniersburgwal 608, on Nieuwmarkt The dinner for this RIPE meeting will be taking place in a local brewery. I thought this might warm the hearts of some, as well as make a change from where we have previously eaten. Beer is brewed on-site in copper kettles (so I am told) so during the dinner you will have the opportunity to sample some of the local beers. - - - - - - -- - - - - - - - - -- - - - - - - - - -- - - - - - MENU Baked mushrooms and rauweham with mustard creme-fraiche dressing **** Leek soup **** Lamb with thyme and apples in a beer sauce Salad Potato dish **** Chocolate mousse **** Coffee - - - - - - -- - - - - - - - - -- - - - - - - - - -- - - - - -- - The cost of the dinner is Hfl. 70,- and includes a welcome drink, coffee at the end of the meal, and 3 drinks during the dinner. If you drink any more than this, it's fine, but you have to pay for what you drink. If you would like to attend, then please complete and send the form below to <ncc(a)ripe.net> - - - - - - -- - - - - 8< cut here - - -- - - - - - - - - - - - -- I would like to attend the 18th RIPE Meeting Evening Dinner. Please reserve a place for : name: guest: Vegeatarian meals can be arranged on request. - - - - - - - - - - - - - - - - - - - - - -- - - -- - - - - - -- -

1 0

Removal of KAVA.NISC.SRI.COM as Root Name Server
by Domain Registration Role Account 09 May '94

09 May '94

KAVA.NISC.SRI.COM (192.33.33.2) will no longer be operated as a root name server. We understand that ISI will be bringing up a root server to replace it. Regards, Duane InterNIC Domain Registration

1 0