Re: [DNSOP] Attrleaf _second-Level modifications

Ray Bellis <ray@bellis.me.uk> Thu, 22 March 2018 16:55 UTC

Return-Path: <ray@bellis.me.uk>
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 29DBC126D3F for <dnsop@ietfa.amsl.com>; Thu, 22 Mar 2018 09:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 pGYYQVsSx4Bn for <dnsop@ietfa.amsl.com>; Thu, 22 Mar 2018 09:55:18 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F98120726 for <dnsop@ietf.org>; Thu, 22 Mar 2018 09:55:18 -0700 (PDT)
Received: from nat64-d8.meeting.ietf.org ([31.130.238.216]:57966 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1ez3Uh-0004bU-9S (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Thu, 22 Mar 2018 16:55:15 +0000
To: dnsop@ietf.org
References: <152150434726.9747.3586273536264334521.idtracker@ietfa.amsl.com> <f7b85bac-b050-5003-2df0-a48b1ef2f929@dcrocker.net> <alpine.OSX.2.21.1803201614180.8721@dhcp-8344.meeting.ietf.org> <eaa2629a-48de-f858-b3da-e2c84abe6c2c@dcrocker.net>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <549a02e0-5375-cbdb-8c4d-8cf129ea600b@bellis.me.uk>
Date: Thu, 22 Mar 2018 16:55:16 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <eaa2629a-48de-f858-b3da-e2c84abe6c2c@dcrocker.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1lM2h_iaVSXXknJPb7PwH0SSjEU>
Subject: Re: [DNSOP] Attrleaf _second-Level modifications
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: Thu, 22 Mar 2018 16:55:22 -0000

On 22/03/2018 15:12, Dave Crocker wrote:

> In the case of SRV, for example, that means that for the core SRV
> template specification document:
> 
>      1. The first-level, _Proto name assignment text has to be updated
> to use the new, Attrleaf global table.
> 
>      2. The second-level _Service name assignment text can remain
> unchanged, per RFC 6335.
> 
> Point #2 is actually not 'special' at all.  I'd entirely missed that the
> very strong need to do the first-level fixup did not also require
> messing with the existing second-level.

That's the conversation I thought we'd had in Orlando :p

Ray