[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00

Network Working Group                                         C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Updates: 7595 (if approved)                               April 04, 2019
Intended status: Standards Track
Expires: October 6, 2019


     Recording Well-Known URI Capability in the URI Scheme Registry
                        draft-bormann-wk-uri-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,
   which has since been adopted by other URI schemes.  The present memo
   formally updates RFC 7595, which defines the URI schemes regustry, to
   record the availability of these well-known URIs to the URI schemes
   registered there.

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 https://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 October 6, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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 October 6, 2019                [Page 1]


Internet-Draft   Well-Known URIs in URI Scheme Registry       April 2019


   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 . . . . . . . . . . . . . . . . . . .   3
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

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).

   [RFC7595], which defines the URI scheme registry [IANA.uri-schemes],
   does not foresee recording the availability of well-known URIs for a
   scheme being registered.  Hence, there is no central reference that
   can easily be used to find out which schemes do support well-known
   URIs.

   The present memo formally updates [RFC7595] to record the
   availability of these well-known URIs to the URI schemes registered
   in [IANA.uri-schemes].

2.  IANA considerations

   IANA is requested to add a column to the Uniform Resource Identifier
   (URI) Schemes Registry [IANA.uri-schemes] labeled "Well-Known URI
   OK", with a default value of "-".  If a URI scheme explicitly has
   been specified to use well-known URIs as per Section 3 of [RFC5785],
   the value changes to a reference to that specification.  Initial
   values not equal to "-" are given in Table 1.







Bormann                  Expires October 6, 2019                [Page 2]


Internet-Draft   Well-Known URIs in URI Scheme Registry       April 2019


                    +------------+--------------------+
                    | URI Scheme | Well-Known URI OK? |
                    +------------+--------------------+
                    | coap       | [RFC7252]          |
                    | coap+tcp   | [RFC8323]          |
                    | coap+ws    | [RFC8323]          |
                    | coaps      | [RFC7252]          |
                    | coaps+tcp  | [RFC8323]          |
                    | coaps+ws   | [RFC8323]          |
                    | http       | [RFC5785]          |
                    | https      | [RFC5785]          |
                    | ws         | [RFC8307]          |
                    | wss        | [RFC8307]          |
                    +------------+--------------------+

       Table 1: Rows in URI scheme registry with nonempty new column

3.  Security considerations

   The Security Considerations of [RFC5785] apply and need to be
   considered for all well-known URIs.

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,
              <https://www.rfc-editor.org/info/rfc5785>.

   [RFC7595]  Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines
              and Registration Procedures for URI Schemes", BCP 35,
              RFC 7595, DOI 10.17487/RFC7595, June 2015,
              <https://www.rfc-editor.org/info/rfc7595>.

4.2.  Informative References

   [IANA.uri-schemes]
              IANA, "Uniform Resource Identifier (URI) Schemes",
              <http://www.iana.org/assignments/uri-schemes>.

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






Bormann                  Expires October 6, 2019                [Page 3]


Internet-Draft   Well-Known URIs in URI Scheme Registry       April 2019


   [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,
              <https://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,
              <https://www.rfc-editor.org/info/rfc7252>.

   [RFC8307]  Bormann, C., "Well-Known URIs for the WebSocket Protocol",
              RFC 8307, DOI 10.17487/RFC8307, January 2018,
              <https://www.rfc-editor.org/info/rfc8307>.

   [RFC8323]  Bormann, C., Lemay, S., Tschofenig, H., Hartke, K.,
              Silverajan, B., and B. Raymor, Ed., "CoAP (Constrained
              Application Protocol) over TCP, TLS, and WebSockets",
              RFC 8323, DOI 10.17487/RFC8323, February 2018,
              <https://www.rfc-editor.org/info/rfc8323>.

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 October 6, 2019                [Page 4]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/