idnits 2.17.1 draft-ietf-dane-registry-acronyms-03.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC6698, but the abstract doesn't seem to directly say this. It does mention RFC6698 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 06, 2014) is 3755 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DANE O. Gudmundsson 3 Internet-Draft Shinkuro Inc. 4 Updates: 6698 (if approved) January 06, 2014 5 Intended status: Standards Track 6 Expires: July 10, 2014 8 Adding acronyms to simplify DANE conversations 9 draft-ietf-dane-registry-acronyms-03 11 Abstract 13 Experience has show that people get confused using the three numeric 14 fields the TLSA record. This document specifies descriptive acronyms 15 for the three numeric fields in the TLSA records. This document 16 updates the format of the IANA registry created by RFC6698. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on July 10, 2014. 35 Copyright Notice 37 Copyright (c) 2014 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. IANA considerations . . . . . . . . . . . . . . . . . . . . . 2 54 2.1. TLSA Certificate Usages . . . . . . . . . . . . . . . . . 3 55 2.2. TLSA Selectors . . . . . . . . . . . . . . . . . . . . . 3 56 2.3. TLSA Matching types . . . . . . . . . . . . . . . . . . . 3 57 3. Examples of usage . . . . . . . . . . . . . . . . . . . . . . 3 58 3.1. TLSA records using/displaying the acronyms: . . . . . . . 4 59 3.2. Acronym use in a specification example: . . . . . . . . . 4 60 4. Security considerations . . . . . . . . . . . . . . . . . . . 4 61 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 62 6. Normative References . . . . . . . . . . . . . . . . . . . . 4 63 Appendix A. Document history . . . . . . . . . . . . . . . . . . 4 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 66 1. Introduction 68 During discussions on how to add DANE [RFC6698] technology to new 69 protocols/services people repeatedly have got confused as what the 70 numeric values stand for and even the order of the fields of a TLSA 71 record. This document updates the IANA registry definition for TLSA 72 record to add a column with acronym for each specified field, in 73 order to reduce confusion. This document does not change the DANE 74 protocol in any way. 76 It is expected that DANE parsers in applications and DNS software can 77 adopt parsing the acronyms for each field. 79 2. IANA considerations 81 This document applies to "DNS-Based Authentication of Named Entities 82 (DANE) Parameters" located at "http://www.iana.org/assignments/dane- 83 parameters/dane-parameters.xhtml". Each one of the Sub-registries 84 will add a column with an acronym for that field. 86 [RFC6698] and this document are both to be the reference documents 87 for the three sub-registries. 89 As these acronyms are offered for human consumption, case does not 90 matter, it is expected that software that parses TLSA records will 91 handle either upper or lower case use as input. 93 2.1. TLSA Certificate Usages 95 +-------+----------+--------------------------------+-------------+ 96 | Value | Acronym | Short Description | Reference | 97 +-------+----------+--------------------------------+-------------+ 98 | 0 | PKIX-TA | CA constraint | [RFC6698] | 99 | 1 | PKIX-EE | Service certificate constraint | [RFC6698] | 100 | 2 | DANE-TA | Trust anchor assertion | [RFC6698] | 101 | 3 | DANE-EE | Domain-issued certificate | [RFC6698] | 102 | 4-254 | | Unassigned | | 103 | 255 | PrivCert | Reserved for Private Use | [RFC6698] | 104 +-------+----------+--------------------------------+-------------+ 106 Table 1: TLSA Certificate Usages 108 Other options suggested for 0: PKIX-TA 110 2.2. TLSA Selectors 112 +-------+---------+--------------------------+-------------+ 113 | Value | Acronym | Short Description | Reference | 114 +-------+---------+--------------------------+-------------+ 115 | 0 | Cert | Full certificate | [RFC6698] | 116 | 1 | SPKI | SubjectPublicKeyInfo | [RFC6698] | 117 | 2-254 | | Unassigned | | 118 | 255 | PrivSel | Reserved for Private Use | [RFC6698] | 119 +-------+---------+--------------------------+-------------+ 121 Table 2: TLSA Selectors 123 2.3. TLSA Matching types 125 +-------+-----------+--------------------------+-------------+ 126 | Value | Acronym | Short Description | Reference | 127 +-------+-----------+--------------------------+-------------+ 128 | 0 | Full | No hash used | [RFC6698] | 129 | 1 | SHA2-256 | 256 bit hash by SHA2 | [RFC6698] | 130 | 2 | SHA2-512 | 512 bit hash by SHA2 | [RFC6698] | 131 | 3-254 | | Unassigned | | 132 | 255 | PrivMatch | Reserved for Private Use | [RFC6698] | 133 +-------+-----------+--------------------------+-------------+ 135 Table 3: TLSA Matching types 137 3. Examples of usage 139 Two examples below 141 3.1. TLSA records using/displaying the acronyms: 142 _666._tcp.first.example. TLSA PKIX-TA CERT SHA2-512 {blob} 143 _666._tcp.second.example. TLSA DANE-TA SPKI SHA2-256 {blob} 145 3.2. Acronym use in a specification example: 147 Protocol FOO only allows TLSA records using PKIX-EE and DANE-EE, with 148 selector SPKI and using SHA2-512. 150 4. Security considerations 152 This document only changes registry fields and does not change the 153 behavior of any protocol. The hope is to reduce confusion and lead 154 to better specification and operations. 156 5. Acknowledgements 158 Scott Schmit offered real good suggestions to decrease the 159 possibility of confusion. Viktor Dukhovni provided comments from 160 expert point of view. Jim Schaad, Wes Hardaker and Paul Hoffman 161 provided feedback during WGLC. 163 6. Normative References 165 [RFC6698] Hoffman, P. and J. Schlyter, "The DNS-Based Authentication 166 of Named Entities (DANE) Transport Layer Security (TLS) 167 Protocol: TLSA", RFC 6698, August 2012. 169 Appendix A. Document history 171 [RFC Editor: Please remove this section before publication ] 173 00 Initial version 175 01 Updated version based on some comments ready for WGLC 177 00 WG version almost identical to 01 179 01 WG version result of WG last call one possible issue remains PKIX- 180 CA ==> PKIX-TA no clear message if that change should be made 182 02 WG version PKIX-CA ==> PKIX-TA 184 03 IETF submission version, abstract needed to mention RFC6698. 186 Author's Address 187 Olafur Gudmundsson 188 Shinkuro Inc. 189 4922 Fairmont Av, Suite 250 190 Bethesda, MD 20814 191 USA 193 Email: ogud@ogud.com