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 ]
Remco van Mook
remco.vanmook at eu.equinix.com
Tue Dec 1 12:29:51 CET 2009
"Nothing is so permanent as a temporary government program." -- Dr. Milton Friedman If we decide to hand out /24s to 6RD and we think that¹s not a waste of address space (even though nobody has been able to give me an satisfactory answer I¹m willing to throw in the towel) make that a permanent allocation, not a temporary one. The pretense that people will actually hand back that prefix is, let¹s say, not consistent with current experiences in IPv4. Once it¹s out of the bag it¹s out of the bag, never to return. Remco On 01-12-09 12:10, "Mikael Abrahamsson" <swmike at swm.pp.se> wrote: > 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 > > This email is from Equinix Europe Limited or one of its associated/subsidiary companies. This email, and any files transmitted with it, contains information which is confidential, may be legally privileged and is solely for the use of the intended recipient. If you have received this email in error, please notify the sender and delete this email immediately. Equinix Europe Limited. Registered Office: Quadrant House, Floor 6, 17 Thomas More Street, Thomas More Square, London E1W 1YW. Registered in England and Wales No. 6293383. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20091201/170633d6/attachment.html>
- 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 ]