This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2007-01 review phase comments (was: Feedback from the WG chairs ...)
- Previous message (by thread): [address-policy-wg] Feedback from the WG chairs group on 2007-01
- Next message (by thread): [address-policy-wg] 2007-01 review phase comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Niall O'Reilly
Niall.oReilly at ucd.ie
Fri May 16 11:09:52 CEST 2008
On 15 May 2008, at 10:02, Gert Doering wrote: > This means that the proposal needs to re-enter review phase, and we'll > ask you to closely look at it, and confirm that you're expressing > support for the *latest revision* of the proposal. I have just now, as requested, looked closely at http://www.ripe.net/ripe/draft-documents/ripe-424-draft.html, which I understand to be the latest revision of the proposal, and have the following comments to make as part of the re-entered review phase. These comments include (a) a request for information from RIPE-NCC and (b) a proposal to remove certain text from the draft. 6.9 Anycasting TLD Nameservers Fine. 9.0 PA vs. PI Address Space 3 proposed changes: 1/3: PI concept, distinction from PA, contract options: fine; 2/3: Suggested warning on potential disadvantages of PI: fine; 3/3: Retroactive application of new policy to existing non-PA: problematic. It is certainly necessary to make explicit that the proposed new policy applies to existing PI assignments, and thus modifies the contractual conditions supporting any such assignment. I expect that existing contractual arrangements actually support fair and reasonable modifications to the terms and conditions involved. It would be useful to have confirmation from RIPE-NCC that this is indeed the case. I doubt that RIPE-NCC has formal competence to modify the terms and conditions (whatever they might be!) under which ERX assignments were made. It is therefore most likely futile for the RIPE community to request any such action of RIPE-NCC. I propose removing the text "including address space marked as Early Registration (ERX)". I see no other problem with this proposed change. By the way, and off-topic for the present discussion, I would see it as a useful exercise to encourage holders of ERX resources to "regularize" their position, perhaps along the lines of ARIN's "Legacy Registration Services Agreement". Best regards, Niall O'Reilly University College Dublin IT Services PGP key ID: AE995ED9 (see www.pgp.net) Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: </ripe/mail/archives/address-policy-wg/attachments/20080516/bfc4865a/attachment.sig>
- Previous message (by thread): [address-policy-wg] Feedback from the WG chairs group on 2007-01
- Next message (by thread): [address-policy-wg] 2007-01 review phase comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]