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]/
[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 ]
michael.dillon at bt.com
michael.dillon at bt.com
Thu Nov 26 00:29:27 CET 2009
> we have much more than 65k customers, with IPv4 addresses > dispersed in many different /8 We therefore cannot easily > compress the IPv4 address and want to use the whole 32bit. > However, we plan to allocate only a /60 subnet to the end customer. > This results in a request for a /28 If you have a lot of customers then I see nothing wrong with giving an allocation larger than /32. There are clear technical reasons that make this necessary. However, I would like to see RIPE discourage end customer prefixes longer than /56 for general Internet access. In other words, I believe that you should get a bigger block than /28, big enough so that you can allocate /56 subnets to each customer. --Michael Dillon
- 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 ]
[ ipv6-wg Archives ]