Ian McDonald wrote: > In introduction you say: > In order for the [RFC4340] encapsulation to pass through Network > Address Translation (NAT) devices, these devices must be updated > to recognize and properly modify DCCP. This is the long-term > objective for DCCP, and work is underway to specify the necessary > operations. > > As regards to work underway there is an implementation in the Linux > kernel to provide NAT/connection tracking for DCCP and it is > believed to work well - basically does the same as UDP/TCP. This has > been in the Linux kernel for sometime now, so may be of some use for > this work. I am guessing/hoping that Rémi's draft-denis-behave-nat-dccp-00.txt documents what the Linux DCCP NAT code does? The BEHAVE working group has a milestone to adopt a DCCP NAT document, and draft-denis-behave-nat-dccp-00.txt is the only candidate document at this point. -d
