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] Re: 200 customer requirements for IPv6
- Previous message (by thread): [address-policy-wg] Re: 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] Re: 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Per Heldal
heldal at eml.cc
Mon Jan 16 14:38:35 CET 2006
On Wed, 4 Jan 2006 11:12:19 +0100, "Marc van Selm" <marc.van.selm at nc3a.nato.int> said: [snip] > > Again, I think we have a solid work around but looking at the controversy > that > this discussion has caused, a non ISP-centric policy would be useful. > The policy might seem ISP-centric, but that's just a coincidence. It reflects the opinion of many in the ops-community that it doesn't make sense to migrate to IPv6 until it is able to provide more than just an extended address-space. At least not as long as there is no *real* shortage of v4-addresses. Unfortunately, very few seem willing to admit that in public. The current policy will work in a future that has mechanisms to separate identifiers from locators. Maybe some people should revise their short-term expectations wrt IPv6. //per -- Per Heldal http://heldal.eml.cc/
- Previous message (by thread): [address-policy-wg] Re: 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] Re: 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]