Re: [DNSOP] [Ext] draft-ietf-dnsop-attrleaf vs. RFC7553

"John R Levine" <johnl@taugh.com> Thu, 07 February 2019 22:06 UTC

Return-Path: <johnl@taugh.com>
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 A007412D4E8 for <dnsop@ietfa.amsl.com>; Thu, 7 Feb 2019 14:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=RRenfKYn; dkim=pass (1536-bit key) header.d=taugh.com header.b=ACt1br0I
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 zzYpQ4Ls9o9g for <dnsop@ietfa.amsl.com>; Thu, 7 Feb 2019 14:06:20 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24095127AC2 for <dnsop@ietf.org>; Thu, 7 Feb 2019 14:06:19 -0800 (PST)
Received: (qmail 70800 invoked from network); 7 Feb 2019 22:06:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1148e.5c5cabda.k1902; bh=RNGWvs1MBBEoF94iM9RC/xDr6UI/Cc1qxBnhq//E7KU=; b=RRenfKYnHhLY1VmEzGpzyF4/f5sRYs8IGaicb5pmR8gmuIqUizVjZ88KF7Sy90W0KY5CEL8aWQvNS7LIzdXCiL/ipvLPGFynWYGrgZf1M7GxgExGzZPqUPttQw8TYNixl0x4vCoadHbSIS4UEgewv7tqRtArvDamUKznBZAmJyJ538p4SUH4aY6QntwEf1oGnb952Pu0+Tjq5BnsPmi3BHFu+vtsKMB5V1NqvDVON6XqPG7ENTEgVVTIqOnZkmvV
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1148e.5c5cabda.k1902; bh=RNGWvs1MBBEoF94iM9RC/xDr6UI/Cc1qxBnhq//E7KU=; b=ACt1br0IOG8EDTeqNoQ+9dQHF+gOXcJ+2CFjkhBnpuXX5BgvQx88/F+HjfmeXuqTdEtpQsYIcLCn8+9quou6/Mb4Qj8VJrj1PKeVgal+W0zS8ZOv2sOWE3djBWcDqZ4WhmgI17CsXx2Td6xX6K1Jrw/XKTm7cg42yBDPoh9ze4/wxeVTBTqZl393YzSmYQKgis3kWgCKkYFb7UhIk4JhbA2py7lzpsPwzJDduIbrseDY0Bdv+/Jtnxu0Kbc6tFKa
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 07 Feb 2019 22:06:18 -0000
Date: 7 Feb 2019 17:06:17 -0500
Message-ID: <alpine.OSX.2.21.1902071705210.47097@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Paul Hoffman" <paul.hoffman@icann.org>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <CED462CB-6C71-43CA-ADC3-FEE9887B1176@icann.org>
References: <20190207192903.2BDB2200DF041A@ary.qy> <CED462CB-6C71-43CA-ADC3-FEE9887B1176@icann.org>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9gxqrUyYRTlQ989mcWg6UQoFecQ>
Subject: Re: [DNSOP] [Ext] draft-ietf-dnsop-attrleaf vs. RFC7553
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, 07 Feb 2019 22:06:23 -0000

>> Dave moved the duct tape patching up all the places that defined
>> underscored names to draft-ietf-dnsop-attrleaf-fix.
>>
>> See sections 2.3 and 2.3 for URI records.
>>
>> It's still a draft so if it seems wrong, send text.
>
> It is a draft, but it is has been in the RFC Editor's queue for 2.5 months. Unless there is a technical problem, fixing it now (without WG review) could cause more harm than benefit.

Oh, definitely.  When I said wrong I meant like it doesn't work, not that 
a sentence could be reworded.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly