[dispatch] E2M: Proposed Charter (draft version only)
Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Tue, 15 December 2009 19:29 UTC
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E17EF3A6882 for <dispatch@core3.amsl.com>; Tue, 15 Dec 2009 11:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VtPGr1NpXLC for <dispatch@core3.amsl.com>; Tue, 15 Dec 2009 11:29:11 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id BA9893A67F3 for <dispatch@ietf.org>; Tue, 15 Dec 2009 11:29:11 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1NKd4r-0002b2-6o for dispatch@ietf.org; Tue, 15 Dec 2009 20:28:57 +0100
Date: Tue, 15 Dec 2009 20:28:57 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF DISPATCH list <dispatch@ietf.org>
Message-ID: <alpine.DEB.2.00.0912152025000.6395@softronics.hoeneisen.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Subject: [dispatch] E2M: Proposed Charter (draft version only)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 19:29:13 -0000
Hi, As suggested by Mary (DISPATCH co-chair), I wrote up a proposal for an E2M charter (draft) for discussion on this mailing list. Have fun! cheers, Bernie --- E.164 to Metadata (E2M) (proposed charter / draft state) ----------------------- Last Modified: 2009-12-15 Additional information is available at tools.ietf.org/wg/e2m [not yet in use] Chair(s): * TBA Real-time Applications and Infrastructure Area Director(s): * Robert Sparks <rjsparks@nostrum.com> * Cullen Jennings <fluffy@cisco.com> Real-time Applications and Infrastructure Area Advisor: * Cullen Jennings <fluffy@cisco.com> Mailing Lists: General Discussion: e2m@ietf.org [not yet in use] To Subscribe: e2m-request@ietf.org [not yet in use] In Body: subscribe Archive: http://www.ietf.org/mail-archive/web/e2m/index.html [not yet in use] Description of Working Group: Abstract E.164 to Metadata (E2M) will use of the Domain Name System (DNS) for resolving E.164 numbers into metadata to provide information about E.164 numbers in cases where E.164 Number to URI Mapping (ENUM) can not be used. Background ENUM provides an identifier mapping mechanism to map E.164 numbers to Uniform Resource Identifiers (URIs) using the DNS. Thus, ENUM can be used to look up the services associated with an E.164 number. However, it is controversial whether or not the result of an ENUM lookup should always be intended to establish a communications session using the URI found in the corresponding Naming Authority Pointer (NAPTR) DNS Resource Record (RR). Problem Statement Several proposals for Enumservice registrations do not fulfill the above mentioned interpretation, which suggests that an ENUM lookup should always be intended to result in a communications session. These proposals are therefore virtually locked in the process. Such proposals include (but are not limited to) Enumservices for 'cnam' to provide information about the calling party name, 'unused' to provide a hint that a number is not in use, and 'send-n' to describe the structure of an ENUM tree. Another issue is that the result of an ENUM (E2U) lookup always needs to be an URI, which unnecessarily complicates simple mappings. The authors of such Enumservice proposals tried to circumvent the issues by introducing the 'data' URI scheme or inventing completely new URI schemes, with limited success however. The main objection remained that an ENUM lookup should always result in a URI intended to establish a communications session. Proposal The E2M Working Group is chartered to develop a new Dynamic Delegation Discovery System (DDDS) application E2M, which can be used with DNS NAPTR RRs for resolving E.164 numbers into metadata. The resulting metadata can be used (for example) to provide hints about properties of certain ENUM domains or to provide information that can be used as attributes of an E.164 number. E2M will provide the means for services related to E.164 numbers that do not fit into the concept of ENUM (E2U), and thus a way forward for such existing ENUM WG documents in the queue. Along with the E2M DDDS application a new IANA registry will be specified for registration of E2M services. The registration policy shall be Expert Review and Specification Required (see RFC 5226), similarly as specified for Enumservice registrations. The E2M specifications shall reuse a much as possible from the ENUM DDDS and its IANA registry specification. The E2M Working Group may take on further proposals for E2M service registrations (e.g. send-n) until the IANA registration for E2M services is approved by the IESG. Goals and Milestones: Aug 2010 Submit Internet Draft(s) for the E2M DDDS application and its IANA registry specification Dec 2010 Submit 'cnam' and 'unused' as E2M service registrations (Informational) XXX 2011 Close the E2M Working Group (or recharter) Internet-Drafts: http://tools.ietf.org/html/draft-hoeneisen-e164-to-metadata-01 http://tools.ietf.org/html/draft-ietf-enum-unused-04 http://tools.ietf.org/html/draft-ietf-enum-cnam-08 (http://tools.ietf.org/html/draft-bellis-enum-send-n-02) Request For Comments: None
- [dispatch] E2M: Proposed Charter (draft version o… Bernie Hoeneisen
- Re: [dispatch] E2M: Proposed Charter (draft versi… Richard Shockey
- Re: [dispatch] E2M: Proposed Charter (draft versi… Paul Kyzivat
- Re: [dispatch] E2M: Proposed Charter (draft versi… Cartwright, Kenneth
- Re: [dispatch] E2M: Proposed Charter (draft versi… Bernie Hoeneisen
- Re: [dispatch] E2M: Proposed Charter (draft versi… Ray.Bellis
- Re: [dispatch] E2M: Proposed Charter (draft versi… Cartwright, Kenneth
- Re: [dispatch] E2M: Proposed Charter (draft versi… Ray.Bellis
- Re: [dispatch] E2M: Proposed Charter (draft versi… Cartwright, Kenneth
- Re: [dispatch] E2M: Proposed Charter (draft versi… Bernie Hoeneisen
- Re: [dispatch] E2M: Proposed Charter (draft versi… Ray.Bellis
- Re: [dispatch] E2M: Proposed Charter (draft versi… Richard Shockey
- Re: [dispatch] E2M: Proposed Charter (draft versi… Ray.Bellis
- Re: [dispatch] E2M: Proposed Charter (draft versi… Cartwright, Kenneth