PEPPERMINT BoF IETF 71 Agenda ====== accepted Charter review ============== David: "may" use 4114 ... we "may" use a lot of things. Ken ??: agree we "may" use a lot of things - slippery slope. shockey proposes to remove reference to 4114 David Schwartz's concerns about "within" / "among" domains... currently says "across". David suggests to use "within" AND "among". Hadriel suggest "within" and "between". ??: Maybe have presentations first, and then look into the charter? Shockey: 2nd BoF already - identified that there is a problem here. Jon: concerned about the "among / between" and the paragraph below that as well.. "various" is not very precise.. doubt this is the right place to do this charter texting. don't think we can get that agreed here. David Schwartz speaking ============== motivation: many peering registries formed, etc.. 3 relationships. between registries, pushing up and pushing down. registry data prefix sub/super compatibility with ENUM resolution data - ownership information carrier of record, etc. bulk considerations logical operations on registry data other attributes: validity fee category... lots of data associated with a number - not neccessarily everthing in a registry. Adam Uzelac: Are there "views", depending on "who is asking"? Shockey: Would be attributes reflecting policy.. Hadriel: covers LUF _and_ LRF? David: _very_ good question - definitely a different problem set. Jon: Break all this into achievable chunks. Jean-Francois - ESPP ==================== effort on ENUM-SIP server provisioning specification - intended as input into the BoF only. Problem: how can back office services provision data out to addressing servers. used the netconf structure to identify high level requirements martin dolly: please expand beyond north america. Sean Kent ========= talking about design principles of ESPP. real time vs. bulk (file) based approach for larger changes. most people in the room understand the problem most of them thinks the IETF should work on this problem. Cullen: Try to get this down to as small as possible. Any ideas on how that could be defined? David: Maybe start with "northbound" provisioning first, and leave out registry-registry-Peering.. Jean-Francois: High level of charter is good - hope to not go into the same discussions as in SPEERMINT Daryl: agree with Jon - use the terminology from SPEERMINT - please! CHAIR additional notes: ======================= A. Confine first pass at Goals and Milestones to Domain to Registry and Registry to Local Cache B. Eliminate references to PBX interface ..at this time. Could be scoped in the future. C. Registry to Registry interface also in the future. #################################### Official Peppermint agenda Below.. IETF 71 PEPPERMINT BOF Agenda Provisioning Extensions in Peering Registries for Multimedia INTerconnection 1510-1610 Afternoon Session II Franklin 11/12 INT dna Detecting Network Attachment WG Franklin 5 OPS grow Global Routing Operations WG Franklin 3/4 RAI peppermint Provisioning Extensions in Peering Registries for Multimedia INTerconnection BOF Franklin 13 RTG isis IS-IS for IP Internets WG Salon I SEC ltans Long-Term Archive and Notary Services WG Franklin 5 SEC msec Multicast Security WG 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 ( see below ) 1. Title : Consolidated Provisioning Problem Statement Author(s) : D. Schwartz, R. Mahy, A. Duric, E. Lewis Filename : draft-schwartz-peppermint-consolidated-provisioning-problem-statement-00.txt Pages : 12 Date : 2008-2-11 This document describes the type of data provisioned among Voice Service Providers and underscores the need for clearly defined structures and interfaces to facilitate this provisioning. This work 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-peppermint-consolidated-p rovisioning-problem-statement-00.txt 2. A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Provisioning Protocol Requirements for ENUM-SIP Addressing Servers Author(s) : T. Creighton, J. Mule Filename : draft-mule-peppermint-espp-requirements-00.txt Pages : 16 Date : 2008-02-18 This document presents use cases and protocol requirements for provisioning ENUM-SIP addressing servers. The provisioned data is used by an addressing server to return part of the session establishment data to SIP entities so that they can route SIP sessions to the target destinations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mule-peppermint-espp-requirements-00.txt 3. Title : A Provisioning Protocol for ENUM-SIP Addressing Servers Author(s) : K. Cartwright, et al. Filename : draft-mule-peppermint-espp-protocol-01.txt Pages : 117 Date : 2008-02-25 This document defines a provisioning protocol for ENUM-SIP addressing servers. This protocol has been recently published as part of CableLabs(r) PacketCable(tm) specifications. It allows SIP service providers to provision and manage session establishment data used by SIP network elements to route SIP sessions to the target destinations which may be served by the SIP service provider's own internal network or by a session peering partner. The data provisioned into an ENUM-SIP addressing server is queried by SIP entities using ENUM or SIP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mule-peppermint-espp-protocol-01.t xt 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 Proposed Charter 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 Chairs: TBD PROPOSED CHARTER FOR PEPPERMINT The IETF has been working on various aspects of session-based Multimedia Interconnection among administrative domains. In addition, the IETF has done significant work on data exchanges among various network elements. 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 administrative boundaries. The PEPPERMINT work group is chartered to define what data needs to be exchanged among Multimedia administrative domains, and how that data should be structured provisioned and propagated. These protocols would be outside the normal scope of establishing various forms of a SIP session. These administrative domains are of any practical size and could be service providers or enterprise SIP proxy’s, such as PBX’s. Data exchanges to facilitate session-based Multimedia Interconnection are typically between various Client User Agents and Registries or bilateral or multilateral Registry to Registry. Data exchanges could include bulk data as well as real time updates. Typical data include mappings of phone numbers to URIs, policies surrounding admission to various points of network interconnection and various types of trunk data. In addition, there is a specific need for redistribution of such Registry data to various types of network databases. The working group will draw upon expert advice and ongoing consultation from the ENUM, SPEERMINT and PROVREG working groups. The working group may also reuse elements of RFC 4114, if possible. The final work product(s) from this working group will utilize and be based on XML documents and XML document exchanges. PROPOSED GOALS AND MILESTONES Requirements for Interconnection data exchanges. Sept 08 Provisioning of Interconnection data registries. Nov 08 Provisioning of Interconnection data caches. Feb 09