Re: [BEHAVE] WGLC: draft-ietf-behave-turn-tcp-04

["Alfred E. Heggestad" <[e-mail]>]

Dan Wing wrote:
> BEHAVE is starting a 3 week working group last call (WGLC), ending August 19,
> for 
> 
>   draft-ietf-behave-turn-tcp-04
>   "Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations"
> 
> Please send technical comments to the BEHAVE list, and editorial comments to
> the authors.
> 

Here are my WGLC review comments on draft-ietf-behave-turn-tcp-04:


General:

  The document is well written and easy to read. 




=== Technical ===

5.2. Receiving a Connect Request

   "Otherwise, the server MUST initiate an outgoing TCP connection.  The
    local endpoint is the relayed transport address associated with the
    allocation. ..."

  ---> why does the local endpoint have to be the relayed transport address?
       is this a technical requirement to make the TURN/TCP protocol work?
       Normally an outgoing TCP connection using BSD sockets will use a
       random port as local endpoint. It is possible to use the same port
       as the TCP socket is listening on, but will require that things are
       initialized in the correct order. You should check that this does
       cause problems for implementors (ref: ICE tcp-SO discussion)



5.4. Receiving a ConnectionBind Request

  ---> 5th paragraph: "...Connect or Listen request..."

  I think the "Listen" request is not defined anymore ...







=== Editorial ===


Abstract, line 2:

    "to allows a" --> "to allow a"

    - some of the text in the abstract is bold in the HTML version

    last line:  "STUN Server"  -->  "TURN Server"





1. Introduction:

    "It also allows the client to initiate connections from that allocation to peers"

    would like to suggest instead:

    "It also allows the client to initiate outgoing TCP connections from that allocation to peers"
                                           ^^^^^^^^^^^^


    ", and accept connection requests from peers made towards that allocation"

    would like to suggest instead:

    ", and accept incoming TCP connections from peers made towards that allocation"




4.4 Receiving a Connection:


    line 12: "..attribute, mirrorred from ..."
                           ^^^^^^^^^
    - (typo)





- eof -