idnits 2.17.1 draft-hallambaker-wellknown-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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 18, 2013) is 4084 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: 'RFC1035' is defined on line 76, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 79, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force P. Hallam-Baker 3 Internet-Draft Comodo Group Inc. 4 Intended status: Standards Track February 18, 2013 5 Expires: August 22, 2013 7 Well Known Service and URI Declarations 8 draft-hallambaker-wellknown-00 10 Abstract 12 Under the current system of registration, separate requests are 13 required to register entries for .well-known HTTP services, discovery 14 via DNS mechanisms such as SRV and NAPTR and for a URI prefix. This 15 proposal encourages Web Services to adopt a consistent approach to 16 configuration through a 'one stop' registration system whereby 17 assignment of a .well-known identifier automatically assigns DNS and 18 URI prefixes. 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 http://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 August 22, 2013. 37 Copyright Notice 39 Copyright (c) 2013 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 (http://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. One Stop Protocol Registration . . . . . . . . . . . . . . . . 3 55 2. The _wk DNS Prefix. . . . . . . . . . . . . . . . . . . . . . . 3 56 3. The ws: URI scheme. . . . . . . . . . . . . . . . . . . . . . . 3 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 59 6. Normative References . . . . . . . . . . . . . . . . . . . . . 3 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 1. One Stop Protocol Registration 64 2. The _wk DNS Prefix. 66 3. The ws: URI scheme. 68 4. Security Considerations 70 5. IANA Considerations 72 TBS 74 6. Normative References 76 [RFC1035] Mockapetris, P., "Domain names - implementation and 77 specification", STD 13, RFC 1035, November 1987. 79 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 80 Requirement Levels", BCP 14, RFC 2119, March 1997. 82 Author's Address 84 Phillip Hallam-Baker 85 Comodo Group Inc. 87 Email: philliph@comodo.com