Re: [DNSOP] [art] Attrleaf _second-Level modifications (was: Re: Fwd: New Version Notification for draft-ietf-dnsop-attrleaf-03.txt)

"John Levine" <johnl@taugh.com> Sat, 24 March 2018 14:25 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 1000B1270B4 for <dnsop@ietfa.amsl.com>; Sat, 24 Mar 2018 07:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.762
X-Spam-Level:
X-Spam-Status: No, score=-1.762 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] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=fd6BunG7; dkim=pass (1536-bit key) header.d=taugh.com header.b=cfM3i4Qc
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 6wAEYYvsPxfn for <dnsop@ietfa.amsl.com>; Sat, 24 Mar 2018 07:25:17 -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 72B0B126CE8 for <dnsop@ietf.org>; Sat, 24 Mar 2018 07:25:16 -0700 (PDT)
Received: (qmail 56404 invoked from network); 24 Mar 2018 14:25:15 -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=dc52.5ab65fcb.k1803; bh=BJGwjHPyCZi9YxnHL0V1worK9EcW7aUqTkawnTtrys4=; b=fd6BunG75ZuaR71CbKl3xjLF+GSV4ok1J9jG+Rh4Z+c5pH13gh6lqaCK74taGM+dpklpegg1+mVqPimZqFr+Hx9bDI6IAUbE5rDa+/crMzzxLgRGbwLCk02bmJ3boqcqk+gbuBXgYd8Jx+ZAgsnbtL5XI0VP7nVfZDubGwSwgzkiEOgn65Q0ptwTakl0u/No+CrsRAbzATmeFkPdiaOEvN0KiAi35KarQ0Kge4EbFwBnGnBAN9LuJ4y9+kOEt9HZ
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=dc52.5ab65fcb.k1803; bh=BJGwjHPyCZi9YxnHL0V1worK9EcW7aUqTkawnTtrys4=; b=cfM3i4QceLC6WpZE9SZYTS3EnKPFVqlyIABux6/kb/0VpGdHyB1W/oVTanOV98YyephiBAaf6IG6gcbtvR8fApZ+tRo0l8EwlT4+jx2yDLYpYMwsalOaG7alsBX0pPJZ6y1VtPOOaxYilm4DDg5hjpM9PM35VYYRi49kwRV76CA8o46z1nB7bxmzMk7FjuPo9SCUl1L3qrvjmiqDUjbEAlLqBaXuDXmtltFg2iFcOBHLVzLidve/XgZt6l9688iK
Received: from dhcp-9173.meeting.ietf.org ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 24 Mar 2018 14:25:14 -0000
Received: by dhcp-9173.meeting.ietf.org (Postfix, from userid 501) id 73168238E24E; Sat, 24 Mar 2018 14:25:14 +0000 (GMT)
Date: 24 Mar 2018 14:25:14 +0000
Message-Id: <20180324142514.73168238E24E@dhcp-9173.meeting.ietf.org>
From: "John Levine" <johnl@taugh.com>
To: art@ietf.org, dnsop@ietf.org
Cc: dcrocker@bbiw.net
In-Reply-To: <eaa2629a-48de-f858-b3da-e2c84abe6c2c@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/woW6Ct8y-H2GN_iZngjQpxC7fas>
Subject: Re: [DNSOP] [art] Attrleaf _second-Level modifications (was: Re: Fwd: 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: Sat, 24 Mar 2018 14:25:18 -0000

Finally catching up.

>For any use of an underscore first-level name, that also uses a 
>second-level name, the authority over that second-level belongs entirely 
>and solely to that first-level name.
>
>    ..._my-second._firsta.example
>
>and
>
>    ..._my-second._firstb.example
>
>have no conflict.

Aha.  That's somewhat different from what I gathered you were saying before.

>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.

Seems right.  If we want to deal with URI names it needs a similar
update to RFC 6117 to put the enumservice type names into the
attrleaf table with a pointer back to the enumservice registry
for the second level subtypes.

>As for the proposed 'common, second-level' table...
>
>Given that this seems to reduce the Attrleaf 'common second-level' table 
>to only _adsp, I think it best to remove that table entirely from the 
>main attrleaf document, and instead have the separate fixup document 
>contain some text specific to the DKIM document's domain naming scheme, 
>to indicate how future second-level names should be assigned.  Since 
>ADSP is historic, specifying modification to it doesn't make sense to 
>modify it.

Agree, no need to set up a registry for one dusty name.

R's,
John