Hi,
On 14 Feb 2008, at 20:13, Phelan, Tom wrote:
It's definitely my intention that DCCP-NAT happens in the end
nodes. It
isn't intended to be some middlebox intercepting a DCCP stream and
converting it. The end nodes originate the packets with DCCP-NAT
encapsulation. I'll try to make that more clear in the next revision.
Nice to hear about NAT for DCCP(-RAW) in Linux. To expand a bit on
the
above paragraph, I wouldn't expect DCCP-NAT in Linux to be implemented
below the DCCP layer as I imagine NAT for DCCP is. In my view, the
encapsulation to use (NAT, RAW, IPv4, IPv6) is chosen by the
application
and implemented (mostly) within the DCCP layer.
Allowing the application to choose runs into connectivity problems
when some applications support the UDP encapsulation, and some do
not. If we're going to define a UDP encapsulation - and it's not at
all clear to me that such a thing is a good idea - then I'd recommend
that we do so in a way that it can be done by the DCCP stack,
transparently to the applications, with a well-defined order for
trying native vs. encapsulated connection requests.
--
Colin Perkins
http://csperkins.org/
