Re: [DNSOP] Spencer Dawkins' Discuss on draft-ietf-dnsop-attrleaf-fix-04: (with DISCUSS)

Warren Kumari <warren@kumari.net> Thu, 11 October 2018 12:02 UTC

Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0AB130E1B for <dnsop@ietfa.amsl.com>; Thu, 11 Oct 2018 05:02:03 -0700 (PDT)
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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 o8Ir1NTy-1Vi for <dnsop@ietfa.amsl.com>; Thu, 11 Oct 2018 05:01:57 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B16D130E4D for <dnsop@ietf.org>; Thu, 11 Oct 2018 05:01:52 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id l6-v6so8964299wrt.1 for <dnsop@ietf.org>; Thu, 11 Oct 2018 05:01:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/xcKBMxJ4Dv2amSCt/ZHBc7mI0wwF8/J2hFhVvLYWls=; b=fmztu1Ni5pi8q0kqaMKixjSfk/yySXsZBKBQhh6sPQBhmNbO6EsW3y6XeAlsSJ//y1 xaOimTpL1H+OdswjP/VjJFUPHksdXcMOFwKbBvRtd/oGuMa/QbrYerScGK1BrMNh40e2 TTpp4A2Qbn90QqPmK3nvPEbtXcWW3b7kiRtBzi91QYmwW5N4rWDwhjm78lpJlayBqZDM qHL48k9n9bKDUg2L/HpnBlpkDyTRnOTUFg5kQjiuDR+zbt5lswC5dcqrqjsddmCiMgcu uMDxSi26HPYu+b0hQ4zZoHW/BWS5wWoqx8yPAYX4irYINFELAdd3BNMjMzAWpVlTxE6P vzlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/xcKBMxJ4Dv2amSCt/ZHBc7mI0wwF8/J2hFhVvLYWls=; b=kLDXI6OBARGhi5nwkR3I90LGO7hD9IIc1uE+hiS2tpbcxuu9YEPKtbWvqlZEV4RZmO omwVajq/QwM8xJIXREDyK2B22j6yyt6vylotsypvNUkd5Wmutpk/eOs5+xWvZXSRHd4M OHeiTYXAuT6z5Qbk3ExzVq8QWEWDTTyRO94wUWLhspo1CwCcyApndHxGr6b0WWdjuAYS naPTqQtHedURvvWgSigPZslbdN7OidHbbU2vFnHKC4Vd4eo+lzsFKrCmD3m7pj8f93Zb L75ZiChiWrQegWcudevhwtoambA2I7MUyPP0KmDfinYrd1cnfvstA3S3SGJcoYXqR5b9 Vs4w==
X-Gm-Message-State: ABuFfog5foDOLPj4SZ382rjFRNTz2wotf/OHlhC/qtYhCiPFc5vp02CK rQVyV8dvZC3MrzGI7jCDr586b2TWm6QdzHH5zVgnYQ==
X-Google-Smtp-Source: ACcGV62cA9VceoHcHaYcEk+0rbUPYW1W/oQDZy+bZdnNp89+hxoPx0orgfZZYZ24GMqYgX6+q/cfsTjBtTzc0g/0tGw=
X-Received: by 2002:adf:b6a0:: with SMTP id j32-v6mr1216714wre.55.1539259310144; Thu, 11 Oct 2018 05:01:50 -0700 (PDT)
MIME-Version: 1.0
References: <153920722543.5924.12920795403929512043.idtracker@ietfa.amsl.com>
In-Reply-To: <153920722543.5924.12920795403929512043.idtracker@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 11 Oct 2018 14:01:10 +0200
Message-ID: <CAHw9_iKyD_X-+fUjDv5hhUs--Djw0dZ3r7g94zVfE5bCtbag5w@mail.gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, Benno Overeinder <benno@nlnetlabs.nl>, dnsop <dnsop@ietf.org>, DNSOP Chairs <dnsop-chairs@ietf.org>, draft-ietf-dnsop-attrleaf-fix@ietf.org
Content-Type: multipart/alternative; boundary="000000000000660da00577f2bcf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kK2EdionXQLHuwoBKyEtFeg71dY>
Subject: Re: [DNSOP] Spencer Dawkins' Discuss on draft-ietf-dnsop-attrleaf-fix-04: (with DISCUSS)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Thu, 11 Oct 2018 12:02:04 -0000

On Wed, Oct 10, 2018 at 11:33 PM Spencer Dawkins <
spencerdawkins.ietf@gmail.com>; wrote:

> 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 ;-)
>

Hi,

I just arrived in Amsterdam, and am somewhat bleary, but I'm not sure I
understand your question / point -- is it simply normalizing the IANA
language?
W


>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>


-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf