Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iw3SU-0005Aa-96; Sat, 24 Nov 2007 17:26:42 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iw3ST-0005AV-1I for peppermint@ietf.org; Sat, 24 Nov 2007 17:26:41 -0500 Received: from moutng.kundenserver.de ([212.227.126.183]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iw3SS-0007ke-2n for peppermint@ietf.org; Sat, 24 Nov 2007 17:26:40 -0500 Received: from [192.168.0.103] (bzq-219-131-200.static.bezeqint.net [62.219.131.200]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1Iw3SP09Mk-0003Di; Sat, 24 Nov 2007 23:26:37 +0100 In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D04415E4@GBNTHT12009MSX.gb002.siemens.net> References: <12bb01c82632$bb267860$31736920$@us> <0D5F89FAC29E2C41B98A6A762007F5D04415E4@GBNTHT12009MSX.gb002.siemens.net> 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: David Schwartz Subject: Re: [PEPPERMINT] FW: I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt Date: Sun, 25 Nov 2007 00:26:33 +0200 To: "Elwell, John" X-Mailer: Apple Mail (2.752.3) X-Provags-ID: V01U2FsdGVkX1+bYDpegyWp9xnEwrrzIzxJQQRy5x62PcAKVhe SzbzQ03weUpLk4Bk7SZtmd54of/bLpU3X1Wc5TAkGr2py8SprP c07rnJR0gfBtZJUlC4L7g== X-Spam-Score: 0.8 (/) X-Scan-Signature: 200d029292fbb60d25b263122ced50fc Cc: peppermint@ietf.org X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org Hi john. inline... On Nov 21, 2007, at 7:02 PM, Elwell, John wrote: > David, > > From an initial read, I am rather confused. There is a clearly defined > split between SPEERMINT work and ENUM work, with ENUM converting a > telephone number into a SIP URI, DS: The draft is trying among other to point out that the exact meaning of the SIP URI returned in the response is vague and open to interpretation. Defining the meaning and context of data that is passed using the ENUM protocol is an open issue and one may argue that this belongs in the ENUM group. I am not convinced. As to whether or not this should be in the SPEERMINT group, this too is an open issue and it was my understanding that the BOF was formed to discuss this. As a side point, using a SIP 302 redirect mechanism for said resolution is completely valid approach (in fact used quite often in practice) and has nothing to do with ENUM or NAPTR records so the relevance of ENUM is somewhat unclear. > and SPEERMINT finding a SIP server, policy, etc. > for the domain indicated in the SIP URI. DS: I would like to quote from the charter as there seems to be some confusion. "... More specifically, SPEERMINT focuses on real-time session routing architectures and their associated use cases. Deliverables here include the specification of the various types of application flows, such as signaling and media flows, in such networks, and includes both trunking and peer-to-peer flows... The most focused deliverables of SPEERMINT are best current practices regarding exchange of real-time sessions among VoIP and other real- time application service providers and, in particular, how such calls are routed... While the the ENUM Working Group is primarily concerned with the structure and lookup of data for the translation of E.164 numbers into URIs (RFC3761), SPEERMINT is concerned with the use of the resulting URI data, as well as non-ENUM-derived URI data, for use in signaling and routing of real-time sessions. " While the charter does mention that SPEERMINT is concerned with "the use of the resulting URI data" none of the work to date has addressed this issue and it is unclear when and if it will. While I fully understand and support the current efforts with SPEERMINT to define the architectures and use cases as a foundation for future peering work I feel that the context, meaning and data model of the E.164 resolution data as well as the provisioning of this data may well be out of scope for SPEERMINT. > However, the draft > seems to approach provisioning without due regard for that split, > i.e., > it seems to tackle provisioning in a way that allows a VSP to take a > phone number as input and directly obtain the information it needs to > route to an appropriate terminating VSP. Shouldn't we try to keep the > two stages separate? Or have I misunderstood something? > > John > >> -----Original Message----- >> From: Richard Shockey [mailto:richard@shockey.us] >> Sent: 13 November 2007 20:21 >> To: peppermint@ietf.org >> Subject: [PEPPERMINT] FW: >> I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt >> >> I believe this is a document we will be discussing in >> Vancouver at the BOF. >> The references to spearmint was, I'm told somewhat >> inadvertent on the part >> of the authors. >> >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> >> >> Title : Managing Client Voice Peering Provisioning >> Author(s) : D. Schwartz, et al. >> Filename : >> draft-schwartz-speermint-provisioning-problem-00.txt >> Pages : 8 >> Date : 2007-11-13 >> >> This document describes the type of data provisioned among Voice >> Service Providers. This is in support of the service provider >> peering as defined by the Speermint WG. >> >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-schwartz-speermint-p >> rovisioning-pr >> oblem-00.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-schwartz-speermint-provisioning-problem-00.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-schwartz-speermint-provisioning-problem >> -00.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. >> >> >> _______________________________________________ >> PEPPERMINT mailing list >> PEPPERMINT@ietf.org >> https://www1.ietf.org/mailman/listinfo/peppermint >> _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivagy-0007Av-CT; Fri, 23 Nov 2007 10:43:44 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivagx-0007Al-20 for peppermint@ietf.org; Fri, 23 Nov 2007 10:43:43 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ivagw-0004y2-Ak for peppermint@ietf.org; Fri, 23 Nov 2007 10:43:42 -0500 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 lANFhBGg032444 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 23 Nov 2007 07:43:17 -0800 From: "Richard Shockey" To: Date: Fri, 23 Nov 2007 10:43:05 -0500 Message-ID: <0cc901c82de7$8e916e10$abb44a30$@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: Acgt54nSlg6HRgOcTB2wTYdL5Gx8Hw== Content-language: en-us X-Spam-Score: 1.8 (+) X-Scan-Signature: 21be852dc93f0971708678c18d38c096 Subject: [PEPPERMINT] FINAL AGENDA PEPPERMINT BOF IETF 70 X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org 1 Hour -- I can accept last minute additions but time is short. IETF 70 PEPPERMINT BOF Agenda PEPPERMINT Session 1 (1 hour) Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2 Chair(s): Richard Shockey Tom Creighton RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com Agenda Bashing. Presentation of the proposed charter. 10 min 1. Review of peppermint problem statement ( David Schwartz ) Title : Managing Client Voice Peering Provisioning Author(s) : D. Schwartz, et al. Filename : draft-schwartz-speermint-provisioning-problem-00.txt Pages : 8 Date : 2007-11-13 This document describes the type of data provisioned among Voice Service Providers. This is in support of the service provider peering as defined by the Speermint WG. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-schwartz-speermint-provisioning-pr oblem-00.txt 2. Title : ENUM Registry Interface Requirements Author(s) : E. Lewis Filename : draft-lewis-peppermint-enum-reg-if-01.txt Pages : 0 Date : 2007-11-16 An ENUM registry interacts with various elements to maintain what is essentially a telephone number to uniform (or a more modern version) resource identifier. The interfaces needed are identified in this requirements document, as well as the requirements for the more generic interfaces. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lewis-peppermint-enum-reg-if-01.tx t 3. Review of existing provisioning protocols in IETF especially RFC 4114 (S.Hollenbeck) 4. 4114 Experiences Joonhyung Lim [mailto:jhlim@nida.or.kr] General Discussion The Usual Questions. A. Is this a problem that the IETF needs to work on? B. Who wants to work on this problem. ************ 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 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. 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 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iut0w-0005ei-8K; Wed, 21 Nov 2007 12:05:26 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iut0u-0005eQ-7G for peppermint@ietf.org; Wed, 21 Nov 2007 12:05:24 -0500 Received: from mailgate.siemenscomms.co.uk ([195.171.110.225] helo=mailhost.siemenscomms.co.uk) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iut0t-0008LY-Kk for peppermint@ietf.org; Wed, 21 Nov 2007 12:05:24 -0500 Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x11 #31430) with ESMTP id <0JRV00A9K8OM92@siemenscomms.co.uk> for peppermint@ietf.org; Wed, 21 Nov 2007 17:02:46 +0000 (GMT) Date: Wed, 21 Nov 2007 17:02:45 +0000 From: "Elwell, John" Subject: RE: [PEPPERMINT] FW: I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt In-reply-to: <12bb01c82632$bb267860$31736920$@us> To: peppermint@ietf.org, David Schwartz Message-id: <0D5F89FAC29E2C41B98A6A762007F5D04415E4@GBNTHT12009MSX.gb002.siemens.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-Topic: [PEPPERMINT] FW: I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt Thread-Index: AcgmMdgMKdv2oqXpQkC67LHdBikRkQAAIctwAYr9n5A= Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: <12bb01c82632$bb267860$31736920$@us> X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Cc: X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org David, >From an initial read, I am rather confused. There is a clearly defined split between SPEERMINT work and ENUM work, with ENUM converting a telephone number into a SIP URI, and SPEERMINT finding a SIP server, policy, etc. for the domain indicated in the SIP URI. However, the draft seems to approach provisioning without due regard for that split, i.e., it seems to tackle provisioning in a way that allows a VSP to take a phone number as input and directly obtain the information it needs to route to an appropriate terminating VSP. Shouldn't we try to keep the two stages separate? Or have I misunderstood something? John > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us] > Sent: 13 November 2007 20:21 > To: peppermint@ietf.org > Subject: [PEPPERMINT] FW: > I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt > > I believe this is a document we will be discussing in > Vancouver at the BOF. > The references to spearmint was, I'm told somewhat > inadvertent on the part > of the authors. > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Managing Client Voice Peering Provisioning > Author(s) : D. Schwartz, et al. > Filename : > draft-schwartz-speermint-provisioning-problem-00.txt > Pages : 8 > Date : 2007-11-13 > > This document describes the type of data provisioned among Voice > Service Providers. This is in support of the service provider > peering as defined by the Speermint WG. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-schwartz-speermint-p > rovisioning-pr > oblem-00.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-schwartz-speermint-provisioning-problem-00.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-schwartz-speermint-provisioning-problem > -00.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. > > > _______________________________________________ > PEPPERMINT mailing list > PEPPERMINT@ietf.org > https://www1.ietf.org/mailman/listinfo/peppermint > _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It5Pf-0002SZ-Ca; Fri, 16 Nov 2007 12:55:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It5Pe-0002SC-7G for peppermint@ietf.org; Fri, 16 Nov 2007 12:55:30 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1It5Pa-0002Yv-K9 for peppermint@ietf.org; Fri, 16 Nov 2007 12:55:30 -0500 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 lAGHkbCQ013325 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 16 Nov 2007 09:55:00 -0800 From: "Richard Shockey" To: Date: Fri, 16 Nov 2007 12:55:04 -0500 Message-ID: <0c0601c82879$d1752b90$745f82b0$@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: AcgodDAyYF3l4i6VTZCVpHisagDULAABJS5g Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Subject: [PEPPERMINT] FW: I-D ACTION:draft-lewis-peppermint-enum-reg-if-01.txt X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org One additional document etc. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Friday, November 16, 2007 12:15 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-lewis-peppermint-enum-reg-if-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : ENUM Registry Interface Requirements Author(s) : E. Lewis Filename : draft-lewis-peppermint-enum-reg-if-01.txt Pages : 0 Date : 2007-11-16 An ENUM registry interacts with various elements to maintain what is essentially a telephone number to uniform (or a more modern version) resource identifier. The interfaces needed are identified in this requirements document, as well as the requirements for the more generic interfaces. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lewis-peppermint-enum-reg-if-01.tx t 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-lewis-peppermint-enum-reg-if-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-lewis-peppermint-enum-reg-if-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. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsuCp-0005U3-SN; Fri, 16 Nov 2007 00:57:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsuCo-0005T2-Vx for peppermint@ietf.org; Fri, 16 Nov 2007 00:57:30 -0500 Received: from hlid.ogud.com ([66.92.146.160] helo=ogud.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsuCm-0003ZZ-J3 for peppermint@ietf.org; Fri, 16 Nov 2007 00:57:30 -0500 Received: from [172.16.45.235] (hlid.ogud.com [66.92.146.160]) by ogud.com (8.13.1/8.13.1) with ESMTP id lAG5vKJt065069; Fri, 16 Nov 2007 00:57:21 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz) Mime-Version: 1.0 Message-Id: Date: Fri, 16 Nov 2007 13:57:25 +0800 To: peppermint@ietf.org From: Edward Lewis Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.63 on 66.92.146.160 X-Spam-Score: -0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: Subject: [PEPPERMINT] resubmitting a requirements draft X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org FYI - I'm going to resubmit the following draft without edits because it has expired. http://tools.ietf.org/html/draft-lewis-peppermint-enum-reg-if-00 The first time around there were a few comments made on the draft, for the most part summarized the following links. I should incorporate them but given the "perfect storm" of the BoF being schedule, the submission deadline, and a vacation, I haven't... http://www1.ietf.org/mail-archive/web/peppermint/current/msg00022.html http://www1.ietf.org/mail-archive/web/peppermint/current/msg00058.html -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Think glocally. Act confused. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsNkd-0003qq-Tn; Wed, 14 Nov 2007 14:18:15 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsNkc-0003nX-3e for peppermint@ietf.org; Wed, 14 Nov 2007 14:18:14 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsNkb-00085n-F2 for peppermint@ietf.org; Wed, 14 Nov 2007 14:18:14 -0500 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 lAEJHmV1015047 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 14 Nov 2007 11:17:49 -0800 From: "Richard Shockey" To: Date: Wed, 14 Nov 2007 14:18:05 -0500 Message-ID: <11de01c826f3$16509f70$42f1de50$@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: Acgm8xVAXmeC6G8STqK1lhKB5Tc6rg== Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593 Subject: [PEPPERMINT] Agenda as of 14 November 2007 X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org IETF 70 PEPPERMINT BOF Agenda PEPPERMINT Session 1 (1 hour) Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2 Chair(s): Richard Shockey Tom Creighton RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com Agenda Bashing. Presentation of the proposed charter. 10 min 1. Review of peppermint problem statement ( David Schwartz ) Title : Managing Client Voice Peering Provisioning Author(s) : D. Schwartz, et al. Filename : draft-schwartz-speermint-provisioning-problem-00.txt Pages : 8 Date : 2007-11-13 This document describes the type of data provisioned among Voice Service Providers. This is in support of the service provider peering as defined by the Speermint WG. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-schwartz-speermint-provisioning-pr oblem-00.txt 2. Review of existing provisioning protocols in IETF especially RFC 4114 (S.Hollenbeck) 3. 4114 Experiences Joonhyung Lim [mailto:jhlim@nida.or.kr] General Discussion The Usual Questions. A. Is this a problem that the IETF needs to work on? B. Who wants to work on this problem. ************ 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 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 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 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKJB-00040f-Up; Wed, 14 Nov 2007 10:37:41 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKJA-0003yL-4v for peppermint@ietf.org; Wed, 14 Nov 2007 10:37:40 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsKJ9-0007iK-Fn for peppermint@ietf.org; Wed, 14 Nov 2007 10:37:40 -0500 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 lAEFbF4B001710 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 14 Nov 2007 07:37:16 -0800 From: "Richard Shockey" To: Subject: FW: [PEPPERMINT] VERSION 00 PEPPERMINT BOF AGENDA Date: Wed, 14 Nov 2007 10:37:34 -0500 Message-ID: <0d2701c826d4$479b2010$d6d16030$@us> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgkefWWmgrmAqjfSJ2fHd+m6oiOUAB05lNAACGpDhA= Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 6852087d2a39b5d20c975154ae1cd415 X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1427654896==" Errors-To: peppermint-bounces@ietf.org This is a multipart message in MIME format. --===============1427654896== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0D28_01C826AA.5EC51810" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0D28_01C826AA.5EC51810 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I think we can have a short presentation on this .very short since we only have 1 hour. _____ From: Joonhyung Lim [mailto:jhlim@nida.or.kr] Sent: Monday, November 12, 2007 12:47 AM To: richard@shockey.us; peppermint@ietf.org Subject: Re: [PEPPERMINT] VERSION 00 PEPPERMINT BOF AGENDA Dear Richard I'm really happy to comment on this BOF that I've been waiting for, since I noticed some needs from industries through KR infrastructure ENUM trial in 2006. About a charter, IMHO, I think it would be better adding a example on paragraph below, to clarify differences between 4114 and new one. >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." "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, such as provisioning number prefix or number blocks" Actually, this example also mentioned in "PEPPERMINT Problem Statement" draft. And if there is ok, I might have short presentation about provisioning issue when we used 4114 during KR ENUM trial in 2006. It mostly leans to comments from several players such as KR VSPs, PSTN carriers, and etc. Thanks. Joonhyung Lim, NIDA ------------------------------------------------------------- COMMENTS PLEASE ESPECIALLY ON THE PROPOSED CHARTER If anyone wants to present anyting let me or Tom know. ********************************** IETF 70 PEPPERMINT BOF Agenda PEPPERMINT Session 1 (1 hour) Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2 Chair(s): Richard Shockey Tom Creighton RAI Director(s): Jon Peterson jon.peterson at neustar.biz Cullen Jennings fluffy at cisco.com Agenda Bashing. Presentation of the proposed charter. 10 min 1. Review of existing provisioning protocols in IETF especially RFC 4114 (S.Hollenbeck) 2. Review of peppermint problem statement ( David Schwartz ) ID forthcoming. General Discussion The Usual Questions. A. Is this a problem that the IETF needs to work on? B. Are people willing to work on this problem? ************ Peppermint BOF Provisioning Extensions in Peering Registries for Multimedia Interconnection. Mailing Lists: peppermint at ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/peppermint 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. 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 ------=_NextPart_000_0D28_01C826AA.5EC51810 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I think we can have a short presentation on this = …very short since we only have 1 hour.

 

From:= Joonhyung = Lim [mailto:jhlim@nida.or.kr]
Sent: Monday, November 12, 2007 12:47 AM
To: richard@shockey.us; peppermint@ietf.org
Subject: Re: [PEPPERMINT] VERSION 00 PEPPERMINT BOF = AGENDA

Dear = Richard

 

I'm really happy to = comment on this BOF that I've been waiting for, since I noticed some needs from = industries through KR infrastructure ENUM trial in 2006. 

 

About a charter, IMHO, I = think it would be better adding a example on paragraph below, to clarify differences between 4114 and new one. 

 

>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."

 

"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, such as provisioning number = prefix or number blocks"

 

Actually, this example = also mentioned in "PEPPERMINT Problem Statement" = draft. 

 

And if there is ok, I = might have short presentation about provisioning issue when we used 4114 during KR ENUM trial in 2006. It mostly leans to comments from several players such as KR VSPs, PSTN carriers, and etc.

 

Thanks.

 

Joonhyung Lim, = NIDA

 

----------------------------------------------= ---------------

 

 

 

COMMENTS PLEASE ESPECIALLY ON THE PROPOSED = CHARTER

If anyone wants to present anyting let me or Tom know.

**********************************


IETF 70 PEPPERMINT BOF Agenda

PEPPERMINT Session 1 (1 hour)
Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2

Chair(s):

Richard Shockey <richard.shockey at neustar.biz>
Tom Creighton  <tom_creighton at cable.comcast.com>


RAI Director(s):

Jon Peterson jon.peterson at neustar.biz
Cullen Jennings fluffy at cisco.com



Agenda Bashing.

Presentation of the proposed charter. <Shockey> 10 min

1. Review of existing provisioning protocols in IETF especially RFC = 4114
(S.Hollenbeck)

2. Review of peppermint problem statement ( David Schwartz )  = ID
forthcoming.


General Discussion

The Usual Questions.

A. Is this a problem that the IETF needs to work on?

B. Are people willing to work on this problem?


************

Peppermint BOF

Provisioning Extensions in Peering Registries for Multimedia
Interconnection.

Mailing Lists:

  peppermint at ietf.org

General information about the mailing list is at:

  https://www1.i= etf.org/mailman/listinfo/peppermint


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.

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
<mailto:richard(at)shockey.us>
<mailto:richard.shockey(at)neustar.biz= >

------=_NextPart_000_0D28_01C826AA.5EC51810-- --===============1427654896== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint --===============1427654896==-- Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is2G2-0007K6-2r; Tue, 13 Nov 2007 15:21:14 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is2G0-0007K0-KG for peppermint@ietf.org; Tue, 13 Nov 2007 15:21:12 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Is2G0-0006wr-3J for peppermint@ietf.org; Tue, 13 Nov 2007 15:21:12 -0500 Received: from rshockeyPC ([12.149.74.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lADKKmvU026638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 13 Nov 2007 12:20:49 -0800 From: "Richard Shockey" To: Date: Tue, 13 Nov 2007 15:21:09 -0500 Message-ID: <12bb01c82632$bb267860$31736920$@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: AcgmMdgMKdv2oqXpQkC67LHdBikRkQAAIctw Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Subject: [PEPPERMINT] FW: I-D ACTION:draft-schwartz-speermint-provisioning-problem-00.txt X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org I believe this is a document we will be discussing in Vancouver at the BOF. The references to spearmint was, I'm told somewhat inadvertent on the part of the authors. A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Managing Client Voice Peering Provisioning Author(s) : D. Schwartz, et al. Filename : draft-schwartz-speermint-provisioning-problem-00.txt Pages : 8 Date : 2007-11-13 This document describes the type of data provisioned among Voice Service Providers. This is in support of the service provider peering as defined by the Speermint WG. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-schwartz-speermint-provisioning-pr oblem-00.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-schwartz-speermint-provisioning-problem-00.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-schwartz-speermint-provisioning-problem-00.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. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpuIn-0006Xh-2A; Wed, 07 Nov 2007 18:27:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpuIl-0006SB-5y for peppermint@ietf.org; Wed, 07 Nov 2007 18:27:15 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpuIh-0006zx-Cb for peppermint@ietf.org; Wed, 07 Nov 2007 18:27:15 -0500 Received: from rshockeyPC (62-50-220-133.client.stsn.net [62.50.220.133]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA7NQhhZ013726 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 7 Nov 2007 15:26:46 -0800 From: "Richard Shockey" To: Date: Wed, 7 Nov 2007 18:26:36 -0500 Message-ID: <116901c82195$a5d89f20$f189dd60$@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: AcghlaNjkaX+Zw8iRkKSC4755k/p9Q== Content-Language: en-us X-Spam-Score: 0.8 (/) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c Subject: [PEPPERMINT] VERSION 00 PEPPERMINT BOF AGENDA X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org COMMENTS PLEASE ESPECIALLY ON THE PROPOSED CHARTER If anyone wants to present anyting let me or Tom know. ********************************** IETF 70 PEPPERMINT BOF Agenda PEPPERMINT Session 1 (1 hour) Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2 Chair(s): Richard Shockey Tom Creighton RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com Agenda Bashing. Presentation of the proposed charter. 10 min 1. Review of existing provisioning protocols in IETF especially RFC 4114 (S.Hollenbeck) 2. Review of peppermint problem statement ( David Schwartz ) ID forthcoming. General Discussion The Usual Questions. A. Is this a problem that the IETF needs to work on? B. Are people willing to work on this problem? ************ 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 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. 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 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iprij-0001fi-LQ; Wed, 07 Nov 2007 15:41:53 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iprii-0001dt-1m for peppermint@ietf.org; Wed, 07 Nov 2007 15:41:52 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iprih-0000Ec-HW for peppermint@ietf.org; Wed, 07 Nov 2007 15:41:51 -0500 Received: from rshockeyPC (62-50-220-133.client.stsn.net [62.50.220.133]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA7KfLDJ001665 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 7 Nov 2007 12:41:24 -0800 From: "Richard Shockey" To: "'Hollenbeck, Scott'" , References: <000601c820b6$5b55de70$12019b50$@us> <046F43A8D79C794FA4733814869CDF07020FD190@dul1wnexmb01.vcorp.ad.vrsn.com> In-Reply-To: <046F43A8D79C794FA4733814869CDF07020FD190@dul1wnexmb01.vcorp.ad.vrsn.com> Subject: RE: [PEPPERMINT] Please submit requests for slots for the BOF.. Date: Wed, 7 Nov 2007 15:41:14 -0500 Message-ID: <0ee701c8217e$8ea62c30$abf28490$@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: AcggY36Dsqvhl/UyQlW8CEE1yv5ThgBDWfLQAANm7lA= Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: "'Creighton, Tom'" X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org Confirmed ... tks. > -----Original Message----- > From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com] > Sent: Wednesday, November 07, 2007 2:09 PM > To: peppermint@ietf.org; Richard Shockey > Cc: Creighton, Tom > Subject: RE: [PEPPERMINT] Please submit requests for slots for the > BOF.. > > > -----Original Message----- > > From: Richard Shockey [mailto:richard@shockey.us] > > Sent: Tuesday, November 06, 2007 3:48 PM > > To: peppermint@ietf.org > > Cc: 'Creighton, Tom' > > Subject: [PEPPERMINT] Please submit requests for slots for the BOF.. > > > > As soon a practically possible. > > Rich, I'd like to have a few minutes to talk about EPP and if/how it > might be useful in this context. > > -Scott- _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpqHo-00009U-1s; Wed, 07 Nov 2007 14:10:00 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpqHm-00005A-5Z for peppermint@ietf.org; Wed, 07 Nov 2007 14:09:58 -0500 Received: from peregrine.verisign.com ([216.168.239.74]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpqHl-0004bY-Sx for peppermint@ietf.org; Wed, 07 Nov 2007 14:09:58 -0500 Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id lA7J3BIa021958; Wed, 7 Nov 2007 14:03:11 -0500 Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Nov 2007 14:09:54 -0500 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: [PEPPERMINT] Please submit requests for slots for the BOF.. Date: Wed, 7 Nov 2007 14:09:13 -0500 Message-ID: <046F43A8D79C794FA4733814869CDF07020FD190@dul1wnexmb01.vcorp.ad.vrsn.com> In-Reply-To: <000601c820b6$5b55de70$12019b50$@us> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PEPPERMINT] Please submit requests for slots for the BOF.. Thread-Index: AcggY36Dsqvhl/UyQlW8CEE1yv5ThgBDWfLQ From: "Hollenbeck, Scott" To: , "Richard Shockey" X-OriginalArrivalTime: 07 Nov 2007 19:09:54.0294 (UTC) FILETIME=[C78C4960:01C82171] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: "Creighton, Tom" X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us]=20 > Sent: Tuesday, November 06, 2007 3:48 PM > To: peppermint@ietf.org > Cc: 'Creighton, Tom' > Subject: [PEPPERMINT] Please submit requests for slots for the BOF.. >=20 > As soon a practically possible. Rich, I'd like to have a few minutes to talk about EPP and if/how it might be useful in this context. -Scott- _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpVLs-0007gJ-Eh; Tue, 06 Nov 2007 15:48:48 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpVLr-0007do-R1 for peppermint@ietf.org; Tue, 06 Nov 2007 15:48:47 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpVLo-0007KI-Bs for peppermint@ietf.org; Tue, 06 Nov 2007 15:48:47 -0500 Received: from rshockeyPC (62-50-219-48.client.stsn.net [62.50.219.48]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA6KlvDt009614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 6 Nov 2007 12:48:13 -0800 From: "Richard Shockey" To: Date: Tue, 6 Nov 2007 15:47:55 -0500 Message-ID: <000601c820b6$5b55de70$12019b50$@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: AcggY36Dsqvhl/UyQlW8CEE1yv5Thg== Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: "'Creighton, Tom'" Subject: [PEPPERMINT] Please submit requests for slots for the BOF.. X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org As soon a practically possible. 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 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Io0MA-0007M8-1m; Fri, 02 Nov 2007 13:30:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Io0M8-0007Ls-VW; Fri, 02 Nov 2007 13:30:52 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Io0M7-0006Vf-MB; Fri, 02 Nov 2007 13:30:52 -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 lA2HUQrH023882 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Nov 2007 09:30:27 -0800 From: "Richard Shockey" To: , Date: Fri, 2 Nov 2007 13:30:36 -0400 Message-ID: <0ab801c81d76$1512f710$3f38e530$@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: AcgdBvbwvFuQjleESTaRQ7z3MMqf+wAbxbwA Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: Subject: [PEPPERMINT] FW: Internet-Drafts Submission Cutoff Dates for the 70th IETF Meeting in Vancouver, BC, Canada X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-bounces@ietf.org -----Original Message----- From: ietf-secretariat@ietf.org [mailto:ietf-secretariat@ietf.org]=20 Sent: Friday, November 02, 2007 12:00 AM To: ietf-announce@ietf.org Subject: Internet-Drafts Submission Cutoff Dates for the 70th IETF = Meeting in Vancouver, BC, Canada=20 There are two (2) Internet-Draft cutoff dates for the 70th=20 IETF Meeting in Vancouver, BC, Canada: November 12th: Cutoff Date for Initial (i.e., version -00)=20 Internet-Draft Submissions=20 All initial Internet-Drafts (version -00) must be submitted by Monday,=20 November 12th at 9:00 AM ET (14:00 UTC/GMT). As always, all initial = submissions with a=20 filename beginning with "draft-ietf" must be approved by the=20 appropriate WG Chair before they can be processed or announced. The=20 Secretariat would appreciate receiving WG Chair approval by Monday,=20 November 5th at 9:00 AM ET (14:00 UTC/GMT). November (14:00 UTC/GMT): Cutoff Date for Revised (i.e., version -01 = and higher)=20 Internet-Draft Submissions=20 All revised Internet-Drafts (version -01 and higher) must be submitted=20 by Monday, November 19th at 9:00 AM ET (14:00 UTC/GMT). Initial and revised Internet-Drafts received after their respective=20 cutoff dates will not be made available in the Internet-Drafts=20 directory or announced until on or after Monday, December 3rd at 9:00=20 AM ET (14:00 UTC/GMT), when Internet-Draft posting resumes. Please do = not wait until=20 the last minute to submit. The Secretariat encourages you to submit your Internet-Drafts via the=20 Internet-Draft Submission Tool (IDST) = https://datatracker.ietf.org/idst/upload.cgi.=20 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=20 are submitting a version -00 WG draft that replaces non-WG draft, then=20 you must submit it manually as the current IDST cannot handle=20 replacements. Please be sure to state that one draft replaces another=20 in the cover note that accompanies your submission. Also, please note=20 that the IDST will not accept drafts submitted after their respective=20 cutoff dates. Thank you for your understanding and cooperation. If you have any=20 questions or concerns, then please send a message to=20 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://www.ietf.org/meetings/cutoff_dates_70.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InZtT-0001W0-O2; Thu, 01 Nov 2007 09:15:31 -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 X-Mailman-Approved-At: Thu, 01 Nov 2007 09:15:30 -0400 Cc: Subject: [PEPPERMINT] FCC VoIP Order/NPRM implementation X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: peppermint-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 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint