DANE O. Gudmundsson
Internet-Draft Shinkuro Inc.
Updates: 6698 (if approved) February 14, 2014
Intended status: Standards Track
Expires: August 18, 2014

Adding acronyms to simplify DANE conversations
draft-ietf-dane-registry-acronyms-04

Abstract

Experience has shown 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. This document updates the format of the IANA registry created by RFC6698.

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 August 18, 2014.

Copyright Notice

Copyright (c) 2014 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

During discussions on how to add DANE [RFC6698] technology to new protocols/services people repeatedly have got confused as to what the numeric values stand for and even the order of the fields of a TLSA record (TLSA is not an acronym but a name). This document updates the IANA registry definition for TLSA record to add a column with an 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 parsers in applications and DNS software can adopt parsing the acronyms for each field.

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 that parses TLSA records will handle upper, mixed or lower case use as input.

2.1. TLSA Certificate Usages Registry

Update reference for this registry to include both [RFC6698] and [RFC-this-document]

TLSA Certificate Usages
Value Acronym Short Description Reference
0 PKIX-TA CA constraint [RFC6698]
1 PKIX-EE Service certificate constraint [RFC6698]
2 DANE-TA Trust anchor assertion [RFC6698]
3 DANE-EE Domain-issued certificate [RFC6698]
4-254 Unassigned
255 PrivCert Reserved for Private Use [RFC6698]

Other options suggested for 0: PKIX-TA

2.2. TLSA Selectors

Update reference for this registry to include both [RFC6698] and [RFC-this-document]

TLSA Selectors
Value Acronym Short Description Reference
0 Cert Full certificate [RFC6698]
1 SPKI SubjectPublicKeyInfo [RFC6698]
2-254 Unassigned
255 PrivSel Reserved for Private Use [RFC6698]

2.3. TLSA Matching types

Update reference for this registry to include both [RFC6698] and [RFC-this-document]

TLSA Matching types
Value Acronym Short Description Reference
0 Full No hash used [RFC6698]
1 SHA2-256 256 bit hash by SHA2 [RFC6234]
2 SHA2-512 512 bit hash by SHA2 [RFC6234]
3-254 Unassigned
255 PrivMatch Reserved for Private Use [RFC6698]

3. Examples of usage

Two examples below

3.1. TLSA records using/displaying the acronyms:


_666._tcp.first.example. TLSA PKIX-TA CERT SHA2-512 {blob}
_666._tcp.second.example. TLSA DANE-TA SPKI SHA2-256 {blob}

3.2. Acronym use in a specification example:

Protocol FOO only allows TLSA records using PKIX-EE and DANE-EE, with selector SPKI and using SHA2-512.

4. Security considerations

This document only changes registry fields and does not change the behavior of any protocol. The hope is to reduce confusion and lead to better specification and operations.

5. Acknowledgements

Scott Schmit offered real good suggestions to decrease the possibility of confusion. Viktor Dukhovni provided comments from expert point of view. Jim Schaad, Wes Hardaker and Paul Hoffman provided feedback during WGLC. Dan Romascanu and Tobias Gondrom provided pointed out few defects in the IESG last call.

6. References

6.1. Normative References

[RFC6698] Hoffman, P. and J. Schlyter, "The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA", RFC 6698, August 2012.

6.2. Informative References

[RFC6234] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)", RFC 6234, May 2011.

Appendix A. Document history

[RFC Editor: Please remove this section before publication ]

00 Initial version

01 Updated version based on some comments ready for WGLC

00 WG version almost identical to 01

01 WG version result of WG last call one possible issue remains PKIX-CA ==> PKIX-TA no clear message if that change should be made

02 WG version PKIX-CA ==> PKIX-TA

03 IETF submission version, abstract needed to mention RFC6698.

04 Addressed all comments received during IETF last call

Author's Address

Olafur Gudmundsson Shinkuro Inc. 4922 Fairmont Av, Suite 250 Bethesda, MD 20814 USA EMail: ogud@ogud.com