2012-07 Draft Document and Impact Analysis will be produced (RIPE NCC Services to Legacy Internet Resource Holders)
Dear Colleagues, The discussion period for the proposal described in 2012-07, "RIPE NCC Services to Legacy Internet Resources Holders", has ended. A draft document and the RIPE NCC Impact Analysis will now be prepared for review. We will publish the documents shortly and we will make an announcement. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-07 Regards Emilio Madaio Policy Development Officer RIPE NCC
Emilio Madaio wrote:
Dear Colleagues,
The discussion period for the proposal described in 2012-07, "RIPE NCC Services to Legacy Internet Resources Holders", has ended.
A draft document and the RIPE NCC Impact Analysis will now be prepared for review. We will publish the documents shortly and we will make an announcement.
In this context, may I ask for clarification of intent and/or word-smithing, by the authors or the NCC, regarding the phrase in 2.6: "... the RIPE NCC will ... and may update the related entries in the RIPE Database from time to time to correspond to current actual situation."
You can find the full proposal at:
https://www.ripe.net/ripe/policies/proposals/2012-07
Regards
Emilio Madaio Policy Development Officer RIPE NCC
Thanks, Wilfried
On 27 Mar 2013, at 12:28, Wilfried Woeber wrote:
In this context, may I ask for clarification of intent and/or word-smithing, by the authors or the NCC, regarding the phrase in 2.6:
Although I attempted to clarify the intent in a message archived here: http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-February/002009.... , you and almost everyone on either of the mailing lists receiving this can't yet have seen how we tried to express this when revising the proposal for v3. Here's what's in my diff-minus-u-style change-tracking copy of the current text of the proposal: 2.6 No relationship ------------------- In cases where the current holder of Legacy Internet Resources cannot be contacted, does not reply to contact from the RIPE NCC or is unknown, there is no formal relationship between the holder and the RIPE NCC. - In such a case, the RIPE NCC will continue to provide those registry - services which are already being provided in respect of the Legacy - Internet Resource or Resources involved, and may update the related - entries in the RIPE Database from time to time to correspond to - current actual situation. + In such a case, the RIPE NCC + - will continue to provide any registry service element already + provided in support of each Legacy Internet Resource involved; + - will have no obligation to begin to provide any registry service + element not already provided in support of a particular Legacy + Internet Resource, even in case the service element is provided in + support of any other Legacy Internet Resource held by the same or + another Resource Holder; + - and may update the related entries in the RIPE Database from time + to time to correspond to the current actual situation. Less formally, this is intended to mean that the NCC should - not curtail service; - not be obliged to implement any missing service element; and - have scope to act to improve the accuracy of the data held. I hope this helps, and encourage you to ask if it doesn't help enough. Best regards, /Niall
On 27/03/2013 16:18, Niall O'Reilly wrote:
Less formally, this is intended to mean that the NCC should
- not curtail service; - not be obliged to implement any missing service element; and - have scope to act to improve the accuracy of the data held.
I hope this helps, and encourage you to ask if it doesn't help enough.
I think it helps to clarify the scope of the proposal, but suspect that paying a service fee for registration services creates an implicit contract between the legacy resource holder and the RIPE NCC. No doubt the NCC will be able to clarify this. Nick
On 28 Mar 2013, at 16:50, Nick Hilliard wrote:
On 27/03/2013 16:18, Niall O'Reilly wrote:
Less formally, this is intended to mean that the NCC should
- not curtail service; - not be obliged to implement any missing service element; and - have scope to act to improve the accuracy of the data held.
I hope this helps, and encourage you to ask if it doesn't help enough.
I think it helps to clarify the scope of the proposal, but suspect that paying a service fee for registration services creates an implicit contract between the legacy resource holder and the RIPE NCC. No doubt the NCC will be able to clarify this.
I'm looking forward to seeing the Impact Analysis. /N
participants (4)
-
Emilio Madaio -
Niall O'Reilly -
Nick Hilliard -
Wilfried Woeber