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 ]
João Damas
joao at bondis.org
Tue Aug 9 22:35:30 CEST 2011
On 9 Aug 2011, at 18:25, Jim Reid wrote: Small intermission. > > Please explain Sascha. I just don't get it. IPv6 deployment isn't hindered by the availability of PI space. At least not in the general case. Can you give some actual examples where a problem getting PI IPv6 space has (or is) a showstopper for IPv6 deployment? There are people who clearly sustain the opposite so this is not a statement that has been without challenges which mostly seem to be grounded on the needs of enterprises. Particularly because they can get this in IPv4 and how do you sell anyone a technology that gives you "less" than the previous one? > >> This policy change is about NOTHING else than aligning the IPv6 PI policy with >> the IPv4 PI policy we have for ages. > > That's all very well. However it may be the answer to the wrong question. Suppose we didn't have IPv4 PI space at all. Would we invent this concept for IPv6? If so, why? If not, why not? > Problem is, Jim, we do have IPv4 PI, and people compare fruits. Joao
- 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 ]