Skip to main content

Last Call Review of draft-ietf-tram-stun-path-data-03
review-ietf-tram-stun-path-data-03-secdir-lc-ladd-2016-02-17-00

Request Review of draft-ietf-tram-stun-path-data
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2016-02-11
Requested 2016-02-04
Authors Paal-Erik Martinsen , Tirumaleswar Reddy.K , Dan Wing , Varun Singh
I-D last updated 2016-02-17
Completed reviews Genart Last Call review of -03 by Wassim Haddad (diff)
Secdir Last Call review of -03 by Watson Ladd (diff)
Opsdir Last Call review of -03 by Lionel Morand (diff)
Assignment Reviewer Watson Ladd
State Completed
Request Last Call review on draft-ietf-tram-stun-path-data by Security Area Directorate Assigned
Reviewed revision 03 (document currently at 05)
Result Has nits
Completed 2016-02-17
review-ietf-tram-stun-path-data-03-secdir-lc-ladd-2016-02-17-00
Dear all,

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This document describes an extension to  STUN for determining the
characteristics of connections, useful in situations where hosts have
multiple interfaces. It does this by enabling
clients to send multiple requests and receive counts of how many
responses were transmitted.

This document was Ready with Nits. Some values need to be assigned by
IANA. It reuses existing security mechanisms from STUN, which do in
fact protect the integrity of messages
properly. I am worried about interoperability questions, but these
come from those earlier
RFCs, and so are outside the scope of this review.

Sincerely,
Watson