September 1993 - lir-wg - mailman.ripe.net

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

Local-IR Draft Minutes
by Daniel Karrenberg 21 Sep '93

21 Sep '93

Thanks to Martijn we have prepared the draft minutes of the WG meeting last week. Please read and comment. The final minutes will be produced next monday. Daniel ------ Minutes of the Meeting of the local-ir working group at the 16th RIPE meeting. Date: September 16th 1993 Location: NIKHEF Amsterdam Chairman: Daniel Karrenberg Minutes: Anne Lord, Daniel Karrenberg, Martijn Roos Lindgreen The proposed agenda (see below) was accepted after extra points were added: - - discuss documentation that is needed - - discuss the procedure to set up new top level domains 0. Reports for information: The DE-NIC will be shut down and moved to another place at the 15th of December. It will be funded by all the DE service providers. A workshop was held on wednesday morning. As it was a closed meeting no minutes were taken. The workshop was considered useful and will be held in conjunction with a RIPE meeting on a yearly basis. A more extensive reporting was asked for, but was considered inappropriate because of the informal nature of the workshop. 1. Proxy network entries: Many participants felt that the network proxy entries should be avoided. After intensive discussion it was decided that a draft policy for this will be worked out by Duncan Rogerson and Daniel Karrenberg. Input from those service providers who are in favor of the proxy entries is necessary. 2. Autonomous Systems Database Template The AS Database template was formally accepted. 3. Should we maintain a list of local IRs and publish it? After intensive discussion it was decided that a list of Internet Registries will be maintained and published by the RIPE NCC. This list will be sorted by country and contain all local provider- and non-provider registries. A draft of the list will be circulated on the local-ir list by the NCC. 4. Input for the Activity Plan It was suggested to add the following activity: Maintain and regularly publish the list of local Internet registries Another suggestion is to strengthen the local registry liaison with tutorials and workshops. 5. AoB It was felt that more documentation is needed. The following volunteers were appointed to edit the documents: FAQ on CIDR and subnetting: GARR/NIS Why return unused IP address space and be a good network citizen: Daniel Karrenberg The problem of finding registrars for new toplevel domains was raised; there was consensus that the RIPE NCC shall offer to serve as temporary registrar for toplevel domains in our region, until about a dozen subdomains have been registered. Agenda for the local IR WG During RIPE Meeting Thursday September 16th 1993 0. Reports for Information - short reports of significant events at local IRs - short reports of significant events at the NCC - short report from local IR workshop the previous day 1. Proxy Network Entries in RIPE Database Some service providers have expressed the wish to act as proxy for some of their clients when registering in the RIPE database in order to protect their clients privacy. Under the present policy this is not possible. A proxy policy could be established. Is this a goo idea? Proposed points: - only on explicit request from client - only if proxy has 24x7 NOC - proxy must reveal client's identity to Internet Registries - proxy must reveal identity on request of other network operator in case of ongoing problems OR take immediate measures to stop traffic 2. Autonomous Systems Database Template Has been circulated. Should be accepted as this. 3. Should we maintain a list of local IRs and publish it? Speaks for itself 4. Input for new NCC activity plan. What do you really want? and pay for it! 5. AoB

1 0

Tomorrow's BOF
by mnorris＠dalkey.hea.ie 14 Sep '93

14 Sep '93

Daniel et al I can't get out of here today so I'll be a bit late at tomorrow's IR bof; should be there in time for the concluding coffee, though ;-) I don't have any war stories as such, just a few things that occur to me: 1. Most clients are beginning to learn about subnetting and are using single Class C addresses for multiple link IP addresses. 2. Some clients complained that they had not been allocated enough addresses. Such clients are always those who have done nothing about getting themselves connected, despite the advice and encouragement we have offered them. Our answer to them is that when they really need more addresses to connect hosts to the Internet, they should ask their local registry. They can't complain. 3. The service provided by the RIPE NCC as the European IP registry is an excellent one. The secondary nameservice for the reverse zones in 193.1.0.0 was a great idea and well implemented. Cheers. Mike

1 0

Draft Agenda local-ir WG
by Daniel Karrenberg 13 Sep '93

13 Sep '93

Draft Agenda for the local IR WG During RIPE Meeting Thursday September 16th 1993 0. Reports for Information - short reports of significant events at local IRs - short reports of significant events at the NCC - short report from local IR workshop the previous day 1. Proxy Network Entries in RIPE Database Some service providers have expressed the wish to act as proxy for some of their clients when registering in the RIPE database in order to protect their clients privacy. Under the present policy this is not possible. A proxy policy could be established. Is this a goo idea? Proposed points: - only on explicit request from client - only if proxy has 24x7 NOC - proxy must reveal client's identity to Internet Registries - proxy must reveal identity on request of other network operator in case of ongoing problems OR take immediate measures to stop traffic 2. Autonomous Systems Database Template Has been circulated. Should be accepted as this. 3. Should we maintain a list of local IRs and publish it? Speaks for itself 4. Input for new NCC activity plan. What do you really want? and pay for it! 5. AoB Daniel

1 0

(no subject)
by Daniel Karrenberg 13 Sep '93

13 Sep '93

Dear all, The closed local-IR workshop on Wednesday 15th September will take place in room Z009 (round the corner from the main auditorium), starting at 10.00 am. The proposed agenda is as follows: A G E N D A Local-IR Workshop September 15th, 10am. 1. Procedures at the RIPE NCC The NCC will describe how registry actions are being done at the RIPE NCC. 3. Procedrues at Local Registries Local Registries will describe how they do things. 2. Criteria for allocations: rfc1466 Short review of RFC1466. 3. Review and discussion of past "interesting" cases (ncc) 4. Review and discussion of past "interesting" cases (Local-ir's) See you there Daniel

1 0