Re: [PATCH 3/5]: Introducing CCMPS

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

 



On 10/12/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote:
> [DCCP]: Introducing CCMPS
>
> This introduces a CCMPS field for setting a CCID-specific upper bound on the application payload
> size, as is defined in RFC 4340, section 14.
>
> Only the TX CCID is considered in setting this limit, since the RX CCID generates comparatively
> small (DCCP-Ack) feedback packets. The CCMPS field includes network and transport layer header
> lengths. The only current CCMPS customer is CCID4 (via RFC 4828).
>
> A wrapper is used to allow querying the CCMPS even at times where the CCID modules may not have
> been fully negotiated yet.
>
> In dccp_sync_mss() the variable `mss_now' has been renamed into `cur_mps', to reflect that we are
> dealing with an MPS, but not an MSS.
> Since the DCCP code closely follows the TCP code, the identifiers `dccp_sync_mss' and
> `dccps_mss_cache' have been kept, as they have direct TCP counterparts.
>
> Signed-off-by: Gerrit Renker <gerrit@xxxxxxxxxxxxxx>

Signed-off-by: Ian McDonald <ian.mcdonald@xxxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux