Last Call Review of draft-ietf-rtcweb-ip-handling-11

Request Review of draft-ietf-rtcweb-ip-handling
Requested rev. no specific revision (document currently at 12)
Type Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2019-02-15
Requested 2019-02-01
Authors Justin Uberti
Draft last updated 2019-02-17
Completed reviews Tsvart Last Call review of -11 by Joseph Touch (diff)
Genart Last Call review of -11 by Vijay Gurbani (diff)
Assignment Reviewer Joseph Touch
State Completed
Review review-ietf-rtcweb-ip-handling-11-tsvart-lc-touch-2019-02-17
Reviewed rev. 11 (document currently at 12)
Review result Ready
Review completed: 2019-02-17


This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC if you reply to or forward this review.

This document has no significant transport issues.

As a very minor issue, the document refers to the use of UDP "connect":

   Once a suitable remote IP has been determined, the implementation can
   create a UDP socket, bind it to the appropriate wildcard address, and
   tell it to connect to the remote IP.  Generally, this results in the
   socket being assigned a local address based on the kernel routing
   table, without sending any packets over the network.

It might be useful to be more clear that this is an OS command (not a protocol one). If the particular semantics of this command are relevant, that should be noted as well.