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

The information below is for an old version of the document
Document Type Active Internet-Draft (dane WG)
Last updated 2014-02-11 (latest revision 2014-01-06)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Paul Hoffman
Shepherd write-up Show (last changed 2013-12-28)
IESG IESG state IESG Evaluation
Telechat date
Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Stephen Farrell
Send notices to dane-chairs@tools.ietf.org, draft-ietf-dane-registry-acronyms@tools.ietf.org, paul.hoffman@vpnc.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
DANE                                                      O. Gudmundsson
Internet-Draft                                             Shinkuro Inc.
Updates: 6698 (if approved)                             January 06, 2014
Intended status: Standards Track
Expires: July 10, 2014

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

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.  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 July 10, 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.

Gudmundsson               Expires July 10, 2014                 [Page 1]
Internet-Draft     Adding acronyms to DANE registries       January 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  TLSA Certificate Usages . . . . . . . . . . . . . . . . .   3
     2.2.  TLSA Selectors  . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  TLSA Matching types . . . . . . . . . . . . . . . . . . .   3
   3.  Examples of usage . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  TLSA records using/displaying the acronyms: . . . . . . .   4
     3.2.  Acronym use in a specification example: . . . . . . . . .   4
   4.  Security considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Appendix A.  Document history . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

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 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 either upper or lower case use as input.

Gudmundsson               Expires July 10, 2014                 [Page 2]
Internet-Draft     Adding acronyms to DANE registries       January 2014

2.1.  TLSA Certificate Usages

    +-------+----------+--------------------------------+-------------+
    | Value | Acronym  | Short Description              | Reference   |
Show full document text