[DNSOP] Spencer Dawkins' Discuss on draft-ietf-dnsop-attrleaf-fix-04: (with DISCUSS)
Spencer Dawkins <spencerdawkins.ietf@gmail.com> Wed, 10 October 2018 21:33 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D487128CB7; Wed, 10 Oct 2018 14:33:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnsop-attrleaf-fix@ietf.org, Benno Overeinder <benno@NLnetLabs.nl>, dnsop-chairs@ietf.org, benno@NLnetLabs.nl, dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.86.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153920722543.5924.12920795403929512043.idtracker@ietfa.amsl.com>
Date: Wed, 10 Oct 2018 14:33:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1ocmqKaLPqpMgaKvBUj1J95WoV4>
Subject: [DNSOP] Spencer Dawkins' Discuss on draft-ietf-dnsop-attrleaf-fix-04: (with DISCUSS)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2018 21:33:46 -0000
Spencer Dawkins has entered the following ballot position for draft-ietf-dnsop-attrleaf-fix-04: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf-fix/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- This is absolutely a "plea for clue Discuss", after which I will immediately clear because the right thing will happen. There are three text blocks that follow this form: If a public specification that defines use of a "TXT" calls for the use of an underscore-prefixed domain name, the global underscored name -- the one closest to the root -- MUST be entered into this registry, if it is not already registered. ->Here is a template of suggested text for this to appear in the IANA ->Considerations section of the specification: "Per" [Attrleaf] "please add the following entry to the DNS Underscore Global Scoped Entry Registry:" Do you have a really strong sense that this shouldn't be If a public specification that defines use of a "TXT" calls for the use of an underscore-prefixed domain name, the global underscored name -- the one closest to the root -- MUST be entered into this registry, if it is not already registered, by adding this text to the IANA Considerations section of the specification: "Per" [Attrleaf] "please add the following entry to the DNS Underscore Global Scoped Entry Registry:" I may be overreacting to "MUST do something like this", which is roughly what I'm reading into "template of suggested text", and if I am, I'm almost sure someone will tell me that ... but I'm not seeing an obvious reason to REQUIRE one of an unbounded set of flowers to bloom ;-)
- [DNSOP] Spencer Dawkins' Discuss on draft-ietf-dn… Spencer Dawkins
- Re: [DNSOP] Spencer Dawkins' Discuss on draft-iet… Warren Kumari
- Re: [DNSOP] Spencer Dawkins' Discuss on draft-iet… Dave Crocker
- Re: [DNSOP] Spencer Dawkins' Discuss on draft-iet… Warren Kumari