Skip to main content

URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol
draft-nandakumar-rtcweb-stun-uri-05

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 7064.
Authors Suhas Nandakumar , Gonzalo Salgueiro , Paul Jones , Marc Petit-Huguenin
Last updated 2013-08-16 (Latest revision 2013-07-12)
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources
Stream WG state (None)
Document shepherd Dan Wing
IESG IESG state Became RFC 7064 (Proposed Standard)
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Gonzalo Camarillo
Send notices to petithug@acm.org, snandaku@cisco.com, gsalguei@cisco.com, paulej@packetizer.com, draft-nandakumar-rtcweb-stun-uri@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
draft-nandakumar-rtcweb-stun-uri-05
Nandakumar, et al.      Expires January 13, 2014                [Page 7]
Internet-Draft                  STUN URI                       July 2013

   [RFC4395]  Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
              Registration Procedures for New URI Schemes", BCP 35, RFC
              4395, February 2006.

   [RFC5389]  Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
              "Session Traversal Utilities for NAT (STUN)", RFC 5389,
              October 2008.

   [RUNNING-CODE]
              Sheffer, Y. and A. Farrel, "Improving Awareness of Running
              Code: the Implementation Status Section", draft-sheffer-
              running-code-06 (work in progress), June 2013.

   [WEBRTC]   Bergkvist, A., Burnett, D., Jennings, C., and A.
              Narayanan, "WebRTC 1.0: Real-time Communication Between
              Browsers", World Wide Web Consortium WD WD-
              webrtc-20120821, August 2012,
              <http://www.w3.org/TR/2012/WD-webrtc-20120821>.

Appendix A.  Examples

   Table 1 shows examples for 'stun/stuns'uri scheme.  For all these
   examples, the <host> component is populated with "example.org".

                         +-----------------------+
                         | URI                   |
                         +-----------------------+
                         | stun:example.org      |
                         | stuns:example.org     |
                         | stun:example.org:8000 |
                         +-----------------------+

                                  Table 1

Appendix B.  Design Notes

   o  The ABNF duplicates some definitions from [RFC3986] instead of
      referencing them.  This was done because the definitions in RFC
      3986 are for hierarchical URIs, so using these references in an
      opaque URI proved confusing.

   o  One recurring comment was to stop using the suffix "s" on URI
      scheme, and to move the secure option to a parameter (e.g.,
      ";proto=tls").  We decided against this idea because the need for
      ";proto=" for the STUN URI cannot be sufficiently explained and
      supporting it would render an incomplete specification.  This
      would also result in lost symmetry between the TURN and STUN URIs.
      A more detailed account of the reasoning behind this is available

Nandakumar, et al.      Expires January 13, 2014                [Page 8]
Internet-Draft                  STUN URI                       July 2013

      at <http://blog.marc.petit-huguenin.org/2012/09/on-design-of-stun-
      and-turn-uri-formats.html>

Appendix C.  Release notes

   NOTE TO RFC EDITOR: This section must be removed before publication
   as an RFC.

C.1.  Modifications between draft-nandakumar-rtcweb-stun-uri-05 and
      draft-nandakumar-rtcweb-stun-uri-04

   o  Changed boilerplate from noModificationTrust200902 to trust200902.

   o  Updated RFC 2119 boilerplate to http://trac.tools.ietf.org/group/
      iesg/trac/wiki/Draft2119BoilerplateSuggestions

   o  Removed non-normative text in "Definition of the STUN and STUNS
      URI" section.

   o  Reordered ABNF production references in the text to match the ABNF
      definition order.

   o  Added a design note explaining the reason for duplicating the ABNF
      productions from RFC 3986.

   o  Updated Acknowledgment section.

   o  Updated Implementation Status section with new template.

   o  Addressed several nits (spelling, grammar, etc.)

Authors' Addresses

   Suhas Nandakumar
   Cisco Systems
   170 West Tasman Drive
   San Jose, CA  95134
   US

   Email: snandaku@cisco.com

Nandakumar, et al.      Expires January 13, 2014                [Page 9]
Internet-Draft                  STUN URI                       July 2013

   Gonzalo Salgueiro
   Cisco Systems
   7200-12 Kit Creek Road
   Research Triangle Park, NC  27709
   US

   Email: gsalguei@cisco.com

   Paul E. Jones
   Cisco Systems
   7025 Kit Creek Road
   Research Triangle Park, NC  27709
   US

   Email: paulej@packetizer.com

   Marc Petit-Huguenin
   Impedance Mismatch

   Email: petithug@acm.org

Nandakumar, et al.      Expires January 13, 2014               [Page 10]