May 1994 - lir-wg - mailman.ripe.net

Action 17.3,4: Proposal - Report format for address assignments
by Wilfried Woeber, UniVie/ACOnet 11 May '94

11 May '94

Dear all, this is the first proposal - for discussion - of a possible report format for the local registries. While I did not yet have a good idea for a simple "graphical" format, this is a format that could be used both internally for keeping track of allocations and could be easy to compare. To have a sort of "live" example, I converted my local file into the proposed format. Any input welcome! Wilfried. -------------------------------------------------------------------------------- # # ACTIVE$DKA300:[WILFRIED.LOCAL_IR]193_170_X_0.LIST history kept by CMS # 193.170.1.0 193.170.254.0 ACONET initially managed by NCC, now by UniVie Legend: Block: CIDR block F/A(+R): F=free, A=assigned + optional reservation Start: first address in block End: last address in block Netname: name of network(s) used in the RIPE-DB to whom: local assignement information (optional) Block F/A(+R) Start End Netname(s) to whom... ------------------------------------------------------------------------------------------------ 01 F.01.-- 193.170.0.0 - not to be assigned! 01 F.01.-- 193.170.1.0 - FREE (revoked ass. for Vienna EB 01 A.01.-- 193.170.2.0 TVLBG Technikum Vorarlberg 01 A.01.-- 193.170.3.0 ATINET Atominst. der Oest. Univ. 01 A.01.-- 193.170.4.0 ELAKVIE HS f. Musik u. darst. Kunst, I.f 01 A.01.-- 193.170.5.0 WAZ Wiener Akad. f. Zukunftsfragen b 02 A.01.01 193.170.6.0 193.170.7.0 VA-EDV HBLVA Spengergasse 04 A.02.02 193.170.8.0 193.170.11.0 TGM TGM Wien-XX 02 A.01.01 193.170.12.0 193.170.13.0 OINET Oekologie Institut 02 A.01.01 193.170.14.0 193.170.15.0 XBIT HTBL Klagenfurt 16 A.16.-- 193.170.16.0 193.170.31.0 UNILEO-C1,2,... Uni Leoben 16 A.08.08 193.170.32.0 193.170.47.0 KGI-LAN Uni-Linz 16 A.16.-- 193.170.48.0 193.170.63.0 UNIVIE11,12,... UniVie scattered nets 02 A.01.01 193.170.64.0 193.170.65.0 ARCS1 Seibersdorf 01 A.01.-- 193.170.66.0 CEDAR CEDAR C.E.Data Request Fac. 01 F.01.-- 193.170.67.0 - FREE 02 A.01.01 193.170.68.0 193.170.69.0 INTIBNET UNIDO/IPCT/TDP/INF 02 A.01.01 193.170.70.0 193.170.71.0 HTL-RANKWEIL HTL Rankweil 08 A.05.03 193.170.72.0 193.170.79.0 TUNET-S6,7,... TU-Wien 16 A.16.-- 193.170.80.0 193.170.95.0 OEAW-C-NETS OeAW, Inst. Netzwerke 08 A.04.04 193.170.96.0 193.170.103.0 KHS-LINZ-NETS Univ. of Arts and Ind. Design 08 A.04.04 193.170.104.0 193.170.111.0 ARSENAL BVFA Arsenal by. A.Deutsch 04 A.02.02 193.170.112.0 193.170.115.0 ONB Oest.Nat.Bibliothek, Pl.Stelle 02 A.01.01 193.170.116.0 193.170.117.0 ODVNET Umweltbundesamt Ozon-DV by H.Mir 02 A.01.01 193.170.118.0 193.170.119.0 HTL-STP Hvhere technische BLA St.Pvlten 04 A.01.03 193.170.120.0 193.170.123.0 ATMAGL Mag. der Stadt Linz 04 A.04.-- 193.170.124.0 193.170.127.0 FHS-HGBG-LAN FHS-Hagenberg 08 A.04.04 193.170.128.0 193.170.135.0 MHS-GRAZ HS f. Musik u. darst. Kunst 02 A.01.01 193.170.136.0 193.170.137.0 UNILEOBEN Uni Leoben 02 A.01.01 193.170.138.0 193.170.139.0 PIB-WIEN PIB Paedag.Inst.d.Bundes 02 A.02.-- 193.170.140.0 193.170.141.0 VIE-EBS1,2 Vienna-EBS1 serial outgoing 02 A.01.01 193.170.142.0 193.170.143.0 AMDA-AT AMDA-AT Linz 04 A.03.01 193.170.144.0 193.170.147.0 ADBK Akad. d. bildenden Kuenste Wien 04 F.04.-- 193.170.148.0 193.170.151.0 - FREE 04 A.02.02 193.170.152.0 193.170.155.0 BDANET Bundesdenkmalamt by H.Hatzinger 04 A.04.-- 193.170.156.0 193.170.159.0 HTL-LEONDING HTL-Leonding 02 A.02.-- 193.170.160.0 193.170.161.0 UBA-VIENNA Umweltbundesamt Wien by H.Mirth 01 A.01.-- 193.170.162.0 HTL-WIEN-1 HTL Wien I, Schellinggasse 01 A.01.-- 193.170.163.0 OESTAT Statistisches Zentralamt by W.St 02 A.01.01 193.170.164.0 193.170.165.0 PTT01NET G.Dir. f.d. Post u. Telegr.verw. 02 A.01.01 193.170.166.0 193.170.167.0 OEHZA OeH Zentralausschuss by K.Egger 08 A.08.-- 193.170.168.0 193.170.175.0 ZAMGRZ ZA f. Meteorologie u. Geodynamik 08 A.06.02 193.170.176.0 193.170.183.0 MOZNET HS MudK "Mozarteum" Salzburg 08 F.08.-- 193.170.184.0 193.170.191.0 - FREE 64 A.01.63 193.170.192.0 193.170.254.0 AEN Ars Electronica Ctr./Mus.3rd.Mil ------------------------------------------------------------------------------------------------ Statistics: Addresses assigned: 130 Addresses reserved: 111 Addresses free: 15 Biggest block ass'd: 64 Size Number Free Ass'd Reserved Comments... 1 10 2 7 0 2 15 0 15 13 4 8 4 17 9 8 7 8 34 18 16 4 0 45 8 32 -- -- -- -- 64 1 0 1 63 see note 1) 128 -- -- -- -- General comments: Some of the previously reserved address blocks have already been cut in size and reassigned or reassigned completely. In at least 3 instances reserved blocks (up to size 8) have been completely allocated within 9 month after the initial allocation. We will continue to reallocate small reserved blocks from this address range to new applications for 1 or two addresses, especially when no growth in the networks -holding the reservation- has been seen within a reasonable timeframe. Note 1: A tentative reservation was made (to be reviewed by the NCC) for a newly built "Museum of Electronic Arts and Museum of the 3rd Millenium", in favour of allocating a large block in the beginning that is potentially never used. -------------------------------------------------------------------------- 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 --------------------------------------------------------------------------

1 0

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