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] IPv6 allocations for 6RD
- Previous message (by thread): [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
michael.dillon at bt.com
michael.dillon at bt.com
Sun Nov 29 18:52:01 CET 2009
> /28 for any ISP having several IPv4 prefixes and committed > to deploy 6rd would be IMHO a good choice. > In practice, /60s to customer sites is quite sufficient, at > least in the short term. No, /60s to customer sites is not sufficient. It breaks the IPv6 model of fixed size site allocations which assumes that all sites will have /48 assignments unless they are private residences in which case they will have /56 prefixes. This uniformity is essential in order to allow people to innovate with IPv6. We should not force 6RD ISPs into making this kind of mistake, especially since 6RD is only a transition measure, and if an ISP gets /60 encoded into all their systems and processes, then they will be stuck with it long after 6RD has disappeared. That would be an IPv6 equivalent of the swamp, i.e. a short sighted, short term decision with negative long term consequences. --Michael Dillon
- Previous message (by thread): [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]