July 1999 - lir-wg - mailman.ripe.net

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

24 Jun '01

Hi Joao! >If the reference is by name then when I query the DB I will get the list of >persons with that name, right? Right. >Whether the object belongs to the person or not is not going to save this >person from being contacted. From the point of view of the database and the >user querying it, the object belongs to that person. Right >The link is via a name. > >Now we substitute the reference by name with a reference by nic handle >pointing to the same person. >What is the difference? > >ALMOST NONE except that: True, for the case where there is a strict one-to-one mapping, e.g the recursion using the name returns *one* object. What do you suggets to do with the case where the recursion, based on the names, returns a *set* of objects? I can see 2 approaches (at least): - do not perform the handle substitution for that referring object and put it on the list of those requiring human intervention - expand the xxxx-c: list (which? the tech-c:?) to refer to *all* objects, but by ref'ing their handles While human beings are quite clever in selecting the "proper" instance of a person: object (by looking at country, address, email,...) a script might be quite clueless with that respect :-) 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 --------------------------------------------------------------------------

3 3

Final RIR ASO Proposal Submission to ICANN
by Mirjam Kuehne 27 Aug '99

27 Aug '99

Dear Colleagues, Thank you very much for the support received regarding the 'Draft proposal for a MoU-based ASO'. As you know, your support is essential to the process and therefore very much appreciated. Discussions following the announcement of the draft proposal on 8 July 1999, and at the recent open ASO meeting which took place at the IETF in Oslo, modifications to the draft proposal were suggested. Following discussions between the RIR excecutive boards, taking into account the collective interests of our communities, further adjustments were made to the proposal which we believe will enhance the prospect of its adoption by ICANN. A proposal for the formation of an ASO has now been formally submitted to ICANN jointly by the Regional Internet Registries: APNIC, ARIN and RIPE NCC. The 'Proposal for a MoU-based ASO' can be found on the RIPE NCC Web site under the 'Current Issues' section at: http://www.ripe.net/info/ncc/icann.html Below please find the modified sections of the draft text as well as comments supporting the motivation for each of these changes. As the adjustments to this proposal have been made for clarity purposes to ensure fair and open processes in all regions, we hope that we can count on your continued support. Kind Regards, Mirjam Kuehne RIPE NCC 2. The Address Council. a. Members. ----------- [original text:] Each RIR signatory of the MOU will appoint two [2] individuals to the Address Council by means of their own choosing. No individual can serve on the Address Council and be on the staff of a RIR at the same time. [final version:] Each RIR signatory of the MOU will select three [3] individuals to the Address Council using the following process: i Annually the RIR will issue a public call for nominees to the Address Council at least 90 days before the RIR's policy meeting. Any individual can submit a nomination to the RIR. ii The due date for this call shall be 30 days before the meeting. iii The nominees must be individuals. iv A list of all nominees who agree to run for the Address Council must be posted on the RIR's web page at least 15 days before the meeting along with a statement from each nominee who wishes to make one. v Selection of the RIR's members of the Address Council will be made via an open and transparent procedure. The individuals selected for the Address Council must not be staff members of the RIR. COMMENTS: Concerns were raised that having only two [2] Address Council members appointed per region would not allow for sufficient representation. Therefore the number was changed to three [3] per RIR signatory. When additional RIRs sign the MoU this will be revised in order to keep the number of Address Council members at a practical size. Principles for the selection of Address Council members were stated in section 3.b. of the original draft proposal. These methods have been refined and included in this section for further clarification. However, please note that the selection process of the Address Council members will be defined by the regions via an open and transparent procedure. b. Term. -------- [original text:] The term of Address Council members will be 2 years. Removal will be pursuant to procedures established through the MOU. (Initial terms will be 1 and 2 years to provide initial conditions for staggered terms.) [final version:] The term of Address Council members will be 3 years. Removal will be pursuant to procedures established through the MOU. (Initial terms will be 1, 2 and 3 years to provide initial conditions for staggered terms.) COMMENTS: With the increased number of Address Coucil members one additonal term has been defined. c. Powers/Duties of the Address Council. ---------------------------------------- ii Qualifications of ICANN Directors. [original text:] No more than 1 of the ASO-appointed Directors may come from the same geographic region. [final version:] a) No more than 1 ASO-appointed Director may come from the same geographic region. (This proposal assumes the regions defined in the ICANN by-laws.) b) No ASO-appointed Director may serve simultaneously on the Address Council. COMMENTS: The additional sentence under a) is to clarify the word 'region' in this context. Parapraph b) was added as no clear prohibition against Address Council members also serving on the ICANN board was stated. d. Address Policy Development. ------------------------------ [final version:] One paragraph was added to this section: In addition the Address Council may accept, for consideration, proposals for changes to global IP address policy from any interested individual. COMMENT: One may imagine a circumstance where it would be more practical to approach the ASO directly to support the fair and open consideration of a proposal in order to stress equal opportunity for all interested parties. In any case, all proposals received by the ASO will be reviewed by the RIR signaories and the community as described in this section following the above noted addition: In all cases when the Address Council reviews proposals for new global policies or proposed modification to existing policies in this area it will first solicit the opinions of all of the RIR signatories of the MOU and of the public. 3. Annual Open Meeting. (General Assembly) a. Hosting an open meeting. --------------------------- [original text:] The Address Council will periodically host an open meeting ("General Assembly") for promoting discussion and receiving input regarding the work of the ASO. A General Assembly meeting will be held once per year, and will permit open participation by all interested individuals. [final version:] The Address Council will periodically host an open meeting ("General Assembly") for promoting discussion and receiving input regarding the work of the ASO. A General Assembly meeting will be held *at least* once per year, and will permit open participation by all interested individuals. COMMENT: It was felt that the number of meetings should not be restricted in this document. The important point here is that there should be *at least* one meeting per year. b. Selection of Address Council Members. ---------------------------------------- [original text:] Ninety days prior to each General Assembly, ICANN and the Address Council shall make an open call for nominations to any potential vacancies in the Address Council. The results of this call will be forwarded to each RIR signatory to the MOU for their information. Each RIR signatory to the ASO MOU will be entitled to select two [2] members of the Address Council by means of its own choosing. The terms of the appointees will be determined by the appointing RIR. [final version:] Ninety days prior to each annual open meeting, ICANN and the Address Council shall make an open call for nominations to any potential vacancies in the Address Council. The results of this call will be forwarded to each RIR signatory to the MOU for their information. Each RIR signatory to the ASO MOU will be entitled to select three [3] members of the Address Council using the process described in Section 2a. COMMENT: This has been changed in order to make the section consistent with the principles outlined in section 2.a (see above). 4. Open Proceedings and Documents. b. ASO Proceedings ------------------ [original text:] All discussions of ASO business will be conducted on or reported on a publicly-archived mailing list accessible through the ICANN/ASO web site. The schedule for the ASO meetings will be posted 90 days in advance of the meeting date. The agenda for the Address Council and annual open meetings will be posted on the ICANN/ASO web site at least 30 days before the meetings. The minutes from all ASO meetings will be publicly posted on the ICANN/ASO web site within 30 days of the meeting. [final version:] All discussions regarding ASO policy formation will be conducted on or reported on a publicly-archived mailing list accessible through the ASO web site. The schedule for the ASO meetings will be posted 90 days in advance of the meeting date. The agenda for the Address Council and annual open meetings will be posted on the ASO web site at least 30 days before the meetings. The minutes from all ASO meetings will be publicly posted on the ASO web site within 30 days of the meeting. In the unlikely event that the policy formation discussions involve confidential commercial data that was presented in an address allocation process the above disclosures must be done in a way to protect the confidentially of that data. COMMENT: The location of the documentation to be published has been more clearly specified (on the ASO web site). The last sentence has been added in order to explicitly exempt confidential data from publication as defined in the existing RIR operational procedures. 6. Recognition. [original text:] 7) That the introduction of a new RIR must be based on a "Sound Business Plan". The plan must be reviewed by ICANN and by the existing RIRs. The process for creating a new RIR must be included in the MOU. [final version:] 6) That the proposed RIR has clearly defined procedures open to all interested parties regarding ensuring fair representation of constituents within the region of coverage in the policy development process. COMMENT: This paragraph was added in order to ensure open and transparent processes of policy development in all new and existing RIRs. For your information, please note that the order of points in appendix A has slightly changed, resulting in the number change noted above.

3 2

New ACK ?
by mediaWays Hostmaster 29 Jul '99

29 Jul '99

[ Moderator note: changed ripe-list(a)ripe.net -> lir-wg(a)ripe.net ] Hi, does anyone know the new ACK !!! format for denic KKs ? MfG "hostmaster of the day" ________________________ Stephan Mankopf +49 5241 80 88729 hostmaster(a)mediaways.net

4 4

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

15 Jul '99

The URL is actually: http://www.ripe.net/lir/registries/ipv6.html Sorry about that. Paula paula(a)ripe.net writes: * #################################################### * This message was not delivered to * registry(a)broadsystem.com * Sender was informed with a copy of this message * #################################################### * * 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

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