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

[Fred Baker <[e-mail]>]

I think the best approach is to start work on it, but decouple it from  
4/6 NAT. There is, for example, no serious question of how to embed an  
IPv6 address into an IPv6 address.

I would recommend considering GSE as a basis - changing the prefix  
between two prefixes, such as a ULA and an operator prefix.

There will be issues with multiple subnet IDs; from a topology hiding  
model one wants them to go away, and in such a case there is a problem  
with host ID collisions. And if the "inside" and "outside" prefixes  
are of different lengths (ISP allocated a /56 but in my ULA I am using  
the equivalent of a /48 and embedding more than 2^8 prefixes in it)  
that also creates an issue. I would suggest a simple approach - tell  
the edge network operator that they need prefixes from the upstream  
LIRs that allow them to map subnets statelessly - that if they have  
2^9 subnets their upstreams need to give them a prefix no longer than  
64-9 bits, and they need to enumerate them so as to allow stateless  
translation.

On Oct 24, 2008, at 1:41 AM, Margaret Wasserman wrote:

>
> On Oct 23, 2008, at 1:35 PM, Dan Wing wrote:
>> BEHAVE is being re-chartered, so if the community wants BEHAVE to
>> do NAT66, now is a good time to tell the IESG to include NAT66 in
>> BEHAVE's charter.  (as you all know.)  The new charter, at this
>> time, does not include NAT66.
>>
>> And I only stated my desire to avoid the 'third rail'; the IESG can
>> certainly decide they want NAT66 standardized.  Based on my
>> understanding of how NAT66 would work, it would belong in BEHAVE.
>
> Thanks, Dan.  This is very reasonable.
>
> So, what's the best way forward?  Perhaps I could write a draft,  
> sent a pointer to behave, and we could have a discussion over the  
> next couple of weeks about whether the community does/doesn't want  
> to include this in the new behave charter?
>
> Margaret
>
> _______________________________________________
> 46translation mailing list
> [e-mail]
> https://www.employees.org/mailman/listinfo/46translation

_______________________________________________
v4v6interim mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/v4v6interim