URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
RFC 7064
| Document | Type |
RFC - Proposed Standard
(November 2013; No errata)
Was draft-nandakumar-rtcweb-stun-uri (individual in rai area)
|
|
|---|---|---|---|
| Authors | Suhas Nandakumar , Gonzalo Salgueiro , Paul Jones , Marc Petit-Huguenin | ||
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Dan Wing | ||
| Shepherd write-up | Show (last changed 2013-09-16) | ||
| IESG | IESG state | RFC 7064 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Gonzalo Camarillo | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) S. Nandakumar
Request for Comments: 7064 G. Salgueiro
Category: Standards Track P. Jones
ISSN: 2070-1721 Cisco Systems
M. Petit-Huguenin
Impedance Mismatch
November 2013
URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
Abstract
This document specifies the syntax and semantics of the Uniform
Resource Identifier (URI) scheme for the Session Traversal Utilities
for NAT (STUN) protocol.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7064.
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
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.
Nandakumar, et al. Standards Track [Page 1]
RFC 7064 STUN URI November 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definition of the "stun" or "stuns" URI . . . . . . . . . . . 3
3.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 3
3.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5.1. "stun" URI Registration . . . . . . . . . . . . . . . . . 5
5.2. "stuns" URI Registration . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 8
Appendix B. Design Notes . . . . . . . . . . . . . . . . . . . . 8
Nandakumar, et al. Standards Track [Page 2]
RFC 7064 STUN URI November 2013
1. Introduction
This document specifies the syntax and semantics of the Uniform
Resource Identifier (URI) scheme for the Session Traversal Utilities
for NAT (STUN) protocol.
STUN is a protocol that serves as a tool for other protocols in
dealing with Network Address Translator (NAT) traversal. It can be
used by an endpoint to determine the IP address and port allocated to
it by a NAT, to perform connectivity checks between two endpoints,
and as a keepalive protocol to maintain NAT bindings. RFC 5389
[RFC5389] defines the specifics of the STUN protocol.
The "stun" and "stuns" URI schemes are used to designate a stand-
alone STUN server or any Internet host performing the operations of a
STUN server in the context of STUN usages (Section 14 of RFC 5389
[RFC5389]). With the advent of standards such as WebRTC [WEBRTC], we
anticipate a plethora of endpoints and web applications to be able to
identify and communicate with such a STUN server to carry out the
STUN protocol. This implies that endpoints and/or applications must
be provisioned with the appropriate configuration to identify the
STUN server. Having an inconsistent syntax adds ambiguity and can
result in non-interoperable solutions and implementation limitations.
The "stun" and "stuns" URI schemes help alleviate most of these
issues by providing a consistent way to describe, configure, and
exchange the information identifying a STUN server.
2. Terminology
Show full document text