Reminder:Cosmetic Surgery Project, new revised RIPE Policy, document for IPv6 database objects
Dear colleagues, As part of the Cosmetic Surgery Project, the RIPE NCC is moving forward with a review of the policy document ripe-513, "Value of the "status:" and "assignment-size:" attributes in INET6NUM objects for sub-assigned PA space". At the request of the proposers of the original policy proposal that produced ripe-513, we’re sending a reminder about the document review and inviting the IPv6 Working Group Mailing List and Database Working Group Mailing List subscribers to participate in the review process. A draft of the policy document is now online and ready for community review at: https://www.ripe.net/ripe/readability/improving-the-readability-of-ripe-docu... We encourage you to read the edited draft of ripe-513 and send any comments to <address-policy-wg at ripe.net> by 10 June 2013. Kind Regards, Emilio Madaio Policy Development Officer RIPE NCC
On Tue, May 21, 2013 at 02:43:32PM +0200, Emilio Madaio wrote:
A draft of the policy document is now online and ready for community review at:
https://www.ripe.net/ripe/readability/improving-the-readability-of-ripe-docu...
May I suggest to omit the first occurence of "Only" in the section "2.1 Definitions" to keep to text more self-contained? Currently proposed text: Only the inet6num object may use the value of "AGGREGATED-BY-LIR" for the “status:" attribute and contain the attribute “assignment-size:”. Suggested change: The inet6num object may use the value of "AGGREGATED-BY-LIR" for the “status:" attribute and contain the attribute “assignment-size:”. Martin
participants (2)
-
Emilio Madaio
-
Martin Stanislav