Adding acronyms to simplify DANE conversations
draft-dane-registry-acronym-01

Abstract

Experience has show that people get confused using the three numeric fields the TLSA record. This document specifies descriptive acronyms for the three numeric fields in the TLSA records.

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 http://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 March 10, 2014.

Copyright Notice

Copyright (c) 2013 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 (http://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
• 1.1. Requirements notation
• 2. IANA considerations
• 2.1. TLSA Certificate Usages
• 2.2. TLSA Selectors
• 2.3. TLSA Matching types
• 3. Examples of usage
• 4. Security considerations
• 5. Acknowledgements
• 6. Normative References
• Appendix A. Document history
• Author's Address

1. Introduction

During discussions on how to add DANE [RFC6698] technology to new protocols/services people repeatedly have got confused as what the numeric values stand for and even the order of the fields of a TLSA record. This document updates the IANA registry definition for TLSA record to add a column with acronym for each specified field, in order to reduce confusion. This document does not change the DANE protocol in any way.

It is expected that DANE parser's in applications and DNS software MAY adopt parsing the acronyms for each field, installed base MAY NOT get updated.

1.1. Requirements notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

2. IANA considerations

This document applies to "DNS-Based Authentication of Named Entities (DANE) Parameters" located at "http://www.iana.org/assignments/dane-parameters/dane-parameters.xhtml". Each one of the Sub-registries will add a column with an acronym for that field.

[RFC6698] and this document are both to be the reference documents for the three sub-registries.

As these acronyms are offered for human consumption, case does not matter, it is expected that software the parses TLSA records will handle any case use in the input> The expectation is that by using the acronyms in production systems fewer bad TLSA records will be published.

2.1. TLSA Certificate Usages