[BEHAVE] AD comments on draft-ietf-behave-turn-tcp-05

[Magnus Westerlund <[e-mail]>]

Hi,

I have reviewed the TURN TCP document and have the following comments.

1. Section 3.4 and 5.2, if the Turn server takes time to complete the
Connect request, can additional connect or other TURN requests be issued
with one connect request outstanding?

2. Section 5.2: Any consideration for timeout for the TCP connection
attempt from the server? Is that purely a server implementation choice?
Some minimal value the client can expect? Maybe a option to specify a
timeout for the client would be appropriate here?

3. Section 5.2: Why is the initial data buffered? Isn't it better to not
read from the socket until its peer TCP connection is available. That
way the stream will not advance until the data can be forwarded. Here
some implementation experience would be good to capture.

4. Section 5.3, shouldn't the connection attempt be checked against the
permissions before being accepted?

5. Section 5.5, what about data sent to the server? I assume that the
peer expects that data is sent prior to closing the server to client
connection.

6. Section 6.4 and 6.5 I expect to be section 7 and 8.



I will expect a revised ID.

Cheers

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------