From enum-bounces@ietf.org Thu Oct 04 16:18:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdX6c-0004Yu-4S; Thu, 04 Oct 2007 16:15:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdX6b-0004Yc-4c; Thu, 04 Oct 2007 16:15:33 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdX6a-0006Np-0l; Thu, 04 Oct 2007 16:15:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id F0DA5329F3; Thu, 4 Oct 2007 20:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IdX65-00011k-S7; Thu, 04 Oct 2007 16:15:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 04 Oct 2007 16:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-cnam-06.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --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 for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for URI type 'pstn' Author(s) : R. Shockey Filename : draft-ietf-enum-cnam-06.txt Pages : 14 Date : 2007-10-4 This document registers the Enumservice 'pstn' and subtype 'cnam' using the URI scheme 'pstn:' as per the IANA registration process defined in the ENUM specification, RFC 3761[1] and registers a new URI type 'pstn:' according to the URI registration procedure in RFC 4395 [15]. This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the Public Switched Telephone Network (PSTN) that may be displayed on VoIP or other Real-time Client User Agents (CUA). The pstn URI is created to facilitate this transfer, however this URI may be used to transport other PSTN data in the future. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-cnam-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-cnam-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-4154123.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-cnam-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-cnam-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-4154123.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Thu Oct 04 21:37:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idc4d-0000Fu-Gi; Thu, 04 Oct 2007 21:33:51 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idc4c-0000CN-HO; Thu, 04 Oct 2007 21:33:50 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Idc4b-00083i-Tg; Thu, 04 Oct 2007 21:33:50 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l951XMlC017923 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 4 Oct 2007 18:33:31 -0700 From: "Richard Shockey" To: , Date: Thu, 4 Oct 2007 21:31:44 -0400 Message-ID: <047301c806ef$8294f650$87bee2f0$@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: AcgG73xvlvmFOVwrSta7zBc9QnPNgg== Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: Subject: [Enum] I'd like to guage interest in restarting a BOF on the subject of Peppermint. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This time last year I tried to start up a BOF on some of the ongoing provisioning issues between various forms of ENUM registries and network entities. I've had a few folks ask what ever happened to that. I still think there is a strong need to do this and the work could have relevance if the scope were expanded not to be just service provider to registry but also PBX to registries as well. I'd like to test the water to see if there is any interest in doing this in Vancouver. The original BOF proposal was this: Comments as usual are welcome Peppermint BOF Provisioning Extensions in Peering Registries for Multimedia Intererconnection. Mailing Lists: BOF chairs: Richard Shockey [rich.shockey@neustar.biz] Temporary Area Directorate: Real Time Applications (RAI) Ultimate Area Directorate: TBD BOF Purpose. The ENUM and SPEERMINT working groups are working on various aspects of Multi Media Interconnection. ENUM is specifically chartered to develop protocols that involve the translation of E.164 numbers to URI's. SPEERMINT has been chartered to develop best current practices among real-time application service providers and how such services interconnect across domain boundaries. It is clear from discussions in both working groups that Multi-Media Interconnection will require various forms of data to be exchanged among administrative domains outside the normal scope of establishing a SIP session. Such data exchanges might be provisioning of various forms of Registries containing mappings of phone numbers to URI, policies surrounding the admission to points of network interconnection and the distribution of Registry data to various types of databases. The purpose of the BOF is to determine the need and scope for such data exchanges, what existing protocols need to be adapted to meet those needs and the appropriate schema and queries are needed to facilitate such exchanges. The IETF has in the past done significant work on data exchanges among various administrative entities. In particular the PROVREG working group developed various schema and query mechanisms to facilitate the exchange of data among domain name registries and registrars. The ENUM Working group has adapted PROVREG working group protocols to develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS tree. However, there has been little adoption of RFC 4114, and many of the participants of the SPEERMINT working group require both data models and protocol features not found in RFC 4114. The proposed PEPPERMINT working group will build upon the knowledge gained from those efforts, and the intent of this proposed working group is to find a provisioning solution for peering as defined by SPEERMINT. The final work product(s) from this working group will be based upon XML. Additionally, bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, or HTTP/SOAP. Proposed Deliverables Requirements for SPEERMINT data exchange. Provisioning of SPEERMINT data registries. Provisioning of SPEERMINT/ENUM data caches. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 05 12:19:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idppw-00029i-2B; Fri, 05 Oct 2007 12:15:36 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idpps-00025B-T9; Fri, 05 Oct 2007 12:15:32 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Idpps-0001lM-Fq; Fri, 05 Oct 2007 12:15:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 600D92AC5F; Fri, 5 Oct 2007 16:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IdppO-0004y7-4g; Fri, 05 Oct 2007 12:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 05 Oct 2007 12:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-cnam-07.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --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 for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for URI type 'pstndata' URI type 'pstn' Author(s) : R. Shockey Filename : draft-ietf-enum-cnam-07.txt Pages : 14 Date : 2007-10-5 This document registers the Enumservice 'pstn' and subtype 'cnam' using the URI scheme 'pstndata:' as per the IANA registration process defined in the ENUM specification, RFC 3761[1] and registers a new URI type 'pstndata:' according to the URI registration procedure in RFC 4395 [15]. This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the Public Switched Telephone Network (PSTN) that may be displayed on VoIP or other Real-time Client User Agents (CUA). The pstndata URI is created to facilitate this transfer, however this URI may be used to transport other PSTN data in the future. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-07.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-cnam-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-cnam-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-5114217.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-cnam-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-cnam-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-5114217.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Mon Oct 08 13:06:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IevzK-000838-Py; Mon, 08 Oct 2007 13:01:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IevzJ-000820-KR for enum@ietf.org; Mon, 08 Oct 2007 13:01:49 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IevzI-000626-B2 for enum@ietf.org; Mon, 08 Oct 2007 13:01:49 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l98H1QDq027104 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 8 Oct 2007 10:01:27 -0700 From: "Richard Shockey" To: Date: Mon, 8 Oct 2007 13:01:30 -0400 Message-ID: <012b01c809cc$e05e6480$a11b2d80$@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: AcgJzN944URXziXDQW+rNilIORVXgg== Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [Enum] a basic reminder Vancouver is coming up ... X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org So I'd like to get a reasonable start on agenda items. In addition I like to gently push existing ID authors that want to discuss drafts to please get your revisions in ASAP so we can have reasonable discussion before the meeting. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 08 13:19:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IewDP-0000RE-8P; Mon, 08 Oct 2007 13:16:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IewDN-0000R9-Bh for enum@ietf.org; Mon, 08 Oct 2007 13:16:21 -0400 Received: from newdev.eecs.harvard.edu ([140.247.60.212]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IewDL-0006Sk-S1 for enum@ietf.org; Mon, 08 Oct 2007 13:16:21 -0400 Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 0A7A85AE048; Mon, 8 Oct 2007 13:15:37 -0400 (EDT) To: enum@ietf.org Message-Id: <20071008171537.0A7A85AE048@newdev.eecs.harvard.edu> Date: Mon, 8 Oct 2007 13:15:37 -0400 (EDT) From: sob@harvard.edu (Scott O. Bradner) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [Enum] RFC 3761 bis revision X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org sorry for being tardy here - as was announced on this list a while back I've agreed to take over the editing 3761bis (currently draft-ietf-enum-3761bis-01.txt) please send the list any specific suggestions/edits/etc asap - I'd like to get as many issues worked out as possible before submitting a revision in a few weeks tnx Scott _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 09 05:54:48 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfBjB-0000xw-IK; Tue, 09 Oct 2007 05:50:13 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfBjA-0000xj-HI for enum@ietf.org; Tue, 09 Oct 2007 05:50:12 -0400 Received: from mail.sbg.nic.at ([192.174.68.200]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IfBj9-0003Of-PT for enum@ietf.org; Tue, 09 Oct 2007 05:50:12 -0400 Received: from localhost [127.0.0.1] by mail.sbg.nic.at with XWall v3.41 ; Tue, 9 Oct 2007 11:50:09 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] RFC 3761 bis revision Date: Tue, 9 Oct 2007 11:50:09 +0200 Message-ID: <8BC845943058D844ABFC73D2220D466506C31993@nics-mail.sbg.nic.at> In-Reply-To: <20071008171537.0A7A85AE048@newdev.eecs.harvard.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] RFC 3761 bis revision thread-index: AcgJz7KO2ffHLzh7StOHF3PU36ByQAAiDIjw From: "Otmar Lendl" To: "Scott O. Bradner" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Scott, > please send the list any specific suggestions/edits/etc asap=20 > - I'd like to get as many issues worked out as possible before=20 > submitting a revision in a few weeks There has been a lot of discussions concerning the "D" flag in NAPTRs and the use of URI records. The consensus has been that this is not a workable solution for a User ENUM / Infrastructure ENUM coexistance. It also blocks the use of DNS wildcards in ENUM Domains which are often needed when dealing with open numbering plans. Detailed arguments are here: http://www1.ietf.org/mail-archive/web/enum/current/msg05736.html http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00116.html http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00141.html http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00138.html http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00119.html http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00120.html (Most of the mails were crossposted to the ietf list.) /ol --=20 / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 09 07:09:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfCvF-0008Ng-L2; Tue, 09 Oct 2007 07:06:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfCvE-0008Lw-DH for enum@ietf.org; Tue, 09 Oct 2007 07:06:44 -0400 Received: from norman.insensate.co.uk ([213.152.49.123] helo=insensate.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfCv8-0002Ft-44 for enum@ietf.org; Tue, 09 Oct 2007 07:06:44 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 69F455BC54; Tue, 9 Oct 2007 12:06:14 +0100 (BST) In-Reply-To: <8BC845943058D844ABFC73D2220D466506C31993@nics-mail.sbg.nic.at> References: <8BC845943058D844ABFC73D2220D466506C31993@nics-mail.sbg.nic.at> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <678CFE58-C75E-40EC-B1AE-7C8D264E6E98@insensate.co.uk> Content-Transfer-Encoding: 7bit From: lconroy Subject: Re: [Enum] RFC 3761 bis revision Date: Tue, 9 Oct 2007 12:06:14 +0100 To: Otmar Lendl X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: enum@ietf.org, "Scott O. Bradner" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Otmar, Now I'm mightily confused. The URI draft is no longer considered a candidate for update to RFC3761. Thus I do not understand how these referenced RIPE emails relate to an update to *the existing* RFC 3761. They reflect a past discussion, since resolved. The authors spell this out in their draft-ietf-enum-uri-01.txt: " The next version of this draft should NOT be a work item of the ENUM wg, but instead an individual submission of name draft-faltstrom-rrtype-uri-00.txt. ". What is the issue requiring an update to RFC3761 that you think these mails reflect? all the best, Lawrence On 9 Oct 2007, at 10:50, Otmar Lendl wrote: > Scott, >> please send the list any specific suggestions/edits/etc asap >> - I'd like to get as many issues worked out as possible before >> submitting a revision in a few weeks > > There has been a lot of discussions concerning the "D" flag in > NAPTRs and the use of URI records. The consensus has been that > this is not a workable solution for a User ENUM / Infrastructure > ENUM coexistance. It also blocks the use of DNS wildcards in ENUM > Domains which are often needed when dealing with open numbering plans. > > Detailed arguments are here: > > http://www1.ietf.org/mail-archive/web/enum/current/msg05736.html > http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00116.html > http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00141.html > http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00138.html > http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00119.html > http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00120.html > > (Most of the mails were crossposted to the ietf list.) > > /ol _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 09 07:32:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfDIA-0000cP-WD; Tue, 09 Oct 2007 07:30:27 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfDIA-0000aq-LP for enum@ietf.org; Tue, 09 Oct 2007 07:30:26 -0400 Received: from nat.labs.nic.at ([83.136.33.3] helo=labs.nic.at) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IfDI5-00064r-0t for enum@ietf.org; Tue, 09 Oct 2007 07:30:21 -0400 Received: from lendl by labs.nic.at with local (Exim 3.36 #1 (Debian)) id 1IfDI1-0001yY-00; Tue, 09 Oct 2007 13:30:17 +0200 Date: Tue, 9 Oct 2007 13:30:17 +0200 From: Otmar Lendl To: lconroy Subject: Re: [Enum] RFC 3761 bis revision Message-ID: <20071009113017.GA7565@nic.at> Mail-Followup-To: Otmar Lendl , lconroy , "Scott O. Bradner" , enum@ietf.org References: <8BC845943058D844ABFC73D2220D466506C31993@nics-mail.sbg.nic.at> <678CFE58-C75E-40EC-B1AE-7C8D264E6E98@insensate.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <678CFE58-C75E-40EC-B1AE-7C8D264E6E98@insensate.co.uk> User-Agent: Mutt/1.5.9i X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: enum@ietf.org, "Scott O. Bradner" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Lawrence, On 2007/10/09 13:10, lconroy wrote: > Hi Otmar, > Now I'm mightily confused. In the ITU sense of the word? > The URI draft is no longer considered a candidate for update to > RFC3761. Thus I do not understand how these referenced RIPE emails > relate to an update to *the existing* RFC 3761. They reflect a past > discussion, since resolved. >What is the issue requiring an update to RFC3761 that you think these >mails reflect? Scott asked about changes to draft-ietf-enum-3761bis-01 and not changes to RFC 3761. My mail was not intended to start the discussion anew, but as simple answers to Scott's question on what edits are needed for -02. It is my understanding as well, that the removal of the URI RR stuff has been agreed upon. To be more specific: In "2.4.1. Flags", remove the D flag, and remove the URI RRs from 4.1. Cheers, /ol -- / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 09 10:55:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfGRD-0007rd-Hl; Tue, 09 Oct 2007 10:51:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfGRC-0007qt-PU for enum@ietf.org; Tue, 09 Oct 2007 10:51:58 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfGR6-0002BD-H1 for enum@ietf.org; Tue, 09 Oct 2007 10:51:58 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l99Ep9k0032342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Oct 2007 07:51:14 -0700 From: "Richard Shockey" To: "'Otmar Lendl'" , "'lconroy'" References: <8BC845943058D844ABFC73D2220D466506C31993@nics-mail.sbg.nic.at> <678CFE58-C75E-40EC-B1AE-7C8D264E6E98@insensate.co.uk> <20071009113017.GA7565@nic.at> In-Reply-To: <20071009113017.GA7565@nic.at> Subject: RE: [Enum] RFC 3761 bis revision Date: Tue, 9 Oct 2007 10:51:10 -0400 Message-ID: <005201c80a83$dd245b00$976d1100$@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: AcgKahXhnhZT4R0QQNiBDdcQfvVebAAGYz4Q Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: enum@ietf.org, "'Scott O. Bradner'" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The larger issue is what to do with the U flag itself and under what conditions can a new flag be created. > -----Original Message----- > From: Otmar Lendl [mailto:lendl@nic.at] > Sent: Tuesday, October 09, 2007 7:30 AM > To: lconroy > Cc: enum@ietf.org; Scott O. Bradner > Subject: Re: [Enum] RFC 3761 bis revision > > > Lawrence, > > On 2007/10/09 13:10, lconroy wrote: > > Hi Otmar, > > Now I'm mightily confused. > > In the ITU sense of the word? > > > The URI draft is no longer considered a candidate for update to > > RFC3761. Thus I do not understand how these referenced RIPE emails > > relate to an update to *the existing* RFC 3761. They reflect a past > > discussion, since resolved. > > >What is the issue requiring an update to RFC3761 that you think these > >mails reflect? > > Scott asked about changes to draft-ietf-enum-3761bis-01 and not > changes to RFC 3761. > > My mail was not intended to start the discussion anew, but as simple > answers to Scott's question on what edits are needed for -02. It is my > understanding as well, that the removal of the URI RR stuff has been > agreed upon. > > To be more specific: In "2.4.1. Flags", remove the D flag, and remove > the URI RRs from 4.1. > > Cheers, > > /ol > -- > / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ > | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | > \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 11 08:30:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ifx78-0006JT-Pu; Thu, 11 Oct 2007 08:26:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfeFV-0003RI-8K; Wed, 10 Oct 2007 12:17:29 -0400 Received: from mail.xconnect.net ([213.187.46.35] helo=xconnect.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfeFI-0007Kr-BD; Wed, 10 Oct 2007 12:17:25 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 10 Oct 2007 17:16:42 +0100 Message-ID: <062B8EE81F2EC945A577C3EFAE1DD68E89571C@mail.xconnect.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] I'd like to guage interest in restarting a BOF on thesubject of Peppermint. Thread-Index: AcgG73xvlvmFOVwrSta7zBc9QnPNggEZjYdw References: <047301c806ef$8294f650$87bee2f0$@us> From: "Eli Katz" To: "Richard Shockey" , , X-Spam-Score: 0.0 (/) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c X-Mailman-Approved-At: Thu, 11 Oct 2007 08:26:05 -0400 Cc: Subject: [Enum] RE: [Speermint] I'd like to guage interest in restarting a BOF on thesubject of Peppermint. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I concur with Rich, in that any efforts to help standardisation of SP Registry Provisioning will be useful to the telecom industry.=20 The lack of a commonly used (standards based or other) methodology is currently hindering take up of industry-demanded registry-based interconnection. Eli Eli Katz Founder & CEO XConnect - Bridging the VoIP Islands T : +44 (0) 870 794 1100 F : +44 (0) 870 794 1101 M : +44 (0) 7973 632 364 eli@xconnect.net www.xconnect.net=20 -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us]=20 Sent: 05 October 2007 02:32 To: enum@ietf.org; speermint@ietf.org Subject: [Speermint] I'd like to guage interest in restarting a BOF on thesubject of Peppermint. This time last year I tried to start up a BOF on some of the ongoing provisioning issues between various forms of ENUM registries and network entities. I've had a few folks ask what ever happened to that. I still think there is a strong need to do this and the work could have relevance if the scope were expanded not to be just service provider to registry but also PBX to registries as well. I'd like to test the water to see if there is any interest in doing this in Vancouver. The original BOF proposal was this: Comments as usual are welcome Peppermint BOF Provisioning Extensions in Peering Registries for Multimedia Intererconnection. Mailing Lists: BOF chairs: Richard Shockey [rich.shockey@neustar.biz] Temporary Area Directorate: Real Time Applications (RAI) Ultimate Area Directorate: TBD BOF Purpose. The ENUM and SPEERMINT working groups are working on various aspects of Multi Media Interconnection. ENUM is specifically chartered to develop protocols that involve the translation of E.164 numbers to URI's. =20 SPEERMINT has been chartered to develop best current practices among real-time application service providers and how such services interconnect across domain boundaries. It is clear from discussions in both working groups that Multi-Media Interconnection will require various forms of data to be exchanged among administrative domains outside the normal scope of establishing a SIP session. Such data exchanges might be provisioning of various forms of Registries containing mappings of phone numbers to URI, policies surrounding the admission to points of network interconnection and the distribution of Registry data to various types of databases. The purpose of the BOF is to determine the need and scope for such data exchanges, what existing protocols need to be adapted to meet those needs and the appropriate schema and queries are needed to facilitate such exchanges. The IETF has in the past done significant work on data exchanges among various administrative entities. In particular the PROVREG working group developed various schema and query mechanisms to facilitate the exchange of data among domain name registries and registrars. The ENUM Working group has adapted PROVREG working group protocols to develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS tree. However, there has been little adoption of RFC 4114, and many of the participants of the SPEERMINT working group require both data models and protocol features not found in RFC 4114. The proposed PEPPERMINT working group will build upon the knowledge gained from those efforts, and the intent of this proposed working group is to find a provisioning solution for peering as defined by SPEERMINT. The final work product(s) from this working group will be based upon XML. =20 Additionally, bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, or HTTP/SOAP. Proposed Deliverables Requirements for SPEERMINT data exchange. Provisioning of SPEERMINT data registries. Provisioning of SPEERMINT/ENUM data caches. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 11 10:48:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfzHZ-0005tq-3R; Thu, 11 Oct 2007 10:45:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfzHY-0004Zh-1l; Thu, 11 Oct 2007 10:45:00 -0400 Received: from mail28.messagelabs.com ([216.82.249.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IfzHN-0004uo-Os; Thu, 11 Oct 2007 10:44:56 -0400 X-VirusChecked: Checked X-Env-Sender: daryl@level3.net X-Msg-Ref: server-17.tower-28.messagelabs.com!1192113867!52720733!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [209.245.18.107] Received: (qmail 10653 invoked from network); 11 Oct 2007 14:44:27 -0000 Received: from unknown.level3.net (HELO f10cc8-10.level3.com) (209.245.18.107) by server-17.tower-28.messagelabs.com with SMTP; 11 Oct 2007 14:44:27 -0000 Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57]) by f10cc8-10.level3.com (Postfix) with ESMTP id 6670D2DC9; Thu, 11 Oct 2007 14:44:27 +0000 (GMT) From: Daryl Malas To: Richard Shockey In-Reply-To: <047301c806ef$8294f650$87bee2f0$@us> References: <047301c806ef$8294f650$87bee2f0$@us> Content-Type: text/plain Date: Thu, 11 Oct 2007 08:51:50 -0600 Message-Id: <1192114310.1297.322.camel@montag.eng.level3.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 (2.6.0-1) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.0 (----) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Cc: enum@ietf.org, speermint@ietf.org Subject: [Enum] Re: [Speermint] I'd like to guage interest in restarting a BOF on the subject of Peppermint. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org IMO, I believe this is warranted, but I do not think we are ready for it yet. I suspect this will be of a lot more interest in this BOF in about 1 year, after several of the SPEERMINT milestones are completed. Daryl On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > This time last year I tried to start up a BOF on some of the ongoing > provisioning issues between various forms of ENUM registries and network > entities. I've had a few folks ask what ever happened to that. I still think > there is a strong need to do this and the work could have relevance if the > scope were expanded not to be just service provider to registry but also PBX > to registries as well. > > I'd like to test the water to see if there is any interest in doing this in > Vancouver. > > > The original BOF proposal was this: > > Comments as usual are welcome > > > Peppermint BOF > > Provisioning Extensions in Peering Registries for Multimedia > Intererconnection. > > Mailing Lists: > > BOF chairs: > > Richard Shockey [rich.shockey@neustar.biz] > > Temporary Area Directorate: Real Time Applications (RAI) > > Ultimate Area Directorate: TBD > > > BOF Purpose. > > The ENUM and SPEERMINT working groups are working on various aspects of > Multi Media Interconnection. ENUM is specifically chartered to develop > protocols that involve the translation of E.164 numbers to URI's. > SPEERMINT has been chartered to develop best current practices among > real-time application service providers and how such services interconnect > across domain boundaries. > > It is clear from discussions in both working groups that Multi-Media > Interconnection will require various forms of data to be exchanged among > administrative domains outside the normal scope of establishing a SIP > session. > > Such data exchanges might be provisioning of various forms of Registries > containing mappings of phone numbers to URI, policies surrounding the > admission to points of network interconnection and the distribution of > Registry data to various types of databases. > > The purpose of the BOF is to determine the need and scope for such data > exchanges, what existing protocols need to be adapted to meet those needs > and the appropriate schema and queries are needed to facilitate such > exchanges. > > The IETF has in the past done significant work on data exchanges among > various administrative entities. In particular the PROVREG working group > developed various schema and query mechanisms to facilitate the exchange of > data among domain name registries and registrars. > > The ENUM Working group has adapted PROVREG working group protocols to > develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS > tree. However, there has been little adoption of RFC 4114, and many of the > participants of the SPEERMINT working group require both data models and > protocol features not found in RFC 4114. > > The proposed PEPPERMINT working group will build upon the knowledge gained > from those efforts, and the intent of this proposed working group is to find > a provisioning solution for peering as defined by SPEERMINT. The final work > product(s) from this working group will be based upon XML. > > Additionally, > bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, or > HTTP/SOAP. > > Proposed Deliverables > > Requirements for SPEERMINT data exchange. > > Provisioning of SPEERMINT data registries. > > Provisioning of SPEERMINT/ENUM data caches. > > Richard Shockey > Director, Member of the Technical Staff > NeuStar > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org > PSTN Office +1 571.434.5651 > PSTN Mobile: +1 703.593.2683 > > > > > > > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 12 08:51:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IgJu4-0001BP-Tk; Fri, 12 Oct 2007 08:46:08 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IgJu4-0001BD-1D; Fri, 12 Oct 2007 08:46:08 -0400 Received: from pacdcimo02.cable.comcast.com ([24.40.8.146]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IgJu3-0002tq-BI; Fri, 12 Oct 2007 08:46:07 -0400 Received: from ([10.52.116.30]) by pacdcimo02.cable.comcast.com with ESMTP id KP-GZL85.12553149; Fri, 12 Oct 2007 08:45:44 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Oct 2007 08:45:44 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest in restarting aBOF on the subject of Peppermint. Date: Fri, 12 Oct 2007 08:45:57 -0400 Message-ID: <45AEC6EF95942140888406588E1A660202D8FBDE@PACDCEXCMB04.cable.comcast.com> In-Reply-To: <1192114310.1297.322.camel@montag.eng.level3.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Re: [Speermint] I'd like to guage interest in restarting aBOF on the subject of Peppermint. Thread-Index: AcgMFicLMUUpmr9ASp2sz3u5Ax1VTgAt6b1A References: <047301c806ef$8294f650$87bee2f0$@us> <1192114310.1297.322.camel@montag.eng.level3.com> From: "Creighton, Tom" To: "Daryl Malas" , "Richard Shockey" X-OriginalArrivalTime: 12 Oct 2007 12:45:44.0614 (UTC) FILETIME=[CE20BC60:01C80CCD] X-Spam-Score: 0.0 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I disagree. This work needs to begin immediately so that in a year from now we might actually have working code. Tom > -----Original Message----- > From: Daryl Malas [mailto:daryl@level3.net] > Sent: Thursday, October 11, 2007 10:52 > To: Richard Shockey > Cc: enum@ietf.org; speermint@ietf.org > Subject: [Enum] Re: [Speermint] I'd like to guage interest in restarting > aBOF on the subject of Peppermint. >=20 > IMO, I believe this is warranted, but I do not think we are ready for it > yet. I suspect this will be of a lot more interest in this BOF in about > 1 year, after several of the SPEERMINT milestones are completed. >=20 > Daryl >=20 > On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > > This time last year I tried to start up a BOF on some of the ongoing > > provisioning issues between various forms of ENUM registries and network > > entities. I've had a few folks ask what ever happened to that. I still > think > > there is a strong need to do this and the work could have relevance if > the > > scope were expanded not to be just service provider to registry but also > PBX > > to registries as well. > > > > I'd like to test the water to see if there is any interest in doing this > in > > Vancouver. > > > > > > The original BOF proposal was this: > > > > Comments as usual are welcome > > > > > > Peppermint BOF > > > > Provisioning Extensions in Peering Registries for Multimedia > > Intererconnection. > > > > Mailing Lists: > > > > BOF chairs: > > > > Richard Shockey [rich.shockey@neustar.biz] > > > > Temporary Area Directorate: Real Time Applications (RAI) > > > > Ultimate Area Directorate: TBD > > > > > > BOF Purpose. > > > > The ENUM and SPEERMINT working groups are working on various aspects of > > Multi Media Interconnection. ENUM is specifically chartered to develop > > protocols that involve the translation of E.164 numbers to URI's. > > SPEERMINT has been chartered to develop best current practices among > > real-time application service providers and how such services > interconnect > > across domain boundaries. > > > > It is clear from discussions in both working groups that Multi-Media > > Interconnection will require various forms of data to be exchanged among > > administrative domains outside the normal scope of establishing a SIP > > session. > > > > Such data exchanges might be provisioning of various forms of Registries > > containing mappings of phone numbers to URI, policies surrounding the > > admission to points of network interconnection and the distribution of > > Registry data to various types of databases. > > > > The purpose of the BOF is to determine the need and scope for such data > > exchanges, what existing protocols need to be adapted to meet those > needs > > and the appropriate schema and queries are needed to facilitate such > > exchanges. > > > > The IETF has in the past done significant work on data exchanges among > > various administrative entities. In particular the PROVREG working group > > developed various schema and query mechanisms to facilitate the exchange > of > > data among domain name registries and registrars. > > > > The ENUM Working group has adapted PROVREG working group protocols to > > develop RFC 4114, which facilitates the provisioning of ENUM data in the > DNS > > tree. However, there has been little adoption of RFC 4114, and many of > the > > participants of the SPEERMINT working group require both data models and > > protocol features not found in RFC 4114. > > > > The proposed PEPPERMINT working group will build upon the knowledge > gained > > from those efforts, and the intent of this proposed working group is to > find > > a provisioning solution for peering as defined by SPEERMINT. The final > work > > product(s) from this working group will be based upon XML. > > > > Additionally, > > bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, or > > HTTP/SOAP. > > > > Proposed Deliverables > > > > Requirements for SPEERMINT data exchange. > > > > Provisioning of SPEERMINT data registries. > > > > Provisioning of SPEERMINT/ENUM data caches. > > > > Richard Shockey > > Director, Member of the Technical Staff > > NeuStar > > 46000 Center Oak Plaza - Sterling, VA 20166 > > sip:rshockey(at)iptel.org > > PSTN Office +1 571.434.5651 > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint >=20 >=20 > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 12 13:23:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IgO9S-0003ka-Cj; Fri, 12 Oct 2007 13:18:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IgO9Q-0003kA-MZ; Fri, 12 Oct 2007 13:18:16 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IgO9K-0005x4-DY; Fri, 12 Oct 2007 13:18:16 -0400 Received: from rshockeyPC (mit.xs4all.nl [213.84.95.205]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9CHFmdm005100 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Oct 2007 10:17:38 -0700 From: "Richard Shockey" To: "'Daryl Malas'" References: <047301c806ef$8294f650$87bee2f0$@us> <1192114310.1297.322.camel@montag.eng.level3.com> In-Reply-To: <1192114310.1297.322.camel@montag.eng.level3.com> Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest in restarting a BOF on the subject of Peppermint. Date: Fri, 12 Oct 2007 13:15:46 -0400 Message-ID: <1aaf01c80cf3$c97a7090$5c6f51b0$@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: AcgMFUfjs9YMQo2nRHOSAEn0KhT6DgAoXWpw Content-language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Don't you think the work can proceed in parallel? Provisioning is the Achillies heel of interconnection .. > -----Original Message----- > From: Daryl Malas [mailto:daryl@level3.net] > Sent: Thursday, October 11, 2007 10:52 AM > To: Richard Shockey > Cc: enum@ietf.org; speermint@ietf.org > Subject: [Enum] Re: [Speermint] I'd like to guage interest in > restarting a BOF on the subject of Peppermint. > > IMO, I believe this is warranted, but I do not think we are ready for > it > yet. I suspect this will be of a lot more interest in this BOF in > about > 1 year, after several of the SPEERMINT milestones are completed. > > Daryl > > On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > > This time last year I tried to start up a BOF on some of the ongoing > > provisioning issues between various forms of ENUM registries and > network > > entities. I've had a few folks ask what ever happened to that. I > still think > > there is a strong need to do this and the work could have relevance > if the > > scope were expanded not to be just service provider to registry but > also PBX > > to registries as well. > > > > I'd like to test the water to see if there is any interest in doing > this in > > Vancouver. > > > > > > The original BOF proposal was this: > > > > Comments as usual are welcome > > > > > > Peppermint BOF > > > > Provisioning Extensions in Peering Registries for Multimedia > > Intererconnection. > > > > Mailing Lists: > > > > BOF chairs: > > > > Richard Shockey [rich.shockey@neustar.biz] > > > > Temporary Area Directorate: Real Time Applications (RAI) > > > > Ultimate Area Directorate: TBD > > > > > > BOF Purpose. > > > > The ENUM and SPEERMINT working groups are working on various aspects > of > > Multi Media Interconnection. ENUM is specifically chartered to > develop > > protocols that involve the translation of E.164 numbers to URI's. > > SPEERMINT has been chartered to develop best current practices among > > real-time application service providers and how such services > interconnect > > across domain boundaries. > > > > It is clear from discussions in both working groups that Multi-Media > > Interconnection will require various forms of data to be exchanged > among > > administrative domains outside the normal scope of establishing a > SIP > > session. > > > > Such data exchanges might be provisioning of various forms of > Registries > > containing mappings of phone numbers to URI, policies surrounding > the > > admission to points of network interconnection and the distribution > of > > Registry data to various types of databases. > > > > The purpose of the BOF is to determine the need and scope for such > data > > exchanges, what existing protocols need to be adapted to meet those > needs > > and the appropriate schema and queries are needed to facilitate such > > exchanges. > > > > The IETF has in the past done significant work on data exchanges > among > > various administrative entities. In particular the PROVREG working > group > > developed various schema and query mechanisms to facilitate the > exchange of > > data among domain name registries and registrars. > > > > The ENUM Working group has adapted PROVREG working group protocols > to > > develop RFC 4114, which facilitates the provisioning of ENUM data in > the DNS > > tree. However, there has been little adoption of RFC 4114, and many > of the > > participants of the SPEERMINT working group require both data models > and > > protocol features not found in RFC 4114. > > > > The proposed PEPPERMINT working group will build upon the knowledge > gained > > from those efforts, and the intent of this proposed working group is > to find > > a provisioning solution for peering as defined by SPEERMINT. The > final work > > product(s) from this working group will be based upon XML. > > > > Additionally, > > bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, > or > > HTTP/SOAP. > > > > Proposed Deliverables > > > > Requirements for SPEERMINT data exchange. > > > > Provisioning of SPEERMINT data registries. > > > > Provisioning of SPEERMINT/ENUM data caches. > > > > Richard Shockey > > Director, Member of the Technical Staff > > NeuStar > > 46000 Center Oak Plaza - Sterling, VA 20166 > > sip:rshockey(at)iptel.org > > PSTN Office +1 571.434.5651 > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 15 15:38:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhVi4-0007fi-0w; Mon, 15 Oct 2007 15:34:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhVi2-0007eM-0M for enum@ietf.org; Mon, 15 Oct 2007 15:34:38 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IhVhv-0000gJ-Nn for enum@ietf.org; Mon, 15 Oct 2007 15:34:37 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9FJXw1H025095 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 15 Oct 2007 12:33:59 -0700 From: "Richard Shockey" To: Date: Mon, 15 Oct 2007 15:33:53 -0400 Message-ID: <018101c80f62$530a1340$f91e39c0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgM5+PdzuSbWufgRQW0ZYb+2MDmdQCemryg Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Subject: [Enum] FW: REVISED Internet-Draft Submission Cutoff Dates for the 70th IETF Meeting in Vancouver, BC, Canada X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org -----Original Message----- From: IETF Secretariat [mailto:ietf-secretariat@ietf.org]=20 Sent: Friday, October 12, 2007 11:45 AM To: IETF Announcement list Subject: REVISED Internet-Draft Submission Cutoff Dates for the 70th = IETF Meeting in Vancouver, BC, Canada=20 There are two (2) Internet-Draft cutoff dates for the 70th IETF=20 Meeting in Vancouver, BC, Canada: November 12th: Cutoff Date for Initial (i.e., version -00) = Internet-Draft Submissions=20 All initial Internet-Drafts (version -00) must be submitted by Monday, November 12th at 9:00 AM ET (14:00 UTC/GMT). The only exception is for version -00 WG drafts that replace existing non-WG drafts. Such drafts may be submitted until the cutoff date for version -01 and higher = drafts. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they = can be processed or announced. The Secretariat would appreciate receiving = WG Chair approval by Monday, November 5th at 9:00 AM ET (14:00 UTC/GMT). November 19th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions=20 All revised Internet-Drafts (version -01 and higher) must be submitted = by Monday, November 19th at 9:00 AM ET (14:00 UTC/GMT). Initial and revised Internet-Drafts submitted after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, December 3rd at 9:00 AM ET (14:00 UTC/GMT), when Internet-Draft posting resumes. Please do not wait until the last minute to submit. The Secretariat encourages you to submit your Internet-Drafts via the Internet-Draft Submission Tool (IDST) https://datatracker.ietf.org/idst/upload.cgi. If you are unable to do = so, then you may still submit your Internet-Drafts manually by sending them = to internet-drafts@ietf.org. If you are submitting a version -00 WG draft that replaces non-WG draft, then you must submit it manually as the current IDST cannot handle replacements. Please be sure to state that = one draft replaces another in the cover note that accompanies your=20 submission. Also, please note that the IDST will not accept drafts submitted after their respective cutoff dates. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 70th IETF Meeting can be found at http://www3.ietf.org/meetings/70-cutoff_dates.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 16 17:45:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ihu9N-0000L5-Gy; Tue, 16 Oct 2007 17:40:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ihu9M-0000Kw-91; Tue, 16 Oct 2007 17:40:28 -0400 Received: from mail34.messagelabs.com ([216.82.241.35]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ihu9F-0006sh-9I; Tue, 16 Oct 2007 17:40:28 -0400 X-VirusChecked: Checked X-Env-Sender: daryl@level3.net X-Msg-Ref: server-7.tower-34.messagelabs.com!1192570801!2951796!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [209.245.18.106] Received: (qmail 774 invoked from network); 16 Oct 2007 21:40:01 -0000 Received: from unknown.level3.net (HELO f10bb8-10) (209.245.18.106) by server-7.tower-34.messagelabs.com with SMTP; 16 Oct 2007 21:40:01 -0000 Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57]) by f10bb8-10 (Postfix) with ESMTP id 6E3184C9A; Tue, 16 Oct 2007 21:40:01 +0000 (GMT) Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest in restarting a BOF on the subject of Peppermint. From: Daryl Malas To: Richard Shockey In-Reply-To: <1aaf01c80cf3$c97a7090$5c6f51b0$@us> References: <047301c806ef$8294f650$87bee2f0$@us> <1192114310.1297.322.camel@montag.eng.level3.com> <1aaf01c80cf3$c97a7090$5c6f51b0$@us> Content-Type: text/plain Date: Tue, 16 Oct 2007 15:47:44 -0600 Message-Id: <1192571265.1297.336.camel@montag.eng.level3.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 (2.6.0-1) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.0 (----) X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org >From my perspective, we are just, finally, nearing completion of the terminology draft. Since, we have not completed drafts, such as "Requirements" and "Architecture", I would be concerned the PEPPERMINT group/BOF understands exactly what the requirements of the interconnection would look like in order to provision it appropriately. IMO, continued discussion around this topic is warranted, but I think the PEPPERMINT BOF should wait until near or after the following SPEERMINT milestone is met: Feb 2008 Submit SPEERMINT minimum requirements for SIP-based VoIP interconnection. (BCP) Based on this, I would recommend a BOF in the spring (likely Summer) and perhaps the need for a WG at the fall 2008 IETF conference. This way the PEPPERMINT group will fully understand the requirements, and will be able to appropriately define a charter. --Daryl On Fri, 2007-10-12 at 13:15 -0400, Richard Shockey wrote: > Don't you think the work can proceed in parallel? > > Provisioning is the Achillies heel of interconnection .. > > > -----Original Message----- > > From: Daryl Malas [mailto:daryl@level3.net] > > Sent: Thursday, October 11, 2007 10:52 AM > > To: Richard Shockey > > Cc: enum@ietf.org; speermint@ietf.org > > Subject: [Enum] Re: [Speermint] I'd like to guage interest in > > restarting a BOF on the subject of Peppermint. > > > > IMO, I believe this is warranted, but I do not think we are ready for > > it > > yet. I suspect this will be of a lot more interest in this BOF in > > about > > 1 year, after several of the SPEERMINT milestones are completed. > > > > Daryl > > > > On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > > > This time last year I tried to start up a BOF on some of the ongoing > > > provisioning issues between various forms of ENUM registries and > > network > > > entities. I've had a few folks ask what ever happened to that. I > > still think > > > there is a strong need to do this and the work could have relevance > > if the > > > scope were expanded not to be just service provider to registry but > > also PBX > > > to registries as well. > > > > > > I'd like to test the water to see if there is any interest in doing > > this in > > > Vancouver. > > > > > > > > > The original BOF proposal was this: > > > > > > Comments as usual are welcome > > > > > > > > > Peppermint BOF > > > > > > Provisioning Extensions in Peering Registries for Multimedia > > > Intererconnection. > > > > > > Mailing Lists: > > > > > > BOF chairs: > > > > > > Richard Shockey [rich.shockey@neustar.biz] > > > > > > Temporary Area Directorate: Real Time Applications (RAI) > > > > > > Ultimate Area Directorate: TBD > > > > > > > > > BOF Purpose. > > > > > > The ENUM and SPEERMINT working groups are working on various aspects > > of > > > Multi Media Interconnection. ENUM is specifically chartered to > > develop > > > protocols that involve the translation of E.164 numbers to URI's. > > > SPEERMINT has been chartered to develop best current practices among > > > real-time application service providers and how such services > > interconnect > > > across domain boundaries. > > > > > > It is clear from discussions in both working groups that Multi-Media > > > Interconnection will require various forms of data to be exchanged > > among > > > administrative domains outside the normal scope of establishing a > > SIP > > > session. > > > > > > Such data exchanges might be provisioning of various forms of > > Registries > > > containing mappings of phone numbers to URI, policies surrounding > > the > > > admission to points of network interconnection and the distribution > > of > > > Registry data to various types of databases. > > > > > > The purpose of the BOF is to determine the need and scope for such > > data > > > exchanges, what existing protocols need to be adapted to meet those > > needs > > > and the appropriate schema and queries are needed to facilitate such > > > exchanges. > > > > > > The IETF has in the past done significant work on data exchanges > > among > > > various administrative entities. In particular the PROVREG working > > group > > > developed various schema and query mechanisms to facilitate the > > exchange of > > > data among domain name registries and registrars. > > > > > > The ENUM Working group has adapted PROVREG working group protocols > > to > > > develop RFC 4114, which facilitates the provisioning of ENUM data in > > the DNS > > > tree. However, there has been little adoption of RFC 4114, and many > > of the > > > participants of the SPEERMINT working group require both data models > > and > > > protocol features not found in RFC 4114. > > > > > > The proposed PEPPERMINT working group will build upon the knowledge > > gained > > > from those efforts, and the intent of this proposed working group is > > to find > > > a provisioning solution for peering as defined by SPEERMINT. The > > final work > > > product(s) from this working group will be based upon XML. > > > > > > Additionally, > > > bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, > > or > > > HTTP/SOAP. > > > > > > Proposed Deliverables > > > > > > Requirements for SPEERMINT data exchange. > > > > > > Provisioning of SPEERMINT data registries. > > > > > > Provisioning of SPEERMINT/ENUM data caches. > > > > > > Richard Shockey > > > Director, Member of the Technical Staff > > > NeuStar > > > 46000 Center Oak Plaza - Sterling, VA 20166 > > > sip:rshockey(at)iptel.org > > > PSTN Office +1 571.434.5651 > > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Speermint mailing list > > > Speermint@ietf.org > > > https://www1.ietf.org/mailman/listinfo/speermint > > > > > > _______________________________________________ > > enum mailing list > > enum@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 16 21:57:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ihy6R-00047E-Nn; Tue, 16 Oct 2007 21:53:43 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ihy6P-00046k-EU; Tue, 16 Oct 2007 21:53:41 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ihy6O-0000KU-CU; Tue, 16 Oct 2007 21:53:41 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9H1rEPO003838 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Oct 2007 18:53:20 -0700 From: "Richard Shockey" To: "'Daryl Malas'" References: <047301c806ef$8294f650$87bee2f0$@us> <1192114310.1297.322.camel@montag.eng.level3.com> <1aaf01c80cf3$c97a7090$5c6f51b0$@us> <1192571265.1297.336.camel@montag.eng.level3.com> In-Reply-To: <1192571265.1297.336.camel@montag.eng.level3.com> Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest in restarting a BOF on the subject of Peppermint. Date: Tue, 16 Oct 2007 21:53:01 -0400 Message-ID: <013001c81060$770b4030$6521c090$@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: AcgQPWAEfB7rFjFDQ7eW54n2AgyFhAAIc5kA Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027 Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Clearly I don't agree. I think there are time to market issues that require a parallel effort. The deployment of ENUM in its various forms specifically private instantiations as well as federations surrounding cable and mobile networks indicate that if action is not taken anarchy will occur. Provisioning as I have stated countless times is the Achilles' Heel of the entire federation process. There are multiple issues in provisioning, not just the location of various points of interconnection but internal provisioning of highly cached ENUM servers, what I refer to as IP-SCP's that are rapidly becoming core network elements of NGN. For instance discovery of points of interconnection may require separate internal trunking decisions on how the traffic is to be routed based on internal policy on how Layer1-3 connections are made. It is my intention to have a new ENUM ID ready shortly that will outline how to create a new ENUMservice based on RFC 4904. > -----Original Message----- > From: Daryl Malas [mailto:daryl@level3.net] > Sent: Tuesday, October 16, 2007 5:48 PM > To: Richard Shockey > Cc: enum@ietf.org; speermint@ietf.org > Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest in > restarting a BOF on the subject of Peppermint. > > >From my perspective, we are just, finally, nearing completion of the > terminology draft. Since, we have not completed drafts, such as > "Requirements" and "Architecture", I would be concerned the PEPPERMINT > group/BOF understands exactly what the requirements of the > interconnection would look like in order to provision it > appropriately. > > IMO, continued discussion around this topic is warranted, but I think > the PEPPERMINT BOF should wait until near or after the following > SPEERMINT milestone is met: > > Feb 2008 Submit SPEERMINT minimum requirements for SIP-based VoIP > interconnection. (BCP) > > Based on this, I would recommend a BOF in the spring (likely Summer) > and > perhaps the need for a WG at the fall 2008 IETF conference. > > This way the PEPPERMINT group will fully understand the requirements, > and will be able to appropriately define a charter. > > --Daryl > > On Fri, 2007-10-12 at 13:15 -0400, Richard Shockey wrote: > > Don't you think the work can proceed in parallel? > > > > Provisioning is the Achillies heel of interconnection .. > > > > > -----Original Message----- > > > From: Daryl Malas [mailto:daryl@level3.net] > > > Sent: Thursday, October 11, 2007 10:52 AM > > > To: Richard Shockey > > > Cc: enum@ietf.org; speermint@ietf.org > > > Subject: [Enum] Re: [Speermint] I'd like to guage interest in > > > restarting a BOF on the subject of Peppermint. > > > > > > IMO, I believe this is warranted, but I do not think we are ready > for > > > it > > > yet. I suspect this will be of a lot more interest in this BOF > in > > > about > > > 1 year, after several of the SPEERMINT milestones are completed. > > > > > > Daryl > > > > > > On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > > > > This time last year I tried to start up a BOF on some of the > ongoing > > > > provisioning issues between various forms of ENUM registries > and > > > network > > > > entities. I've had a few folks ask what ever happened to that. > I > > > still think > > > > there is a strong need to do this and the work could have > relevance > > > if the > > > > scope were expanded not to be just service provider to registry > but > > > also PBX > > > > to registries as well. > > > > > > > > I'd like to test the water to see if there is any interest in > doing > > > this in > > > > Vancouver. > > > > > > > > > > > > The original BOF proposal was this: > > > > > > > > Comments as usual are welcome > > > > > > > > > > > > Peppermint BOF > > > > > > > > Provisioning Extensions in Peering Registries for Multimedia > > > > Intererconnection. > > > > > > > > Mailing Lists: > > > > > > > > BOF chairs: > > > > > > > > Richard Shockey [rich.shockey@neustar.biz] > > > > > > > > Temporary Area Directorate: Real Time Applications (RAI) > > > > > > > > Ultimate Area Directorate: TBD > > > > > > > > > > > > BOF Purpose. > > > > > > > > The ENUM and SPEERMINT working groups are working on various > aspects > > > of > > > > Multi Media Interconnection. ENUM is specifically chartered to > > > develop > > > > protocols that involve the translation of E.164 numbers to > URI's. > > > > SPEERMINT has been chartered to develop best current practices > among > > > > real-time application service providers and how such services > > > interconnect > > > > across domain boundaries. > > > > > > > > It is clear from discussions in both working groups that Multi- > Media > > > > Interconnection will require various forms of data to be > exchanged > > > among > > > > administrative domains outside the normal scope of establishing > a > > > SIP > > > > session. > > > > > > > > Such data exchanges might be provisioning of various forms of > > > Registries > > > > containing mappings of phone numbers to URI, policies > surrounding > > > the > > > > admission to points of network interconnection and the > distribution > > > of > > > > Registry data to various types of databases. > > > > > > > > The purpose of the BOF is to determine the need and scope for > such > > > data > > > > exchanges, what existing protocols need to be adapted to meet > those > > > needs > > > > and the appropriate schema and queries are needed to facilitate > such > > > > exchanges. > > > > > > > > The IETF has in the past done significant work on data > exchanges > > > among > > > > various administrative entities. In particular the PROVREG > working > > > group > > > > developed various schema and query mechanisms to facilitate the > > > exchange of > > > > data among domain name registries and registrars. > > > > > > > > The ENUM Working group has adapted PROVREG working group > protocols > > > to > > > > develop RFC 4114, which facilitates the provisioning of ENUM > data in > > > the DNS > > > > tree. However, there has been little adoption of RFC 4114, and > many > > > of the > > > > participants of the SPEERMINT working group require both data > models > > > and > > > > protocol features not found in RFC 4114. > > > > > > > > The proposed PEPPERMINT working group will build upon the > knowledge > > > gained > > > > from those efforts, and the intent of this proposed working > group is > > > to find > > > > a provisioning solution for peering as defined by SPEERMINT. > The > > > final work > > > > product(s) from this working group will be based upon XML. > > > > > > > > Additionally, > > > > bias will be given to re-using either EPP, HTTP/REST, HTTP/XML- > RPC, > > > or > > > > HTTP/SOAP. > > > > > > > > Proposed Deliverables > > > > > > > > Requirements for SPEERMINT data exchange. > > > > > > > > Provisioning of SPEERMINT data registries. > > > > > > > > Provisioning of SPEERMINT/ENUM data caches. > > > > > > > > Richard Shockey > > > > Director, Member of the Technical Staff > > > > NeuStar > > > > 46000 Center Oak Plaza - Sterling, VA 20166 > > > > sip:rshockey(at)iptel.org > > > > PSTN Office +1 571.434.5651 > > > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Speermint mailing list > > > > Speermint@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/speermint > > > > > > > > > _______________________________________________ > > > enum mailing list > > > enum@ietf.org > > > https://www1.ietf.org/mailman/listinfo/enum > > > > > > _______________________________________________ > > enum mailing list > > enum@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 17 15:13:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiEIb-0001Qn-K1; Wed, 17 Oct 2007 15:11:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiEIa-0001PX-Qg; Wed, 17 Oct 2007 15:11:20 -0400 Received: from paoakoavas09.cable.comcast.com ([208.17.35.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IiEIZ-00083W-LZ; Wed, 17 Oct 2007 15:11:20 -0400 Received: from ([24.40.15.118]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.47847303; Wed, 17 Oct 2007 15:10:59 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Oct 2007 15:10:59 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest inrestarting a BOF on the subject of Peppermint. Date: Wed, 17 Oct 2007 15:11:02 -0400 Message-ID: <45AEC6EF95942140888406588E1A660202ECC379@PACDCEXCMB04.cable.comcast.com> In-Reply-To: <1192571265.1297.336.camel@montag.eng.level3.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Re: [Speermint] I'd like to guage interest inrestarting a BOF on the subject of Peppermint. Thread-Index: AcgQPjS4npWhayLGTPSlxlVzIGMceQAqtQ6A References: <047301c806ef$8294f650$87bee2f0$@us><1192114310.1297.322.camel@montag.eng.level3.com><1aaf01c80cf3$c97a7090$5c6f51b0$@us> <1192571265.1297.336.camel@montag.eng.level3.com> From: "Creighton, Tom" To: "Daryl Malas" , "Richard Shockey" X-OriginalArrivalTime: 17 Oct 2007 19:10:59.0700 (UTC) FILETIME=[73DBB340:01C810F1] X-Spam-Score: 0.0 (/) X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027 Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Daryl: I understand your concern that we might be placing the cart before the horse; but have you considered that the cart might actually be a horse? SPEERMINT, as we all know, was designed to take a collection of protocols and provide a set of recommendations as to how they should be used. PEPPERMINT, however, would need to define a set of protocols that could be used to exchange provisioning data in support of efforts such as SPEERMINT. These standards would need to support a myriad of use cases within the IETF which could then be the basis of a SPEERMINT BCP. There is a DIRE need for standardization in this area today because the current standard of exchanging provisioning data (such as call routing tables) using Excel is not acceptable. Tom > -----Original Message----- > From: Daryl Malas [mailto:daryl@level3.net] > Sent: Tuesday, October 16, 2007 17:48 > To: Richard Shockey > Cc: enum@ietf.org; speermint@ietf.org > Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest > inrestarting a BOF on the subject of Peppermint. >=20 > >From my perspective, we are just, finally, nearing completion of the > terminology draft. Since, we have not completed drafts, such as > "Requirements" and "Architecture", I would be concerned the PEPPERMINT > group/BOF understands exactly what the requirements of the > interconnection would look like in order to provision it appropriately. >=20 > IMO, continued discussion around this topic is warranted, but I think > the PEPPERMINT BOF should wait until near or after the following > SPEERMINT milestone is met: >=20 > Feb 2008 Submit SPEERMINT minimum requirements for SIP-based VoIP > interconnection. (BCP) >=20 > Based on this, I would recommend a BOF in the spring (likely Summer) and > perhaps the need for a WG at the fall 2008 IETF conference. >=20 > This way the PEPPERMINT group will fully understand the requirements, > and will be able to appropriately define a charter. >=20 > --Daryl >=20 > On Fri, 2007-10-12 at 13:15 -0400, Richard Shockey wrote: > > Don't you think the work can proceed in parallel? > > > > Provisioning is the Achillies heel of interconnection .. > > > > > -----Original Message----- > > > From: Daryl Malas [mailto:daryl@level3.net] > > > Sent: Thursday, October 11, 2007 10:52 AM > > > To: Richard Shockey > > > Cc: enum@ietf.org; speermint@ietf.org > > > Subject: [Enum] Re: [Speermint] I'd like to guage interest in > > > restarting a BOF on the subject of Peppermint. > > > > > > IMO, I believe this is warranted, but I do not think we are ready for > > > it > > > yet. I suspect this will be of a lot more interest in this BOF in > > > about > > > 1 year, after several of the SPEERMINT milestones are completed. > > > > > > Daryl > > > > > > On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > > > > This time last year I tried to start up a BOF on some of the > ongoing > > > > provisioning issues between various forms of ENUM registries and > > > network > > > > entities. I've had a few folks ask what ever happened to that. I > > > still think > > > > there is a strong need to do this and the work could have relevance > > > if the > > > > scope were expanded not to be just service provider to registry but > > > also PBX > > > > to registries as well. > > > > > > > > I'd like to test the water to see if there is any interest in doing > > > this in > > > > Vancouver. > > > > > > > > > > > > The original BOF proposal was this: > > > > > > > > Comments as usual are welcome > > > > > > > > > > > > Peppermint BOF > > > > > > > > Provisioning Extensions in Peering Registries for Multimedia > > > > Intererconnection. > > > > > > > > Mailing Lists: > > > > > > > > BOF chairs: > > > > > > > > Richard Shockey [rich.shockey@neustar.biz] > > > > > > > > Temporary Area Directorate: Real Time Applications (RAI) > > > > > > > > Ultimate Area Directorate: TBD > > > > > > > > > > > > BOF Purpose. > > > > > > > > The ENUM and SPEERMINT working groups are working on various > aspects > > > of > > > > Multi Media Interconnection. ENUM is specifically chartered to > > > develop > > > > protocols that involve the translation of E.164 numbers to URI's. > > > > SPEERMINT has been chartered to develop best current practices > among > > > > real-time application service providers and how such services > > > interconnect > > > > across domain boundaries. > > > > > > > > It is clear from discussions in both working groups that Multi- > Media > > > > Interconnection will require various forms of data to be exchanged > > > among > > > > administrative domains outside the normal scope of establishing a > > > SIP > > > > session. > > > > > > > > Such data exchanges might be provisioning of various forms of > > > Registries > > > > containing mappings of phone numbers to URI, policies surrounding > > > the > > > > admission to points of network interconnection and the distribution > > > of > > > > Registry data to various types of databases. > > > > > > > > The purpose of the BOF is to determine the need and scope for such > > > data > > > > exchanges, what existing protocols need to be adapted to meet those > > > needs > > > > and the appropriate schema and queries are needed to facilitate > such > > > > exchanges. > > > > > > > > The IETF has in the past done significant work on data exchanges > > > among > > > > various administrative entities. In particular the PROVREG working > > > group > > > > developed various schema and query mechanisms to facilitate the > > > exchange of > > > > data among domain name registries and registrars. > > > > > > > > The ENUM Working group has adapted PROVREG working group protocols > > > to > > > > develop RFC 4114, which facilitates the provisioning of ENUM data > in > > > the DNS > > > > tree. However, there has been little adoption of RFC 4114, and > many > > > of the > > > > participants of the SPEERMINT working group require both data > models > > > and > > > > protocol features not found in RFC 4114. > > > > > > > > The proposed PEPPERMINT working group will build upon the knowledge > > > gained > > > > from those efforts, and the intent of this proposed working group > is > > > to find > > > > a provisioning solution for peering as defined by SPEERMINT. The > > > final work > > > > product(s) from this working group will be based upon XML. > > > > > > > > Additionally, > > > > bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, > > > or > > > > HTTP/SOAP. > > > > > > > > Proposed Deliverables > > > > > > > > Requirements for SPEERMINT data exchange. > > > > > > > > Provisioning of SPEERMINT data registries. > > > > > > > > Provisioning of SPEERMINT/ENUM data caches. > > > > > > > > Richard Shockey > > > > Director, Member of the Technical Staff > > > > NeuStar > > > > 46000 Center Oak Plaza - Sterling, VA 20166 > > > > sip:rshockey(at)iptel.org > > > > PSTN Office +1 571.434.5651 > > > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Speermint mailing list > > > > Speermint@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/speermint > > > > > > > > > _______________________________________________ > > > enum mailing list > > > enum@ietf.org > > > https://www1.ietf.org/mailman/listinfo/enum > > > > > > _______________________________________________ > > enum mailing list > > enum@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum >=20 >=20 > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 17 23:12:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiLhw-0006Yn-2L; Wed, 17 Oct 2007 23:06:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiLht-0006Xx-CM; Wed, 17 Oct 2007 23:05:57 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IiLhs-00065U-3X; Wed, 17 Oct 2007 23:05:57 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9I35WE1009611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 17 Oct 2007 20:05:33 -0700 From: "Richard Shockey" To: , , References: In-Reply-To: Date: Wed, 17 Oct 2007 23:05:16 -0400 Message-ID: <011001c81133$b6867ad0$23937070$@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: Acdq2YSxJnBpAM8fRfeozkdMO0FALymWRc5w Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: Subject: [Enum] I have formally requested a BOF on the PEPPERMINT proposition for Vancouver. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I have submitted to the RAI AD's and the agenda folks a proposed BOF. I would like folks to consider the proposed charter and comment. Should folks wish to present drafts or simply wish to present ideas let us know ASAP. Peppermint BOF Provisioning Extensions in Peering Registries for Multimedia Interconnection. Mailing Lists: peppermint@ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/peppermint BOF chairs: Richard Shockey [richard.shockey@neustar.biz] Other co-chairs TBD waiting on approvals... Temporary Area Directorate: Real Time Applications (RAI) Ultimate Area Directorate: TBD BOF Purpose. The ENUM and SPEERMINT working groups are working on various aspects of Multi Media Interconnection. ENUM is specifically chartered to develop protocols that involve the translation of E.164 numbers to URI's. SPEERMINT has been chartered to develop best current practices among real-time application service providers and how such services interconnect across domain boundaries. It is clear from discussions in both working groups that Multi-Media Interconnection will require various forms of data to be exchanged among administrative domains outside the normal scope of establishing various forms of a SIP session. Such data exchanges might be provisioning of various forms of Registries containing mappings of phone numbers to URI, policies surrounding the admission to points of network interconnection, trunking data and the distribution of Registry data to various types of databases. Provisioning may include PBX to service provider data exchanges as well. The purpose of the BOF is to determine the need and scope for such data exchanges, what existing protocols need to be adapted to meet those needs and the appropriate schema and queries are needed to facilitate such exchanges. The IETF has in the past done significant work on data exchanges among various administrative entities. In particular the PROVREG working group developed various schema and query mechanisms to facilitate the exchange of data among domain name registries and registrars. The ENUM Working group has adapted PROVREG working group protocols to develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS tree. However, there has been little adoption of RFC 4114, and many of the participants of the SPEERMINT working group require both data models and protocol features not found in RFC 4114. The proposed PEPPERMINT working group will build upon the knowledge gained from those efforts, and the intent of this proposed working group is to find a provisioning solution for peering as defined by SPEERMINT. The final work product(s) from this working group will be based upon XML. Additionally, bias will be given to re-using either EPP, HTTP/REST, HTTP/XML-RPC, or HTTP/SOAP. Proposed Deliverables Requirements for PEPPERMINT data exchanges. Provisioning of PEPPERMINT data registries. Provisioning of PEPPERMINT/ENUM data caches. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 18 11:11:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiWyN-0000OE-Bn; Thu, 18 Oct 2007 11:07:43 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiWyL-0000MZ-BA; Thu, 18 Oct 2007 11:07:41 -0400 Received: from mail28.messagelabs.com ([216.82.249.131]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IiWyK-0005YQ-7K; Thu, 18 Oct 2007 11:07:41 -0400 X-VirusChecked: Checked X-Env-Sender: daryl@level3.net X-Msg-Ref: server-21.tower-28.messagelabs.com!1192720058!42239860!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [209.245.18.106] Received: (qmail 25906 invoked from network); 18 Oct 2007 15:07:38 -0000 Received: from unknown.level3.net (HELO f10bb8-10) (209.245.18.106) by server-21.tower-28.messagelabs.com with SMTP; 18 Oct 2007 15:07:38 -0000 Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57]) by f10bb8-10 (Postfix) with ESMTP id 9A2CF4CB4; Thu, 18 Oct 2007 15:07:38 +0000 (GMT) Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest inrestarting a BOF on the subject of Peppermint. From: Daryl Malas To: "Creighton, Tom" In-Reply-To: <45AEC6EF95942140888406588E1A660202ECC379@PACDCEXCMB04.cable.comcast.com> References: <047301c806ef$8294f650$87bee2f0$@us> <1192114310.1297.322.camel@montag.eng.level3.com> <1aaf01c80cf3$c97a7090$5c6f51b0$@us> <1192571265.1297.336.camel@montag.eng.level3.com> <45AEC6EF95942140888406588E1A660202ECC379@PACDCEXCMB04.cable.comcast.com> Content-Type: text/plain Date: Thu, 18 Oct 2007 09:15:28 -0600 Message-Id: <1192720528.1297.340.camel@montag.eng.level3.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 (2.6.0-1) Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e5bfa71b340354e384155def5e70b13b Cc: enum@ietf.org, speermint@ietf.org, Richard Shockey X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Tom/Richard, I perceive you both are closer to an existing problem relative to this than I am. Let me know how I can support you from SPEERMINT aspects. --Daryl On Wed, 2007-10-17 at 15:11 -0400, Creighton, Tom wrote: > Daryl: > > I understand your concern that we might be placing the cart before the > horse; but have you considered that the cart might actually be a horse? > SPEERMINT, as we all know, was designed to take a collection of > protocols and provide a set of recommendations as to how they should be > used. PEPPERMINT, however, would need to define a set of protocols that > could be used to exchange provisioning data in support of efforts such > as SPEERMINT. These standards would need to support a myriad of use > cases within the IETF which could then be the basis of a SPEERMINT BCP. > > There is a DIRE need for standardization in this area today because the > current standard of exchanging provisioning data (such as call routing > tables) using Excel is not acceptable. > > Tom > > > -----Original Message----- > > From: Daryl Malas [mailto:daryl@level3.net] > > Sent: Tuesday, October 16, 2007 17:48 > > To: Richard Shockey > > Cc: enum@ietf.org; speermint@ietf.org > > Subject: RE: [Enum] Re: [Speermint] I'd like to guage interest > > inrestarting a BOF on the subject of Peppermint. > > > > >From my perspective, we are just, finally, nearing completion of the > > terminology draft. Since, we have not completed drafts, such as > > "Requirements" and "Architecture", I would be concerned the PEPPERMINT > > group/BOF understands exactly what the requirements of the > > interconnection would look like in order to provision it > appropriately. > > > > IMO, continued discussion around this topic is warranted, but I think > > the PEPPERMINT BOF should wait until near or after the following > > SPEERMINT milestone is met: > > > > Feb 2008 Submit SPEERMINT minimum requirements for SIP-based VoIP > > interconnection. (BCP) > > > > Based on this, I would recommend a BOF in the spring (likely Summer) > and > > perhaps the need for a WG at the fall 2008 IETF conference. > > > > This way the PEPPERMINT group will fully understand the requirements, > > and will be able to appropriately define a charter. > > > > --Daryl > > > > On Fri, 2007-10-12 at 13:15 -0400, Richard Shockey wrote: > > > Don't you think the work can proceed in parallel? > > > > > > Provisioning is the Achillies heel of interconnection .. > > > > > > > -----Original Message----- > > > > From: Daryl Malas [mailto:daryl@level3.net] > > > > Sent: Thursday, October 11, 2007 10:52 AM > > > > To: Richard Shockey > > > > Cc: enum@ietf.org; speermint@ietf.org > > > > Subject: [Enum] Re: [Speermint] I'd like to guage interest in > > > > restarting a BOF on the subject of Peppermint. > > > > > > > > IMO, I believe this is warranted, but I do not think we are ready > for > > > > it > > > > yet. I suspect this will be of a lot more interest in this BOF > in > > > > about > > > > 1 year, after several of the SPEERMINT milestones are completed. > > > > > > > > Daryl > > > > > > > > On Thu, 2007-10-04 at 21:31 -0400, Richard Shockey wrote: > > > > > This time last year I tried to start up a BOF on some of the > > ongoing > > > > > provisioning issues between various forms of ENUM registries > and > > > > network > > > > > entities. I've had a few folks ask what ever happened to that. > I > > > > still think > > > > > there is a strong need to do this and the work could have > relevance > > > > if the > > > > > scope were expanded not to be just service provider to registry > but > > > > also PBX > > > > > to registries as well. > > > > > > > > > > I'd like to test the water to see if there is any interest in > doing > > > > this in > > > > > Vancouver. > > > > > > > > > > > > > > > The original BOF proposal was this: > > > > > > > > > > Comments as usual are welcome > > > > > > > > > > > > > > > Peppermint BOF > > > > > > > > > > Provisioning Extensions in Peering Registries for Multimedia > > > > > Intererconnection. > > > > > > > > > > Mailing Lists: > > > > > > > > > > BOF chairs: > > > > > > > > > > Richard Shockey [rich.shockey@neustar.biz] > > > > > > > > > > Temporary Area Directorate: Real Time Applications (RAI) > > > > > > > > > > Ultimate Area Directorate: TBD > > > > > > > > > > > > > > > BOF Purpose. > > > > > > > > > > The ENUM and SPEERMINT working groups are working on various > > aspects > > > > of > > > > > Multi Media Interconnection. ENUM is specifically chartered to > > > > develop > > > > > protocols that involve the translation of E.164 numbers to > URI's. > > > > > SPEERMINT has been chartered to develop best current practices > > among > > > > > real-time application service providers and how such services > > > > interconnect > > > > > across domain boundaries. > > > > > > > > > > It is clear from discussions in both working groups that Multi- > > Media > > > > > Interconnection will require various forms of data to be > exchanged > > > > among > > > > > administrative domains outside the normal scope of establishing > a > > > > SIP > > > > > session. > > > > > > > > > > Such data exchanges might be provisioning of various forms of > > > > Registries > > > > > containing mappings of phone numbers to URI, policies > surrounding > > > > the > > > > > admission to points of network interconnection and the > distribution > > > > of > > > > > Registry data to various types of databases. > > > > > > > > > > The purpose of the BOF is to determine the need and scope for > such > > > > data > > > > > exchanges, what existing protocols need to be adapted to meet > those > > > > needs > > > > > and the appropriate schema and queries are needed to facilitate > > such > > > > > exchanges. > > > > > > > > > > The IETF has in the past done significant work on data > exchanges > > > > among > > > > > various administrative entities. In particular the PROVREG > working > > > > group > > > > > developed various schema and query mechanisms to facilitate the > > > > exchange of > > > > > data among domain name registries and registrars. > > > > > > > > > > The ENUM Working group has adapted PROVREG working group > protocols > > > > to > > > > > develop RFC 4114, which facilitates the provisioning of ENUM > data > > in > > > > the DNS > > > > > tree. However, there has been little adoption of RFC 4114, and > > many > > > > of the > > > > > participants of the SPEERMINT working group require both data > > models > > > > and > > > > > protocol features not found in RFC 4114. > > > > > > > > > > The proposed PEPPERMINT working group will build upon the > knowledge > > > > gained > > > > > from those efforts, and the intent of this proposed working > group > > is > > > > to find > > > > > a provisioning solution for peering as defined by SPEERMINT. > The > > > > final work > > > > > product(s) from this working group will be based upon XML. > > > > > > > > > > Additionally, > > > > > bias will be given to re-using either EPP, HTTP/REST, > HTTP/XML-RPC, > > > > or > > > > > HTTP/SOAP. > > > > > > > > > > Proposed Deliverables > > > > > > > > > > Requirements for SPEERMINT data exchange. > > > > > > > > > > Provisioning of SPEERMINT data registries. > > > > > > > > > > Provisioning of SPEERMINT/ENUM data caches. > > > > > > > > > > Richard Shockey > > > > > Director, Member of the Technical Staff > > > > > NeuStar > > > > > 46000 Center Oak Plaza - Sterling, VA 20166 > > > > > sip:rshockey(at)iptel.org > > > > > PSTN Office +1 571.434.5651 > > > > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Speermint mailing list > > > > > Speermint@ietf.org > > > > > https://www1.ietf.org/mailman/listinfo/speermint > > > > > > > > > > > > _______________________________________________ > > > > enum mailing list > > > > enum@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/enum > > > > > > > > > _______________________________________________ > > > enum mailing list > > > enum@ietf.org > > > https://www1.ietf.org/mailman/listinfo/enum > > > > > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 18 13:21:48 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiYzs-0004Eh-58; Thu, 18 Oct 2007 13:17:24 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiYzq-0004EE-I9; Thu, 18 Oct 2007 13:17:22 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IiYzq-0001iU-4X; Thu, 18 Oct 2007 13:17:22 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id 3F826E8129; Thu, 18 Oct 2007 10:12:04 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20071018171204.3F826E8129@bosco.isi.edu> Date: Thu, 18 Oct 2007 10:12:04 -0700 (PDT) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: enum@ietf.org, rfc-editor@rfc-editor.org Subject: [Enum] RFC 5028 on A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5028 Title: A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services Author: R. Mahy Status: Standards Track Date: October 2007 Mailbox: rohan@ekabal.com Pages: 5 Characters: 9804 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-im-service-03.txt URL: http://www.rfc-editor.org/rfc/rfc5028.txt This document registers a Telephone Number Mapping (ENUM) service for Instant Messaging (IM). Specifically, this document focuses on provisioning 'im:' URIs (Uniform Resource Identifiers) in ENUM. [STANDARDS TRACK] This document is a product of the Telephone Number Mapping Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 18 17:12:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iicao-0001n4-AY; Thu, 18 Oct 2007 17:07:46 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iical-0001ii-AE; Thu, 18 Oct 2007 17:07:43 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iicak-000150-SU; Thu, 18 Oct 2007 17:07:43 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9IL7MaB029091 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 18 Oct 2007 14:07:23 -0700 From: "Richard Shockey" To: , , Date: Thu, 18 Oct 2007 17:07:03 -0400 Message-ID: <015401c811ca$d62a1fd0$827e5f70$@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: AcgRytTsDz5Ud6eaTUeuHZBKD8ZgGQ== Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: Subject: [Enum] These were the documents from the last time we considered a Peppermint BOF. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org http://tools.ietf.org/html/draft-schwartz-peppermint-e164-provisioning-data- set-00 http://tools.ietf.org/html/draft-newton-peppermint-problem-statement-00 http://tools.ietf.org/html/draft-lewis-peppermint-enum-reg-if-00 It would be a good time to review them and see whether they are still relevant. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 22 09:45:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjxVk-0000Im-HF; Mon, 22 Oct 2007 09:40:04 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjxVj-0000I2-AA; Mon, 22 Oct 2007 09:40:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IjxVi-0000vL-V2; Mon, 22 Oct 2007 09:40:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id D8CB52AC78; Mon, 22 Oct 2007 13:40:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IjxVi-0005td-C8; Mon, 22 Oct 2007 09:40:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 22 Oct 2007 09:40:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-combined-08.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --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 : Combined User and Infrastructure ENUM in the e164.arpa tree Author(s) : M. Haberler, et al. Filename : draft-ietf-enum-combined-08.txt Pages : 9 Date : 2007-10-22 This memo defines an interim solution for Infrastructure ENUM to allow a combined User and Infrastructure ENUM implementation in e164.arpa as a national choice. This interim solution will be deprecated after approval and implementation of the long-term solution. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-combined-08.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-combined-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-combined-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-22093133.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-combined-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-combined-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-22093133.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Mon Oct 22 12:02:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjzhY-0000FO-88; Mon, 22 Oct 2007 12:00:24 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjzhC-0008Hd-Ru; Mon, 22 Oct 2007 12:00:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IjzhC-0002Qf-GQ; Mon, 22 Oct 2007 12:00:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6BAAF2AC7C; Mon, 22 Oct 2007 16:00:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IjzhC-0004ba-68; Mon, 22 Oct 2007 12:00:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 22 Oct 2007 12:00:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --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 : Guide and Template for IANA Registrations of Enumservices Author(s) : B. Hoeneisen, et al. Filename : draft-ietf-enum-enumservices-guide-05.txt Pages : 23 Date : 2007-10-22 This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) services. It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-enumservices-guide-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-enumservices-guide-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-22115025.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-enumservices-guide-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-enumservices-guide-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-22115025.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Mon Oct 22 17:38:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ik4ty-0005Qi-IG; Mon, 22 Oct 2007 17:33:34 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ik4tx-0005O1-2W for enum@ietf.org; Mon, 22 Oct 2007 17:33:33 -0400 Received: from smtp.denic.de ([81.91.161.3]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ik4tw-0004ZE-MV for enum@ietf.org; Mon, 22 Oct 2007 17:33:32 -0400 Received: from mail-int1.denic.de (mail-int1.denic.de [192.168.0.45]) by smtp.denic.de with esmtp id 1Ik4tb-0003P6-CL; Mon, 22 Oct 2007 23:33:11 +0200 Received: from localhost by mail-int1.denic.de with local id 1Ik4tb-0002fP-00; Mon, 22 Oct 2007 23:33:11 +0200 Date: Mon, 22 Oct 2007 23:33:11 +0200 From: Peter Koch To: enum@ietf.org Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt Message-ID: <20071022213311.GE679@denics7.denic.de> Mail-Followup-To: enum@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org wrote: > Title : Guide and Template for IANA Registrations of Enumservices > Author(s) : B. Hoeneisen, et al. > Filename : draft-ietf-enum-enumservices-guide-05.txt {NIT: use of "" in the xml2rfc source might have lead to less changes in the diff and usually makes references easier to comprehend} The ASCII art I like, but I still think the document tries to reinvent the wheel by designing a specific review process instead of using the available choices. It also might produce strange corner cases, e.g. where it demands the proposed service be submitted as "individual submission", which could even exclude a WG from the proposing a new service (well, there's a solution to that, but why not get it right in the first place). The proposal mixes "Designated Expert" (in 2434bis terms) with "IETF Review" by maintaining the requirement that any ENUMservice be published as a BCP, Standards Track or Experimental RFC. The draft in question would be an excellent opportunity to relax that. IMHO the ENUM service registration should be based on "Expert Review" plus "RFC required" with additional guiding information provided to the Expert-to-be by the various obligatory sections currently present in the template. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 23 07:34:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkHyF-0000gN-Uq; Tue, 23 Oct 2007 07:30:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkHwY-0006nX-1m for enum@ietf.org; Tue, 23 Oct 2007 07:29:06 -0400 Received: from medel.switch.ch ([2001:620:0:14:214:4fff:fe75:4775]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkHwM-0002pC-On for enum@ietf.org; Tue, 23 Oct 2007 07:29:06 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by medel.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1IkHwH-0007MU-4f for enum@ietf.org; Tue, 23 Oct 2007 13:28:49 +0200 Date: Tue, 23 Oct 2007 13:02:03 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: Peter Koch Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt In-Reply-To: <20071022213311.GE679@denics7.denic.de> Message-ID: References: <20071022213311.GE679@denics7.denic.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed ReSent-Date: Tue, 23 Oct 2007 13:28:23 +0200 (CEST) ReSent-From: Bernie Hoeneisen ReSent-To: enum@ietf.org ReSent-Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt ReSent-Message-ID: X-SWITCH-SCANNER: bypassed X-Spam-Score: -3.9 (---) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: enum-bounces@ietf.org Errors-To: enum-bounces@ietf.org Hi Peter Thanks for your feedback. We'll take it into consideration for the next update, which hopefully is ready before the upcoming submission deadline. Comments inline. On Mon, 22 Oct 2007, Peter Koch wrote: > On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org wrote: > The ASCII art I like, but I still think the document tries to reinvent the > wheel by designing a specific review process instead of using the available > choices. I agree with you. We are certainly trying to allign it with existing processes for IANA registrations. We did not have the time so far to study those in detail. > It also might produce strange corner cases, e.g. where it > demands the proposed service be submitted as "individual submission", > which could even exclude a WG from the proposing a new service (well, > there's a solution to that, but why not get it right in the first place). What exactly do you mean here? > The proposal mixes "Designated Expert" (in 2434bis terms) with "IETF Review" I am aware of the mixing part, which certainly needs to be sorted out. There is also the open issue at which time in the process the expert comes into action. > by maintaining the requirement that any ENUMservice be published as a > BCP, Standards Track or Experimental RFC. The draft in question would > be an excellent opportunity to relax that. What would be your concrete proposal for relaxing? > IMHO the ENUM service registration should be based on "Expert Review" plus > "RFC required" with additional guiding information provided to the > Expert-to-be by the various obligatory sections currently present in the > template. I agree with you. We are trying to map this into a proper process. cheers, Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 23 11:02:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkLDo-0007M7-LG; Tue, 23 Oct 2007 10:59:08 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkLDn-0007Lz-6P; Tue, 23 Oct 2007 10:59:07 -0400 Received: from services.erkkila.org ([24.97.94.217] helo=erkkila.org) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkLDm-0002Mt-SX; Tue, 23 Oct 2007 10:59:07 -0400 Received: from [10.1.1.20] (peetop.erkkila.org [::ffff:10.1.1.20]) (AUTH: PLAIN pee@erkkila.org, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by erkkila.org with esmtp; Tue, 23 Oct 2007 14:59:06 +0000 id 0020B228.471E0C3A.000065AF Message-ID: <471E0C98.7010303@erkkila.org> Date: Tue, 23 Oct 2007 15:00:40 +0000 From: Paul Erkkila User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Richard Shockey Subject: Re: [Enum] I'd like to guage interest in restarting a BOF on the subject of Peppermint. References: <047301c806ef$8294f650$87bee2f0$@us> In-Reply-To: <047301c806ef$8294f650$87bee2f0$@us> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I would be interested in this BOF, as I believe there are significant resources being expended towards solving this problem right now. The sooner open dialog on issues and methods can be established the better. -pee (If it turns out to be a B2B interface for exchanging excel spreadsheets I'm going to cry in public...) Richard Shockey wrote: > This time last year I tried to start up a BOF on some of the ongoing > provisioning issues between various forms of ENUM registries and network > entities. I've had a few folks ask what ever happened to that. I still think > there is a strong need to do this and the work could have relevance if the > scope were expanded not to be just service provider to registry but also PBX > to registries as well. > > I'd like to test the water to see if there is any interest in doing this in > Vancouver. > > > The original BOF proposal was this: > > Comments as usual are welcome > > > Peppermint BOF > > Provisioning Extensions in Peering Registries for Multimedia > Intererconnection. > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 23 11:08:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkLLO-0004Wc-NF; Tue, 23 Oct 2007 11:06:58 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjzYQ-0005re-Lk for enum@ietf.org; Mon, 22 Oct 2007 11:50:58 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IjzYQ-0001Fi-FL for enum@ietf.org; Mon, 22 Oct 2007 11:50:58 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id 241C0175EF; Mon, 22 Oct 2007 15:50:28 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IjzXv-00079F-Lo; Mon, 22 Oct 2007 11:50:27 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: hoeneisen@switch.ch From: IETF I-D Submission Tool Message-Id: Date: Mon, 22 Oct 2007 11:50:27 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 X-Mailman-Approved-At: Tue, 23 Oct 2007 11:06:56 -0400 Cc: enum@ietf.org, jason_livingood@cable.comcast.com, alexander.mayrhofer@enum.at Subject: [Enum] New Version Notification for draft-ietf-enum-enumservices-guide-05 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A new version of I-D, draft-ietf-enum-enumservices-guide-05.txt has been successfuly submitted by Bernie Hoeneisen and posted to the IETF repository. Filename: draft-ietf-enum-enumservices-guide Revision: 05 Title: Guide and Template for IANA Registrations of Enumservices Creation_date: 2007-10-22 WG ID: enum Number_of_pages: 23 Abstract: This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) services. It is also to be used for updates of existing IANA registrations. The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 24 00:02:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkXMI-0006wX-NB; Tue, 23 Oct 2007 23:56:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkXMH-0006wR-Ql for enum@ietf.org; Tue, 23 Oct 2007 23:56:41 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkXME-0003VK-NG for enum@ietf.org; Tue, 23 Oct 2007 23:56:41 -0400 Received: from rshockeyPC (67.108.228.34.ptr.us.xo.net [67.108.228.34]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9O3nmWd011094 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Oct 2007 20:56:00 -0700 From: "Richard Shockey" To: "'Peter Koch'" , References: <20071022213311.GE679@denics7.denic.de> In-Reply-To: <20071022213311.GE679@denics7.denic.de> Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt Date: Tue, 23 Oct 2007 23:49:48 -0400 Message-ID: <001e01c815f1$d8ead770$8ac08650$@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: AcgU8zpuVi6h3aNQTESpdhzKiFzJuQAFcCTQ Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Peter thank you for taking the time to comment here... I thought we decided that we would use existing procedures here and not reinvent the wheel. http://www3.ietf.org/proceedings/07jul/minutes/enum.txt Expert Review certainly with the option to require IESG review via a RFC. > -----Original Message----- > From: Peter Koch [mailto:pk@DENIC.DE] > Sent: Monday, October 22, 2007 5:33 PM > To: enum@ietf.org > Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- > 05.txt > > On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org > wrote: > > > Title : Guide and Template for IANA Registrations of > Enumservices > > Author(s) : B. Hoeneisen, et al. > > Filename : draft-ietf-enum-enumservices-guide-05.txt > > {NIT: use of "" in the xml2rfc source might have > lead > to less changes in the diff and usually makes references easier > to > comprehend} > > The ASCII art I like, but I still think the document tries to reinvent > the > wheel by designing a specific review process instead of using the > available > choices. It also might produce strange corner cases, e.g. where it > demands the proposed service be submitted as "individual submission", > which could even exclude a WG from the proposing a new service (well, > there's a solution to that, but why not get it right in the first > place). > > The proposal mixes "Designated Expert" (in 2434bis terms) with "IETF > Review" > by maintaining the requirement that any ENUMservice be published as a > BCP, Standards Track or Experimental RFC. The draft in question would > be an excellent opportunity to relax that. > > IMHO the ENUM service registration should be based on "Expert Review" > plus > "RFC required" with additional guiding information provided to the > Expert-to-be by the various obligatory sections currently present in > the > template. > > -Peter > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 24 05:17:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkcGd-0001mZ-Mz; Wed, 24 Oct 2007 05:11:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkcGb-0001U5-QB for enum@ietf.org; Wed, 24 Oct 2007 05:11:09 -0400 Received: from aletsch.switch.ch ([2001:620:0:1b:203:baff:febe:905a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkcGN-0005CL-Sv for enum@ietf.org; Wed, 24 Oct 2007 05:11:07 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by aletsch.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1IkcFw-0005GE-DQ; Wed, 24 Oct 2007 11:10:28 +0200 Date: Wed, 24 Oct 2007 11:10:26 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: Richard Shockey Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt In-Reply-To: <001e01c815f1$d8ead770$8ac08650$@us> Message-ID: References: <20071022213311.GE679@denics7.denic.de> <001e01c815f1$d8ead770$8ac08650$@us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SWITCH-SCANNER: bypassed X-Spam-Score: -3.9 (---) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: enum@ietf.org, 'Peter Koch' , "Livingood, Jason" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On Tue, 23 Oct 2007, Richard Shockey wrote: > Peter thank you for taking the time to comment here... I thought we decided > that we would use existing procedures here and not reinvent the wheel. Rich, Peter: Which of the existing procedures do you have in mind? Jason: As the original text for the procdure now proposed in the I-D was contributed by you, did you take the idea from an existing registration procedure? cheers, Bernie > http://www3.ietf.org/proceedings/07jul/minutes/enum.txt > > Expert Review certainly with the option to require IESG review via a RFC. > >> -----Original Message----- >> From: Peter Koch [mailto:pk@DENIC.DE] >> Sent: Monday, October 22, 2007 5:33 PM >> To: enum@ietf.org >> Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- >> 05.txt >> >> On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org >> wrote: >> >> > Title : Guide and Template for IANA Registrations of >> Enumservices >> > Author(s) : B. Hoeneisen, et al. >> > Filename : draft-ietf-enum-enumservices-guide-05.txt >> >> {NIT: use of "" in the xml2rfc source might have >> lead >> to less changes in the diff and usually makes references easier >> to >> comprehend} >> >> The ASCII art I like, but I still think the document tries to reinvent >> the >> wheel by designing a specific review process instead of using the >> available >> choices. It also might produce strange corner cases, e.g. where it >> demands the proposed service be submitted as "individual submission", >> which could even exclude a WG from the proposing a new service (well, >> there's a solution to that, but why not get it right in the first >> place). >> >> The proposal mixes "Designated Expert" (in 2434bis terms) with "IETF >> Review" >> by maintaining the requirement that any ENUMservice be published as a >> BCP, Standards Track or Experimental RFC. The draft in question would >> be an excellent opportunity to relax that. >> >> IMHO the ENUM service registration should be based on "Expert Review" >> plus >> "RFC required" with additional guiding information provided to the >> Expert-to-be by the various obligatory sections currently present in >> the >> template. >> >> -Peter >> >> _______________________________________________ >> enum mailing list >> enum@ietf.org >> https://www1.ietf.org/mailman/listinfo/enum > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 24 21:07:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikr5A-0002pz-N0; Wed, 24 Oct 2007 21:00:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikr59-0002pr-Q6; Wed, 24 Oct 2007 21:00:19 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ikr59-0002Ns-F1; Wed, 24 Oct 2007 21:00:19 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 4A81A26E77; Thu, 25 Oct 2007 01:00:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Ikr4s-0005rP-6K; Wed, 24 Oct 2007 21:00:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 24 Oct 2007 21:00:02 -0400 X-Spam-Score: -1.4 (-) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-softswitch-req-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --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 : ENUM-based Softswitch Requirement Author(s) : J. Lim, et al. Filename : draft-ietf-enum-softswitch-req-01.txt Pages : 17 Date : 2007-10-24 This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-softswitch-req-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-softswitch-req-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-softswitch-req-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-24205050.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-softswitch-req-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-softswitch-req-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-24205050.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Thu Oct 25 08:58:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il2EW-0001y6-Nb; Thu, 25 Oct 2007 08:54:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkqwV-0000yJ-VE for enum@ietf.org; Wed, 24 Oct 2007 20:51:23 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkqwU-0002FS-SE for enum@ietf.org; Wed, 24 Oct 2007 20:51:23 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id BC2A73289A; Thu, 25 Oct 2007 00:50:52 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Ikqw0-0000ao-Kt; Wed, 24 Oct 2007 20:50:52 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: jhlim@nida.or.kr From: IETF I-D Submission Tool Message-Id: Date: Wed, 24 Oct 2007 20:50:52 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a X-Mailman-Approved-At: Thu, 25 Oct 2007 08:54:43 -0400 Cc: enum@ietf.org, ckp@nida.or.kr, wkim@nida.or.kr, lconroy@insensate.co.uk Subject: [Enum] New Version Notification for draft-ietf-enum-softswitch-req-01 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A new version of I-D, draft-ietf-enum-softswitch-req-01.txt has been successfuly submitted by JoonHyung Lim and posted to the IETF repository. Filename: draft-ietf-enum-softswitch-req Revision: 01 Title: ENUM-based Softswitch Requirement Creation_date: 2007-10-25 WG ID: enum Number_of_pages: 17 Abstract: This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 08:58:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il2Ep-0002QF-4v; Thu, 25 Oct 2007 08:55:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkMJs-0003Zf-8D for enum@ietf.org; Tue, 23 Oct 2007 12:09:28 -0400 Received: from web90607.mail.mud.yahoo.com ([216.252.100.190]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IkMJl-000832-Vy for enum@ietf.org; Tue, 23 Oct 2007 12:09:28 -0400 Received: (qmail 93798 invoked by uid 60001); 23 Oct 2007 16:09:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=03IzrxQLbueOwROiYJswtmqrQE9Eu0ZfXCgyZSaR4sPqjksaUQiYccqRYtwUVdVSwi9mpC+FqIkWjsdWWmu09FkaqJky9rEzinjSWz1N/ActI2Z1a0L82xwyp1yVp52jqCTnll/ZLJuVLmqcuyZMdZXLy+LB9fu8+ddZazVVCdE=; X-YMail-OSG: Xsl5QecVM1njrOR2W3DfpkU.NQCTcTWpsuS.FPAkQZp29kGHclvliTHchWJmUvU3ZEVE5U_8KlLVR34nJJY.cQ_Jl0KmWdCZyP5NaDuNUVqC0CQOx1k- Received: from [65.113.98.146] by web90From enum-bounces@ietf.org Thu Oct 25 08:58:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il2EW-0001y6-Nb; Thu, 25 Oct 2007 08:54:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkqwV-0000yJ-VE for enum@ietf.org; Wed, 24 Oct 2007 20:51:23 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkqwU-0002FS-SE for enum@ietf.org; Wed, 24 Oct 2007 20:51:23 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id BC2A73289A; Thu, 25 Oct 2007 00:50:52 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Ikqw0-0000ao-Kt; Wed, 24 Oct 2007 20:50:52 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: jhlim@nida.or.kr From: IETF I-D Submission Tool Message-Id: Date: Wed, 24 Oct 2007 20:50:52 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a X-Mailman-Approved-At: Thu, 25 Oct 2007 08:54:43 -0400 Cc: enum@ietf.org, ckp@nida.or.kr, wkim@nida.or.kr, lconroy@insensate.co.uk Subject: [Enum] New Version Notification for draft-ietf-enum-softswitch-req-01 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A new version of I-D, draft-ietf-enum-softswitch-req-01.txt has been successfuly submitted by JoonHyung Lim and posted to the IETF repository. Filename: draft-ietf-enum-softswitch-req Revision: 01 Title: ENUM-based Softswitch Requirement Creation_date: 2007-10-25 WG ID: enum Number_of_pages: 17 Abstract: This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 08:58:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il2Ep-0002QF-4v; Thu, 25 Oct 2007 08:55:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkMJs-0003Zf-8D for enum@ietf.org; Tue, 23 Oct 2007 12:09:28 -0400 Received: from web90607.mail.mud.yahoo.com ([216.252.100.190]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IkMJl-000832-Vy for enum@ietf.org; Tue, 23 Oct 2007 12:09:28 -0400 Received: (qmail 93798 invoked by uid 60001); 23 Oct 2007 16:09:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=03IzrxQLbueOwROiYJswtmqrQE9Eu0ZfXCgyZSaR4sPqjksaUQiYccqRYtwUVdVSwi9mpC+FqIkWjsdWWmu09FkaqJky9rEzinjSWz1N/ActI2Z1a0L82xwyp1yVp52jqCTnll/ZLJuVLmqcuyZMdZXLy+LB9fu8+ddZazVVCdE=; X-YMail-OSG: Xsl5QecVM1njrOR2W3DfpkU.NQCTcTWpsuS.FPAkQZp29kGHclvliTHchWJmUvU3ZEVE5U_8KlLVR34nJJY.cQ_Jl0KmWdCZyP5NaDuNUVqC0CQOx1k- Received: from [65.113.98.146] by web90607.mail.mud.yahoo.com via HTTP; Tue, 23 Oct 2007 09:09:10 PDT X-Mailer: YahooMailRC/814.06 YahooMailWebService/0.7.134.12 Date: Tue, 23 Oct 2007 09:09:10 -0700 (PDT) From: Sukanta ganguly Subject: Re: [Speermint] Re: [Enum] I'd like to guage interest in restarting a BOF on the subject of Peppermint. To: Paul Erkkila , Richard Shockey MIME-Version: 1.0 Message-ID: <530636.92774.qm@web90607.mail.mud.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a X-Mailman-Approved-At: Thu, 25 Oct 2007 08:55:02 -0400 Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0058287678==" Errors-To: enum-bounces@ietf.org --===============0058287678== Content-Type: multipart/alternative; boundary="0-722659610-1193155750=:92774" --0-722659610-1193155750=:92774 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I would be very interested in this BoF. This is going to be a very importan= t area.=0A=0AThanks=0ASG=0A=0A=0A----- Original Message ----=0AFrom: Paul E= rkkila =0ATo: Richard Shockey =0ACc: e= num@ietf.org; speermint@ietf.org=0ASent: Tuesday, October 23, 2007 8:00:40 = AM=0ASubject: [Speermint] Re: [Enum] I'd like to guage interest in restarti= ng a BOF on the subject of Peppermint.=0A=0A=0A I would be interested in t= his BOF, as I believe there are significant=0Aresources being expended towa= rds solving this problem right now. The=0Asooner open dialog on issues and = methods can be established the better.=0A=0A-pee=0A=0A=0A(If it turns out t= o be a B2B interface for exchanging excel spreadsheets=0AI'm going to cry i= n public...)=0A=0A=0ARichard Shockey wrote:=0A> This time last year I tried= to start up a BOF on some of the ongoing=0A> provisioning issues between v= arious forms of ENUM registries and network=0A> entities. I've had a few fo= lks ask what ever happened to that. I still think=0A> there is a strong nee= d to do this and the work could have relevance if the=0A> scope were expand= ed not to be just service provider to registry but also PBX=0A> to registri= es as well.=0A> =0A> I'd like to test the water to see if there is any inte= rest in doing this in=0A> Vancouver.=0A> =0A> =0A> The original BOF proposa= l was this:=0A> =0A> Comments as usual are welcome=0A> =0A> =0A> Peppermint= BOF=0A> =0A> Provisioning Extensions in Peering Registries for Multimedia= =0A> Intererconnection.=0A> =0A=0A=0A________________________________= _______________=0ASpeermint mailing list=0ASpeermint@ietf.org=0Ahttps://www= 1.ietf.org/mailman/listinfo/speermint=0A=0A________________________________= __________________=0ADo You Yahoo!?=0ATired of spam? Yahoo! Mail has the b= est spam protection around =0Ahttp://mail.yahoo.com --0-722659610-1193155750=:92774 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable
I would be very interested in this BoF. This is g= oing to be a very important area.
=0A
 
=0A
SG

=0A
----- Original Mess= age ----
From: Paul Erkkila <pee@erkkila.org>
To: Richard Shock= ey <richard@shockey.us>
Cc: enum@ietf.org; speermint@ietf.org
S= ent: Tuesday, October 23, 2007 8:00:40 AM
Subject: [Speermint] Re: [Enum= ] I'd like to guage interest in restarting a BOF on the subject of Peppermi= nt.


  I would be interested in this BOF, as I believe there= are significant
resources being expended towards solving this problem r= ight now. The
sooner open dialog on issues and methods can be establishe= d the better.

-pee


(If it turns out to be a B2B interface= for exchanging excel spreadsheets
I'm going to cry in public...)

Richard Shockey wrote:
> This time last year I tried to start up= a BOF on some of the ongoing
> provisioning issues between various f= orms of ENUM registries and network
> entities. I've had a few folks ask what ever happened to t= hat. I still think
> there is a strong need to do this and the work c= ould have relevance if the
> scope were expanded not to be just servi= ce provider to registry but also PBX
> to registries as well.
>=
> I'd like to test the water to see if there is any interest in doi= ng this in
> Vancouver.
>
>
> The original BOF pr= oposal was this:
>
> Comments as usual are welcome
> >
> Peppermint BOF
>
> Provisioning Extensions in P= eering Registries for Multimedia
> Intererconnection.
>
<= ;snip>

_______________________________________________
Speermi= nt mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint
=0A


______________________________________= ____________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best = spam protection around
http://mail.yahoo.com --0-722659610-1193155750=:92774-- --===============0058287678== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============0058287678==-- 607.mail.mud.yahoo.com via HTTP; Tue, 23 Oct 2007 09:09:10 PDT X-Mailer: YahooMailRC/814.06 YahooMailWebService/0.7.134.12 Date: Tue, 23 Oct 2007 09:09:10 -0700 (PDT) From: Sukanta ganguly Subject: Re: [Speermint] Re: [Enum] I'd like to guage interest in restarting a BOF on the subject of Peppermint. To: Paul Erkkila , Richard Shockey MIME-Version: 1.0 Message-ID: <530636.92774.qm@web90607.mail.mud.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a X-Mailman-Approved-At: Thu, 25 Oct 2007 08:55:02 -0400 Cc: enum@ietf.org, speermint@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0058287678==" Errors-To: enum-bounces@ietf.org --===============0058287678== Content-Type: multipart/alternative; boundary="0-722659610-1193155750=:92774" --0-722659610-1193155750=:92774 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I would be very interested in this BoF. This is going to be a very importan= t area.=0A=0AThanks=0ASG=0A=0A=0A----- Original Message ----=0AFrom: Paul E= rkkila =0ATo: Richard Shockey =0ACc: e= num@ietf.org; speermint@ietf.org=0ASent: Tuesday, October 23, 2007 8:00:40 = AM=0ASubject: [Speermint] Re: [Enum] I'd like to guage interest in restarti= ng a BOF on the subject of Peppermint.=0A=0A=0A I would be interested in t= his BOF, as I believe there are significant=0Aresources being expended towa= rds solving this problem right now. The=0Asooner open dialog on issues and = methods can be established the better.=0A=0A-pee=0A=0A=0A(If it turns out t= o be a B2B interface for exchanging excel spreadsheets=0AI'm going to cry i= n public...)=0A=0A=0ARichard Shockey wrote:=0A> This time last year I tried= to start up a BOF on some of the ongoing=0A> provisioning issues between v= arious forms of ENUM registries and network=0A> entities. I've had a few fo= lks ask what ever happened to that. I still think=0A> there is a strong nee= d to do this and the work could have relevance if the=0A> scope were expand= ed not to be just service provider to registry but also PBX=0A> to registri= es as well.=0A> =0A> I'd like to test the water to see if there is any inte= rest in doing this in=0A> Vancouver.=0A> =0A> =0A> The original BOF proposa= l was this:=0A> =0A> Comments as usual are welcome=0A> =0A> =0A> Peppermint= BOF=0A> =0A> Provisioning Extensions in Peering Registries for Multimedia= =0A> Intererconnection.=0A> =0A=0A=0A________________________________= _______________=0ASpeermint mailing list=0ASpeermint@ietf.org=0Ahttps://www= 1.ietf.org/mailman/listinfo/speermint=0A=0A________________________________= __________________=0ADo You Yahoo!?=0ATired of spam? Yahoo! Mail has the b= est spam protection around =0Ahttp://mail.yahoo.com --0-722659610-1193155750=:92774 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable
I would be very interested in this BoF. This is g= oing to be a very important area.
=0A
 
=0A
SG

=0A
----- Original Mess= age ----
From: Paul Erkkila <pee@erkkila.org>
To: Richard Shock= ey <richard@shockey.us>
Cc: enum@ietf.org; speermint@ietf.org
S= ent: Tuesday, October 23, 2007 8:00:40 AM
Subject: [Speermint] Re: [Enum= ] I'd like to guage interest in restarting a BOF on the subject of Peppermi= nt.


  I would be interested in this BOF, as I believe there= are significant
resources being expended towards solving this problem r= ight now. The
sooner open dialog on issues and methods can be establishe= d the better.

-pee


(If it turns out to be a B2B interface= for exchanging excel spreadsheets
I'm going to cry in public...)

Richard Shockey wrote:
> This time last year I tried to start up= a BOF on some of the ongoing
> provisioning issues between various f= orms of ENUM registries and network
> entities. I've had a few folks ask what ever happened to t= hat. I still think
> there is a strong need to do this and the work c= ould have relevance if the
> scope were expanded not to be just servi= ce provider to registry but also PBX
> to registries as well.
>=
> I'd like to test the water to see if there is any interest in doi= ng this in
> Vancouver.
>
>
> The original BOF pr= oposal was this:
>
> Comments as usual are welcome
> >
> Peppermint BOF
>
> Provisioning Extensions in P= eering Registries for Multimedia
> Intererconnection.
>
<= ;snip>

_______________________________________________
Speermi= nt mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint
=0A


______________________________________= ____________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best = spam protection around
http://mail.yahoo.com --0-722659610-1193155750=:92774-- --===============0058287678== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============0058287678==-- From enum-bounces@ietf.org Thu Oct 25 09:55:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il38S-00047s-DT; Thu, 25 Oct 2007 09:52:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il38R-00047U-5D; Thu, 25 Oct 2007 09:52:31 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Il38Q-00047b-Sl; Thu, 25 Oct 2007 09:52:31 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id BA29A26E77; Thu, 25 Oct 2007 13:52:20 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Il38G-0000HU-LF; Thu, 25 Oct 2007 09:52:20 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Thu, 25 Oct 2007 09:52:20 -0400 X-Spam-Score: -1.4 (-) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Cc: enum mailing list , enum chair , Internet Architecture Board , RFC Editor Subject: [Enum] Protocol Action: 'ENUM Validation Token Format Definition' to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has approved the following document: - 'ENUM Validation Token Format Definition ' as a Proposed Standard This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Jon Peterson and Cullen Jennings. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-token-04.txt Technical Summary An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes a signed XML data format -- the Validation Token -- with which Validation Entities can convey successful completion of a validation procedure in a secure fashion. Working Group Summary No controversial issues with this document. Protocol Quality This document was reviewed for the IESG by Jon Peterson. Richard Shockey is the PROTO shepherd. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 11:28:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il4aQ-0000XF-PM; Thu, 25 Oct 2007 11:25:30 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il4aP-0000Wt-2X for enum@ietf.org; Thu, 25 Oct 2007 11:25:29 -0400 Received: from 77-99-145-183.cable.ubr06.hari.blueyonder.co.uk ([77.99.145.183] helo=romek-szczesniaks-computer.local) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il4aO-0002OJ-JL for enum@ietf.org; Thu, 25 Oct 2007 11:25:28 -0400 Received: from romek-szczesniaks-computer.local (localhost [127.0.0.1]) by romek-szczesniaks-computer.local (Postfix) with ESMTP id BE2A1414D47 for ; Thu, 25 Oct 2007 16:25:27 +0100 (BST) Message-ID: <4720B567.8060809@spikyblackcat.co.uk> Date: Thu, 25 Oct 2007 16:25:27 +0100 From: Romek Szczesniak User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: enum@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.7 (+) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Subject: [Enum] Re: I-D Action:draft-hoeneisen-enum-x-service-regs-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-hoeneisen-enum-x-service-regs-02.txt Pages : 8 Date : 2007-10-23 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. --- Hello all, Firstly, I must thank Bernie Hoeneisen on his work on the draft, draft-hoeneisen-enum-x-service-regs-02.txt. I haven't seen any discussion on it here so I thought I would. Having tested various experimental services to see how they perform, I recommend the following with such service types. Typically, we use E2U+X- services when: (i) the defined service does not conform to the usage we require e.g. IN NAPTR 100 115 "u" "E2U+x-im:msn" "!^.*$!msn:!" . (ii) there is no defined service in the Enumservices list. e.g. IN NAPTR 100 115 "u" "E2U+x-rss:http" "!^.*$!http://rss.cnn.com/rss/cnn_topstories.rss!" . (iii) when a client does not wish a service type to be evaluated by a standards-based ENUM clients. I suggest that: 1. We specify that X- services SHOULD follow the same syntax as other registered services (so that ENUM clients do not break on receipt of such rules). 2. Provide a standardised mechanism for service types (if needed for public use) to be appended to the list of Enum service types after review. This review period should be at most about 6 months (to prevent all service types remaining as X- ). 3. Intended use for these is "EXPERIMENTAL". Your thoughts appreciated. Romek Szczesniak _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 15:04:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7w9-0000Lr-Mi; Thu, 25 Oct 2007 15:00:09 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7w8-0000LN-EA for enum@ietf.org; Thu, 25 Oct 2007 15:00:08 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il7w7-0002d1-Sj for enum@ietf.org; Thu, 25 Oct 2007 15:00:08 -0400 Received: from rshockeyPC (dhcp16.rice.iit.edu [216.47.140.229]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9PIxNii019865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 25 Oct 2007 11:59:47 -0700 From: "Richard Shockey" To: Date: Thu, 25 Oct 2007 14:59:31 -0400 Message-ID: <05d701c81739$3b829f10$b287dd30$@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: AcgVaKBJeIwPmePGTPurV1toC4RFfAA4fk7A Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Subject: [Enum] FW: I-D Action:draft-hoeneisen-enum-x-service-regs-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Bernie I'll send a note to Internet Drafts that this is a WG document. You might want to rename future versions. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Tuesday, October 23, 2007 7:30 AM To: i-d-announce@ietf.org Subject: I-D Action:draft-hoeneisen-enum-x-service-regs-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-hoeneisen-enum-x-service-regs-02.txt Pages : 8 Date : 2007-10-23 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hoeneisen-enum-x-service-regs-02.t xt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-hoeneisen-enum-x-service-regs-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-hoeneisen-enum-x-service-regs-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 15:04:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7wh-0000Vg-6u; Thu, 25 Oct 2007 15:00:43 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7we-0000TH-DV for enum@ietf.org; Thu, 25 Oct 2007 15:00:40 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il7wd-0002e4-OC for enum@ietf.org; Thu, 25 Oct 2007 15:00:40 -0400 Received: from rshockeyPC (dhcp16.rice.iit.edu [216.47.140.229]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9PIxNij019865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Oct 2007 11:59:52 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" References: <20071022213311.GE679@denics7.denic.de> <001e01c815f1$d8ead770$8ac08650$@us> In-Reply-To: Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt Date: Thu, 25 Oct 2007 14:59:31 -0400 Message-ID: <060201c81739$40569550$c103bff0$@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: AcgWHf3rwvn/U4b9SaWaq5HMbcaEFgAKyRUg Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Cc: enum@ietf.org, 'Peter Koch' , "'Livingood, Jason'" , david.conrad@icann.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Well there are multiple IANA procedures for doing this. .what I thought we wanted to do was select the procedure from the best practices here. The new URI scheme registration for instance. [15] Hansen, T, et al., "The "Guidelines and Registration Procedures for New URI Schemes", RFC 4395, February 2006 I think one thing we should do is check with David Conrad the GM IANA for input. I spoke to him in Chicago specifically about providing a little expert guidance of what works and what doesn't. > -----Original Message----- > From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch] > Sent: Wednesday, October 24, 2007 5:10 AM > To: Richard Shockey > Cc: enum@ietf.org; 'Peter Koch'; Livingood, Jason > Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- > 05.txt > > On Tue, 23 Oct 2007, Richard Shockey wrote: > > > Peter thank you for taking the time to comment here... I thought we > decided > > that we would use existing procedures here and not reinvent the > wheel. > > > Rich, Peter: > Which of the existing procedures do you have in mind? > > > Jason: > As the original text for the procdure now proposed in the I-D was > contributed by you, did you take the idea from an existing > registration procedure? > > > cheers, > Bernie > > > > http://www3.ietf.org/proceedings/07jul/minutes/enum.txt > > > > Expert Review certainly with the option to require IESG review via a > RFC. > > > >>From enum-bounces@ietf.org Thu Oct 25 15:04:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7w9-0000Lr-Mi; Thu, 25 Oct 2007 15:00:09 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7w8-0000LN-EA for enum@ietf.org; Thu, 25 Oct 2007 15:00:08 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il7w7-0002d1-Sj for enum@ietf.org; Thu, 25 Oct 2007 15:00:08 -0400 Received: from rshockeyPC (dhcp16.rice.iit.edu [216.47.140.229]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9PIxNii019865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 25 Oct 2007 11:59:47 -0700 From: "Richard Shockey" To: Date: Thu, 25 Oct 2007 14:59:31 -0400 Message-ID: <05d701c81739$3b829f10$b287dd30$@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: AcgVaKBJeIwPmePGTPurV1toC4RFfAA4fk7A Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Subject: [Enum] FW: I-D Action:draft-hoeneisen-enum-x-service-regs-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Bernie I'll send a note to Internet Drafts that this is a WG document. You might want to rename future versions. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Tuesday, October 23, 2007 7:30 AM To: i-d-announce@ietf.org Subject: I-D Action:draft-hoeneisen-enum-x-service-regs-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-hoeneisen-enum-x-service-regs-02.txt Pages : 8 Date : 2007-10-23 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hoeneisen-enum-x-service-regs-02.t xt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-hoeneisen-enum-x-service-regs-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-hoeneisen-enum-x-service-regs-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME mes -----Original Message----- > >> From: Peter Koch [mailto:pk@DENIC.DE] > >> Sent: Monday, October 22, 2007 5:33 PM > >> To: enum@ietf.org > >> Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- > >> 05.txt > >> > >> On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org > >> wrote: > >> > >> > Title : Guide and Template for IANA Registrations of > >> Enumservices > >> > Author(s) : B. Hoeneisen, et al. > >> > Filename : draft-ietf-enum-enumservices-guide-05.txt > >> > >> {NIT: use of "" in the xml2rfc source might > have > >> lead > >> to less changes in the diff and usually makes references > easier > >> to > >> comprehend} > >> > >> The ASCII art I like, but I still think the document tries to > reinvent > >> the > >> wheel by designing a specific review process instead of using the > >> available > >> choices. It also might produce strange corner cases, e.g. where > it > >> demands the proposed service be submitted as "individual > submission", > >> which could even exclude a WG from the proposing a new service > (well, > >> there's a solution to that, but why not get it right in the first > >> place). > >> > >> The proposal mixes "Designated Expert" (in 2434bis terms) with > "IETF > >> Review" > >> by maintaining the requirement that any ENUMservice be published > as a > >> BCP, Standards Track or Experimental RFC. The draft in question > would > >> be an excellent opportunity to relax that. > >> > >> IMHO the ENUM service registration should be based on "Expert > Review" > >> plus > >> "RFC required" with additional guiding information provided to the > >> Expert-to-be by the various obligatory sections currently present > in > >> the > >> template. > >> > >> -Peter > >> > >> _______________________________________________ > >> enum mailing list > >> enum@ietf.org > >> https://www1.ietf.org/mailman/listinfo/enum > > > > > > _______________________________________________ > > enum mailing list > > enum@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum > > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum sages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 15:04:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7wh-0000Vg-6u; Thu, 25 Oct 2007 15:00:43 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il7we-0000TH-DV for enum@ietf.org; Thu, 25 Oct 2007 15:00:40 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il7wd-0002e4-OC for enum@ietf.org; Thu, 25 Oct 2007 15:00:40 -0400 Received: from rshockeyPC (dhcp16.rice.iit.edu [216.47.140.229]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9PIxNij019865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Oct 2007 11:59:52 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" References: <20071022213311.GE679@denics7.denic.de> <001e01c815f1$d8ead770$8ac08650$@us> In-Reply-To: Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt Date: Thu, 25 Oct 2007 14:59:31 -0400 Message-ID: <060201c81739$40569550$c103bff0$@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: AcgWHf3rwvn/U4b9SaWaq5HMbcaEFgAKyRUg Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Cc: enum@ietf.org, 'Peter Koch' , "'Livingood, Jason'" , david.conrad@icann.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Well there are multiple IANA procedures for doing this. .what I thought we wanted to do was select the procedure from the best practices here. The new URI scheme registration for instance. [15] Hansen, T, et al., "The "Guidelines and Registration Procedures for New URI Schemes", RFC 4395, February 2006 I think one thing we should do is check with David Conrad the GM IANA for input. I spoke to him in Chicago specifically about providing a little expert guidance of what works and what doesn't. > -----Original Message----- > From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch] > Sent: Wednesday, October 24, 2007 5:10 AM > To: Richard Shockey > Cc: enum@ietf.org; 'Peter Koch'; Livingood, Jason > Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- > 05.txt > > On Tue, 23 Oct 2007, Richard Shockey wrote: > > > Peter thank you for taking the time to comment here... I thought we > decided > > that we would use existing procedures here and not reinvent the > wheel. > > > Rich, Peter: > Which of the existing procedures do you have in mind? > > > Jason: > As the original text for the procdure now proposed in the I-D was > contributed by you, did you take the idea from an existing > registration procedure? > > > cheers, > Bernie > > > > http://www3.ietf.org/proceedings/07jul/minutes/enum.txt > > > > Expert Review certainly with the option to require IESG review via a > RFC. > > > >> -----Original Message----- > >> From: Peter Koch [mailto:pk@DENIC.DE] > >> Sent: Monday, October 22, 2007 5:33 PM > >> To: enum@ietf.org > >> Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- > >> 05.txt > >> > >> On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org > >> wrote: > >> > >> > Title : Guide and Template for IANA Registrations of > >> Enumservices > >> > Author(s) : B. Hoeneisen, et al. > >> > Filename : draft-ietf-enum-enumservices-guide-05.txt > >> > >> {NIT: use of "" in the xml2rfc source might > have > >> lead > >> to less changes in the diff and usually makes references > easier > >> to > >> comprehend} > >> > >> The ASCII art I like, but I still think the document tries to > reinvent > >> the > >> wheel by designing a specific review process instead of using the > >> available > >> choices. It also might produce strange corner cases, e.g. where > it > >> demands the proposed service be submitted as "individual > submission", > >> which could even exclude a WG from the proposing a new service > (well, > >> there's a solution to that, but why not get it right in the first > >> place). > >> > >> The proposal mixes "Designated Expert" (in 2434bis terms) with > "IETF > >> Review" > >> by maintaining the requirement that any ENUMservice be published > as a > >> BCP, Standards Track or Experimental RFC. The draft in question > would > >> be an excellent opportunity to relax that. > >> > >> IMHO the ENUM service registration should be based on "Expert > Review" > >> plus > >> "RFC required" with additional guiding information provided to the > >> Expert-to-be by the various obligatory sections currently present > in > >> the > >> template. > >> > >> -Peter > >> > >> _______________________________________________ > >> enum mailing list > >> enum@ietf.org > >> https://www1.ietf.org/mailman/listinfo/enum > > > > > > _______________________________________________ > > enum mailing list > > enum@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum > > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 25 20:04:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCcK-0003OC-D3; Thu, 25 Oct 2007 20:00:00 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCcJ-0003Il-LT for enum@ietf.org; Thu, 25 Oct 2007 19:59:59 -0400 Received: from norman.insensate.co.uk ([213.152.49.123] helo=insensate.co.uk) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlCcI-0002wZ-7c for enum@ietf.org; Thu, 25 Oct 2007 19:59:59 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 1015C5A6E6; Fri, 26 Oct 2007 00:59:57 +0100 (BST) In-Reply-To: <060201c81739$40569550$c103bff0$@us> References: <20071022213311.GE679@denics7.denic.de> <001e01c815f1$d8ead770$8ac08650$@us> <060201c81739$40569550$c103bff0$@us> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: lconroy Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt Date: Fri, 26 Oct 2007 00:59:47 +0100 To: Richard Shockey X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: a743e34ab8eb08259de9a7307caed594 Cc: enum@ietf.org, "'Livingood, Jason'" , 'Peter Koch' , 'Bernie Hoeneisen' , david.conrad@icann.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Esteemed chair, folks, OK - I'll rise to this. Is your preference for the URI scheme process (of RFC 4395) that you believe that the requirements spelt out in the URI scheme process are appropriate for Enumservices? The URI scheme process has a very high barrier to entry - see in particular section 2.1 of RFC 4395. This seems to me to be wildly inappropriate for Enumservices that will be used in specific access controlled environments like carrier or federated ENUM. Section 3 of that document would seem to be ideal for X- Enumservices or ones that are going to be used in controlled environments. However, section 5.2 point 4 ("as needed to bring it into line with the guidelines given in this document") seems to apply the same rules for *both* permanent and provisional registrations. As written, that's an awfully high bar. Looking at the real issues with Enumservices so far, it seems to me that most of writing an Enumservice specification is straightforward. Putting text strings into a NAPTR and decoding it *should* be simple by now. Defining a complete specification for the textual syntax is easy. It's been done many times. The trick is describing what happens if a program (or a person) uses this NAPTR. Enumservices will continue to need a domain expert to review them (preferably NOT the authors :), to handle the very important job of deciding if some poor sod can understand what happens if you use this Enumservice and believing that the same poor sod can implement based on the specification. Given that new Enumservices may well be used in fairly esoteric environments (e.g. closed systems in one country or another), selecting an expert who is familiar (or even aware) of the intended environment is not going to be easy. [IMHO, environments around the world differ markedly. What makes sense to a person with experience on one Continent will be wrong for someone else] My biggest concern with all of these procedures is that there are simply not enough domain experts active in this WG (and certainly outside this WG) to form a pool of reviewers. We may end up with some very busy people struggling to cover Enumservice uses and environments with which they are not familiar. Although it doesn't mention it in 4395, I ASSUME that (like 2929bis), the IESG designates the pool of experts. However, I have no idea how IANA is expected to select the designated expert for a given Enumservice document, unless we ASSUME that any Enumservice must make sense to everyone and be used anywhere. If we DO make that assumption, that would be a pity. If we don't assume that all Enumservices must have "clear utility to the broad Internet community", then the putative mailing list is going to have to give some guidance, otherwise IANA is going to be lumbered with a *very* hard selection job. all the best, Lawrence On 25 Oct 2007, at 19:59, Richard Shockey wrote: > Well there are multiple IANA procedures for doing this. .what I > thought we > wanted to do was select the procedure from the best practices here. > The new > URI scheme registration for instance. > > [15] Hansen, T, et al., "The "Guidelines and Registration > Procedures for New > URI Schemes", RFC 4395, February 2006 > > I think one thing we should do is check with David Conrad the GM > IANA for > input. I spoke to him in Chicago specifically about providing a little > expert guidance of what works and what doesn't. > >> -----Original Message----- >> From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch] >> Sent: Wednesday, October 24, 2007 5:10 AM >> To: Richard Shockey >> Cc: enum@ietf.org; 'Peter Koch'; Livingood, Jason >> Subject: RE: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- >> 05.txt >> >> On Tue, 23 Oct 2007, Richard Shockey wrote: >> >>> Peter thank you for taking the time to comment here... I thought we >> decided >>> that we would use existing procedures here and not reinvent the >> wheel. >> >> >> Rich, Peter: >> Which of the existing procedures do you have in mind? >> >> >> Jason: >> As the original text for the procdure now proposed in the I-D was >> contributed by you, did you take the idea from an existing >> registration procedure? >> >> >> cheers, >> Bernie >> >> >>> http://www3.ietf.org/proceedings/07jul/minutes/enum.txt >>> >>> Expert Review certainly with the option to require IESG review via a >> RFC. >>> >>>> -----Original Message----- >>>> From: Peter Koch [mailto:pk@DENIC.DE] >>>> Sent: Monday, October 22, 2007 5:33 PM >>>> To: enum@ietf.org >>>> Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide- >>>> 05.txt >>>> >>>> On Mon, Oct 22, 2007 at 12:00:02PM -0400, Internet-Drafts@ietf.org >>>> wrote: >>>> >>>>> Title : Guide and Template for IANA Registrations > of >>>> Enumservices >>>>> Author(s) : B. Hoeneisen, et al. >>>>> Filename : draft-ietf-enum-enumservices-guide-05.txt >>>> >>>> {NIT: use of "" in the xml2rfc source might >> have >>>> lead >>>> to less changes in the diff and usually makes references >> easier >>>> to >>>> comprehend} >>>> >>>> The ASCII art I like, but I still think the document tries to >> reinvent >>>> the >>>> wheel by designing a specific review process instead of using the >>>> available >>>> choices. It also might produce strange corner cases, e.g. where >> it >>>> demands the proposed service be submitted as "individual >> submission", >>>> which could even exclude a WG from the proposing a new service >> (well, >>>> there's a solution to that, but why not get it right in the first >>>> place). >>>> >>>> The proposal mixes "Designated Expert" (in 2434bis terms) with >> "IETF >>>> Review" >>>> by maintaining the requirement that any ENUMservice be published >> as a >>>> BCP, Standards Track or Experimental RFC. The draft in question >> would >>>> be an excellent opportunity to relax that. >>>> >>>> IMHO the ENUM service registration should be based on "Expert >> Review" >>>> plus >>>> "RFC required" with additional guiding information provided to the >>>> Expert-to-be by the various obligatory sections currently present >> in >>>> the >>>> template. >>>> >>>> -Peter >>>> >>>> _______________________________________________ >>>> enum mailing list >>>> enum@ietf.org >>>> https://www1.ietf.org/mailman/listinfo/enum >>> >>> >>> _______________________________________________ >>> enum mailing list >>> enum@ietf.org >>> https://www1.ietf.org/mailman/listinfo/enum >>> >> >> _______________________________________________ >> enum mailing list >> enum@ietf.org >> https://www1.ietf.org/mailman/listinfo/enum > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sat Oct 27 13:25:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlpJM-0005et-Qw; Sat, 27 Oct 2007 13:19:00 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlpJL-0005eO-AW; Sat, 27 Oct 2007 13:18:59 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlpJK-0001SZ-TF; Sat, 27 Oct 2007 13:18:59 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9RHISTj011099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 27 Oct 2007 10:18:34 -0700 From: "Richard Shockey" To: , , Date: Sat, 27 Oct 2007 13:18:30 -0400 Message-ID: <013401c818bd$6af29ef0$40d7dcd0$@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: AcgYvVkvcd5GTwa4TB2EnGvHOpcoZg== Content-language: en-us x-cr-hashedpuzzle: Dq7y NmQL SXgb VWcZ XfcI Xvnl cVd0 dJwj fkWQ hQEU jGt5 jQS1 js6T mE3f r4Ik sSc0; 4; ZQBuAHUAbQBAAGkAZQB0AGYALgBvAHIAZwA7AHAAZQBwAHAAZQByAG0AaQBuAHQAQABpAGUAdABmAC4AbwByAGcAOwBzAHAAZQBlAHIAbQBpAG4AdABAAGkAZQB0AGYALgBvAHIAZwA7AHQAbwBtAF8AYwByAGUAaQBnAGgAdABvAG4AQABjAGEAYgBsAGUALgBjAG8AbQBjAGEAcwB0AC4AYwBvAG0A; Sosha1_v1; 7; {87B3EDCC-8D4B-4AA6-AE6E-69B84F4A9A57}; cgBpAGMAaABhAHIAZABAAHMAaABvAGMAawBlAHkALgB1AHMA; Sat, 27 Oct 2007 17:18:16 GMT; SQAgAGgAYQB2AGUAIABpAHQAIABvAG4AIABnAG8AbwBkACAAYQB1AHQAaABvAHIAaQB0AHkAIAB0AGgAYQB0ACAAdABoAGUAIABQAEUAUABQAEUAUgBNAEkATgBUACAAQgBPAEYAIABoAGEAcwAgAGIAZQBlAG4AIABhAHAAcAByAG8AdgBlAGQAIABmAG8AcgAgAEkARQBUAEYAIAA3ADAA x-cr-puzzleid: {87B3EDCC-8D4B-4AA6-AE6E-69B84F4A9A57} X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: "'Creighton, Tom'" Subject: [Enum] I have it on good authority that the PEPPERMINT BOF has been approved for IETF 70 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Time TBD. We will be working or a revised agenda ASAP. Individuals interested in making presentations should contact myself or Tom Creighton. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 29 04:36:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImQ0a-00045M-8f; Mon, 29 Oct 2007 04:30:04 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImQ0Y-00045C-Oh; Mon, 29 Oct 2007 04:30:02 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImQ0Y-0006wS-CP; Mon, 29 Oct 2007 04:30:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 45FE62AC73; Mon, 29 Oct 2007 08:30:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1ImQ0Y-0006lN-1h; Mon, 29 Oct 2007 04:30:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 29 Oct 2007 04:30:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-unused-03.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --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 for Enumservice UNUSED Author(s) : R. Stastny, et al. Filename : draft-ietf-enum-unused-03.txt Pages : 16 Date : 2007-10-29 This document registers the Enumservice "unused" using the URI scheme "data:" as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice may be used to indicate that the E.164 number (or E.164 number range) tied to the domain in which the enclosing NAPTR is published is not allocated or assigned for communications service. When such an indication is provided, an ENUM client can detect calls that will fail "early". A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-unused-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-unused-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-unused-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-29042040.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-unused-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-unused-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-29042040.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Mon Oct 29 10:18:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImVOo-0003kH-76; Mon, 29 Oct 2007 10:15:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImPs2-0005F4-DM for enum@ietf.org; Mon, 29 Oct 2007 04:21:14 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImPs1-0007nn-A0 for enum@ietf.org; Mon, 29 Oct 2007 04:21:14 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id 454A7328E4; Mon, 29 Oct 2007 08:20:43 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1ImPrX-0004gv-50; Mon, 29 Oct 2007 04:20:43 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: richard.stastny@oefeg.at From: IETF I-D Submission Tool Message-Id: Date: Mon, 29 Oct 2007 04:20:43 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 X-Mailman-Approved-At: Mon, 29 Oct 2007 10:15:23 -0400 Cc: enum@ietf.org, Richard.stastny@oefeg.at, lwc@roke.co.uk, jim@dns-moda.org Subject: [Enum] New Version Notification for draft-ietf-enum-unused-03 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A new version of I-D, draft-ietf-enum-unused-03.txt has been successfuly submitted by Richard Stastny and posted to the IETF repository. Filename: draft-ietf-enum-unused Revision: 03 Title: IANA Registration for Enumservice UNUSED Creation_date: 2007-10-28 WG ID: enum Number_of_pages: 16 Abstract: This document registers the Enumservice "unused" using the URI scheme "data:" as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice may be used to indicate that the E.164 number (or E.164 number range) tied to the domain in which the enclosing NAPTR is published is not allocated or assigned for communications service. When such an indication is provided, an ENUM client can detect calls that will fail "early". The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 29 14:58:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZik-0004fw-Sh; Mon, 29 Oct 2007 14:52:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZik-0004f6-8K for enum@ietf.org; Mon, 29 Oct 2007 14:52:18 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImZgt-0008CY-NN for enum@ietf.org; Mon, 29 Oct 2007 14:52:18 -0400 Received: from rshockeyPC ([64.251.114.2]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9TInuMV026361 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Oct 2007 10:49:59 -0800 From: "Richard Shockey" To: Date: Mon, 29 Oct 2007 14:50:13 -0400 Message-ID: <0af301c81a5c$8c7bdbe0$a57393a0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca3xY1iIc3tIYqQTKyYngbYZG9Jtg== Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" Subject: [Enum] ENUM Working Group Last Call draft-ietf-enum-unused-03.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Filename: draft-ietf-enum-unused Revision: 03 Title: IANA Registration for Enumservice UNUSED Creation_date: 2007-10-28 WG ID: enum Number_of_pages: 16 Abstract: This document registers the Enumservice "unused" using the URI scheme "data:" as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice may be used to indicate that the E.164 number (or E.164 number range) tied to the domain in which the enclosing NAPTR is published is not allocated or assigned for communications service. When such an indication is provided, an ENUM client can detect calls that will fail "early". 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 or so from today October 29 until at least September though we can modify that if new issues come up. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 29 14:58:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZmk-0007Ws-Og; Mon, 29 Oct 2007 14:56:26 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZmj-0007Wb-RF for enum@ietf.org; Mon, 29 Oct 2007 14:56:25 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImZmj-00071k-EF for enum@ietf.org; Mon, 29 Oct 2007 14From enum-bounces@ietf.org Mon Oct 29 14:58:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZik-0004fw-Sh; Mon, 29 Oct 2007 14:52:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZik-0004f6-8K for enum@ietf.org; Mon, 29 Oct 2007 14:52:18 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImZgt-0008CY-NN for enum@ietf.org; Mon, 29 Oct 2007 14:52:18 -0400 Received: from rshockeyPC ([64.251.114.2]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9TInuMV026361 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Oct 2007 10:49:59 -0800 From: "Richard Shockey" To: Date: Mon, 29 Oct 2007 14:50:13 -0400 Message-ID: <0af301c81a5c$8c7bdbe0$a57393a0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca3xY1iIc3tIYqQTKyYngbYZG9Jtg== Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" Subject: [Enum] ENUM Working Group Last Call draft-ietf-enum-unused-03.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Filename: draft-ietf-enum-unused Revision: 03 Title: IANA Registration for Enumservice UNUSED Creation_date: 2007-10-28 WG ID: enum Number_of_pages: 16 Abstract: This document registers the Enumservice "unused" using the URI scheme "data:" as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice may be used to indicate that the E.164 number (or E.164 number range) tied to the domain in which the enclosing NAPTR is published is not allocated or assigned for communications service. When such an indication is provided, an ENUM client can detect calls that will fail "early". 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 or so from today October 29 until at least September though we can modify that if new issues come up. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 29 14:58:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZmk-0007Ws-Og; Mon, 29 Oct 2007 14:56:26 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImZmj-0007Wb-RF for enum@ietf.org; Mon, 29 Oct 2007 14:56:25 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImZmj-00071k-EF for enum@ietf.org; Mon, 29 Oct 2007 14:56:25 -0400 Received: from rshockeyPC ([64.251.114.2]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9TIu2rg028057 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Oct 2007 10:56:04 -0800 From: "Richard Shockey" To: , References: <0af301c81a5c$8c7bdbe0$a57393a0$@us> In-Reply-To: <0af301c81a5c$8c7bdbe0$a57393a0$@us> Subject: RE: [Enum] ENUM Working Group Last Call draft-ietf-enum-unused-03.txt Date: Mon, 29 Oct 2007 14:56:19 -0400 Message-ID: <0b0f01c81a5d$65dde220$3199a660$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Aca3xY1iIc3tIYqQTKyYngbYZG9Jtlil68ew Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org What meant to write is "Work group last call will extend for 2 weeks or so from today October 29 until at least November 13 though we can modify that if new issues come up." > > > Filename: draft-ietf-enum-unused > Revision: 03 > Title: IANA Registration for Enumservice UNUSED > Creation_date: 2007-10-28 > WG ID: enum > Number_of_pages: 16 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum :56:25 -0400 Received: from rshockeyPC ([64.251.114.2]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9TIu2rg028057 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Oct 2007 10:56:04 -0800 From: "Richard Shockey" To: , References: <0af301c81a5c$8c7bdbe0$a57393a0$@us> In-Reply-To: <0af301c81a5c$8c7bdbe0$a57393a0$@us> Subject: RE: [Enum] ENUM Working Group Last Call draft-ietf-enum-unused-03.txt Date: Mon, 29 Oct 2007 14:56:19 -0400 Message-ID: <0b0f01c81a5d$65dde220$3199a660$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Aca3xY1iIc3tIYqQTKyYngbYZG9Jtlil68ew Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org What meant to write is "Work group last call will extend for 2 weeks or so from today October 29 until at least November 13 though we can modify that if new issues come up." > > > Filename: draft-ietf-enum-unused > Revision: 03 > Title: IANA Registration for Enumservice UNUSED > Creation_date: 2007-10-28 > WG ID: enum > Number_of_pages: 16 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 31 15:22:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InJ6t-0004sr-LA; Wed, 31 Oct 2007 15:20:15 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InJ6r-0004iO-EM; Wed, 31 Oct 2007 15:20:13 -0400 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InJ6r-0003BY-1y; Wed, 31 Oct 2007 15:20:13 -0400 Received: from rshockeyPC ([64.251.114.2]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9VJJj70032507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 31 Oct 2007 11:19:46 -0800 From: "Richard Shockey" To: , , Date: Wed, 31 Oct 2007 15:19:52 -0400 Message-ID: <094801c81bf3$0a0c99e0$1e25cda0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acgb4Dxl8GZpM9lXRU2x47JCMPzMqAAEpC1w Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: Subject: [Enum] FW: PEPPERMINT - Requested session has been scheduled for IETF 70 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org PEPPERMINT Session 1 (1 hour) Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2 ---------------------------------------------- Requested Information: --------------------------------------------------------- Working Group Name: peppermint Area Name: Real-time Applications and Infrastructure Area Number of Sessions: 1 Length of Session(s): 1 hour Number of Attendees: 100 Conflicts to Avoid: _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 31 15:54:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InJaq-0008HC-Fw; Wed, 31 Oct 2007 15:51:12 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InJap-00088M-Eg; Wed, 31 Oct 2007 15:51:11 -0400 Received: from osprey.verisign.com ([216.168.239.75]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InJag-00055D-77; Wed, 31 Oct 2007 15:51:02 -0400 Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id l9VJilMb009020; Wed, 31 Oct 2007 14:44:47 -0500 Received: from dul1trutkow-l1.verisign.com ([10.26.0.8]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Oct 2007 15:50:27 -0400 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 31 Oct 2007 15:50:50 -0400 To: "Richard Shockey" , , , From: Tony Rutkowski In-Reply-To: <094801c81bf3$0a0c99e0$1e25cda0$@us> References: <094801c81bf3$0a0c99e0$1e25cda0$@us> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: X-OriginalArrivalTime: 31 Oct 2007 19:50:27.0955 (UTC) FILETIME=[493B3C30:01C81BF7] X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: Subject: [Enum] FCC VoIP Order/NPRM implementation X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Rich, Considering the Commission's adoption of VoIP portability requirements today, is the implementation something you will be considering at the next ENUM fete. --tony _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum