Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
draft-petithuguenin-behave-turn-uri-bis-00

Abstract

This document defines two URI schemes that can be used to provision the configuration values needed by the resolution mechanism defined in [I‑D.ietf‑behave‑turn‑uri] (Petit-Huguenin, M., “Traversal Using Relays around NAT (TURN) Resolution Mechanism,” November 2009.).

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on May 29, 2010.

Copyright Notice

Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License.

Table of Contents

1.  Introduction
2.  Syntax of a TURN or TURNS URI
3.  Security Considerations
4.  IANA Considerations
    4.1.  TURN URI Registration
    4.2.  TURNS URI Registration
5.  Acknowledgements
6.  References
    6.1.  Normative References
    6.2.  Informative References
Appendix A.  Release notes
    A.1.  Design Notes
    A.2.  Running Code Considerations
    A.3.  TODO List
§  Author's Address

1.  Introduction

[I‑D.ietf‑behave‑turn‑uri] (Petit-Huguenin, M., “Traversal Using Relays around NAT (TURN) Resolution Mechanism,” November 2009.) defines a resolution mechanism to convert a secure flag, an host name or IP address, a eventually empty port, and an eventually empty transport to a list of IP address, port and TURN transport tuples.

To simplify the provisioning of TURN clients, this document defines a TURN and a TURNS URI scheme that can carry the four components needed for the resolution mechanism.

2.  Syntax of a TURN or TURNS URI

A TURN/TURNS URI has the following ABNF syntax [RFC5234] (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.):

turnURI       = scheme ":" turn-host [ ":" turn-port ]
              [ "?transport=" transport ]
scheme        = "turn" / "turns"
transport     = "udp" / "tcp" / transport-ext
transport-ext = 1*unreserved
turn-host     = IP-literal / IPv4address / reg-name
turn-port     = *DIGIT
IP-literal    = "[" ( IPv6address / IPvFuture  ) "]"
IPvFuture     = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" )
IPv6address   =                            6( h16 ":" ) ls32
              /                       "::" 5( h16 ":" ) ls32
              / [               h16 ] "::" 4( h16 ":" ) ls32
              / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32
              / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32
              / [ *3( h16 ":" ) h16 ] "::"    h16 ":"   ls32
              / [ *4( h16 ":" ) h16 ] "::"              ls32
              / [ *5( h16 ":" ) h16 ] "::"              h16
              / [ *6( h16 ":" ) h16 ] "::"
h16           = 1*4HEXDIG
ls32          = ( h16 ":" h16 ) / IPv4address
IPv4address   = dec-octet "." dec-octet "." dec-octet "." dec-octet
dec-octet     = DIGIT                 ; 0-9
              / %x31-39 DIGIT         ; 10-99
              / "1" 2DIGIT            ; 100-199
              / "2" %x30-34 DIGIT     ; 200-249
              / "25" %x30-35          ; 250-255
reg-name      = *( unreserved / pct-encoded / sub-delims )

<unreserved>, <sub-delims> and <pct-encoded> are specified in [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.).

<secure> is equal to false is <scheme> is equal to "turn" and equal to false if <scheme> is equal to "turns".

3.  Security Considerations

Security considerations for the resolution mechanism are discussed in [I‑D.ietf‑behave‑turn‑uri] (Petit-Huguenin, M., “Traversal Using Relays around NAT (TURN) Resolution Mechanism,” November 2009.).

The "turn" and "turns" URI schemes do not introduce any specific security issues beyond the security considerations discussed in [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.).

4.  IANA Considerations

This section contains the registration information for the "turn" and "turns" URI Schemes (in accordance with [RFC4395] (Hansen, T., Hardie, T., and L. Masinter, “Guidelines and Registration Procedures for New URI Schemes,” February 2006.)).

4.1.  TURN URI Registration

URI scheme name: turn

Status: permanent

URI scheme syntax: See Section 2 (Syntax of a TURN or TURNS URI).

URI scheme semantics: See [I‑D.ietf‑behave‑turn‑uri] (Petit-Huguenin, M., “Traversal Using Relays around NAT (TURN) Resolution Mechanism,” November 2009.).

Encoding considerations: There are no encoding considerations beyond those in [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.).

Applications/protocols that use this URI scheme name:

The "turn" URI scheme is intended to be used by applications that might need access to a TURN server.

Interoperability considerations: N/A

Security considerations: See Section 3 (Security Considerations).

Contact: Marc Petit-Huguenin <petithug@acm.org>

Author/Change controller: Marc Petit-Huguenin <petithug@acm.org>

References: This document.

4.2.  TURNS URI Registration

URI scheme name: turns

Status: permanent

URI scheme syntax: See Section 2 (Syntax of a TURN or TURNS URI).

URI scheme semantics: See [I‑D.ietf‑behave‑turn‑uri] (Petit-Huguenin, M., “Traversal Using Relays around NAT (TURN) Resolution Mechanism,” November 2009.).

Encoding considerations: There are no encoding considerations beyond those in [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.).

Applications/protocols that use this URI scheme name:

The "turns" URI scheme is intended to be used by applications that might need access to a TURN server.

Interoperability considerations: N/A

Security considerations: See Section 3 (Security Considerations).

Contact: Marc Petit-Huguenin <petithug@acm.org>

Author/Change controller: Marc Petit-Huguenin <petithug@acm.org>

References: This document.

5.  Acknowledgements

Thanks to Margaret Wasserman, Magnus Westerlund, Juergen Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes and Jim Kleck for their comments, suggestions and questions that helped to improve this document.

The <turn-port> and <turn-host> ABNF productions have been copied from the <port> and <host> ABNF productions from [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.).

This document was written with the xml2rfc tool described in [RFC2629] (Rose, M., “Writing I-Ds and RFCs using XML,” June 1999.).

6.  References

6.1. Normative References

6.2. Informative References

Appendix A.  Release notes

This section must be removed before publication as an RFC.

A.1.  Design Notes

• <password> is not used in the URIs because it is deprecated. <username> is not used in the URIs because it is not used to guide the resolution mechanism.
• As discussed in Dublin, there is no generic parameters in the URI to prevent compatibity issues.

A.2.  Running Code Considerations

• Reference Implementation of TURN URI parser and resolver (<http://ietf.implementers.org/turn-uri-0.3.zip>). Marc Petit-Huguenin. Implements version -00

A.3.  TODO List

(Empty)

Author's Address