Re: [art] draft-ietf-dnsop-attrleaf

"John Levine" <johnl@taugh.com> Thu, 27 July 2017 05:03 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E6E129AD2 for <art@ietfa.amsl.com>; Wed, 26 Jul 2017 22:03:57 -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, 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 0rmvBu-Wb2z2 for <art@ietfa.amsl.com>; Wed, 26 Jul 2017 22:03:56 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2F58127868 for <art@ietf.org>; Wed, 26 Jul 2017 22:03:55 -0700 (PDT)
Received: (qmail 19085 invoked from network); 27 Jul 2017 05:03:54 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 27 Jul 2017 05:03:54 -0000
Date: Thu, 27 Jul 2017 05:03:32 -0000
Message-ID: <20170727050332.1445.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: art@ietf.org
Cc: tjw.ietf@gmail.com
In-Reply-To: <CADyWQ+HiVOz1zrhNeEYnzy4hryrhFu+v5GNWqcXdOqQBeB9Cig@mail.gmail.com>
Organization:
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/art/Xu13WqNSg-oNjv8E-Mic5zherJc>
Subject: Re: [art] draft-ietf-dnsop-attrleaf
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 05:03:57 -0000

In article <CADyWQ+HiVOz1zrhNeEYnzy4hryrhFu+v5GNWqcXdOqQBeB9Cig@mail.gmail.com> you write:
>We in DNSOP have a draft that is formalizing the use of _underscore labels
>in DNS, and the creation of a "DNS Global Underscore Scoped Entry
>Registry".   We want the application folks to give us some comments, as we
>feel we are fairly  close to Working Group Last Call.

When I last talked to Dave about this, we had a problem with URI records.

They can be named _service._tranport.whatever, just like SRV, but they
can also be named with enumservice (RFC 3761 and 6117) names,
_subtype._type.whatever.  There are about 24 type names in the
enumservice registry, none of which currently collide the transport
names.  To prevent collisions in the future, we need somehow to
cross-reference the port and service name registries so any attempt
to register a name in one checks for an entry in the other.

I asked IANA and as I recall Michelle said they can do that, but Dave
was worried about the long term viability of a special case in the
registration process.

We also noted that the number of URI records in the wild is still
small, so another possibility would be to change RFC 7553 so
enumservice URIs are _subtype._type._enum.whatever, and then reserve
"enum" as a transport name.

R's,
John