Re: draft-ietf-dccp-udpencap-03 - 6-tuple

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Gorry.

Any comments, anyone? If not, I think we need should proceed with this new text, and announce WGLC for the updated version.

Small correction below, otherwise the text looks good to me.

On Feb 10, 2011, at 9:58 AM, Gorry Fairhurst wrote:

> My first attempt at replacement text reads:

[..snip..] all good this far.

>   The demultiplexing at a DCCP-UDP endpoint occurs in two stages:
> 
> 	1) In the first stage DCCP-UDP packets are demultiplexed
>        using the 4-tuple, <source address, UDP Source Port,
> 	DCCP Source Port, destination address, UDP Destination Port>.

I believe the DCCP source port should not be here.

> 	2) In the second stage, a receiving endpoint MUST ensure
> 	that two independent DCCP connections that were
> 	multiplexed to the
> 	same 4-tuple are not associated with the same connection
> 	in the DCCP module. The endpoint therefore needs to keep
>        state for the set of active DCCP-UDP endpoints using each
>        4-tuple. This may be achieved in one of two ways:

[..snip..]

- Pasi




[Index of Archives]     [Linux Kernel Development]     [Linux DCCP]     [IETF Annouce]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]

  Powered by Linux