]> Shinkuro Inc.

4922 Fairmont Av, Suite 250 Bethesda MD 20814 USA ogud@ogud.com

Security DANE 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.

During discussions on how to add DANE 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.

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 .

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. and this document are both to be reference documents for the three sub-registries.

Value Acronym Short Description Reference 0 PKIX-CA CA constraint 1 PKIX-EE Service certificate constraint 2 DANE-TA Trust anchor assertion 3 DANE-EE Domain-issued certificate 4-254 Unassigned 255 PrivCert Reserved for Private Use Note: should the short description be updated to be more expressive ? Other options suggested for 0: PKIX-TA

Value Acronym Short Description Reference 0 Full Full certificate 1 Hash SubjectPublicKeyInfo 2-254Unassigned 255PrivSelReserved for Private Use

Value Acronym Short Description Reference 0 NoHash No hash used 1 SHA2-256 256 bit hash by SHA2 2 SHA2-512 512 bit hash by SHA2 3-254 Unassigned 255 PrivHash Reserved for Private Use

None, 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.

TBD

[RFC Editor: Please remove this section before publication ] 00 Initial version