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] PI for IPv6 == PI for IPv4?
- Previous message (by thread): [address-policy-wg] PI for IPv6 == PI for IPv4?
- Next message (by thread): [address-policy-wg] PI for IPv6 == PI for IPv4?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
boggits
boggits at gmail.com
Wed Aug 10 11:53:40 CEST 2011
On 10 August 2011 10:33, Jasper Jans <Jasper.Jans at espritxb.nl> wrote: > I am all for learning from our mistakes - but we cannot deploy policy that excludes a group of people > when it comes to IPv6 that already qualified for ipv4 PI. If we really have to do the dual-homing > requirement (I'm of the opinion we don't) then at the very least make it so that the clause states > that you need to be dual-homed for any new IPv6 PI, or must already own IPv4 PI. This way you can > prevent people from getting it that do not have it yet but allow the ones that already run IPv4 PI to > get IPv6 PI. That would be an option, adding the requirement for Dual Homing or existing IPv4 PI would seem to solve the issue - it might even increase the number of v4 PI requests and speed depletion which some would see as a good thing. J -- James Blessing 07989 039 476
- Previous message (by thread): [address-policy-wg] PI for IPv6 == PI for IPv4?
- Next message (by thread): [address-policy-wg] PI for IPv6 == PI for IPv4?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]