Re: [DNSOP] URI text for attrleaf? (was: Re: New Version Notification for draft-ietf-dnsop-attrleaf-06.txt)

"John R. Levine" <johnl@iecc.com> Sat, 31 March 2018 16:08 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 E6B8B12D880 for <dnsop@ietfa.amsl.com>; Sat, 31 Mar 2018 09:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com
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 Rj7PRCn3Sj1B for <dnsop@ietfa.amsl.com>; Sat, 31 Mar 2018 09:08:33 -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 07DE11270A0 for <dnsop@ietf.org>; Sat, 31 Mar 2018 09:08:32 -0700 (PDT)
Received: (qmail 75912 invoked from network); 31 Mar 2018 16:08:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=12886.5abfb27f.k1803; bh=pcaDixYE4jJ/wIq9zrMb3/Ps4zrnqhFzfMnWSwP2Z+o=; b=rxqXc9hV+n6Fn5D6HvR8R7wYbFyTtEzMRnxWp1dxk0OWW+MighKDvQ5FJ7Xj0038vTILryj277ZM0K19ccSRc27X5YEhrISwqNBrwGPRKdECbBwF5TM491HEo4Kle1CZDn8IKV4WGwN0yz4rvA7SFqjPaq5wLTUGFHKVkHSzVab6gXYWe9PO8Jq604CGZGX+EVgPkY2bozB0LsqNhMDbOMYx3gevhwvPLJkwWL5w2UMZ2KnUOOKhX9fjbikNUlZO
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 31 Mar 2018 16:08:31 -0000
Date: Sat, 31 Mar 2018 12:08:29 -0400
Message-ID: <alpine.OSX.2.21.1803310916500.3351@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: dcrocker@bbiw.net
Cc: dnsop@ietf.org
In-Reply-To: <81903d1e-ae7c-8955-8a55-b4f7383f02c4@dcrocker.net>
References: <152225104728.29861.12317860292894301994.idtracker@ietfa.amsl.com> <81903d1e-ae7c-8955-8a55-b4f7383f02c4@dcrocker.net>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XYijqc1aIwHn_pOLZu0RusE9y0U>
Subject: Re: [DNSOP] URI text for attrleaf? (was: Re: New Version Notification for draft-ietf-dnsop-attrleaf-06.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, 31 Mar 2018 16:08:35 -0000

On Fri, 30 Mar 2018, Dave Crocker wrote:
> what that means.  (Nor of "ENUMService Parameter".) I assume it is meant to 
> draw from
>
> https://www.iana.org/assignments/enum-services/enum-services.xhtml#enum-services-1

Agreed.

> but I can't figure exactly how, nor how to resolve drawing the global value 
> from two independent namespaces...

> But this ignores handling names from enumservice.
> Thoughts?  Suggestion?  Text?

Add URI entries for all of the enumservices types, _acct, _email, _ems, 
_fax, _ft, _h323, _iax, _ical-access, _ical-sched, _ifax, _im, _mms, 
_pres, _pstn, _sip, _sms, _unifmsg, _vcard, _videomsg, _voice, _voicemsg, 
_vpim, _web, _xmpp that point to RFC 7553.

This has the hypothetical possibility that someone might define a 
transport with a name the same as an enumservice type, but I think we're 
into "don't do that" territory.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly