8307
PROPOSED STANDARD
Well-Known URIs for the WebSocket Protocol
Authors: C. Bormann
Date: January 2018
Working Group: NON WORKING GROUP
Stream: IETF
Updates:
RFC 6455
Abstract
RFC 5785 defines a path prefix, "/.well-known/", that can be used by well-known URIs. It was specifically defined for the "http" and "https" URI schemes. The present memo formally updates RFC 6455, which defines the URI schemes defined for the WebSocket Protocol, to extend the use of these well-known URIs to those URI schemes.
RFC 8307
PROPOSED STANDARD
Internet Engineering Task Force (IETF) C. Bormann
Request for Comments: 8307 Universitaet Bremen TZI
Updates: <a href="./rfc6455">6455</a> January 2018
Category: Standards Track
ISSN: 2070-1721
<span class="h1">Well-Known URIs for the WebSocket Protocol</span>
Abstract
<a href="./rfc5785">RFC 5785</a> defines a path prefix, "/.well-known/", that can be used by
well-known URIs. It was specifically defined for the "http" and
"https" URI schemes. The present memo formally updates <a href="./rfc6455">RFC 6455</a>,
which defines the URI schemes defined for the WebSocket Protocol, to
extend the use of these well-known URIs to those URI schemes.
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 <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8307">https://www.rfc-editor.org/info/rfc8307</a>.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Bormann Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc8307">RFC 8307</a> Well-Known URIs for the WebSocket Protocol January 2018</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-4">4</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.1">4.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.2">4.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a id="ref-RFC5785">RFC5785</a>] defines a path prefix, "/.well-known", that can be used by
well-known URIs. It also contains an IANA registry for URI suffixes
to be used with this path prefix for forming well-known URIs.
In [<a href="./rfc5785" title=""Defining Well-Known Uniform Resource Identifiers (URIs)"">RFC5785</a>], this mechanism is specifically defined for the "http"
and "https" URI schemes (now defined in [<a href="./rfc7230" title=""Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"">RFC7230</a>]). Other URI
schemes such as "coap" and "coaps" [<a href="./rfc7252" title=""The Constrained Application Protocol (CoAP)"">RFC7252</a>] have since picked up
this mechanism, sharing the registry of URI suffixes with that for
HTTP(S).
[<a href="./rfc6455" title=""The WebSocket Protocol"">RFC6455</a>], which defines the URI schemes defined for the WebSocket
Protocol, "ws" and "wss", does not define the use of well-known URIs
for these URI schemes.
The present memo formally updates [<a href="./rfc6455" title=""The WebSocket Protocol"">RFC6455</a>] to extend the use of
[<a href="./rfc5785" title=""Defining Well-Known Uniform Resource Identifiers (URIs)"">RFC5785</a>] well-known URIs to the URI schemes "ws" and "wss".
Well-known URIs for "ws" and "wss" share the registry for URI
suffixes established by [<a href="./rfc5785" title=""Defining Well-Known Uniform Resource Identifiers (URIs)"">RFC5785</a>]; no change is necessitated by the
present memo in the registry or its IANA considerations.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Considerations</span>
This document does not require any IANA actions.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
The Security Considerations of [<a href="./rfc5785" title=""Defining Well-Known Uniform Resource Identifiers (URIs)"">RFC5785</a>] apply and need to be
considered for all well-known URIs.
It has always been possible to form "ws" and "wss" URIs in such a way
that they map to well-known HTTP(S) URIs when using the procedure in
<a href="./rfc6455#section-4">Section 4 of [RFC6455]</a>; no new security considerations are created by
now formally making the well-known URI mechanism available for "ws"
and "wss".
<span class="grey">Bormann Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc8307">RFC 8307</a> Well-Known URIs for the WebSocket Protocol January 2018</span>
However, with well-known URIs becoming available for the WebSocket
Protocol, applications that want to define well-known URI suffixes
specifically for WebSocket use also need to consider whether the
resources becoming available under the equivalent HTTP(S) URI formed
by <a href="./rfc6455#section-4">Section 4 of [RFC6455]</a> pose any information disclosure or other
security considerations.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Normative References</span>
[<a id="ref-RFC5785">RFC5785</a>] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
Uniform Resource Identifiers (URIs)", <a href="./rfc5785">RFC 5785</a>,
DOI 10.17487/RFC5785, April 2010,
<<a href="https://www.rfc-editor.org/info/rfc5785">https://www.rfc-editor.org/info/rfc5785</a>>.
[<a id="ref-RFC6455">RFC6455</a>] Fette, I. and A. Melnikov, "The WebSocket Protocol",
<a href="./rfc6455">RFC 6455</a>, DOI 10.17487/RFC6455, December 2011,
<<a href="https://www.rfc-editor.org/info/rfc6455">https://www.rfc-editor.org/info/rfc6455</a>>.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Informative References</span>
[<a id="ref-RFC7230">RFC7230</a>] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing",
<a href="./rfc7230">RFC 7230</a>, DOI 10.17487/RFC7230, June 2014,
<<a href="https://www.rfc-editor.org/info/rfc7230">https://www.rfc-editor.org/info/rfc7230</a>>.
[<a id="ref-RFC7252">RFC7252</a>] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", <a href="./rfc7252">RFC 7252</a>,
DOI 10.17487/RFC7252, June 2014,
<<a href="https://www.rfc-editor.org/info/rfc7252">https://www.rfc-editor.org/info/rfc7252</a>>.
Author's Address
Carsten Bormann
Universitaet Bremen TZI
Postfach 330440
Bremen D-28359
Germany
Phone: +49-421-218-63921
Email: [email protected]
Bormann Standards Track [Page 3]
Annotations
Select text to annotate