Dear all, As you all know, the RIPE NCC was actioned to review the current IP& ASN policy document, ripe-185 (European Internet Registry Policy and Procedures) and to present a raw first draft to the lir-wg August 29, 2001. Please find this draft attached. As outlined in Hans Petter's mail below, the task was to update the current policy document with policy changes implemented since the publication of ripe-185. Based on feedback from the membership, the objective was also to create a more condensed, clear and concise policy document that would make it easier for new LIRs and End Users to learn relevant IPv4 and ASN policies and procedures. Experience with the previous policy document clearly showed that new members found ripe-185 very complex. There was a clearly expressed need for a simpler and clearer document that could be used on a daily basis as a reference document for the LIRs. I have followed the structure in Hans Petter's mail below and have produced a first draft for the lir-wg to revise. The changes between this document and ripe-185 are the following: - Structure The structure has been completely revised in order to improve readability and making the information easy to find. - Update of policy The policy changes that have taken place since the last published version of the policy document have been incorporated in this draft. In addition to this, the document has been shortened to make it easier for readers to find the relevant information. Some sections have been completely removed as they are either covered elsewhere and/or not within the scope of a concise policy document. The sections that have been removed are: - Reverse Delegation procedures - Separate RIPE Document will be published (Reverse Delegation Policy distilled and kept) - Mergers, transfers & Closures - Separate RIPE Document will be published - RIPE NCC Registration Services - information available on the web (not policy nor procedure) - Request documentation - Available in the Supporting notes document (Currently ripe-220) (Sections pertaining to policy kept) - Obtaining an AS Number - Available in ASN request form and supporting notes (currently ripe-147) (ASN Policy kept however) - Routing considerations - (not policy nor procedure) As explained, this is a first draft produced by the RIPE NCC to facilitate the writing of this document as requested by the lir-wg. We are now welcoming the feedback on the community and the work of the editorial commitee to finalise this policy document. Kind regards, Nurani *--------------------------------------------------------* | Nurani Nimpuno <nurani@ripe.net> | | Internet Address Policy Manager | | RIPE Network Co-ordination Centre | | http://www.ripe.net | *--------------------------------------------------------* ------- Forwarded Message
From: "Hans Petter Holen" <hph@online.no> To: lir-wg@ripe.net Subject: a Proposal to replacing RIPE 185 Date: Wed, 22 Aug 2001 22:17:43 +0200
Dear Working Group. Last year we set up the 17th of May task force to help the RIPE NCC identify potential improvements to the handeling of requests sent to hostmaster@ripe.net. May of theese have been implemented with success. The continuing growth of the number of LIRs does however call for other meassures to be taken.
One of the suggestions by the task force and by the RIPE NCC hostmasters was to improve the IP address request form. A fruther analysis of the underlying problems seems to indicate that the shortcomings of the form is merely a symptom. There are clear indications that the whole policy and procedure document, RIPE 185, would benefit from an overhaul.
After studying this document which was created when CIRD was still young and unknow to large parts of our community, we have found that it cotains a lot of usefull information, which is strictly speaking not Policies or Procedures. Rewriten in a clearer and more concise way we may archive a much better common understanding between the individual LIRs and the RIPE NCCC hostmasters.
Our hypothesis is therefore that by creating a new strucure for documenting policy and procedures with better examples, and work on clearifying the language in the policy statements the work load of the RIPE NCC hostmasters may be reduced drasticaly. This is due to the fact that for a large propotion of the requests handeled by the RNH's there is lacking information the NRH's. By making it clear to the LIRs that it is the LIRs responsibility to request from the customer and make sure all relevant information is in the application before it is submittet to the RNH, we belive the total time spent, both by RNH's, and by LIR staff will be significantly reduced.
We have therefor proposed the following structure for a replacement of RIPE 185: "Addressing Policies and Procedures for the RIPE NCC service region"
(Abstract, Introduction, Scope) Internet Address Space and the Internet Registry System Policy framework Policies Glossary References Appendices (bitboundary chart, examples etc)
Remove the following sections: All instructions on how to fill out an IP or ASN request form (in separate "supporting notes" ripe docs) PA vs PI (Is described in ripe-127) RIPE NCC RS (mailboxes, ticketing system, robot etc) (Instructions on website) Inaddr procedures (policy to be left in) (separate ripe doc will be created) Routing considerations
Our proposal is that the RIPE NCC will present a first draft by doing the ground work on the document, re-writing some sections in a more clear and concise manner. This will then be presented to the lir-wg and the editorial committe for comments and input.
We also belive that there is a strong need to publish all policy changes as RIPE document. If there is a need to reduce the administrative overhead of changing the procedures and policies document for every policy document, the changes and amenedments could be made in a single (not more than one at a time !) "Amendments to Policies and procedures.
I have spent some days with Nurani and Sabrina at the RIPE NCC and discussed various ways to do this, and our proposal is to form a RIPE-185bis editorial team to facilitate discussion on the lir-wg mailing list and working group meetings and summarise the community consensus.
----- Hans Petter Holen, http://hph.home.online.no Phone: +47 40 20 39 16, Stalsberggt 28 B, 2010 Strxmmen, Norway