[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 6rd - Rapid Deployment on existing IPv4 infrastructures - a new approach



Le Tuesday 12 February 2008 12:29:19 Rémi Després, vous avez écrit :
> The I-D is available at:
> http://www.ietf.org/internet-drafts/draft-despres-v6ops-6rd-ipv6-rapid-depl
>oyment-00.txt
>
> (A previous file name had to be replaced by this one, more compatible
> with recommended practices, and including the now selected WG reference)

Lets clear: /64 subnet at the CPE plain simply SUCKS. Badly.

Next thing is IPv6 NAT, when people try to "cascade" access points/routers 
within their home network. Like it or not, CPEs MUST get more than /64, and 
MUST support downstream prefix delegation.

Last time I checked, Free was not assigned the whole IPv4 address space. I 
assume they don't want to provide the Rapid Deployment service to customers 
of *other* ISPs. So while they do only have a /32 IPv6 prefix, they don't 
need to burn 32 further bits to keep track of each of the IPv4 address of 
each of their customers. Storing the 24 lower order bits should be 
sufficient. And this leaves 64-32-24=8 rouable bits per customer.

-- 
Rémi Denis-Courmont
http://www.remlab.net/

Attachment: signature.asc
Description: This is a digitally signed message part.