[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google
  Web www.spinics.net

Re: I-D Action:draft-ietf-dccp-simul-open-06.txt




Thanks Magnus,

Please see my comments in-line.

Gorry

Magnus Westerlund wrote:
Hi,

Some comments on the new draft:

Section 2.2.1: One of the bullets is missing an "a" to read "At the time
..."
Will be fixed.


Figure 2: Is the figure really correct with the listen' state. Does it
really take two receive request events to go from invited to Respond?
Seems that the Invited to Listen' (receive request) should go directly
to Respond?
>
It wasn't the intention to imply two receptions were required, since the text says that INVITED->LISTEN' is triggered by a DCCP-Request, and then causes immediate transition to RESPOND.

I don't know how best to reflect this in the figure, so I'll suggest a footnote. Better ideas are most welcome!

Proposed new diagram:


        unspecified remote   +--------+   fully specified remote
       +---------------------| CLOSED |---------------------+
       |                     +--------+   send DCCP-Listen  |
       |                                                    |
       v                                                    v
  +--------+                                  timeout  +---------+
  | LISTEN |                           +---+-----------| INVITED |
  +--------+                           |   |           +---------+
       |                               |   |  1st / 2nd  ^  |
       |                 more than 2   |   |  retransm.  |  | receive
       |               retransmissions |   +-------------+  | Request
       |                               |    resend Listen   v
       |                               |               +---------+
       |                               +-------------->| LISTEN' |
       |                                               +---------+
       |                                                    |
       |  receive Request   +---------+    receive Request* |
       +------------------->| RESPOND |<--------------------+
          send Response     +---------+    send Response

* Note: A server that responds a DCCP-Request in the INVITED state, transitions to the LISTEN' state and then immediately transitions to the RESPOND state. This does not require reception of an additional DCCP-Request packet.

---------


Section 2.2.3: Should that have a section title?

Indeed:
Protocol Method for DCCP Client Endpoints

Otherwise I think the changes looks ok, although I haven't read them in
super detail nit-picking mode.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@xxxxxxxxxxxx
----------------------------------------------------------------------




[Kernel List]     [Linux DCCP]     [IETF Annouce]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]     [Linux Resources]

Powered by Linux