- lir-wg - mailman.ripe.net

New Draft Document available: ripe-inetnum
by RIPE NCC Draft Document Annoucement Service 10 May '94

10 May '94

Short content description ------------------------- This is to announce a draft update to the inetnum document originally known as ripe-050. 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/drafts/" followed by the command "get filename". The relevant filenames for this document are: ripe-inetnum.txt for the ASCII version ripe-inetnum.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/drafts/ripe-inetnum.txt

1 0

New Draft Document available: ripe-clarep
by RIPE NCC Draft Document Annoucement Service 10 May '94

10 May '94

This is to announce a draft version of the classless reperesentation document. 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/drafts/" followed by the command "get filename". The relevant filenames for this document are: ripe-clarep.txt for the ASCII version ripe-clarep.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/drafts/ripe-clarep.txt

1 0

New Draft Document available: ripe-81++
by RIPE NCC Draft Document Annoucement Service 10 May '94

10 May '94

This is to announce a draft version of ripe-81++. 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/drafts/" followed by the command "get filename". The relevant filenames for this document are: ripe-81++.txt for the ASCII version ripe-81++.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/drafts/ripe-81++.txt

1 0

Classless Registry Drafts
by Daniel Karrenberg 10 May '94

10 May '94

Dear colleagues, we have prepared three draft documents describing how support for classless addresses can be added to the RIPE database. At the same time we propose a clear split between the allocation registry and the routing registry functions of the database. The allocation registry holds information about address space assignments done by Internet registries, while the routing registry holds information about routing policies and is largely maintained by the service providers. The three documents each describe one part of this new database. ripe-81++ - routing registry ripe-inetnum - allocation registry ripe-clarep - representation of classless addresses ripe-81++ is the longest document of the three. It describes the routing registry part of the database. It is a direct descendant of ripe-81. There are major changes as required by the separation of allocation and routing information. Also there is now support for classless routes and hence CIDR aggregation. It is also now possible to describe multiple ASes originating the same route. ripe-inetnum describes the changed inetnum object which is basically stripped of all routing and obsoleted attributes. ripe-inetnum also describes the person object and thus constitutes a complete reference for the allocation registry. ripe-clarep describes the representation of classless addresses in the RIPE database and thus in both the routing and the allocation registry. As these proposals are relevant to all three working groups addressed, we would appreciate if they could be discussed at the upcoming meeting and if at all possible consensus reached at least about the general design behind them. We need to make the registries classless as soon as possible and it will take some time to do the implementation. The documents can be found in ftp.ripe.net:ripe/drafts/<name>.{ps,txt}. We will be sending MIMEd announcements for all three shortly. Comments are very welcome indeed. Daniel Marten Tony

1 0

2nd Local IR workshop announcement and registration form.
by Anne Lord 06 May '94

06 May '94

The second Local IR workshop will be held on Monday 16th May. The meeting will run from 10.00 - 12.30. The number of participants will be limited to *only* those who register using the form below. Coffee and lunch is included. The location of the meeting will be announced just before the meeting and only to those who register. Please register asap so we can organise the catering. Thanks, Anne - - - - - - - - - - - - - -- - - - - - -- - - - - - -- -- - - -- - - 18th RIPE meeting LOCAL IR CLOSED WORKSHOP Amsterdam, May 16th, 10.00 am Programme and Registration Form Total useful time: 120 minutes Breaks: 30 Minutes 1. Review of the Program (10') If any participant has something interesting we would love to hear it. Please mail to <dfk(a)ripe.net> in advance if possible. 2. Tools for registries (30') At the NCC we have developed some tools to help with registry work. We are sure other registries have done the same. We would like such tools to be more widely used if applicable. Overview of tools being developed at the NCC Overview of tools being developed elsewhere stt: Standard Text Tool or How to reply to answer mail courteously and efficiently 3. Private Address Space (RFC1597) (30'): RFC1597 has been published and IANA has reserved IP address space for private parts of enterprise networks. We'll have a short review of the RFC by one of the authors and a discussion what local registries should do with it. What is private address space? How does it affect local registries? Discussion. 4. Common pitfalls in in-addr.arpa name service (20') The NCC sees quite a numberof configuration errors in in-addr.arpa zones. Common pitfalls are going to be discussed and ripe-105 reviewed. 5. Interesting Assignment Cases (30') A discussion of difficult cases of address space assignment from the NCC and local registries. - - - - - - - - - - - -- - - - -Registration Form- - - -- - - - - - - Local IR workshop Monday 16th May, 10.00 ( ) I would like take part in the LOCAL IR workshop. Name: Organisation/affiliation: Country: Please send your completed form to <ncc(a)ripe.net>. - - - - - - - - - - - - - - - - - - - -- - - - - -- - - - - - - - - -

1 0

Re: Chairman Resigns
by Juergen Rauschenbach 28 Apr '94

28 Apr '94

Daniel, Wilfried, ... > > While this is true, I view the local registries very much as customers > of the NCC as well. We provide a service for you. One of the tasks of > the local-ir group is to provide feedback (critisism, requests) > about that service to the NCC and maybe even complain to others > if the NCC doesn't provide the required service. Even more important is the opportunity to put the local-ir forces together to defend the Internet address room ... ... > > > > While I don't want to try to keep bothering you to reconsider your > > decision - let me say that I think we (all the Local-IRs) were *VERY* > > happy with the way this WG was chaired by you. > I want to second this. > Thank you for your kind words. They really help sometimes. > > > I hope that we can find > > a way to keep this collaborative attitude instead of implementing > > "pressure groups" within RIPE. > > I hope so too. > > Daniel > Juergen

1 0

RE: Chairman Resigns
by Wilfried Woeber, UniVie/ACOnet 28 Apr '94

28 Apr '94

Daniel, >I am sorry but this coming meeting I have to definitely >resign as the chairman of this group. There are two reasons: If this is a final decision then we have to accept it :-( But - >1) I (still) do not think it is right that an NCCer chairs a > this group. One of the missions of the group is to act as > a pressure group towards the NCC. I have expressed this in I'm not sure whether this is the one and only possible position. My understanding was that the NCC as the Regional Registry has some responsibilities towards the Global Registry, and thus I don't see where a "pressure group" approach would fit into the picture. > the past but those present at that meeting forcefully :-) > agreed that they were happy I agreed to stay on. > Since the fact that I chair this group now has been used > as one of the arguments to critisise the RIPE NCC management > structure as a whole I have to resign. Given the recent history in networking in Europe, this is probably not going to stop the criticisms but at least lifts the responsibility from your shoulders :-( >2) The NCC is currently understaffed and any reduction in the load > on all staff is welcome. This seems to be the most valid point. >So please be prepared that a new chairperson will have to be elected >at the next meeting. While I don't want to try to keep bothering you to reconsider your decision - let me say that I think we (all the Local-IRs) were *VERY* happy with the way this WG was chaired by you. I hope that we can find a way to keep this collaborative attitude instead of implementing "pressure groups" within RIPE. Best regards, Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Wilfried.Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

3 2

Chairman Resigns
by Daniel Karrenberg 26 Apr '94

26 Apr '94

This is a message to the local-ir working group of RIPE. I am sorry but this coming meeting I have to definitely resign as the chairman of this group. There are two reasons: 1) I (still) do not think it is right that an NCCer chairs a this group. One of the missions of the group is to act as a pressure group towards the NCC. I have expressed this in the past but those present at that meeting forcefully :-) agreed that they were happy I agreed to stay on. Since the fact that I chair this group now has been used as one of the arguments to critisise the RIPE NCC management structure as a whole I have to resign. 2) The NCC is currently understaffed and any reduction in the load on all staff is welcome. So please be prepared that a new chairperson will have to be elected at the next meeting. Daniel

2 2

Agenda of the local IR working group for the 18th meeting
by Daniel Karrenberg 25 Apr '94

25 Apr '94

Draft Agenda for the Local IR working group at the 18th RIPE meeting 1. Agenda Bashing 2. Minutes of last meeting (already circulated) 3. Election of new chairperson 4. European Registry Report by the NCC 5. Reports of significant events at local registries 6. RFC1597 and its implications for local IRs (very short) 7. Funding of and Charging for local registry service 8. AoB Suggestions (for additional points) welcome. Daniel

1 0

Alert: Harlow Butler Brokering Services
by RIPE NCC Hostmaster 22 Apr '94

22 Apr '94

Dear Internet Registries, we have received some messages that Harlow Butler Brokering Services, an international stockbroker, might try to apply for more IP address space at easy local-IR individually because their request for an unjustified amount of address space has been denied. They are talking about going to the registeries in each country directly to circumvent this decision and try to collect address space this way. We would apreciate if any address assignement to this organisation would be handled with extreme discretion and we be notified of any requests from them, so we can coordinate an orderly process. Kind regards, Geert Jan de Groot RIPE NCC Hostmaster of the day.

2 2