IETF Logo Mail Archive

Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.txt

"John Levine" <johnl@taugh.com> Fri, 23 March 2018 18:02 UTC

Return-Path: <johnl@iecc.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 2B66912DA23 for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 11:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=cnAwGfqE; dkim=pass (1536-bit key) header.d=taugh.com header.b=V2ngykXl
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 bvfIxyWYu80k for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 11:02:50 -0700 (PDT)
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 4B2CA12DA12 for <dnsop@ietf.org>; Fri, 23 Mar 2018 11:02:50 -0700 (PDT)
Received: (qmail 12985 invoked from network); 23 Mar 2018 18:02:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=32aa.5ab54149.k1803; bh=+HOUYu1oam6pWIDj2ts1aOd89MH5vtn01ueUG7/GMcs=; b=cnAwGfqEGSwR1ZsaxKkyRDlO86h2ta9c4OGqqrv1dRtkmN6kOeFVPJrG5za92XVj+BMN9FS/q5UwPgW53uvSDzJzJtuxvDuPT6lp+hmDuJWMtKBdKNE74au4T6HWYrgSbEjRo5XpvOq4NKxFMhFlLxl3/q4YOyTsXq78iDoISK+68XMkfn4UWSloXmMuWrRJAwvIk1znxutLUrAwpa5sOSjPG2ivz4C0EdX0Ihw37q8aRiMpdzPxRYby3euP/+K6
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=32aa.5ab54149.k1803; bh=+HOUYu1oam6pWIDj2ts1aOd89MH5vtn01ueUG7/GMcs=; b=V2ngykXlXAyoxVXfkZdPiMP+8X6vmYDCevviv198XymL+Ow8IR8pO5+lCCLdJNJLN7LhErrmrWQWDtZ1iegjANFWvU5H389aZ/rnFJDSCMYW5ITulKVUctBp6v1iaymrSMPadhOZDu+28hbOG9fyRqDXThQD7JLgkw6MZYXYdf+k5s/fi+3c8vvylgQ/vvmuzbg/BCuZyd3VGIhly/R1rjKXzzrCLOr7HuQnEEggF79lNqOvOUElvNqP9nuyE9iX
Received: from ary.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 23 Mar 2018 18:02:49 -0000
Received: by ary.iecc.com (Postfix, from userid 501) id 9B2AD238892C; Fri, 23 Mar 2018 18:02:47 +0000 (GMT)
Date: Fri, 23 Mar 2018 18:02:47 +0000
Message-Id: <20180323180248.9B2AD238892C@ary.iecc.com>
From: John Levine <johnl@taugh.com>
To: art@ietf.org, dnsop@ietf.org
Cc: dcrocker@bbiw.net, ajs@anvilwalrusden.com, petr.spacek@nic.cz
In-Reply-To: <6d3c77a3-2326-a4b4-1e99-50fe4647d7c8@dcrocker.net>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/WOSJndPv9cWHx31CPPca0Mp8RZI>
Subject: Re: [DNSOP] [art] New Version Notification for draft-ietf-dnsop-attrleaf-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 23 Mar 2018 18:02:52 -0000

In article <6d3c77a3-2326-a4b4-1e99-50fe4647d7c8@dcrocker.net> you write:
>It occurs to me that some folk might not have a perfect memory of a 
>dnsop working group agreement from Aug, 2017.  So here's a tag into it:
>
>    https://www.ietf.org/mail-archive/web/dnsop/current/msg20708.html

I see a message on dnsop from you proposing a bunch of things
including "rationalizing" names, and comments from Andrew and Peter
saying they like that approach.

Maybe I'm odd, but I wouldn't call a change to SRV that retroactively
breaks some unknown and probably large number of existing SRV records
"rationalizing".

I agree that a registry of top level underscore names would be a good
idea.  I completely disagree with the assertion that we need to make
any significant change to the way the second level names are managed.

A good way to rationalize them would be to document the the rules in
one place with pointers to the relevant registries.

R's,
John

v2.23.0 | Report a Bug | By Email