Skip to main content

Well-Known URIs for the WebSocket Protocol
draft-bormann-hybi-ws-wk-00

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 8307.
Author Carsten Bormann
Last updated 2018-01-02 (Latest revision 2017-05-11)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Reviews
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 8307 (Proposed Standard)
Action Holders
(None)
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Alexey Melnikov
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
draft-bormann-hybi-ws-wk-00
Network Working Group                                         C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Updates: 6455 (if approved)                                 May 11, 2017
Intended status: Standards Track
Expires: November 12, 2017

               Well-known URIs for the WebSocket Protocol
                      draft-bormann-hybi-ws-wk-00

Abstract

   RFC 5785 defines a path prefix, "/.well-known/", that can be used by
   well-known URIs, specifically 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.

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 12, 2017.

Copyright Notice

   Copyright (c) 2017 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

Bormann                 Expires November 12, 2017               [Page 1]
Internet-Draft Well-known URIs for the WebSocket Protocol       May 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   2
   3.  Security considerations . . . . . . . . . . . . . . . . . . .   2
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   [RFC5785] defines a path prefix, "/.well-known", that can be used by
   well-known URIs, as well as an IANA registry for URI suffixes to be
   used with this path prefix for forming well-known URIs.

   In [RFC5785], this mechanism is specifically defined for the "http"
   and "https" URI schemes (now defined in [RFC7230]).  Other URI
   schemes such as "coap" and "coaps" [RFC7252] have since picked up
   this mechanism, sharing the registry of URI suffixes with that for
   HTTP(S).

   [RFC6455], 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 [RFC6455], to extend the use of
   [RFC5785] 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 [RFC5785]; no change is necessicated by the
   present memo in the registry or its IANA considerations.

2.  IANA considerations

   This memo does not require any IANA actions.

3.  Security considerations

   The Security Considerations of [RFC5785] 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

Bormann                 Expires November 12, 2017               [Page 2]
Internet-Draft Well-known URIs for the WebSocket Protocol       May 2017

   Section 4 of [RFC6455], so no new security considerations about this
   are created by now formally making the well-known URI mechanism
   available for "ws" and "wss", as well.

   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 Section 4 of [RFC6455] pose any information disclosure or other
   security considerations.

4.  References

4.1.  Normative References

   [RFC5785]  Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
              Uniform Resource Identifiers (URIs)", RFC 5785,
              DOI 10.17487/RFC5785, April 2010,
              <http://www.rfc-editor.org/info/rfc5785>.

   [RFC6455]  Fette, I. and A. Melnikov, "The WebSocket Protocol",
              RFC 6455, DOI 10.17487/RFC6455, December 2011,
              <http://www.rfc-editor.org/info/rfc6455>.

4.2.  Informative References

   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
              Protocol (HTTP/1.1): Message Syntax and Routing",
              RFC 7230, DOI 10.17487/RFC7230, June 2014,
              <http://www.rfc-editor.org/info/rfc7230>.

   [RFC7252]  Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
              Application Protocol (CoAP)", RFC 7252,
              DOI 10.17487/RFC7252, June 2014,
              <http://www.rfc-editor.org/info/rfc7252>.

Acknowledgements

Author's Address

   Carsten Bormann
   Universitaet Bremen TZI
   Postfach 330440
   Bremen  D-28359
   Germany

   Phone: +49-421-218-63921
   Email: cabo@tzi.org

Bormann                 Expires November 12, 2017               [Page 3]