Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
draft-petithuguenin-behave-turn-uris-08

[Ballot comment]
[3.1: ABNF changed to reference 3986]

3.2: I suggest changing "MUST be" to "is" in both cases. The MUSTs are gratuitous. Then get rid of the reference to 2119. It's unnecessary.

[Ballot comment]
3.2: I suggest changing "MUST be" to "is" in both cases. The MUSTs are gratuitous. Then get rid of the reference to 2119. It's unnecessary.

[Ballot discuss]


I have more or less the same comments on STUN.

TURN can inherit STUNs username/password feature, right?. If
a turns URI is used in some protocol for some use-case, (e.g.
webrtc) then shouldn't you REQUIRE that the username/password
is also not sent in clear in that protocol?

[Ballot comment]

- intro: are you saying that w3c goofed in soem draft of
their webrtc spec? The phrase "non-uniform syntaxes proposed"
could be read to mean that.

- I'd have been interested in knowing if the turns scheme is
implemented in section 6. (And thanks for section 6 btw.)

[Ballot comment]
In 3.1, last paragraph:

  The ,  and  components are passed without

The ABNF says turn-host and turn-port, not host and port.  This is not a major nit, but it would be good to be consistent here.  This inconsistency is repeated further in the document.

[Ballot comment]
I agree with Pete's comments about the ABNF, and share his dismay that these documents copy significant bits of standard ABNF productions from the URI document.  I think that's a Bad Idea.

Comment for the document shepherd: Thanks for a good, useful writeup!

[Ballot comment]
3.1: Could you not have gotten some of this syntax from another document?

3.2: I suggest changing "MUST be" to "is" in both cases. The MUSTs are gratuitous. Then get rid of the reference to 2119. It's unnecessary.

[Ballot comment]
1.  Introduction

  [RFC5928] defines a resolution mechanism to convert a secure flag, a
  host name or IP address, an eventually empty port, and an eventually
  empty transport to a list of IP address, port, and TURN transport
  tuples.

I'm not understanding the use of "eventually empty" in this paragraph, and that's not a term I saw in [RFC5928]. Is it familiar to those skilled in the art of TURN?

IESG/Authors/WG Chairs:

IANA has reviewed draft-petithuguenin-behave-turn-uris-05.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

We received the following comments/questions from the IANA's reviewer:

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

This document requests adding two Permanent URIs to the Permanent URI registry located at:

http://www.iana.org/assignments/uri-schemes

The Permanent URI schemes to be added are:

turn
turns

NOTE: Currently the Permanent URI registry is maintained through expert review as defined in RFC 5226.  We will initiate a request and send
this to the designated expert for review.

Note:  The actions requested in this document will not be completed
until the document has been approved for publication as an RFC.
This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard


The IESG has received a request from an individual submitter to consider
the following document:
- 'Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers'
  as Proposed Standard

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 2013-08-16. 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.

Abstract


  This document specifies the syntax of Uniform Resource Identifier
  (URI) schemes for the Traversal Using Relays around NAT (TURN)
  protocol.  It defines two URI schemes to provision the TURN
  Resolution Mechanism [RFC5928].




The file can be obtained via
http://datatracker.ietf.org/doc/draft-petithuguenin-behave-turn-uris/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-petithuguenin-behave-turn-uris/ballot/


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