Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)
draft-ietf-mmusic-rtsp-nat-evaluation-16

[Ballot comment]
Editorial remarks by David Black, posted here for the record as I understand that they are already taken into account in Magnus' temp version.

-- Editorial Comments:

Section 4.6.5

OLD
The three way latching is significantly securer than
NEW
Three way latching is significantly more secure than

I saw a number of other editorial items in the newly added text that
I'll leave to the RFC Editor.

idnits 2.13.02 found an obsolete reference:

  -- Obsolete informational reference (is this intentional?): RFC 3489
    (Obsoleted by RFC 5389)

This is intentional, as the draft refers to an obsolete STUN feature
in that obsolete RFC, so this idnits complaint can be ignored.

[Ballot comment]
I have two comments:

1. The introduction states that multiple levels of NATs (including CGNs) were  not considered.  While I understand the history behind this draft and the time frame when it was written, I would really like to see something mentioned about the potential impact on the different techniques.  (I could only find a brief discussion in section 4.4 (Latching) to the potential effect of multiple NATs/CGN.  Something similar to the text there would be ideal.)

2. Section 8 (Security Considerations) mentions the fact that "three way latching as well as ICE mitigates these security issues and performs the important return-routability check".  Please add a reference to this important check.  I looked at RFC5245 (ICE), but could not find that check described (just connectivity checks); is that what you're referring to with a different name?

IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-mmusic-rtsp-nat-evaluation-14, which is currently in Last Call, and has the following comments:

We understand that, upon approval of this document, there are no IANA Actions that need completion.

While it is helpful for the IANA Considerations section of the document to remain in place upon publication, if the authors prefer to remove it, IANA doesn't object.

If this assessment is not accurate, please respond as soon as possible.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (The Evaluation of Different Network Address Translator (NAT) Traversal Techniques for Media Controlled by Real-time Streaming Protocol (RTSP)) to Informational RFC


The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document:
- 'The Evaluation of Different Network Address Translator (NAT) Traversal
  Techniques for Media Controlled by Real-time Streaming Protocol
  (RTSP)'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-06-13. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Some helpful state about this draft is available here: http://www.ietf.org/mail-archive/web/mmusic/current/msg13385.html.

Abstract


  This document describes several Network Address Translator (NAT)
  traversal techniques that were considered to be used for establishing
  the RTP media flows controlled by the Real-time Streaming Protocol
  (RTSP).  Each technique includes a description of how it would be
  used, the security implications of using it and any other deployment
  considerations it has.  There are also discussions on how NAT
  traversal techniques relate to firewalls and how each technique can
  be applied in different use cases.  These findings were used when
  selecting the NAT traversal for RTSP 2.0, which is specified in a
  separate document.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mmusic-rtsp-nat-evaluation/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mmusic-rtsp-nat-evaluation/ballot/


No IPR declarations have been submitted directly on this I-D.