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/
[ipv6-wg] RE: [address-policy-wg] IPv6 allocations for 6RD
- Previous message (by thread): [ipv6-wg] RE: [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [ipv6-wg] RE: [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mohacsi Janos
mohacsi at niif.hu
Thu Feb 24 10:27:04 CET 2011
On Wed, 23 Feb 2011, Wyatt Mattias Gyllenvarg wrote: > Hi > > We would like to weigh in here. > We feel that it should be RIPEs policy to allocate ONE /32 to any LIR who > requests it for 6rd. > > 6rd is the only way for us to reach all our residential customers. Especially > those in Municipal Networks that are very slow to invest in their networks > and often do not have the competence and time to impelment IPv6. > > Also, Cisco has not yet implemented even a small part of the protective > mechanisms we rely on in IPv4 to secure our residential networks. Many of > these features are required to meet the demands contracted with the > customers. We cannot use native IPv6 until Cisco implements these features > and we have tested and rolled them out on hundreds of switches. > > 6rd bypasses all these issues. IF we can get a /32 for that purpuse. I think /32 for each LIR which wants to deploy 6RD is rather overwhelming: if you allocated /16 to your broadband customers from your IPv4 pool, then you might use that pool and for 6RD tunneling. You have allocated /32 in IPv6 from your RIR: Then you can omit the most significant 16 bits of (or less if you prefer) from forming the 6RD IPv6 prefix since it is always that 16 bit, and use only the least significant bits of IPv4 address which is 16 bits. Then at the end you decide to assign /56 for your broadband customers (which is acceptable - 256 subnets), then you can easily put all your broadband customers: 56-16 = 40 bits. You use only a single /40 for your broadband customers. If you allocate /8 for you broadband customers - with the same /56 IPv6 assignment, your IPv6 broadband allocations will be: 32-8 = 24 significant bit 56-24 = 32 bits for IPv6 broadband customers. Note: For non-mass deployment probably you don't want to use 6RD, but a real dual-stack deployment Best Regards, Janos Mohacsi > > -- > > Med Vänliga Hälsningar - Best regards > Mattias Gyllenvarg > Network Operations Center > Bredband2 > > ---------------------- end of line --------------------------- > >
- Previous message (by thread): [ipv6-wg] RE: [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [ipv6-wg] RE: [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]