Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE charter

[" Rémi Denis-Courmont" <[e-mail]>]

On Friday 24 October 2008 14:22:51 ext Iljitsch van Beijnum, you wrote:
> > You only need a large
> > address space if you want STATELESS mappings.
>
> Wouldn't every internal address map to a single external address in
> that case? That wouldn't use very many addresses.

For stateless mapping, unless you have some extra assumptions about the 
internal addresses (e.g. only SLAAC EUI-48 are used, no static address, no 
privacy addresses), you need as large an external prefix as the internal one.

> No, in this case we also do a mapping per flow, but the difference is
> that we don't need to understand the transport to recognize flows
> because we have the flow label, and because we use a different source
> address per flow we don't need to recognize incoming packets by their
> port numbers so referrals work.

NAT44 provide N:1 internal:external address mappings, not N:M. With N:M you 
will break applications that _do_ work with NAT44, including a very long tail 
of HTTP-based applications. Making NAT66 worse than NAT44 is unlikely to fly, 
even with those people who _do_ want to deploy NAT66.

-- 
Rémi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/v4v6interim