Special-Use Labels
draft-moonesamy-dnsop-special-use-label-registry-00

Abstract

This document describes what it means to say that a label is reserved for special use, when reserving such a label is appropriate, and the procedure for doing so. It establishes an IANA registry for such special-use labels, and seeds it with entries for some of the already established special labels.

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 April 26, 2019.

Copyright Notice

Copyright (c) 2018 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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Security Considerations
• 3. IANA Considerations
• 3.1. Registration Procedures
• 4. References
• 4.1. Normative References
• 4.2. Informative References
• Authors' Addresses

1. Introduction

The Domain Name System (DNS) rules for an Internet host name are specified in [RFC0952] and [RFC1123]. Underscore scoping [ID.draft-ietf-dnsop-attrleaf] was introduced as an alternative to circumvent the deployment issues of using a new RR type [RFC1034]. Some applications, e.g. web browsers, do not consider those underscore names as valid they do not adhere to the rules for a host name [RFC1123]. This document defines a registry to reserve special-use labels for cases where such labels are needed as a workaround.

2. Security Considerations

A wildcard such as *.example.com could match a host name where a special-use label is prepended to the domain name.

3. IANA Considerations

The DNS Special-Use Label registry entries consist of two fields: Label, RR type, and Reference. The Label has to conform to DNS rules for a label as defined in [RFC1034]. The initial assignment is as follows:

     +---------------------------------------+---------+------------+
     | Label                                 | RR Type | Reference  |
     +---------------------------------------+---------+------------+
     | root-key-sentinel-is-ta-<key-tag>     |  A      | [KSK-roll] |
     | root-key-sentinel-is-ta-<key-tag>     |  AAAA   | [KSK-roll] |
     | root-key-sentinel-not-ta-<key-tag>    |  A      | [KSK-roll] |
     | root-key-sentinel-not-ta-<key-tag>    |  AAAA   | [KSK-roll] |
     +---------------------------------------+---------+------------+
          

3.1. Registration Procedures

The registration policy for this registry is "IETF Review" [RFC8126]. The registrant of the label should provide the following information:

• Label
• RR Type
• Reference

4. References

4.1. Normative References

4.2. Informative References

Authors' Addresses