Re: [DNSOP] [apps-discuss] Draft of interest in DNSOP: draft-ietf-dnsop-attrleaf
"John Levine" <johnl@taugh.com> Mon, 29 August 2016 01:42 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 138CD12D0CD for <dnsop@ietfa.amsl.com>; Sun, 28 Aug 2016 18:42:25 -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 vv9hnlkGq6sa for <dnsop@ietfa.amsl.com>; Sun, 28 Aug 2016 18:42:23 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20B3B12B054 for <dnsop@ietf.org>; Sun, 28 Aug 2016 18:42:23 -0700 (PDT)
Received: (qmail 95348 invoked from network); 29 Aug 2016 01:42:21 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 29 Aug 2016 01:42:21 -0000
Date: Mon, 29 Aug 2016 01:42:00 -0000
Message-ID: <20160829014200.4338.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <1073c89f-1158-ccde-df02-ae9a416eacf5@bbiw.net>
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/dnsop/_KioUNdsu89-Ej2h05yAB0F-EEk>
Cc: dcrocker@bbiw.net
Subject: Re: [DNSOP] [apps-discuss] Draft of interest in DNSOP: draft-ietf-dnsop-attrleaf
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 29 Aug 2016 01:42:25 -0000
>> So after going through all that and then looking at RFC 6335, including >> its assorted references to support for SRV, I gather the IANA table in >> question is: >> >> Service Name and Transport Protocol Port Number Registry > >And the draft -attrleaf- needs to point to this, I believe. So far, so good. >>> For URI records RFC 7553 says they're either named the same as SRV >>> records, or they use enumservice names from the Enumservice >> >> Declaring a namespace as the union of two, independently-maintained >> registries is a very efficient way to encourage -- actually in >> theoretical terms, it guarantees -- collisions. > >Patrik's and John 's postings notwithstanding, I'm still concerned about >the proposed way of handling this, namely to rely on IANA to do a manual >check of the two registries the URI RR might call on. First, it does >not seem reasonable to me to impose that burden on the IANA staff and >second a manual process like that is almost certain to produce errors. Well, either you can persuade Patrik and Olaf to revise RFC 7553 to add a _enumservice psedudo-transport to disambiguate, or you can't. When I look at the enumservice registry, I see that it's not very big and doesn't change very often. Rather than speculating about how hard this would be for IANA, why don't you ask them. Do they have any other groups of registries that they have to monitor for name collisions? How much harder is that than the checking they have to do in a large registry like ports and services to be sure they don't reuse a name? R's, John
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Matt Larson
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Patrik Fältström
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Ray Bellis
- Re: [DNSOP] [apps-discuss] Draft of interest in D… John R Levine
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- [DNSOP] Fwd: Re: [apps-discuss] Draft of interest… Dave Crocker
- [DNSOP] Fwd: Re: [apps-discuss] Draft of interest… Dave Crocker
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- Re: [DNSOP] [apps-discuss] Draft of interest in D… John Levine
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Paul Hoffman
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Patrik Fältström
- Re: [DNSOP] [apps-discuss] Draft of interest in D… John R Levine
- Re: [DNSOP] [apps-discuss] Draft of interest in D… John Levine
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- Re: [DNSOP] [apps-discuss] Draft of interest in D… Dave Crocker
- [DNSOP] _attrleaf - "scoping rules" terminology Dave Crocker