- lir-wg - mailman.ripe.net

IPv6 allocation from IANA.
by Paula Caslav 15 Jul '99

15 Jul '99

Hello colleagues, The RIPE NCC is pleased to announce that we have received an allocation of IPv6 address space from the IANA and can start accepting requests for sub-TLA allocations. If you wish to request a sub-TLA from the RIPE NCC, please write to hostmaster(a)ripe.net. Please note that you have to be a Local IR in order to apply. Early next week we will publish ripe-195, an IPv6 request form and ripe-196, the IPv6 policy document. A current version of the policy document can already be seen on: http://www/lir/registries/ipv6.html The only change in the ripe-196 document will be the addition of a section on reverse DNS. A draft version of the request form is now available if you write to hostmaster(a)ripe.net. I include the announcement message from the IANA below. Kind regards, Paula Caslav RIPE NCC ------- Forwarded Message From: "IANA" <iana(a)ISI.EDU> To: <iana-announce(a)ISI.EDU> Subject: Delegation of IPv6 address space Date: Wed, 14 Jul 1999 12:32:07 -0700 (text/plain) Internet Community, After much discussion concerning the policy guidelines for the deployment of IPv6 addresses, in addition to the years of technical development done throughout the Internet community, the IANA has delegated the initial IPv6 address space to the regional registries in order to begin immediate worldwide deployment of IPv6 addresses. We would like to thank the current Regional Internet Registries (RIR) for their invaluable work in the construction of the policy guidelines, which seem to have general consensus from the Internet community. We would also like to thank the efforts of the IETF community and the support of the IAB in making this effort a reality. If you have further questions concerning this issue, please contact your RIR, or you may also contact the IANA at iana(a)iana.org. The policy guidelines can be found online at one of the Regional Internet Registries: http://www.apnic.net http://www.arin.net http://www.ripe.net This is an historic moment in the continued development of the Internet. Thank you for your valuable support and participation in the Internet community. Josh Elliott On Behalf of the IANA Staff ------- End of Forwarded Message

1 0

Re: IMPORTANT: ICANN ASO, Your Expicit Support Required.
by Hans Petter Holen 15 Jul '99

15 Jul '99

[ Moderator note: changed ripe-list(a)ripe.net -> lir-wg(a)ripe.net ] Dear Colleagues, as chair of the RIPE local-ir working group I would realy urge you all to read the proposal and voice your active support. I have not been directly involved in creating theese documnets, just been following the disussions at RIPE meeting and now even at the Open ASO meeting tuesday at IETF here in Oslo. The documents to study are pointed to from http://www.ripe.net/info/ncc/icann.html and the specific proposal is in http://www.ripe.net/info/ncc/icann.cover.letter.html http://www.ripe.net/info/ncc/icann.mou.html The discussions on the ASO list may be viewed at http://www.ripe.net/mail-archives/aso-discuss/index.html for those who are not at the list. In my personal belif this current proposal reflecs the opinions that have been started from the RIPE community. Idealy we should have had a RIPE meeting to discuss this proposal in detail, but we do not have time for that. However the principles of this proposal were indeed discussed in detail on the last RIPE meeting. Please read the proposal and voice your active support as indicated by the original message from Daniel. Sincerely, Hans Petter Holen Local IR WG Chair

1 0

Regional Internet Registries Announce Proposal for an ICANN ASO
by RIPE NCC 08 Jul '99

08 Jul '99

Regional Internet Registries Announce Proposal for an ICANN Address Supporting Organisation (ASO) Amsterdam, The Netherlands -- 8 July 1999 -- The Reseaux IP Europeens Network Coordination Centre (RIPE NCC), the American Registry for Internet Numbers (ARIN), and the Asia Pacific Network Information Centre (APNIC) have published today a collectively developed policy draft describing the Address Supporting Organisation (ASO). The proposal will be submitted to the Internet Corporation for Assigned Names and Numbers (ICANN) later this month. At this stage, the RIPE NCC has distributed the proposal to its membership, the RIPE community and the general public for comment. The current Regional Internet Registries (RIRs) ensure that IP address space is managed in a globally consistent, fair and responsible manner. The primary activity of the RIRs is the allocation of Internet resources required for the stable and reliable operation of the Internet. In addition, the RIRs play a key role in Internet administration directly in keeping with the interests of their membership and the Internet community. The RIPE NCC has carried out these activities in Europe and surrounding areas since 1992. Policies governing these activities are developed in an open process accessible to all interested parties. Global policies have long been established in a bottom-up method whereby the Internet community develops policies that are co-ordinated among the RIRs and the Internet Assigned Numbers Authority (IANA) that were ultimately approved by IANA. These structures are currently established in all regions. The regional processes are open and transparent and have existed for several years in the RIPE NCC service region through RIPE, a collaborative organisation open to all parties. The main purpose of RIPE is to discuss technical and policy issues affecting the Internet Service Providers in the RIPE NCC service region. The ASO is part of the ICANN structure established to formalise activities previously carried out by IANA. The ICANN bylaws call for an ASO to co-ordinate Internet address policy development. As the activities of IANA related to IP address administration will be formally transferred to ICANN, the RIRs are defining the structure of the ASO building on the existing and well established processes. The collective proposal reflects the desire of the Internet community to be represented through the successful regional structures and not be compelled to participate in another global process to defend their interests. Similar to the set-up of the Protocol Supporting Organisation and the Domain Name System Supporting Organisation, the ASO proposal is based on the formation of a Memorandum of Understanding among ICANN and the Regional Internet Registries. The cover letter and draft proposal for a MOU-based ASO document can be found under the current issues section at: http://www.ripe.net/info/ncc/icann.html - About RIPE Network Coordination Centre (RIPE NCC) Established in 1992 and located in Amsterdam, The Netherlands, the Reseaux IP Europeens Network Coordination Centre (RIPE NCC) is one of three Regional Internet Registries providing resources necessary to support the operation of the Internet. The RIPE NCC is a membership based association and is open to anyone using the RIPE NCC services, primarily Internet Service Providers (ISPs). The services provided to its members ensure the fair and impartial distribution of global Internet resources in the RIPE NCC service region. These resources include IP address space and Autonomous System (AS) numbers. The organisation currently provides services for members in over 80 countries. The activities and services are defined, performed, discussed and evaluated in an open manner. In all of its activities, the RIPE NCC observes strict neutrality and impartiality with respect to individual members. For further information please see: http://www.ripe.net/ - About American Registry for Internet Numbers (ARIN) http://www.arin.net/ - About Asia Pacific Network Information Centre (APNIC) http://www.apnic.net - About Internet Corporation for Assigned Names and Numbers (ICANN) http://www.icann.org Press Contact: RIPE NCC Tel: +31 20 535 4444 / Fax +31 20 535 4445 rendek(a)ripe.net

1 0

Converting named references to NIC handle references
by Engin Gunduz 29 Jun '99

29 Jun '99

Dear collegues, As discussed and agreed to in the mailing lists, we will be converting unambiguous named references in the admin-c and tech-c fields of as-macro, autnum, community, dom-prefix, inet-rtr, mntner and role objects to NIC handle references, on 1 July, 1999, at 17:00, GMT. The process will take around half an hour, and during the process the updates will be queued. Whois queries will not be affected. The maintainers of the affected objects will get notifications about the changes. The conversion on domain and inetnum objects will be done at a later date, due to substantial time they require for this process. If you have any questions, please do not hesitate to contact us. Regards, Engin Gunduz RIPE NCC DB Group

1 0

admin-c in inetnum
by Paula Caslav 24 Jun '99

24 Jun '99

Hello all, It's good to see so much discussion. Just to clarify something, the admin-c can be a role object. This is something that was decided 1 or 2 RIPE meetings ago. The latest release of the database code supports this fully now. When you do a recursive look-up of an inetnum object you will now see any role objects that were referenced in the admin-c attribute (in the past you would only see role objects referenced in tech-c but not admin-c). I will wait until the end of the week for responses, and then try to summarize the views here and come up with a suggestion. Kind regards, Paula Caslav RIPE NCC

2 1

Re: Modifying references to contact info in the RIPE DB
by Wilfried Woeber, UniVie/ACOnet 24 Jun '99

24 Jun '99

>I explicitly excluded those objects from this run. Great. >I knew this thing was going to be a bit polemic so I am trying to split into >smaller problems and stages that we can all agree to. Well, complex, at least. I fully support your approach! >Hopefully every step will reduce the number of objects that need repairs. And >believe me, it's not the same to have to fix 250000 objects than to fix 25000. >Somehow the latter seems a bit more feasible (from a "let's deal with this" >attitude). Certainly. >So, can we agree to proceed with our suggestion as stated below? >** >Change references by names to references by nic handle where these are unique >(there are not already more than two persons with the same referenced name). >** I agree. >For the cases where the ambiguity is already there: we'll look at them, try to >categorize them Sounds interesting. I really like the approach taken by Poul-Henning with his IP address page. Maybe we can come up with a similar list, e.g. categorized by object type, and within the object type by LIR, TLD, AS-#, Maintainer... >and maybe identify another subset which can be handled by >drawing information from some other source. >We'll get back to you with our suggestion (and we take the two you mention as >input). Any input is most welcome. Wilfried.

1 0

Re: Modifying references to contact info in the RIPE DB
by Janos Zsako 24 Jun '99

24 Jun '99

> From owner-db-wg(a)ripe.net Thu Jun 24 15:23:02 1999 > From: Joao Luis Silva Damas <joao(a)ripe.net> > ALMOST NONE except that: > from that point on if someone else with a name equal to one already in the > database is entered into the database the reference will not be made ambiguous > while if we leave it as a reference by name it sure becomes ambiguous. I agree with Joao that there is virtually nothing to lose. I don't think it is better to have a reference by name with a single incorrect instance of a person object with that name, rather than a NIC-handle reference to the same incorrect instance... (By incorrect instance I mean a person object with the same name, but who has nothing to do with the referring object). At the same time the benefit is obvious (see above). Also, the longer one delays this process, the better the chances to have several instances to be handled manually (i.e. to try to identify the correct person object from several ones with the same name). Just my 2 filler (.01 HUF). :)) Janos

1 0

Re: Modifying references to contact info in the RIPE DB
by Janos Zsako 24 Jun '99

24 Jun '99

> From owner-db-wg(a)ripe.net Thu Jun 24 14:35:25 1999 > From: "Wilfried Woeber, UniVie/ACOnet" <woeber(a)cc.univie.ac.at> > One of the key things might be to make sure that we (you :-) can perform > a roll-back, if it turns out that we've messed up things badly... My feeling is that if one replaces the name reference with the NIC-handle, at least as long as the referenced person object is not deleted (which I suppose cannot be deleted once it has an other object referencing it), the roll-back is always possible (i.e. one could re-substitute the NIC-handle with the name). Although, I feel this would be in the best case useless, since either there is no other person object with the same name, or the other object(s) was(were) added later. Janos

1 0

Re: Modifying references to contact info in the RIPE DB
by Wilfried Woeber, UniVie/ACOnet 24 Jun '99

24 Jun '99

Hi Joao! >So, in spite of the concerns raised (valid as they are) I would still >vote to go ahead on this one as proposed. > >What do people think? Well, some as yet unstructured rants, off the top of my head... I'd love to see some sort of test-run being performed, e.g. going ahead and putting the result up as the (or an additional) test db? One of the key things might be to make sure that we (you :-) can perform a roll-back, if it turns out that we've messed up things badly... Is there any chance to do some sort of dry-run, and put up some sort of list of cases deserving investigation? Poul's page is a very good thing, indeed, although tackling a different aspect. My reasoning is that whatever can be fixed by humans, in a distributed project, before the brute-force attack would make life easier. Most probably basic rule #1 applies to my comments: use the brain before using the keyboard :-) Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Vienna University : Fax: +43 1 4277 - 9 140 Universitaetsstrasse 7 : RIPE-DB (&NIC) Handle: WW144 A-1010 Vienna, Austria, Europe : PGP public key ID 0xF0ACB369 --------------------------------------------------------------------------

2 1

Modifying references to contact info in the RIPE DB
by Joao Luis Silva Damas 24 Jun '99

24 Jun '99

Dear all, the Database consistency project has been going forward in its goals since RIPE 33 (eg. addition of nic handles to all objects without one.) Statistics and reports about the "status" of the database can be seen at http://www.ripe.net/db/state/. We will keep adding information to these pages as the project progresses. We are now at the point where we would like to tackle the issue of references by name in the admin-c, tech-c and zone-c. As a next step, we would like to have references by nic handles (which are unique) instead of references by name (which can be non -unique). At this point, we would like to automatically go through all the references by name which can uniquely be assigned to a person or role object and substitute them by references to their nic handles. This will prevent these references from becoming non-unqiue in the future. Later we will go through the process of fixing the non-unique references left in the database. This process requires user intervention since we can't decide who "owns" a particular set of resources. For this later stage, we will be preparing reports that we will send to all maintainers for whom we detect objects with inconsistencies and try to get them fixed. Information about this part will be sent to the lists in a few weeks. We would like to do this after as much as possible has been done by automatic means to correct inconsistencies so that human effort is reduced to a minimum. If there are any concerns regarding this move, please make them known before next Friday (June 25th). Looking forward to your comments, Joao Damas Database Group RIPE NCC

4 5