- ripe-list - mailman.ripe.net

Apologies for resent mail
by Tim Grimer 20 Jan '95

20 Jan '95

Many apologies for some 16 messages sent by accident to this list. We know of only one way this could have occured. At Unipalm, our windows based mail application allows you to "Drag-and-drop" selected groups of mail messages to folders. Unfortunately, it is possible to drop messages into the out-tray by accident at which point they are promptly sent. Peter Dawe has a separate mail account, Peter2, which is used by his Personal Assistant to organise the large volume of mail he receives daily. The unwanted mail came from there. We are taking steps to make sure that mail cannot originate from this source in the future. Tim Grimer. Unipalm Postmaster.

1 0

RIPE meeting special request
by RIPE NCC Staff 20 Jan '95

20 Jan '95

Dear All, I would like to ask your help at the forthcoming RIPE meeting. I am "retiring" from the minute-taking task at this and future RIPE meetings :-). Instead, David Kessens our new colleague will be doing this. Since this is his first time, I will of course be helping him, but it would be great if everyone who is giving a presentation could coordinate with David and with the Working Group chairs so that the task of collecting all the information for the minutes is made easier for him. Your help is much appreciated. (aplogies to anyone who gets this message twice) Kind Regards, Anne RIPE NCC

1 0

RIPE20 : Terminal room facilities
by RIPE NCC Staff 20 Jan '95

20 Jan '95

Terminal-room facilities during the RIPE-meeting. ------------------------------------------------- Time allowing, we will provide a terminal room during the RIPE meeting. There will be a number of ASCII terminals connected to a terminal-server (hef-ts1.nikhef.nl or hef-ts2.nikhef.nl), which will allow for telnet access. We will also provide ethernet tap points for laptop computers. 10base2 and 10baseT will be provided. 110V will be available too, on request of some of our guests from other continents. We will assign static IP addresses to persons to avoid having to reconfigure their machines. People in need of a 'permanent' IP address for the time of the meeting should send a message to <ncc(a)ripe.net> with 'Terminalroom' in the subject; the addresses will be assigned on-site. People that need to have access lists changed should allow access from 192.16.199.0/24 and 193.0.0.0/24. Printer access will be provided via an uuencoded-file-via-mail gateway. Unfortunately, Apple localtalk access cannot be provided, sorry. We're not trying to match an IETF terminal room, but if you have special requests in this area, please send them to us. Kind regards, Geert Jan de Groot

1 0

Re: CIX Europe?
by Bernard.Tuy＠renater.fr 19 Jan '95

19 Jan '95

| From: Havard Eidnes <Havard.Eidnes(a)runit.sintef.no> | | If you are specifically thinking of the route you have to follow to | get from res.enst.fr to e.g. ub4b.eunet.be, well, ask the respective | parties and find out why they appear to be dragging their feet. (My | somewhat old information tells me that an interconnection was planned, | and for all I know it may still be planned.) ====BT: you *were* right but from now the peering between Eunet and Ebone is running thru Vienna-EBS and not only planned ... Cheers, +Bernard Tuy.

1 0

Re: CIX Europe?
by Bernard.Tuy＠renater.fr 18 Jan '95

18 Jan '95

> Can anyone tell me why there isn't a CIX in Europe? Or >perhaps one is in the works? ====BT: That's a matter of fact that there is no one but many GIXes (not CIXes -as every kind of traffic is allowed : academic and commercial) at the moment all over Europe ... the nearest from you is located in Paris (where Oleane, Phynet and Renater are connected and exchanging traffic, soon will be connected there too : Pipex, Transpac-Fr and Eunet-Fr). Other GIXes are already running : London, Amsterdam, Stockholm and Geneva -for the most well known. +Bernard Tuy. \Renater-CIC/

1 0

Re: CIX Europe?
by Havard Eidnes 18 Jan '95

18 Jan '95

> Can anyone tell me why there isn't a CIX in Europe? Or > perhaps one is in the works? Well, there are a number of interconnect points in Europe, the one in London being one, the ones in Stockholm, Amsterdam and Paris (and Oslo, Helsinki and Copenhagen) being other ones. There are probably more. Some of these are there mainly (or solely) to give more efficient connectivity internally in a country, some of them have a wider scope. > This may seem like an ignorant question (or at least, > "politically uninformed"), but it seems abhorent to me that all > the various commerical providers in Europe have to pull lines to > Alexandria, VA (or wherever) to connect to each other. The network service providers in Europe have a need to go to the US anyway, and widening the US capacity may be cheaper than buying corresponding europe-internal international capacity (sad but true). This is however only one side of the issue. The issue is also one of priorities, money and (gee ;-) politics. I can't see that we wouldn't have the same problems with a CIX in Europe as we have with the currently established Internet exchange points. Please also note that the "CIX" concept has some perceived extra baggage (e.g. the original concrete implementation) that some people feel we are better off without. If you are specifically thinking of the route you have to follow to get from res.enst.fr to e.g. ub4b.eunet.be, well, ask the respective parties and find out why they appear to be dragging their feet. (My somewhat old information tells me that an interconnection was planned, and for all I know it may still be planned.) - Havard

1 0

Re: CIX Europe?
by bob＠informatics.rutherford.ac.uk 18 Jan '95

18 Jan '95

> at least for demon, pipex, bt and ukerna it does.... and for EUmet Britain. Basically any (UK) primary service provider is free to join if it wishes. Bob

1 0

34-155 MBIT Interconnection of Research Networks - Call for proposals
by martin＠terena.nl 18 Jan '95

18 Jan '95

These notes are from a talk given as part of the Telematics Applications programme information days in Brussels on the 17th January 1995 where the launch of a call for proposals for provision of a 34/155 M bits/s network was launched jointly by DGXIII and DGIII. These are my own notes. I make no guarantees for their correctness and you should consult the references given (and not me!) for more information. Queries about the Telematics Applications programme should be directed to: telematics(a)dg13.cec.be. Please feel free to forward this message to other interested parties. Regards, John Interconnection of European Research and University Networks ------------------------------------------------------------ at 34 and 155 Mbits/s --------------------- Call for proposals. The Workprogramme for Telematics Applications for Research included a series of tasks (RE 1.1 to RE 1.3) which defined the validation of a trans-European network of 34 Mbits/s, progressing to 155 Mbits/s. The validation of this network has now become a joint initiative between DGXIII (Telematics Applications Programme) and DGIII (ESPRIT). A call for proposals for the validation of this network has now been launched. The closing date for submissions of proposals is the 15th March. The complimentary information concerning these specific tasks and accompanying the Telematics Applications Call for Proposals can be seen at: http://www.terena.nl/telematics/rtdninfo.html The Telematics Applications Call for Proposals can be seen at: http://www.terena.nl/telematics/cfp.html 1. Funding and Timing --------------------- * A collaborative approach between users and suppliers is encouraged. * The action will have a duration of 2 years. * The action will be a shared cost action. The EC is expected to fund up to 50% of the cost in the first year and up to 30% in the second year. * The total budgetary contribution from the EC is expected to be a maximum of 30 MECU for the 2 years. This contribution by the EC is seen as a starting block for a high- bandwidth network service in Europe. It is expected that the people who make use of this network will eventually have to pay for it. There will be a continuation phase after the initial 2 years but at a lower level. 2. Consortia Composition ------------------------ * European Telecoms operators and service providers. * National Research Networks in Europe operating at, or planning to operate at 34 M bits/s (or higher). * It is essential that there is evidence of consultation with user representatives. 3. Content of proposal ---------------------- The proposal must contain: * Description of technical approach. * Timescales for operational deployment. * Details of the technology to be deployed (both initially and at later stages). * Approach to service provision and quality management. (The EC will specify service and quality levels but not technology.) * Approach to trans-Atlantic connections. * Approach to maintaining connections to the existing European national research networks operating at lower speeds. * Access by academic and industrial researchers (but _not_ industry). Acceptable use policy (AUP). * Approach to connectivity between multiple high-speed pilots. --end John

1 0

CIX Europe?
by Philippe-Andre Prindeville 18 Jan '95

18 Jan '95

Hi. Can anyone tell me why there isn't a CIX in Europe? Or perhaps one is in the works? This may seem like an ignorant question (or at least, "politically uninformed"), but it seems abhorent to me that all the various commerical providers in Europe have to pull lines to Alexandria, VA (or wherever) to connect to each other. Thanks, -Philip

2 1

RIPE 19 actions status report (JANUARY)
by RIPE NCC Staff 16 Jan '95

16 Jan '95

RIPE 19 actions status report (JANUARY) Below is the list of action items from the RIPE meeting (and previously). The actions are grouped into two different categories: "Done" and "Open". If you are on the list with an action against your name, would you please reply confirming the status of that action : ie. whether it has been "Done" or whether it is still "Open", with an expected approx date for completion, if possible. This is the FINAL reminder before the RIPE meeting which is just over a week away. Thanks ! David Kessens RIPE NCC ------------- Action List - RIPE 19 ===================== 1. Done Action: 19.9 Marten Terpstra To set up environment to allow objects to be sent to "a test database". Action: 19.13 Milan Sterba Send e-mail to the prospective contributors to the CDS. Action: 19.16 Stephan Biesbroeck To ask RIPE NCC to create a trouble ticket only mailing list which is maintained by the RIPE NCC. 2. Open Action: 17.1 Glenn Kowack Volunteered to write a paper for discussion which would focus on a funding model for the RIPE NCC. Action: 17.7 Wilfried Woeber, NCC To produce the necessary documentation for the new DB software - ongoing Action: 17.8 NCC To update and re-circulate the RIPE-Handle proposal and then go ahead with the implementation - pending. Action: 17.11 NCC Investigate and propose a syntax-checking facility for the new db software. volunteer needed. 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: 18.3 Geert Jan de Groot Investigate monthly publication of error files on reverse zone files, similar to hostcount error files. Action: 18.5 Wilfried Woeber Post the CEEnet Initiative maps to the RIPE FTP server. Action: 18.16 Everyone in the Mbone group Send in your Mbone maps to Erik-Jan Bos. Action: 19.1 RIPE NCC To survey RIPE community on content of RIPE NCC Quarterly Reports. Action: 19.2 Mike Norris At the 20th meeting to raise the training of local IR's as a topic for discussion. Action: 19.3 Daniel Karrenberg To make an inventory document of the problems associated with charging for address space. Action: 19.4 Daniel Karrenberg To recirculate draft proposal on use of private address space for VSE's not connecting to the Internet. Circulate proposal to the WG mailing list. Action: 19.5 RIPE NCC To organise a meeting between regional registries, with representatives from the RIPE local - IR working group. Action: 19.6 Geert Jan de Groot To document new attribute "status" proposed to describe whether a network is delegated, reserved or assigned. In progress. Action: 19.7 RIPE NCC Circulate revised reipe-115 to the local-ir mailing list for comments. Action: 19.8 Daniel Karrenberg To prepare specification for the format of the list of service providers. Action: 19.10 Erik Jan Bos, Wilfried Woeber Written proposal to extend the "inet-rtr" object ready before RIPE 20. Action: 19.11 RIPE NCC To propose new domain object for in-addr.arpa. Action: 19.12 Marten Terpstra To write up the proposed "stored"/"processed" attribute. Action: 19.14 Erik-Jan Bos Write document describing how to use the rtr-obj to describe location of m-routers. Action: 19.15 Erik-Jan Bos Find out about other vendors' implementations of PIM.

1 0