From richard@shockey.us Tue Dec 15 08:04:34 2009 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACC273A6A03 for ; Tue, 15 Dec 2009 08:04:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.615 X-Spam-Level: X-Spam-Status: No, score=-1.615 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] 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 hdBpl52Ga8ms for ; Tue, 15 Dec 2009 08:04:34 -0800 (PST) Received: from outbound-mail-31.bluehost.com (outbound-mail-31.bluehost.com [69.89.18.151]) by core3.amsl.com (Postfix) with SMTP id E80E93A6A00 for ; Tue, 15 Dec 2009 08:04:33 -0800 (PST) Received: (qmail 19279 invoked by uid 0); 15 Dec 2009 16:04:19 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by outboundproxy2.bluehost.com with SMTP; 15 Dec 2009 16:04:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:thread-index:Content-Language:X-Identified-User; b=oy7tXPGD9ZuUxrzF2OnUZiCI3OJndfR5xnfqCpZbgomiFHJUnCZKyBVaMBnVPAN7CYFLfq/sha0IX6i/k42sNqRcDQ6yB0jnX6YSHy0NbKC00X/mY4E5609/yEzpbeL5; Received: from pool-96-241-233-91.washdc.fios.verizon.net ([96.241.233.91] helo=rshockeyPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1NKZsn-0008AM-71 for enum@ietf.org; Tue, 15 Dec 2009 09:04:19 -0700 From: "Richard Shockey" To: Date: Tue, 15 Dec 2009 11:04:14 -0500 Message-ID: <00bb01ca7da0$40083700$c018a500$@us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00BC_01CA7D76.57322F00" X-Mailer: Microsoft Office Outlook 12.0 thread-index: Acp9BqxzMYZ2jE/UQtuQR24tQZNPWgAmY2Yg Content-Language: en-us X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.241.233.91 authed with richard+shockey.us} Subject: [Enum] FW: I-D ACTION:draft-hoeneisen-e164-to-metadata-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 16:04:34 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_00BC_01CA7D76.57322F00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, December 14, 2009 4:45 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-hoeneisen-e164-to-metadata-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : E.164 to Metadata (E2M) Dynamic Delegation Discovery System (DDDS) Application Author(s) : B. Hoeneisen Filename : draft-hoeneisen-e164-to-metadata-01.txt Pages : 14 Date : 2009-12-14 This document proposes a new Dynamic Delegation Discovery System (DDDS) Application to map E.164 numbers to metadata. It discusses the 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hoeneisen-e164-to-metadata-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------=_NextPart_000_00BC_01CA7D76.57322F00 Content-Type: Message/External-body; name="draft-hoeneisen-e164-to-metadata-01.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-hoeneisen-e164-to-metadata-01.txt" Content-Type: text/plain Content-ID: <2009-12-14133615.I-D@ietf.org> ------=_NextPart_000_00BC_01CA7D76.57322F00 Content-Type: text/plain; name="ATT00261.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00261.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ------=_NextPart_000_00BC_01CA7D76.57322F00-- From bernie@ietf.hoeneisen.ch Tue Dec 15 08:57:55 2009 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D025B3A6AB8; Tue, 15 Dec 2009 08:57:55 -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 ReyE1G-fdnkN; Tue, 15 Dec 2009 08:57:55 -0800 (PST) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id CC91A3A6A9D; Tue, 15 Dec 2009 08:57:54 -0800 (PST) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1NKaiO-0002GC-8r; Tue, 15 Dec 2009 17:57:36 +0100 Date: Tue, 15 Dec 2009 17:57:36 +0100 (CET) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: IETF DISPATCH list Message-ID: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed Content-ID: 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 Cc: IETF ENUM list Subject: [Enum] E2M: Find a proper home for draft-hoeneisen-e164-to-metadata-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 16:57:55 -0000 Hi DISPATCH E.164 to Metadata (E2M) defines a new DDDS application for all the services that do not fit into the original ENUM concept, but still are relevant in today's deployments, such as 'cnam', 'unused' or 'send-n'. draft-hoeneisen-e164-to-metadata decribes how E2M can resolve the issues with certain ENUM WG documents that are currently locked in the publication queue. The sheperding AD (Cullen) does not see E2M happening in the ENUM WG, as he intends to shut down the ENUM WG. He advised me to send this proposal to the DISPATCH WG and task DISPATCH to find a proper home for this work. Several people generally support to E2M proposal, however, some details of the E2M proposal still need more work. So lets find soon a proper home for E2M! cheers, Bernie PS (to ENUM mailing list subscribers): Since -01 the E2M discussion has moved from the ENUM to the DISPATCH mailing list. Those of you who are only subscribed to the ENUM mailing list, please subscribe also to the DISPATCH mailing list and send your comments to (only). PPS (to those of you, who reply to this email): Please remove from the destination list of your replies to avoid crossposting. -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, December 14, 2009 4:45 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-hoeneisen-e164-to-metadata-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : E.164 to Metadata (E2M) Dynamic Delegation Discovery System (DDDS) Application Author(s) : B. Hoeneisen Filename : draft-hoeneisen-e164-to-metadata-01.txt Pages : 14 Date : 2009-12-14 This document proposes a new Dynamic Delegation Discovery System (DDDS) Application to map E.164 numbers to metadata. It discusses the 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hoeneisen-e164-to-metadata-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. From richard@shockey.us Tue Dec 15 09:57:54 2009 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EFC53A684D for ; Tue, 15 Dec 2009 09:57:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.708 X-Spam-Level: X-Spam-Status: No, score=-1.708 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] 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 mI5QzuokYfAW for ; Tue, 15 Dec 2009 09:57:54 -0800 (PST) Received: from outbound-mail-313.bluehost.com (outbound-mail-313.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id 19A9B3A67F8 for ; Tue, 15 Dec 2009 09:57:54 -0800 (PST) Received: (qmail 7113 invoked by uid 0); 15 Dec 2009 17:51:01 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by outboundproxy6.bluehost.com with SMTP; 15 Dec 2009 17:51:01 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:thread-index:Content-Language:X-Identified-User; b=WLpvoz2tNUHA3CMOl7cYBmXTdVK+GLk/NFTpaEiEj3bMqoV0nuwTXoZS/OZXvZ3gcIauZQJxqA+OP7wLI6r+XPRtSifbjD5sQl8M6whPotuYAgSRIKMTxZzLlrdtd/d9; Received: from pool-96-241-233-91.washdc.fios.verizon.net ([96.241.233.91] helo=rshockeyPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1NKbY5-0002mc-8j; Tue, 15 Dec 2009 10:51:01 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" , "'IETF DISPATCH list'" References: In-Reply-To: Date: Tue, 15 Dec 2009 12:50:58 -0500 Message-ID: <010501ca7daf$28e4c2f0$7aae48d0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 thread-index: Acp9p7hjWgKKwjSNQRWPUUlN2ssjDwAB1duw Content-Language: en-us X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.241.233.91 authed with richard+shockey.us} Cc: 'IETF ENUM list' Subject: Re: [Enum] E2M: Find a proper home for draft-hoeneisen-e164-to-metadata-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:57:54 -0000 And as the ENUM WG co-chair (for now) I wholeheartedly support this idea. > -----Original Message----- > From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf > Of Bernie Hoeneisen > Sent: Tuesday, December 15, 2009 11:58 AM > To: IETF DISPATCH list > Cc: IETF ENUM list > Subject: [Enum] E2M: Find a proper home for draft-hoeneisen-e164-to- > metadata-01.txt > > Hi DISPATCH > > E.164 to Metadata (E2M) defines a new DDDS application for all the > services that do not fit into the original ENUM concept, but still are > relevant in today's deployments, such as 'cnam', 'unused' or 'send-n'. > > draft-hoeneisen-e164-to-metadata decribes how E2M can resolve the > issues with certain ENUM WG documents that are currently locked in the > publication queue. > > The sheperding AD (Cullen) does not see E2M happening in the ENUM WG, > as > he intends to shut down the ENUM WG. He advised me to send this > proposal > to the DISPATCH WG and task DISPATCH to find a proper home for this > work. > > Several people generally support to E2M proposal, however, some > details of > the E2M proposal still need more work. > > So lets find soon a proper home for E2M! > > cheers, > Bernie > > > PS (to ENUM mailing list subscribers): > Since -01 the E2M discussion has moved from the ENUM to the DISPATCH > mailing list. Those of you who are only subscribed to the ENUM mailing > list, please subscribe also to the DISPATCH mailing list > and send your > comments to > (only). > > > PPS (to those of you, who reply to this email): > Please remove from the destination list of your > replies to > avoid crossposting. > > > > > -----Original Message----- > From: i-d-announce-bounces@ietf.org [mailto:i-d-announce- > bounces@ietf.org] > On Behalf Of Internet-Drafts@ietf.org > Sent: Monday, December 14, 2009 4:45 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-hoeneisen-e164-to-metadata-01.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : E.164 to Metadata (E2M) Dynamic Delegation > Discovery System (DDDS) Application > Author(s) : B. Hoeneisen > Filename : draft-hoeneisen-e164-to-metadata-01.txt > Pages : 14 > Date : 2009-12-14 > > This document proposes a new Dynamic Delegation Discovery System > (DDDS) Application to map E.164 numbers to metadata. > > It discusses the 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. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-hoeneisen-e164-to-metadata- > 01.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ > enum mailing list > enum@ietf.org > https://www.ietf.org/mailman/listinfo/enum From trutkowski@netmagic.com Tue Dec 15 10:12:25 2009 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FA4D3A6ADF; Tue, 15 Dec 2009 10:12:25 -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 7n9WETHKYTLA; Tue, 15 Dec 2009 10:12:23 -0800 (PST) Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by core3.amsl.com (Postfix) with ESMTP id C70053A68F2; Tue, 15 Dec 2009 10:12:23 -0800 (PST) Received: from [192.168.0.31] ([173.72.150.224]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KUP00G7AH7MCGO9@vms173005.mailsrvcs.net>; Tue, 15 Dec 2009 12:11:51 -0600 (CST) Message-id: <4B27D162.4080000@netmagic.com> Date: Tue, 15 Dec 2009 13:11:46 -0500 From: Tony Rutkowski Organization: Netmagic Associates User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091208 Shredder/3.0 MIME-version: 1.0 To: Bernie Hoeneisen References: In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit Cc: IETF ENUM list , Georges Sebek , IETF DISPATCH list Subject: Re: [Enum] E2M: Find a proper home for draft-hoeneisen-e164-to-metadata-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: trutkowski@netmagic.com List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 18:12:25 -0000 Hi Bernie, Since Rec. ITU-T E.164 is ITU-T's standard and they are significantly engaged in IdM standards activities in SG17, this should probably be coordinated with them. Although it might be regarded as apostasy by some IETFers, it might even be done together with them. cheers, tony > Hi DISPATCH > > E.164 to Metadata (E2M) defines a new DDDS application for all the > services that do not fit into the original ENUM concept, but still are > relevant in today's deployments, such as 'cnam', 'unused' or 'send-n'. > > draft-hoeneisen-e164-to-metadata decribes how E2M can resolve the > issues with certain ENUM WG documents that are currently locked in the > publication queue. > > The sheperding AD (Cullen) does not see E2M happening in the ENUM WG, > as he intends to shut down the ENUM WG. He advised me to send this > proposal to the DISPATCH WG and task DISPATCH to find a proper home > for this work. > > Several people generally support to E2M proposal, however, some > details of the E2M proposal still need more work. > > So lets find soon a proper home for E2M! > > cheers, > Bernie > > > PS (to ENUM mailing list subscribers): > Since -01 the E2M discussion has moved from the ENUM to the DISPATCH > mailing list. Those of you who are only subscribed to the ENUM mailing > list, please subscribe also to the DISPATCH mailing list > and send your > comments to (only). > > > PPS (to those of you, who reply to this email): > Please remove from the destination list of your > replies to avoid crossposting. > > > > > -----Original Message----- > From: i-d-announce-bounces@ietf.org > [mailto:i-d-announce-bounces@ietf.org] > On Behalf Of Internet-Drafts@ietf.org > Sent: Monday, December 14, 2009 4:45 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-hoeneisen-e164-to-metadata-01.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : E.164 to Metadata (E2M) Dynamic Delegation > Discovery System (DDDS) Application > Author(s) : B. Hoeneisen > Filename : draft-hoeneisen-e164-to-metadata-01.txt > Pages : 14 > Date : 2009-12-14 > > This document proposes a new Dynamic Delegation Discovery System > (DDDS) Application to map E.164 numbers to metadata. > > It discusses the 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. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-hoeneisen-e164-to-metadata-01.txt > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ > enum mailing list > enum@ietf.org > https://www.ietf.org/mailman/listinfo/enum > From richard@shockey.us Wed Dec 16 09:05:09 2009 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 846C23A69CE for ; Wed, 16 Dec 2009 09:05:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.665 X-Spam-Level: X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] 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 ql6lOeLB1XUm for ; Wed, 16 Dec 2009 09:05:08 -0800 (PST) Received: from outbound-mail-305.bluehost.com (outbound-mail-305.bluehost.com [67.222.53.251]) by core3.amsl.com (Postfix) with SMTP id B99BB3A6A20 for ; Wed, 16 Dec 2009 09:05:07 -0800 (PST) Received: (qmail 31628 invoked by uid 0); 16 Dec 2009 17:04:54 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by outboundproxy6.bluehost.com with SMTP; 16 Dec 2009 17:04:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-language:X-Identified-User; b=EAQT9jssZk07z6baFvfa5VTtgYwg/tjSBTVkx5TWkHxei1tLTfSixke6637VwHn1A/FaS9gedpG1trR1tqjvPekUEi0k+WDHT53aH1kyq9hPPeK/GH2INTI0I6OrgqDg; Received: from pool-96-241-233-91.washdc.fios.verizon.net ([96.241.233.91] helo=rshockeyPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1NKxIz-0000h7-Ji for enum@ietf.org; Wed, 16 Dec 2009 10:04:53 -0700 From: "Richard Shockey" To: "'IETF ENUM list'" Date: Wed, 16 Dec 2009 12:04:51 -0500 Message-ID: <00e401ca7e71$e1fe63f0$a5fb2bd0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acp+XLdALrx38z9gS3qLVki4quF/zgAFQVZg Content-language: en-us X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.241.233.91 authed with richard+shockey.us} Subject: [Enum] FW: [dispatch] E2M: Proposed Charter (draft version only) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 17:05:09 -0000 FYI my note to DISPATCH -----Original Message----- From: Paul Kyzivat [mailto:pkyzivat@cisco.com] Sent: Wednesday, December 16, 2009 9:33 AM To: Richard Shockey Cc: 'IETF DISPATCH list' Subject: Re: [dispatch] E2M: Proposed Charter (draft version only) Richard Shockey wrote: > +1 in support of this charter > > As the editor of the ENUM draft on CNAM frankly I was a bit appalled at what > I was forced to go through to try and make this work to the satisfaction of > some in the RAI directorate and the IESG. The result was nothing if not a > total kludge (see the draft) . It would have been much simpler to add the > parameter to the SIP URI but there are those that have a layer 10 conviction > that only routing information can be in the URI... but then I couldn't use > the DATA URI since that was too much like TXT RR's etc. So you have to > invent a total kludge PSTN PSTNDATA uri I'm not sure if I am one of "those that have a layer 10 conviction" or not. I did argue against adding a parameter to the sip URI, not because of a general objection to non-routing information in a URI, but rather an objection to spurious information in a URI type that *is* intended for routing. I recommended the data URI, and never understood the arguments against it. This proposal seems like a reasonable way forward, modulo my limited knowledge of DNS. Thanks, Paul > http://tools.ietf.org/html/draft-ietf-enum-cnam-08 > > The point here is, BTW, that phone numbers are not going away. Not now not > ever, some folks just need to get over that issue ASAP. 99.9999 % of all SIP > transactions in the field involve phone numbers and there needs to be > simpler and more effective way of expressing and or looking up metadata > associated with those identifiers. > >> -----Original Message----- >> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On >> Behalf Of Bernie Hoeneisen >> Sent: Tuesday, December 15, 2009 2:29 PM >> To: IETF DISPATCH list >> Subject: [dispatch] E2M: Proposed Charter (draft version only) >> >> 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 >> * Cullen Jennings >> >> Real-time Applications and Infrastructure Area Advisor: >> >> * Cullen Jennings >> >> >> 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 mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > From root@core3.amsl.com Wed Dec 16 13:00:02 2009 Return-Path: X-Original-To: enum@ietf.org Delivered-To: enum@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 235683A6A70; Wed, 16 Dec 2009 13:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20091216210002.235683A6A70@core3.amsl.com> Date: Wed, 16 Dec 2009 13:00:02 -0800 (PST) Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-enumservices-guide-19.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 21:00:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : IANA Registration of Enumservices: Guide, Template and IANA Considerations Author(s) : B. Hoeneisen, A. Mayrhofer, J. Livingood Filename : draft-ietf-enum-enumservices-guide-19.txt Pages : 47 Date : 2009-12-16 This document specifies a revision of the IANA Registration Guidelines for Enumservices, describes corresponding registration procedures, and provides a guideline for creating Enumservice Specifications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-19.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-enum-enumservices-guide-19.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-12-16124631.I-D@ietf.org> --NextPart--