Re: [PATCH 2/5]: Support for the exchange of NN options in established state

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

 



On 10/5/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote:
> [DCCP]: Support for the exchange of NN options in established state
>
> This patch introduces a variant of feature negotiation which differs from
> feature negotiation during connection setup in the following aspects.
>  * It is a restricted variant - only NN options can be exchanged;
>  * NN options are activated directly after validating them. The rationale is
>    that a peer must accept every valid NN value (RFC 4340, 6.3.2), hence it
>    will either accept the value and send a ConfirmR, or it will send an
>    empty Confirm (which will reset the connection according to FN rules).
>  * An Ack is scheduled directly after activation to accelerate communicating
>    the update to the peer.
>
> The facility of exchanging NN options is currently only needed by CCID2's Ack Ratio
> (RFC 4341, 6.1.2). Although the code will in principle work for any NN option, this
> fact has been the reason for limiting the current use to Ack Ratio.
>
> Signed-off-by: Gerrit Renker <gerrit@xxxxxxxxxxxxxx>

Acked-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