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/address-policy-wg@ripe.net/
[address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
- Previous message (by thread): [address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
- Next message (by thread): [address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Elvis Daniel Velea
elvis at velea.eu
Thu Oct 20 18:47:19 CEST 2016
Hi Sander, I think I should've carefully looked at Ingrid's e-mail, maybe through some glasses :) Indeed, the message from Ingrid stated exactly what I was asking for. I am still hoping to receive a message (it can be in private) from one of the the NCC's ops to see if we can find out why my initial message did not make it to the list. Apologies for all the noise, at least this is not 'popcorn style' like yesterday's :) Regards, Elvis On 10/20/16 7:33 PM, Sander Steffann wrote: > Hello Elvis, > >> Therefore, I think that the RIPE NCC should talk to every single company >> holding a PI assignment from an ALLOCATED PI/UNSPECIFIED block and give >> them the option to give up on the maintenance of the IPs (and the right >> to transfer/sell) and transform them into ASSIGNED PA, or become a PI >> user - like all the others in the world - and sign a maintenance >> agreement with a LIR (and have the €50/year associated cost). > The message Ingrid sent on the 4th of August already stated: "The WG agreed that, where the LIR can document a mutual agreement that they administer the address space, a conversion from PI to PA should take place. In all other cases, assignments with the status ASSIGNED PI should be treated as being assigned by the RIPE NCC." > > So no need to talk to each and every resource holder. The responsibility is with the LIR to show documentation, and the default is to convert the assignment to normal PI. And that is as far as we need to go here. The rest are implementation details and should be left to the RIPE NCC. Let's not micro-manage who exactly they should talk to. > > So to summarise: I think what you want is already part of what the RIPE NCC proposed, modulo implementation details. So the previous message holds: RIPE NCC, please move ahead. > > Cheers, > Sander >
- Previous message (by thread): [address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
- Next message (by thread): [address-policy-wg] 2016-04 New Policy Proposal (IPv6 PI Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]