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 ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue Dec 1 12:10:21 CET 2009
On Tue, 1 Dec 2009, michael.dillon at bt.com wrote: > regardless of whether or not it is in RIPE policy, the /56 > for private residences is still good practice and is being > tracked by vendors. Just for the record, I've reconsidered and now agree with Michael that we should hand out /24 to ISPs who want to run 6RD, to facilitate /56 handouts to end customers. I would want a discussion on this being 6RD exclusive use and a 5 year temporary handout with option for 5 year extension per time until the community deems that 6RD is depreciated and this space should no longer be used for that. Should we reserve a /8 for 6RD use, approximately one per ASN? Should we just say that a certain /8 is for 6RD use and it's not even handled by RIRs but instead handled like GLOP space for multicast, ie that it's just the ASN mapped into this space? Do we need a /6 to handle future 32bit ASN increase in the next 10 years? Perhaps there should be this kind of IPv4-mapped-into-IPv6-per-ASN space available for general use, not being 6RD exclusive? I do think this should be temporary though, with the aim at this being deprecated in 5-10 years. -- Mikael Abrahamsson email: swmike at swm.pp.se
- 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 ]