October 1995 - lir-wg - mailman.ripe.net

Abuse of RIPE Database for Junkmail
by Daniel Karrenberg 28 Oct '95

28 Oct '95

If we can find more evidence of this, I would like to take action. Any more sightings before we ask in a broader forum? Daniel ------- Forwarded Message Date: Thu, 26 Oct 95 07:28:25 IST From: Hank Nussbacher <HANK(a)VM.TAU.AC.IL> To: ncc(a)ripe.net Subject: Possible copyright violation I seem to remember the RIPE database is copyright and users are not to make commercial use of it. Today I got a 7 page fax from PACT conferences in relation ot Net User - the first major exhibition dedicated to the Internet in France (from Herve Thevenet). PACT is in partnership with Eunet, Informatiques Magazine, Skyworld, Apple and World Channel Technologies. They list their e-mail contact as ht11(a)calvanet.calvacom.fr. The only place they could have extracted my fax number is from the RIPE database - and my interest in Israel to such a conference is minimal. Is this the start of junkfax based on your database? I think the ripe list should be polled to see if others have received such a fax and if so legal options should be persued if you don't want everyone ripping off your DB. Hank ------- End of Forwarded Message

2 1

Announcement for Local IR Training Course in Wimbledon (London), UK
by RIPE NCC Training 20 Oct '95

20 Oct '95

------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Local IR Training Course Announcement * * * Announcement * * * Local Internet Registries Training Course Date: Monday, 27th November, 1995 Time: 0900 - 1700 Venue: The Internet Centre 43 Wimbledon Hill Rd Wimbledon London SW19 UK ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Course Description Course Audience --------------- The target audience for this course is personnel of European Local Internet Registries that contribute to the RIPE NCC. Material Covered ---------------- The course is a one day introduction on Internet name, address and routing policy registration procedures in Europe. It also teaches how to query and use the information registered for operational purposes. This includes the following material and activities: o Overview of name, address and routing registration procedures. o Responsibilities of both RIPE NCC and Local IR's to each other. o Wider context of the Delegated Registry system and relevant issues (IPv4 address depletion, CIDR) and how this relates to IP requests. o How to use the RIPE NCC Database. o Use of AS numbers, Routing Registry concepts and an introduction to using PRIDE tools. o DNS feedback on commor errors, how to request delegations, and pointers to useful tools. We again stress that this course will *not* teach Local Registries on how to run their business as Internet Service Providers. It is clearly focussed on registration procedures and the interaction between the RIPE NCC and local IR's. A detailed outline is appended below. The course itself will include lunch and will be free. This of course does not include your travel and subsitence ;-). How to Register --------------- Please send an RSVP to <training(a)ripe.net> if you would like to attend the course. If you have previously approached us about attending this course, we ask you to confirm that you (or a colleague) will be attending. Registrations will be accepted on a first come, first served basis. If the course is oversubscribed, we will give priority to local IRs who have paid the signup fee in 1995. If it is still oversubscribed, we will accept only one person per new local registry. We will provide additional course dates in Amsterdam as necessary. If a number of local registries so request, we will present courses at other European locations. If you would like a local course or have any questions or suggestions, please do not hesitate to contact us. The RIPE NCC Training Team: Mirjam Kuehne, Daniel Karrenberg --- Course Outline -------------- For this second course, we will provide a slidebook and a reader on the day of the course, as well as electronically. Once feedback is received, it is planned to make detailed documentation available in the form of a guide much like the PRIDE guide. The program will divide the actual content into the following sections: 1. Introduction For those unfamiliar with the Delegated Internet Registry system and the RIPE NCC, this section will give a historical overview of how we have arrived at today's model of operation and why training of local IR's is a much needed activity. 2. IP Registry procedures This section will clarify the procedures between the RIPE NCC and local IR's with respect to requests for IP address space. It will take a step by step approach on how to complete documentation, the kind of information that is required, what the "handholding" procedure is, how to deal with very large requests, and very small requests, and more generally what criteria the RIPE NCC and local IR's use for their customers in the context of CIDR and IPv4 address depletion. 3. RIPE NCC Database This section will explain what the RIPE NCC Database is and how it fits into the scheme of other registry databases. It will cover how to create and update RIPE NCC Database objects and will explain how to query the database. 4. Routing Registry procedures This section will examine AS numbers, when you need them and how to request them. This will be set within the context of how AS numbers are used as part of the RIPE Routing Registry. Understanding the basic principles behind the Internet Routing Registry and how registering your policy is an important element in the global schema. This section will also include a brief introduction to the PRIDE tools and how they can be useful to you. 5. DNS procedures Where to request forward and reverse domain delegation. Which documentation should be completed. How reverse domain delegation requests are processed at the RIPE NCC (with a useful tool). We will also take a look at common errors in setting up DNS with respect to relevant RFCs and RIPE recommendations. Feedback Please! Throughout the course there will be ample chance for feedback and discussion with an emphasis for you to tell us how we can improve ;-). ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Registration Form %%%%%%%%%%% PLEASE NOTE %%%%%%%%%%% Our handling of ALL course registrations is fully automated. To register for the course, please complete the registration form and send it to <training(a)ripe.net>. Please send only the registration form in your reply and edit out all other text. Add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). If you have any questions about the training course or your registration form, please contact us at <training(a)ripe.net>. You will receive a notification message that your request has been processed. Many thanks, and look forward to seeing you, RIPE NCC Training Team ---------------------------------------------------------------------------- %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Announcement for Local IR Training Course in Oslo, Norway
by RIPE NCC Training 20 Oct '95

20 Oct '95

------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Local IR Training Course Announcement * * * Announcement * * * Local Internet Registries Training Course Date: Monday, 13th November, 1995 Time: 0900 - 1700 Venue: Fornebu Konferansesenter Marin Lyngvej 2nd floor Fornebu Airport ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Course Description Course Audience --------------- The target audience for this course is personnel of European Local Internet Registries that contribute to the RIPE NCC. Material Covered ---------------- The course is a one day introduction on Internet name, address and routing policy registration procedures in Europe. It also teaches how to query and use the information registered for operational purposes. This includes the following material and activities: o Overview of name, address and routing registration procedures. o Responsibilities of both RIPE NCC and Local IR's to each other. o Wider context of the Delegated Registry system and relevant issues (IPv4 address depletion, CIDR) and how this relates to IP requests. o How to use the RIPE NCC Database. o Use of AS numbers, Routing Registry concepts and an introduction to using PRIDE tools. o DNS feedback on commor errors, how to request delegations, and pointers to useful tools. We again stress that this course will *not* teach Local Registries on how to run their business as Internet Service Providers. It is clearly focussed on registration procedures and the interaction between the RIPE NCC and local IR's. A detailed outline is appended below. The course itself will include lunch and will be free. This of course does not include your travel and subsitence ;-). How to Register --------------- Please send an RSVP to <training(a)ripe.net> if you would like to attend the course. If you have previously approached us about attending this course, we ask you to confirm that you (or a colleague) will be attending. Registrations will be accepted on a first come, first served basis. If the course is oversubscribed, we will give priority to local IRs who have paid the signup fee in 1995. If it is still oversubscribed, we will accept only one person per new local registry. We will provide additional course dates in Amsterdam as necessary. If a number of local registries so request, we will present courses at other European locations. If you would like a local course or have any questions or suggestions, please do not hesitate to contact us. The RIPE NCC Training Team: Mirjam Kuehne, Daniel Karrenberg --- Course Outline -------------- For this second course, we will provide a slidebook and a reader on the day of the course, as well as electronically. Once feedback is received, it is planned to make detailed documentation available in the form of a guide much like the PRIDE guide. The program will divide the actual content into the following sections: 1. Introduction For those unfamiliar with the Delegated Internet Registry system and the RIPE NCC, this section will give a historical overview of how we have arrived at today's model of operation and why training of local IR's is a much needed activity. 2. IP Registry procedures This section will clarify the procedures between the RIPE NCC and local IR's with respect to requests for IP address space. It will take a step by step approach on how to complete documentation, the kind of information that is required, what the "handholding" procedure is, how to deal with very large requests, and very small requests, and more generally what criteria the RIPE NCC and local IR's use for their customers in the context of CIDR and IPv4 address depletion. 3. RIPE NCC Database This section will explain what the RIPE NCC Database is and how it fits into the scheme of other registry databases. It will cover how to create and update RIPE NCC Database objects and will explain how to query the database. 4. Routing Registry procedures This section will examine AS numbers, when you need them and how to request them. This will be set within the context of how AS numbers are used as part of the RIPE Routing Registry. Understanding the basic principles behind the Internet Routing Registry and how registering your policy is an important element in the global schema. This section will also include a brief introduction to the PRIDE tools and how they can be useful to you. 5. DNS procedures Where to request forward and reverse domain delegation. Which documentation should be completed. How reverse domain delegation requests are processed at the RIPE NCC (with a useful tool). We will also take a look at common errors in setting up DNS with respect to relevant RFCs and RIPE recommendations. Feedback Please! Throughout the course there will be ample chance for feedback and discussion with an emphasis for you to tell us how we can improve ;-). ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Registration Form %%%%%%%%%%% PLEASE NOTE %%%%%%%%%%% Our handling of ALL course registrations is fully automated. To register for the course, please complete the registration form and send it to <training(a)ripe.net>. Please send only the registration form in your reply and edit out all other text. Add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). If you have any questions about the training course or your registration form, please contact us at <training(a)ripe.net>. You will receive a notification message that your request has been processed. Many thanks, and look forward to seeing you, RIPE NCC Training Team ---------------------------------------------------------------------------- %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Announcement for Local IR Training Course in Amsterdam
by RIPE NCC Training 20 Oct '95

20 Oct '95

------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Local IR Training Course Announcement * * * Announcement * * * Local Internet Registries Training Course Date: Friday, 3. November, 1995 Time: 0900 - 1700 Venue: RIPE NCC Kruislaan 409 1098 SJ Amsterdam The Netherlands ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Course Description Course Audience --------------- The target audience for this course is personnel of European Local Internet Registries that contribute to the RIPE NCC. Material Covered ---------------- The course is a one day introduction on Internet name, address and routing policy registration procedures in Europe. It also teaches how to query and use the information registered for operational purposes. This includes the following material and activities: o Overview of name, address and routing registration procedures. o Responsibilities of both RIPE NCC and Local IR's to each other. o Wider context of the Delegated Registry system and relevant issues (IPv4 address depletion, CIDR) and how this relates to IP requests. o How to use the RIPE NCC Database. o Use of AS numbers, Routing Registry concepts and an introduction to using PRIDE tools. o DNS feedback on commor errors, how to request delegations, and pointers to useful tools. We again stress that this course will *not* teach Local Registries on how to run their business as Internet Service Providers. It is clearly focussed on registration procedures and the interaction between the RIPE NCC and local IR's. A detailed outline is appended below. The course itself will include lunch and will be free. This of course does not include your travel and subsitence ;-). How to Register --------------- Please send an RSVP to <training(a)ripe.net> if you would like to attend the course. If you have previously approached us about attending this course, we ask you to confirm that you (or a colleague) will be attending. Registrations will be accepted on a first come, first served basis. If the course is oversubscribed, we will give priority to local IRs who have paid the signup fee in 1995. If it is still oversubscribed, we will accept only one person per new local registry. We will provide additional course dates in Amsterdam as necessary. If a number of local registries so request, we will present courses at other European locations. If you would like a local course or have any questions or suggestions, please do not hesitate to contact us. The RIPE NCC Training Team: Mirjam Kuehne, Daniel Karrenberg --- Course Outline -------------- For this second course, we will provide a slidebook and a reader on the day of the course, as well as electronically. Once feedback is received, it is planned to make detailed documentation available in the form of a guide much like the PRIDE guide. The program will divide the actual content into the following sections: 1. Introduction For those unfamiliar with the Delegated Internet Registry system and the RIPE NCC, this section will give a historical overview of how we have arrived at today's model of operation and why training of local IR's is a much needed activity. 2. IP Registry procedures This section will clarify the procedures between the RIPE NCC and local IR's with respect to requests for IP address space. It will take a step by step approach on how to complete documentation, the kind of information that is required, what the "handholding" procedure is, how to deal with very large requests, and very small requests, and more generally what criteria the RIPE NCC and local IR's use for their customers in the context of CIDR and IPv4 address depletion. 3. RIPE NCC Database This section will explain what the RIPE NCC Database is and how it fits into the scheme of other registry databases. It will cover how to create and update RIPE NCC Database objects and will explain how to query the database. 4. Routing Registry procedures This section will examine AS numbers, when you need them and how to request them. This will be set within the context of how AS numbers are used as part of the RIPE Routing Registry. Understanding the basic principles behind the Internet Routing Registry and how registering your policy is an important element in the global schema. This section will also include a brief introduction to the PRIDE tools and how they can be useful to you. 5. DNS procedures Where to request forward and reverse domain delegation. Which documentation should be completed. How reverse domain delegation requests are processed at the RIPE NCC (with a useful tool). We will also take a look at common errors in setting up DNS with respect to relevant RFCs and RIPE recommendations. Feedback Please! Throughout the course there will be ample chance for feedback and discussion with an emphasis for you to tell us how we can improve ;-). ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Registration Form %%%%%%%%%%% PLEASE NOTE %%%%%%%%%%% Our handling of ALL course registrations is fully automated. To register for the course, please complete the registration form and send it to <training(a)ripe.net>. Please send only the registration form in your reply and edit out all other text. Add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). If you have any questions about the training course or your registration form, please contact us at <training(a)ripe.net>. You will receive a notification message that your request has been processed. Many thanks, and look forward to seeing you, RIPE NCC Training Team ---------------------------------------------------------------------------- %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Training Course Slides available
by Mirjam Kuehne 20 Oct '95

20 Oct '95

Dear all, I have made the slides from the last Training Course available on our ftp server: ftp://ftp.ripe.net/ripe/local-ir/training/*.ps.gz I will update the files after every course so that you can always pick up the latest version of the slides. Kind regards, Mirjam Kuehne RIPE NCC

1 0

FYI: lost RADB transactions on 10/14 (fwd)
by David.Kessens＠ripe.net 19 Oct '95

19 Oct '95

> Brian Renaud writes : > From list-admin(a)merit.edu Wed Oct 18 20:49:32 1995 > Message-Id: <199510181853.OAA08985(a)home.merit.edu> > X-Mailer: exmh version 1.6.2 7/18/95 > From: Brian Renaud <renaud(a)merit.edu> > To: nanog(a)merit.edu > Subject: lost RADB transactions on 10/14 > Reply-To: renaud(a)merit.edu > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Date: Wed, 18 Oct 1995 14:53:04 -0400 > Sender: renaud(a)merit.edu > > > On Saturday the 14th, a mail loop caused a disk partition to fill up on > the RADB server machine. It appears that any transaction sent to the RADB > between 17:00 and 23:58 EDT on 10/14 was not processed. > > If you sent in a transaction to auto-dbm(a)ra.net during that time and did not > receive a positive acknowledgement from the database software, then you > should re-send the transactions. > > -Brian > >

1 0

Stop 'time permitting' service now!
by Daniel Karrenberg 18 Oct '95

18 Oct '95

Dear Contributors and Local-IRs, Since there have been no objections at all, time-permtting service has been abandoned as of this week. The RIPE NCC will from now on provide registration services only to established local registries in good standing. This has been announced at the RIPE meeting last week. Individuals requesting address space will be referred to their service provider and/or the list of local registries. Service providers requesting address space will be informed about how they can establish a local IR and/or be referred to their upstream providers. We will notify all those who have time-permitting requests pending. If you have any further questions, please do not hesitate to contact us. Regards Daniel Karrenberg RIPE NCC Manager

1 0

Local IR mtg, draft minutes
by mnorris＠dalkey.hea.ie 17 Oct '95

17 Oct '95

Please see the following draft minutes of the meeting last Wednesday. Anne Lord mailed them to me on Friday, just after the end of RIPE 22 - is this a record? Whatever, well done and many thanks, Anne. I'd be glad to hear comments, corrections etc. Cheers. Mike Norris Local IR Working Group Minutes - RIPE 22 Wednesday 11th October, 1995 At this working group meeting there were 43 attenders. 1. Preliminaries Anne Lord (auto) volunteered to take the minutes. The agenda was agreed as previously drafted to the working group mailing list. No additions to the agenda were made. 2. RIPE 21 As the draft minutes of the working group meeting from RIPE 21 had been circulated and no objections were raised, they were formally approved. 3. Reports from Registries 3.1 European Regional Registry (NCC) Staff Developments: Since the last RIPE meeting, the RIPE NCC has appointed three new junior hostmasters: - Nick Reid (full time) from UK - Hatice Kuey (full time) from Turkey - Els Willems (part time) from The Netherlands Additionally a further two more part-time junior hostmasters will start on 16th October: - John Crane from UK - Soodabey Eshkey from Iran. It is estimated that by the end of the year with these additional resources that local IR's will no longer experience hostmaster delays. Request Tracking System: This is currently being implemented at the RIPE NCC. The tracking system has been described in RIPE document ftp://ftp.ripe.net/ripe/docs/ripe-183.txt. All new requests are issued a ticket number, which should be used in future related correspondence. Absolutely crucial to any dealings with the RIPE NCC hostmasters is your registry ID. The RIPE NCC now deals with around 300 local IR's, an increase of around 60 since the last RIPE meeting. 3.2 Last Resort Registries There are currently around 30 Last Resort Registries. In the context of previous discussions around Provider Independant and Provider Allocated address space (ripe-127) it has been agreed that Last Resort Registries should be phased out. At the NCC contributors meeting it was decided that the last resort IR's should be charged like any other registry. This has had the desired impact of accelerating the number of Last Resort IR's wanting to close. Billing for 1996 will be issued in November. A question was raised as to how many last resort registries expect to continue operation after November and the answer was that out of the 7 present, only 1 expected to continue. A question was also raised regarding what to do with the remaining address space held by the last resort registry if they wished to close. The answer was to contact <hostmaster(a)ripe.net> to discuss the procedures. There was another question, regarding what to do with large companies who are requesting PI address space. They can contact the RIPE NCC to discuss becoming an enterprise registry. They can also receive PI address space but this will carry with it no guarantees of routability in the Global Internet. Local IR's can hold PI address space, but this will be allocated by the RIPE NCC probably from the remaining 192.x.x.x address space. 3.3 Other Registries There were no reports from other registries. 3.4 Global Coordination There has been minimal progress on rfc1466++ due to lack of time from all parties involved. The revision of ripe-104++ had been dependent on this rfc being updated. It was proposed to finish updating ripe-104++ irrespective of the development of the rfc as the RIPE document is urgently required as a guideline document for the many new IR's coming on board. There were no objections to this proposal. Action: Mike Norris and RIPE NCC To find volunteers from the Local IR working group to continue working on the revision of ripe-104++ without waiting for the publication of rfc1466++. 4. RIPE NCC Services 4.1 Charging model for 1996. At the RIPE NCC contributors committee meeting in September a charging scheme for 1996 was agreed (This scheme was circulated in the minutes of that meeting). The billing scheme is described at ftp://ftp.ripe.net/ /new-registry/billing-96.txt. Bills will be issued in November, unless you contact <billing(a)ripe.net> to say that you would like to be billed in January 1996. So far, there have been no cancellations for RIPE NCC services from any registries. It was also decided that the "time-permitting" service would be discontinued from 16th October. The RIPE NCC hostmaster service is offered to contributing registries only. 4.2 Billing procedures In summary, there are 4 categories and each registry decides which category they would like to be in. The category information per registry is public information but the RIPE NCC commented that in the future they may be more active in suggesting, movement between categories to established local IR's. 4.3 Charging by local IR's There was an outstanding action on Mike Norris to prepare a paper on charging by local IRs. He would complete this asap. 4.4 Tracking and ticketing system (ripe-183) Already discussed above. 4.5 Training There have been 4 courses held. There are approximately 15 attenders per course, and this is the maximum number of attenders sought per course. There are two further courses planned for November, one in the UK and one in Norway. The dates are not yet fixed but there will be an announcement to the local IR mailing list. Note should be made that the training courses are only open to local contributing local IR's. If any local IR is interested to host a course, then the RIPE NCC would be happy to deliver a course in your country. Please contact <training(a)ripe.net> to dicuss the details further. The slides from the training courses in Amsterdam and Munich are available in the RIPE document store in ftp://ftp.ripe.net/ripe/local-ir/training/* 5. Address Assignment 5.1 Procedures (ripe-104) As discussed above the need for ripe-104++ documentation is now so great that it was suggested to form a group of volunteers from the local IR working group to actually progress this document asap. Ideally, this document should be ready before the next RIPE meeting in January. It was suggested to have the volunteers to come to the RIPE NCC for a day to meet to progress this work. The RIPE NCC offered to pay for travel and subsistence for those interested. 5.2 PI vs PA address space (ripe-127 upcoming rfc) Ripe-127 is on track to become an rfc. Daniel Karrenberg was informed by the rfc editor that the publication of this document is on track. It was generally recommended to include in documentation to your customers a clarification over the PI and PA recommendations in ripe-127. 5.3 Reverse domains The procedure for delegating revers domains has now been automated. Requests can be sent to <auto-inaddr(a)ripe.net>. David Kessens gave a short presentation of this. In summary: use 'inetnum' object with one nameserver per 'rev-svr' attribute or for block (/16) delegations, with one nameserver per 'nserver' attribute Using the wrong attributes in the objects will not break the auto-delegation procedure. The software for this tool is available in ftp://ftp.ripe.net/tools/ inaddrtool-950815.tar.gz. Note that the RIPE NCC only makes delegations for 194.x.x.x. and 193.x.x.x blocks of address space. There was a question regarding delegations for > er than /24 prefixes. This is possible and there is a description of how to do this in the document store in: ftp://ftp.ripe.net/internet-drafts/draft-degroot-classless-inaddr-00.txt. 5.4 Status and use of rfc1597 The revision to rfc1597 is currently being discussed within the IETF CIDR-D working group. The revision will be reissued as a BCP - "Best Current Practices" rfc series. It was again recommended to point not only large organisations with firewalls at this document, but also VSE 's < 50 hosts not wanting to connect to the internet. It is hoped that this document will be out by the December IETF. The actual content of rfc1597 will be changed considerably. It is noted that the address space reserved and used for private address space still stand. 6. Tools There were no other reported tools other than that circulated previously by Nigel Titley. The tool checks the status of the registrations in the RIPE database against another file in which records of registrations are held. The source code is available from : ftp://ftp.bt.net/networking/tools/tree/tree-2.1.1.tar.Z 7. Input from other working groups 7.1 Database There was a request for clarification of the difference between the <auto-assign(a)ripe.net> mail address and the <auto-dbm(a)ripe.net>. It was noted that the <auto-assign> address contained some additional sanity checking for new objects, so that existing objects could not be clobbered. Further discussion over this was deferred to the database working group. Additionally, there was a question over whether route objects, with no matching inetnum objects should be allowed or checked for. It was deferred to the database working group for potential discussion. 7.2 EOF The EOF working group highlighted a need for a survey of domain procedures amongst different top level domains. This topic was taken up in the DNS working group. 8. AOB There were no items discussed. The chair thanked the audience for their input.

1 0

Alert: Mannesmann / Hartmann & Braun AG
by RIPE NCC Hostmaster 16 Oct '95

16 Oct '95

If any registry is currently handling requests from: descr: Mannesmann group, Germany descr: Netzbetrieb, Ratingen country: DE admin-c: Alois Fiedler tech-c: Stefan Paetzold tech-c: Thomas Wolf Or: descr: Hartmann & Braun AG descr: Frankfurt am Main country: DE admin-c: Peter Radig tech-c: Peter Radig Please get in touch with the RIPE NCC Kind regards, Geert Jan de Groot RIPE NCC staff

1 0

RIPE22: terminal room
by RIPE NCC Staff 06 Oct '95

06 Oct '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, using 10baseT ethernet. Unfortunately, Apple localtalk access cannot be provided, sorry. If 10base2, AUI or 110V is required, please send mail to <ncc(a)ripe.net> b e f o r e thuesday. If time allows, I will try to bring up an experimental DHCP server. In any case, a limited number of static IP addresses will be available & can be applied for at the registration desk. People that need to have access lists changed should allow access from 192.16.199.0/24 and 192.16.192.0/24. Printer access will be provided via an uuencoded-file-via-mail gateway. Hope this helps, Geert Jan

1 0