BEHAVE M. Petit-Huguenin
Internet-Draft Impedance Mismatch
Intended status: Standards Track S. Nandakumar
Expires: November 07, 2013 G. Salgueiro
P. Jones
Cisco Systems
May 06, 2013
Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
draft-petithuguenin-behave-turn-uris-04
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 that can be used to provision
the configuration values needed by the resolution mechanism defined
in [RFC5928].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on November 07, 2013.
Copyright Notice
Copyright (c) 2013 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
Petit-Huguenin, et al. Expires November 07, 2013 [Page 1]
Internet-Draft TURN URIs May 2013
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 Simplified BSD License.
This document may not be modified, and derivative works of it may not
be created, except to format it for publication as an RFC or to
translate it into languages other than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definitions of the TURN and TURNS URI . . . . . . . . . . . . 3
3.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 3
3.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . 4
4. Implementation Status . . . . . . . . . . . . . . . . . . . . 5
4.1. turnuri . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. libjingle . . . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Firefox . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6.1. TURN URI Registration . . . . . . . . . . . . . . . . . . 6
6.2. TURNS URI Registration . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 9
Appendix B. Release notes . . . . . . . . . . . . . . . . . . . 9
B.1. Design Notes . . . . . . . . . . . . . . . . . . . . . . 9
B.2. Modifications between petithuguenin-behave-turn-uris-04
and petithuguenin-behave-turn-uris-03 . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document specifies the syntax and semantics of the Uniform
Resource Identifier (URI) scheme for the Traversal Using Relays
around NAT (TURN) protocol.
The TURN protocol is a specification allowing hosts behind NAT to
control the operation of a relay server. The relay server allows
hosts to exchange packets with its peers. The peers themselves may
also be behind NATs. RFC 5766 [RFC5766] defines the specifics of the