- lir-wg - mailman.ripe.net

Re: Document announcement
by Wilfried Woeber, UniVie/ACOnet 18 Oct '93

18 Oct '93

Daniel, | | > - agree on a fixed document name both for the RIPE document store and local | > versions | > [acceptable] | |We have implemented fixed aliases. This had been the plan form the beginning |but implementation was lacking. It is done now and I hope it is |acceptable to you and the other local IRs. I think this is pefectly ok. Now I (again) have a "fixed" name that I can put into the heads of our users, attach to the ACOnet version of this document on our FTP-Server and put into local documentation. And I prefer the new "useful" names for these documents over ripe-xxx. Thanks a lot, Wilfried.

2 1

RE: Document announcement
by Wilfried Woeber, UniVie/ACOnet 15 Oct '93

15 Oct '93

>A revised document below European Internet Network Number Application Form >is available from the RIPE document store. > > >Ref: ripe-095 >Title: European Internet Network Number Application Form >Title: and Supporting Notes > Is there a major change in the contents, format or function of this document? I'm a bit worried, about the name change from ripe-088 to ripe-095, because right now our users/customers get comfortable with the idea to just "pick up ripe-88 from the ftp server" whenever they apply for a new Class C address. Also we would have to update all local text to refer to the new document. So I see 3 possible approaches: - keep the ripe-document number the same unless there is a major change in content, maybe appending some version or date information [preferred] - agree on a fixed document name both for the RIPE document store and local versions [acceptable] - we have to store the document (and/or it's local version) with a fixed name (different from the RIPE document id) on our system [not desirable but workable] Anybody else with strong feelings? Wilfried.

4 4

Current RIPE Forms and Procedures Available in Fixed Place
by Daniel Karrenberg 15 Oct '93

15 Oct '93

The files with the current RIPE forms and procedures can from now on always be found in a fixed place in the RIPE dcoument store. This makes it possible to refer to the current version of these documents in other documentation. There are two subdirectories in the document store called "forms" and "procedures" respectively. forms: This directory contains the current RIPE NCC application forms. All of these are links to the current RIPE documents also available in ~ftp/ripe/docs/ripe-docs. as-appl - Application for an Autonomous System Number netmum-appl - Application for an IP network number (IP address space) procedures: This directory contains descriptions of RIPE NCC procedures. All of these are links to the current RIPE documents also available in ~ftp/ripe/docs/ripe-docs. inaddr-delegation Delegation of subdomains of 193.in-addr.arpa and 194.in-addr.arpa ncc-funding Fnding of NCC core activities. netnum-assignment Assignment of IP netowrk numbers by European Internet Registries routing-registry Description of the RIPE Routing Registry

1 0

Document announcement
by Anne Lord 01 Oct '93

01 Oct '93

New/Revised RIPE Document Announcement -------------------------------------- A revised document below European Internet Network Number Application Form is available from the RIPE document store. Ref: ripe-095 Title: European Internet Network Number Application Form Title: and Supporting Notes Author: Anne Lord, Daniel Karrenberg Date: 1st October, 1993 Format: PS=63045 TXT=26784 bytes Obsoletes: ripe-088.txt Obsoleted by: ripe-095{ps,txt} Updates: Updated by: Old: Short content description ------------------------- Updated version of the European IP network number request form. The new version contains some new text on "Requesting Additional address space". 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/ripe-docs" followed by the command "get <filename>". For example "get ripe-095.txt". 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 host 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 ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-095.txt

1 0

Database beta: Bug in enkeys.pl
by Daniel Karrenberg 28 Sep '93

28 Sep '93

Gabor Kiss <kissg(a)sztaki.hu> found a bug in enkeys.pl. His fix is included below. It has been incorporated in the beta release. Future announcements like this will only be made to the list <db-beta(a)ripe.net>. Be sure to get on this list if you use the beta release. Daniel *** /tmp/T0a09361 Tue Sep 28 17:40:00 1993 --- enkeys.pl Tue Sep 28 17:17:28 1993 *************** *** 1,9 **** # enkeys - extract keys from entry # # $RCSfile: enkeys.pl,v $ ! # $Revision: 0.13 $ ! # $Author: marten $ ! # $Date: 1993/08/19 14:53:37 $ # require "misc.pl"; --- 1,9 ---- # enkeys - extract keys from entry # # $RCSfile: enkeys.pl,v $ ! # $Revision: 0.14 $ ! # $Author: dfk $ ! # $Date: 1993/09/28 16:16:57 $ # require "misc.pl"; *************** *** 39,45 **** $i = $#result; while ($i >= 0) { $result[$i] =~ tr/A-Z/a-z/; ! $result[$i] =~ tr/a-z0-9-,\.'\///cd; if (length($result[$i])<2) { splice(@result, "$i", 1); } --- 39,45 ---- $i = $#result; while ($i >= 0) { $result[$i] =~ tr/A-Z/a-z/; ! $result[$i] =~ tr/a-z0-9\-,\.'\///cd; if (length($result[$i])<2) { splice(@result, "$i", 1); }

1 0

Beta RIPE database software
by Marten Terpstra 27 Sep '93

27 Sep '93

folks, I have made a beta database distribution for you all, with the emphasis on BETA. I just packed all the sources and stuff together, documentation and manual pages have not been updated to include all the changes we made over the last weeks, so this is "as is". A "real" distribution will follow whenever I am back in November, or Daniel may make one before that. You can find it on: ncc.ripe.net:/dbase-beta/dbase-beta.tar.Z NOTE this is NOT on ftp.ripe.net. The directory dbase-beta is NOT readable, but the dist can be fetched anyway. Have fun, -Marten

2 1

Guarded Objects are now better protected
by Daniel Karrenberg 24 Sep '93

24 Sep '93

Dear colleagues, A recent accident has caused us to protect the guarded objects in the database a little better before the maintainer attribute is fully implemented. Guarded objects can from now on only be updated thru the manual procedure which involves plausibility checking by NCC staff. The manual procedure uses the old mailbox ripe-dbm(a)ripe.net. Any updates for guarded objects sent to the auto-dbm(a)ripe.net mailbox will be refused with the error message: *ERROR*: guarded objects cannot be updated via automatic procedure If you get such an error, re-send the update to ripe-dbm. Once the maintainer attribute is implemented authorisation will be handled automatically. Daniel PS: We hope to have the update procedure for guarded *attributes* deployed next week.

1 0

action item RIPE 15.3
by Ruediger Volk 24 Sep '93

24 Sep '93

Hi, this is the wording as promised (for input to the local IR session) in the RIPE plenary today. Please find below proposed text, followed by some more remarks. (BTW the other day I got a request to expand the allocation for a certain federal German bureaucrazy and told them on the phone "first document current use" - and they asked for a written request/explanation why they should send that information...) Wording for action item RIPE 15.3 (the intension was: make applicants aware that their use of assigned adress space may be inspected, in particular when requesting additional allocations) When additional network numbers are needed by an organization the application sould include information on the utilization of address space already held by the same organization. This information needs to include the numbers of actually used/unused IP network numbers, and the numbers of actually used adresses, and installed subnets; more structural information may be apropriate to substantiate the new request. This data for previously assigned network numbers provides essential input for global monitoring of utilization of IP address space and feedback to registry operation. ----------- This text could be inserted into the explanation of the IP application template, and used in messages reporting allocations to applicants. When introducing the notion of "assigning additional address space" into the application document set it might be useful to also add hints that explain: The goal of the evaluation is to - ensure proper use is made of the available address space (i.e. high utiliziation) - have single contiguous blocks of addresses assigned if possible and apropriate (so routing information can be aggregated) For this a good estimate of real network requirements is needed and planning not just for the immediate needs or a specific parts of a network is encouraged. One further comment: When future policies should foresee auditing the use of assigned numbers for the purpose of reclaiming unused or underutilized space, the wording could/should be adjusted to mention eventual calls for usage reports. Cheers, Ruediger Ruediger Volk Universitaet Dortmund, Informatik IRB DE-NIC D-44221 Dortmund, Germany E-Mail: rv(a)Informatik.Uni-Dortmund.DE Phone: +49 231 755 4760 Fax: +49 231 755 2386

2 1

Re: RIPE NCC Temporary Registrar
by postel＠ISI.EDU 23 Sep '93

23 Sep '93

Daniel: Hi. An interesting idea that may get us out a a few difucult situations, but i'd really like to keep this to a very few cases, and much prefer to use local registrar whenever possible. --jon.

1 0

RIPE NCC Temporary Registrar
by Daniel Karrenberg 23 Sep '93

23 Sep '93

Dear Jon (and others), during last week's RIPE meeting the question of start up toplevel domains has been discussed in the local registry working group. The concern (spawned by the situation in Lebanon) is that when first starting it is difficult to find a registrar acceptable to the community within the country and this could delay things very much. The RIPE NCC was asked and accepted to offer a temporary TLD registry service for start up TLDs in and around Europe as necessary. The procedure would be to wait for about a dozen registrations and then have the registered organisations agree on a local registrar. I hereby offer this service whenever you may think it is appropriate. Please note that we still feel that having a local registrar accepted by the local community is much preferrable to an external registrar. This offer is intended only to speed up the creation and population of new TLDs where necessary and appropriate. Regards Daniel

1 0