idnits 2.17.1 draft-moonesamy-dnsop-special-use-label-registry-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 (October 23, 2018) is 2011 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Unknown state RFC: RFC 952 == Outdated reference: A later version (-16) exists of draft-ietf-dnsop-attrleaf-14 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 dnsop S. Moonesamy 3 Internet-Draft 4 Intended status: Best Current Practice J. Yao 5 Expires: April 26, 2019 CNNIC 6 October 23, 2018 8 Special-Use Labels 9 draft-moonesamy-dnsop-special-use-label-registry-00 11 Abstract 13 This document describes what it means to say that a label is reserved 14 for special use, when reserving such a label is appropriate, and the 15 procedure for doing so. It establishes an IANA registry for such 16 special-use labels, and seeds it with entries for some of the already 17 established special labels. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 26, 2019. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Security Considerations . . . . . . . . . . . . . . . . . . . 2 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 56 3.1. Registration Procedures . . . . . . . . . . . . . . . . . 3 57 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4.1. Normative References . . . . . . . . . . . . . . . . . . 3 59 4.2. Informative References . . . . . . . . . . . . . . . . . 3 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 62 1. Introduction 64 The Domain Name System (DNS) rules for an Internet host name are 65 specified in [RFC0952] [RFC0952] and [RFC1123] [RFC1123]. Underscore 66 scoping [ID.draft-ietf-dnsop-attrleaf] [ID.draft-ietf-dnsop-attrleaf] 67 was introduced as an alternative to circumvent the deployment issues 68 of using a new RR type [RFC1034] [RFC1034]. Some applications, e.g. 69 web browsers, do not consider those underscore names as valid they do 70 not adhere to the rules for a host name [RFC1123]. This document 71 defines a registry to reserve special-use labels for cases where such 72 labels are needed as a workaround. 74 2. Security Considerations 76 A wildcard such as *.example.com could match a host name where a 77 special-use label is prepended to the domain name. 79 3. IANA Considerations 81 The DNS Special-Use Label registry entries consist of two fields: 82 Label, RR type, and Reference. The Label has to conform to DNS rules 83 for a label as defined in [RFC1034]. The initial assignment is as 84 follows: 86 +---------------------------------------+---------+------------+ 87 | Label | RR Type | Reference | 88 +---------------------------------------+---------+------------+ 89 | root-key-sentinel-is-ta- | A | [KSK-roll] | 90 | root-key-sentinel-is-ta- | AAAA | [KSK-roll] | 91 | root-key-sentinel-not-ta- | A | [KSK-roll] | 92 | root-key-sentinel-not-ta- | AAAA | [KSK-roll] | 93 +---------------------------------------+---------+------------+ 95 3.1. Registration Procedures 97 The registration policy for this registry is "IETF Review" [RFC8126] 98 [RFC8126]. The registrant of the label should provide the following 99 information: 101 o Label 103 o RR Type 105 o Reference 107 4. References 109 4.1. Normative References 111 [RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet 112 host table specification", RFC 952, DOI 10.17487/RFC0952, 113 October 1985, . 115 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 116 STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, 117 . 119 [RFC1123] Braden, R., Ed., "Requirements for Internet Hosts - 120 Application and Support", STD 3, RFC 1123, 121 DOI 10.17487/RFC1123, October 1989, 122 . 124 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 125 Writing an IANA Considerations Section in RFCs", BCP 26, 126 RFC 8126, DOI 10.17487/RFC8126, June 2017, 127 . 129 4.2. Informative References 131 [ID.draft-ietf-dnsop-attrleaf] 132 Crocker, D., "ID.draft-ietf-dnsop-attrleaf", draft-ietf- 133 dnsop-attrleaf-14 (work in progress), October 2018. 135 [KSK-roll] 136 Huston, G., Damas, J., and W. Kumari, "A Root Key Trust 137 Anchor Sentinel for DNSSEC", draft-ietf-dnsop-kskroll- 138 sentinel-17 (work in progress), July 2018. 140 Authors' Addresses 142 S. Moonesamy 143 76, Ylang Ylang Avenue 144 Quatres Bornes 145 Mauritius 147 Email: sm+ietf@elandsys.com 149 Jiankang Yao 150 CNNIC 151 4 South 4th Street, Zhongguancun, Haidian District 152 Beijing, Beijing 100190 153 China 155 Phone: +86 10 5881 3007 156 Email: yaojk@cnnic.cn