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] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Previous message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carsten Schiefner
ripe-wgs.cs at schiefner.de
Tue May 4 16:58:52 CEST 2010
Richard, all - Richard Hartmann wrote: >> This discussion will of course be followed up on this mailing list. > > 3) Although I am in the comfortable position of being able to use PA > space exclusively, if the usage of PI space has indeed changed over > time, there seem to be three possible solutions: > > a) Force the users of said PI space to become LIRs and use PA space. I indeed think that convincing those PI space users to become LIRs after all bears quite some merits: "It regulatively makes sense to treat user groups the same way that are (almost) indistinguishable" is only one of them. Yet, I am not entirely sure what could be the convincing arguments (or in the absence thereof: the mild pressure) that should be applied to those PI space users. Oh, and yes: I am in favour of a v4/v6 harmonisation, too. Best, Carsten
- Previous message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]