All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Jero <sj323707@ohio.edu>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 01/07] dccp: support for the exchange of NN options in
Date: Sat, 16 Jul 2011 17:43:30 +0000	[thread overview]
Message-ID: <4E21CDC2.6070505@ohio.edu> (raw)
In-Reply-To: <1310650955-5159-2-git-send-email-gerrit@erg.abdn.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]

You have my signed-off-by for this patch.

I'm not clear if you intend to use this top commit message for the
entire patch, if so, see comment below.

> In contrast to static feature negotiation at the begin of a connection, which
> establishes the capabilities of both endpoints, this patch introduces support
> for dynamic exchange of feature negotiation options.
> 
> Such a dynamic exchange is necessary in at least two cases:
>  * CCID-2's Ack Ratio (RFC 4341, 6.1.2) which changes during the connection;
>  * Sequence Window values that, as per RFC 4340, 7.5.2, should be sent "as
>    as the connection progresses".
> 
> Both are NN (non-negotiable) features. Hence dynamic feature "negotiation" is
> distinguished from static/pre-connection negotiation by the following:
>  * no new capabilities are negotiated (those that matter for the connection
>    are negotiated prior to setting up the connection, comparable to SIP);
>  * features must be understood by each endpoint: as per RFC 4340, 6.4,
>    Sequence Window is "Req'd" and Ack Ratio must be understood when CCID-2
>    is used as per the note underneath Table 4.
> 
> These characteristics are reflected in the implementation:
>  * only NN options can be exchanged after connection setup;

>  * 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 "Confirm R", or it will send an
>    empty Confirm (which will reset the connection according to FN rules).

This statement is confusing. While the receiving side will activate a
immediately, the sender will now wait for the CONFIRM before activating
the new value. This changed as a result of one of the merged patches. I
would recommend leaving this statement out.

>  * An Ack is scheduled directly after activation to accelerate communicating
>    the update to the peer.
> 
> Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
> Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>

Signed-off-by: Samuel Jero <sj323707@ohio.edu>


Samuel Jero
Internetworking Research Group
Ohio University


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-07-16 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 13:42 [PATCH 01/07] dccp: support for the exchange of NN options in established state 1/2 Gerrit Renker
2011-07-16 17:43 ` Samuel Jero [this message]
2011-07-18  1:59 ` [PATCH 01/07] dccp: support for the exchange of NN options in Gerrit Renker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E21CDC2.6070505@ohio.edu \
    --to=sj323707@ohio.edu \
    --cc=dccp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.