Re: [dane] Start of WGLC for draft-ietf-dane-registry-acronym
Viktor Dukhovni <viktor1dane@dukhovni.org> Sun, 01 December 2013 21:34 UTC
Return-Path: <viktor1dane@dukhovni.org>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D87FE1AE19F for <dane@ietfa.amsl.com>; Sun, 1 Dec 2013 13:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id arSfzD-4MCYp for <dane@ietfa.amsl.com>; Sun, 1 Dec 2013 13:34:31 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) by ietfa.amsl.com (Postfix) with ESMTP id D17B51ADFA3 for <dane@ietf.org>; Sun, 1 Dec 2013 13:34:30 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 3080C2AB16A; Sun, 1 Dec 2013 21:34:28 +0000 (UTC)
Date: Sun, 01 Dec 2013 21:34:28 +0000
From: Viktor Dukhovni <viktor1dane@dukhovni.org>
To: dane@ietf.org
Message-ID: <20131201213427.GH761@mournblade.imrryr.org>
References: <20130919201216.14866.61161.idtracker@ietfa.amsl.com> <EACEEB05-2023-4F76-A6FE-A9B2FDC0AA59@kumari.net> <024c01cec2dc$72b596e0$5820c4a0$@augustcellars.com> <309DDDEA-6A01-4A68-AFCE-9B6A1B2CE874@ogud.com> <2A8E39E3-5E76-4724-8CE0-839EA2678B65@kumari.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2A8E39E3-5E76-4724-8CE0-839EA2678B65@kumari.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [dane] Start of WGLC for draft-ietf-dane-registry-acronym
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dane@ietf.org
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Dec 2013 21:34:33 -0000
On Sun, Dec 01, 2013 at 02:00:41PM -0500, Warren Kumari wrote: > I'm not sure where these "wise chairs" are, but I believe we have > consensus for PKIX-TA. It's not ideal but seems good enough. [ FWIW, I still maintain that PKIX-CA (being just a constraint and not necessarily an anchor for the chain) is correct, while PKIX-TA is misleading. PKIX-CA is quite different from DANE-TA, where the association data in fact specifies a trust-anchor. Multiple implementations have failed to correctly capture the semantics of DANE-TA, we should not IMNSHO make PKIX-CA and DANE-TA appear to be more similar than they are. ] Suggested word-smithing final touches: In the Abstract change: ----- Experience has show that people get confused using the three numeric fields the TLSA record. ----- to: ----- Experience has shown that people are sometimes confused by the three numeric fields in the TLSA record. ----- Replace the introduction: ----- In 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. ----- with: ----- In discussions on how to add DANE [RFC6698] technology to new protocols/services there has been repeated confusion as to what the numeric values stand for and even the order of these fields in a TLSA record. This document updates the IANA registry definition for the TLSA record to add 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 parsers in applications and DNS software will accept the new acronyms as alternatives to the underlying numeric values in the presentation format of TLSA records. ----- In "IANA considerations replace: ----- [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. ----- with: ----- [RFC6698] and this document will 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 process the acronyms in a case-insensitive manner. ----- In "Acknowledgements" replace: ----- 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. ----- with ----- The author thanks Jim Schaad, Paul Hoffman, Scott Schmit, Viktor Dukhovni and Wes Hardaker for their helpful comments. ----- -- Viktor.
- [dane] I-D Action: draft-ietf-dane-registry-acron… internet-drafts
- [dane] Start of WGLC for draft-ietf-dane-registry… Warren Kumari
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Andreas Schulze
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Yoav Nir
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Stephen Farrell
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Warren Kumari
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… James Cloos
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… James Cloos
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Olle E. Johansson
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… James Cloos
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Paul Hoffman
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Wes Hardaker
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Warren Kumari
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Wes Hardaker
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Wes Hardaker
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Warren Kumari
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Jim Schaad
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Mark Andrews
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Stephen Kent
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Jim Schaad
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Jim Schaad
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Olafur Gudmundsson
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Olafur Gudmundsson
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Olafur Gudmundsson
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Warren Kumari
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Olafur Gudmundsson
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Viktor Dukhovni
- Re: [dane] Start of WGLC for draft-ietf-dane-regi… Jim Schaad