idnits 2.17.1 draft-bormann-wk-uri-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 04, 2019) is 1811 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC6455' is defined on line 136, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5785 (Obsoleted by RFC 8615) -- Obsolete informational reference (is this intentional?): RFC 7230 (Obsoleted by RFC 9110, RFC 9112) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Bormann 3 Internet-Draft Universitaet Bremen TZI 4 Updates: 7595 (if approved) April 04, 2019 5 Intended status: Standards Track 6 Expires: October 6, 2019 8 Recording Well-Known URI Capability in the URI Scheme Registry 9 draft-bormann-wk-uri-00 11 Abstract 13 RFC 5785 defines a path prefix, "/.well-known/", that can be used by 14 well-known URIs, specifically for the "http" and "https" URI schemes, 15 which has since been adopted by other URI schemes. The present memo 16 formally updates RFC 7595, which defines the URI schemes regustry, to 17 record the availability of these well-known URIs to the URI schemes 18 registered there. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on October 6, 2019. 37 Copyright Notice 39 Copyright (c) 2019 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. IANA considerations . . . . . . . . . . . . . . . . . . . . . 2 56 3. Security considerations . . . . . . . . . . . . . . . . . . . 3 57 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4.1. Normative References . . . . . . . . . . . . . . . . . . 3 59 4.2. Informative References . . . . . . . . . . . . . . . . . 3 60 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 4 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 [RFC5785] defines a path prefix, "/.well-known", that can be used by 66 well-known URIs, as well as an IANA registry for URI suffixes to be 67 used with this path prefix for forming well-known URIs. 69 In [RFC5785], this mechanism is specifically defined for the "http" 70 and "https" URI schemes (now defined in [RFC7230]). Other URI 71 schemes such as "coap" and "coaps" [RFC7252] have since picked up 72 this mechanism, sharing the registry of URI suffixes with that for 73 HTTP(S). 75 [RFC7595], which defines the URI scheme registry [IANA.uri-schemes], 76 does not foresee recording the availability of well-known URIs for a 77 scheme being registered. Hence, there is no central reference that 78 can easily be used to find out which schemes do support well-known 79 URIs. 81 The present memo formally updates [RFC7595] to record the 82 availability of these well-known URIs to the URI schemes registered 83 in [IANA.uri-schemes]. 85 2. IANA considerations 87 IANA is requested to add a column to the Uniform Resource Identifier 88 (URI) Schemes Registry [IANA.uri-schemes] labeled "Well-Known URI 89 OK", with a default value of "-". If a URI scheme explicitly has 90 been specified to use well-known URIs as per Section 3 of [RFC5785], 91 the value changes to a reference to that specification. Initial 92 values not equal to "-" are given in Table 1. 94 +------------+--------------------+ 95 | URI Scheme | Well-Known URI OK? | 96 +------------+--------------------+ 97 | coap | [RFC7252] | 98 | coap+tcp | [RFC8323] | 99 | coap+ws | [RFC8323] | 100 | coaps | [RFC7252] | 101 | coaps+tcp | [RFC8323] | 102 | coaps+ws | [RFC8323] | 103 | http | [RFC5785] | 104 | https | [RFC5785] | 105 | ws | [RFC8307] | 106 | wss | [RFC8307] | 107 +------------+--------------------+ 109 Table 1: Rows in URI scheme registry with nonempty new column 111 3. Security considerations 113 The Security Considerations of [RFC5785] apply and need to be 114 considered for all well-known URIs. 116 4. References 118 4.1. Normative References 120 [RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known 121 Uniform Resource Identifiers (URIs)", RFC 5785, 122 DOI 10.17487/RFC5785, April 2010, 123 . 125 [RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines 126 and Registration Procedures for URI Schemes", BCP 35, 127 RFC 7595, DOI 10.17487/RFC7595, June 2015, 128 . 130 4.2. Informative References 132 [IANA.uri-schemes] 133 IANA, "Uniform Resource Identifier (URI) Schemes", 134 . 136 [RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", 137 RFC 6455, DOI 10.17487/RFC6455, December 2011, 138 . 140 [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer 141 Protocol (HTTP/1.1): Message Syntax and Routing", 142 RFC 7230, DOI 10.17487/RFC7230, June 2014, 143 . 145 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 146 Application Protocol (CoAP)", RFC 7252, 147 DOI 10.17487/RFC7252, June 2014, 148 . 150 [RFC8307] Bormann, C., "Well-Known URIs for the WebSocket Protocol", 151 RFC 8307, DOI 10.17487/RFC8307, January 2018, 152 . 154 [RFC8323] Bormann, C., Lemay, S., Tschofenig, H., Hartke, K., 155 Silverajan, B., and B. Raymor, Ed., "CoAP (Constrained 156 Application Protocol) over TCP, TLS, and WebSockets", 157 RFC 8323, DOI 10.17487/RFC8323, February 2018, 158 . 160 Acknowledgements 162 Author's Address 164 Carsten Bormann 165 Universitaet Bremen TZI 166 Postfach 330440 167 Bremen D-28359 168 Germany 170 Phone: +49-421-218-63921 171 Email: cabo@tzi.org