Re: [Enum] Last Call on Presence enumservice field
Jonathan Rosenberg <jdrosen@dynamicsoft.com> Thu, 11 March 2004 06:24 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00928 for <enum-archive@odin.ietf.org>; Thu, 11 Mar 2004 01:24:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1JcC-0000HZ-H1 for enum-archive@odin.ietf.org; Thu, 11 Mar 2004 01:24:21 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2B6OKfs001081 for enum-archive@odin.ietf.org; Thu, 11 Mar 2004 01:24:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1Jbu-0000H0-G3; Thu, 11 Mar 2004 01:24:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1JbG-0000Er-FC for enum@optimus.ietf.org; Thu, 11 Mar 2004 01:23:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00879 for <enum@ietf.org>; Thu, 11 Mar 2004 01:23:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B1JbD-00030q-00 for enum@ietf.org; Thu, 11 Mar 2004 01:23:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B1JaM-0002s5-00 for enum@ietf.org; Thu, 11 Mar 2004 01:22:27 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1B1JZU-0002aS-00 for enum@ietf.org; Thu, 11 Mar 2004 01:21:32 -0500
Received: from dynamicsoft.com ([63.113.46.42]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i2B6LCNr016546; Thu, 11 Mar 2004 01:21:13 -0500 (EST)
Message-ID: <4050054D.9080906@dynamicsoft.com>
Date: Thu, 11 Mar 2004 01:21:01 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Richard Shockey <richard@shockey.us>
CC: enum@ietf.org, jon.peterson@neustar.biz, mankin@psg.com
Subject: Re: [Enum] Last Call on Presence enumservice field
References: <6.0.3.0.2.20040304215737.0469e0e0@popd.ix.netcom.com>
In-Reply-To: <6.0.3.0.2.20040304215737.0469e0e0@popd.ix.netcom.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BIZ_TLD autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Id: Enum Discussion List <enum.ietf.org>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Some comments on the draft: 1. The abstract includes references to rfc2778 and rfc2916bis. I believe that you are not allowed to have references in an abstract, since the abstract frequently appears in isolation, without the rest of the document (see http://www.ietf.org/ID-nits.html). > ENUM exists primarily to facilitate > the interconnection of systems that rely on telephone numbers with > those that use URIs to route transactions. Nit: URIs don't do routing. They're names. Suggest: ".. that use URIs to identify resources." > The IMPP WG of the IETF has a defined a generic URI used to identify > a presence service for a particular resource: the 'pres' URI scheme > (defined in CPP [4]). This document describes an enumservice for > advertising presence information associated with an E.164 number. Nit: I'm not a fan of naming working groups in standards document, since standards frequently persist beyond the group itself. I would suggest: "The Common Profile for Presence (CPP) [4] defines the 'pres' URI scheme for identifying a presence resource". > The presence information that is shared varies by communications > service. The IETF IMPP WG has defined a Presence Information Data > Format (or PIDF [6]) for describing the presence data associated with > a presentity. same comment as above. > The scheme of the URI that will appear in the regexp field of a NAPTR > record using the 'E2U+pres' enumservice will be the 'pres' URI > scheme. There are, however, other URI schemes that can be used to > identify presence services. Its unclear from this text whether the URI MUST be a pres URI, or just SHOULD be a pres URI, and therefore a SIP URI, for example, would be OK. > However, revealing a pres URI in and of itself is unlikely to > introduce many privacy concerns (although depending on the structure > of the URI, it might reveal the full name or employer of the target). I think its worth saying that, in cases where this bit is a security concern (revealing the full name or employer of the target), anonymized URIs can be used to avoid such disclosure. > References This section is not split into normative and informative. I'm assuming that this specification is targeted for PS and not informational, right? Thanks, Jonathan R. Richard Shockey wrote: > > It was the consensus of the WG in Seoul that we proceed to last call > with this document. > > The intent of the last call is to solicit comments before submitting the > ID to the IESG as a Proposed Standard. > > The purpose of a working group Last Call is in the style of "speak now or > forever hold your peace" in case there are fundamental objections which > have > not gotten previous or adequate discussion, or minor errors which need > correction. > > Work group last call will extend for 2 weeks from today March 8 to at > least March 22 though we can modify that if new issues come up. > > Title : Enumservice Registration for Presence > Services > Author(s) : J. Peterson > Filename : draft-ietf-enum-pres-00.txt > Pages : 8 > Date : 2003-12-18 > > This document registers an ENUM service for presence services (as > described in RFC2778 [2]) pursuant to the guidelines in RFC2916bis > [1]. Specifically, this document focuses on provisioning pres URIs > in ENUM. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-enum-pres-00.txt > > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Senior Manager, Strategic Technology Initiatives > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org sip:57141@fwd.pulver.com > ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 > 815.333.1237 > <mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz> > <http://www.neustar.biz> ; <http://www.enum.org> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- [Enum] Last Call on Presence enumservice field Richard Shockey
- Re: [Enum] Last Call on Presence enumservice field Jonathan Rosenberg
- RE: [Enum] Last Call on Presence enumservice field Peterson, Jon
- Re: [Enum] Last Call on Presence enumservice field Jonathan Rosenberg