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

[Margaret Wasserman <[e-mail]>]

> If #2 does not remind you of how we got into so much trouble nat44,  
> well it should. Because of the impact on NAT66 on applications, if  
> IETF does decide to do NAT66 specifications, I think it is very  
> important that the specification is developed not only in the  
> context of v6ops people but is also developed with input of folks  
> from applications that need to use it. Today that would roughly mean  
> behave.

I agree with you that NAT66 could (and probably would) have impact on  
other layers, so this problem is not specific to any one area.  I also  
share your concerns about working on NAT66 within v6ops or any other  
IPv6-specific WG, because we may get a solution that has unknown or  
unacceptable impact on applications.

I agree that the behave WG would be the best forum for this work,  
which is why I have suggested adding NAT66 to the behave charter while  
it is currently in the process of being updated.  Several people  
expressed interest in this work, but Dan Wing, who is one of the  
behave chairs, indicated that he considers NAT66 to be a political  
"third rail" and that he doesn't want to go there.  Magnus, one of the  
transport ADs, said that he sees "some interest" interest in NAT66,  
but that it is not a priority item.  He wants to finish "the important  
things first" before using resources to discuss NAT66.

I consider NAT66 to be an important and timely topic. So, I'm trying  
to figure out a way that we can make some progress on a NAT66 document  
in some other forum.  I'd be happy to bring it to behave when the  
current work has been completed, but that's likely to take quite a  
while, and I'm hoping we can make some progress on NAT66 in the  
meantime.

Do you think it would be better to just wait until behave finishes its  
current work and is ready to recharter again?

Margaret


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