Re: [PEPPERMINT] DRINKS Charter v 02
"PFAUTZ, PENN L, ATTCORP" <ppfautz@att.com> Mon, 12 May 2008 14:08 UTC
Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECD413A6B7E; Mon, 12 May 2008 07:08:04 -0700 (PDT)
X-Original-To: peppermint@core3.amsl.com
Delivered-To: peppermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EE7C3A6979 for <peppermint@core3.amsl.com>; Mon, 12 May 2008 07:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ylGBbZ4q8pma for <peppermint@core3.amsl.com>; Mon, 12 May 2008 07:08:01 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.245.115]) by core3.amsl.com (Postfix) with ESMTP id 61C7B3A68C3 for <peppermint@ietf.org>; Mon, 12 May 2008 07:08:01 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ppfautz@att.com
X-Msg-Ref: server-15.tower-121.messagelabs.com!1210601251!15003923!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 19094 invoked from network); 12 May 2008 14:07:31 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-15.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 12 May 2008 14:07:31 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m4CE79oM031792; Mon, 12 May 2008 10:07:10 -0400
Received: from ACCLUST02EVS1.ugd.att.com (acst03.ugd.att.com [135.37.16.8]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m4CE73Kr031700; Mon, 12 May 2008 10:07:04 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 May 2008 10:07:02 -0400
Message-ID: <34DA635B184A644DA4588E260EC0A25A12CCE87D@ACCLUST02EVS1.ugd.att.com>
In-Reply-To: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PEPPERMINT] DRINKS Charter v 02
Thread-Index: Acizsp2LQlJn2qAERK+lvfgFG3QLAgAgnREw
References: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
From: "PFAUTZ, PENN L, ATTCORP" <ppfautz@att.com>
To: Richard Shockey <richard@shockey.us>, peppermint@ietf.org
Subject: Re: [PEPPERMINT] DRINKS Charter v 02
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org
I have no great substantive issues but the current text seems a little choppy. Giving in to my inner editor I'd suggest the following Penn Pfautz AT&T National Access Management +1-732-420-4962 -----Original Message----- From: peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org] On Behalf Of Richard Shockey Sent: Sunday, May 11, 2008 6:02 PM To: peppermint@ietf.org Subject: [PEPPERMINT] DRINKS Charter v 02 Well ..moving along here .. the IESG has made initial pass on DRINKS charter review and there are a few minor editorial changes that were suggested. First issues surrounding milestones which are minor and second further discussion of tightening and defining initial scope. I want to make it clear again that any discussion of the need to limit scope is fruitless. The only relevant question is how. I've suggested an additional sentence that defines initial scope of SED data shall be typically that involved in ENUM databases with limited exceptions and if there is WG desire to look at data types outside the scope of ENUM databases and registries that will trigger a recharter. ****************** Proposed Charter DRINKS Data for Reachability of Inter/tra-NetworK SIP Current Status: Proposed Working Group Mailing Lists: peppermint@ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/peppermint Area Directorate: Real Time Applications (RAI) RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com Chairs: TBD PROPOSED CHARTER FOR PEPPERMINT The IETF has been working on various aspects of communication between SIP-enabled Multimedia administrative domains among SIP Service Providers (SSP's). SSP's are entities that provide session services utilizing SIP signaling to their customers. In addition, the IETF has done significant work on data exchanges among various network elements. The ENUM and SPEERMINT working groups provide the underlying context for much of the intended work that the DRINKS working group will undertake. The ENUM working group is specifically chartered to develop protocols that involve the translation of E.164 numbers to URIs. The SPEERMINT working group has been chartered to develop requirements and best current practices among real-time application SSPs to describe how multimedia services may best interconnect across administrative boundaries. Specifically, DRINKS will provide details of how Session Establishment Data (SED) is distributed, what comprises SED, how SED should be used to properly identify an optimal path to a destination SIP user agent (UA),either internally or externally to the SSP. RS: For the initial iteration of this charter, the SED data is assumed to be fields that might be provisioned for ENUM, with limited exceptions. If the working group would like to work on data types unrelated to ENUM registries and databases, the WG will recharter. RS: In addition DRINKS will ensure that the SED and the SIP session data are securely exchanged between the peering functions. Typical SED data might include: + Routes - Destination SIP/SIPS/TEL URI Egress and Ingress Routes - Relevant route names, identifiers, and services - Attributes affecting route selection - PSTN database information + Targets - Individual, ranges, or groups of user-agent identifiers - Target aggregation entities (e.g. service areas) and target-to-aggregate associations + Treatment Profiles - Priority - Location Potential SED Data types not in scope will be session rating or other billing or pricing information between SSP's. It is also recognized that peering relationships become more complex as multiple peers are added to a common relationship; these complex aspects and requirements are defined within the contexts of a peering Federation. The DRINKS working group is chartered with a scope that is orthogonal to SPEERMINT and ENUM. The protocol work of DRINKS will be designed to build from the work of SPEERMINT and ENUM to identify and define the data structures and data exchange protocol(s) among SIP based Multimedia administrative domains. These administrative domains may be of any practical size and could be any type of SSP, such as recognized telephony carriers, enterprises, end-user groups, or Federations. Data exchanges among these administrative domains may be bi-lateral or multi-lateral in nature, and could include bulk updates and/or more granular real-time updates. Administrative domains may exchange data directly between each other or might use an external registry to aggregate data from multiple administrative domains or multiple data providers into a single view. The working group will draw upon expert advice and on-going consultation from the ENUM and SPEERMINT working groups, and also the XML Directorate. The working group will consider the reuse of elements of RFC 4114. 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 Session Establishment Data (SED) data exchanges. Status Proposed Standard. WGLC - Nov 08 Exchanging of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners. Intended Status - Proposed standard. WGLC - Jan 09 Exchange of Session Establishment Data (SED) from registries to Location Routing Function databases. Intended Status-Proposed Status. WGLC - Mar 09 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> _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint
- Re: [PEPPERMINT] DRINKS Charter v 02 Jean-Francois Mule
- Re: [PEPPERMINT] DRINKS Charter v 02 PFAUTZ, PENN L, ATTCORP
- [PEPPERMINT] DRINKS Charter v 02 Richard Shockey