[PEPPERMINT] FIRST cut at DRINKS agenda.
"Richard Shockey" <richard@shockey.us> Thu, 03 July 2008 17:22 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 91C9C3A693C; Thu, 3 Jul 2008 10:22:23 -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 446913A693C; Thu, 3 Jul 2008 10:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ps+wlDbCySZL; Thu, 3 Jul 2008 10:22:21 -0700 (PDT)
Received: from mail.songbird.com (unknown [IPv6:2001:470:1:76:2c0:9fff:fe3e:4009]) by core3.amsl.com (Postfix) with ESMTP id 93A403A68D3; Thu, 3 Jul 2008 10:22:20 -0700 (PDT)
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 m63HJ2ro013703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jul 2008 10:19:18 -0700
From: Richard Shockey <richard@shockey.us>
To: drinks@ietf.org
Date: Thu, 03 Jul 2008 13:19:41 -0400
Message-ID: <00bc01c8dd31$0debeac0$29c3c040$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcjdMPrq3K8K/8RlQkCUP4shfApiRA==
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
Cc: peppermint@ietf.org
Subject: [PEPPERMINT] FIRST cut at DRINKS agenda.
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
IETF 72 DRINKS Agenda Data for Reachability of Inter/tra-NetworK SIP (drinks) Chair(s): Richard Shockey richard.shockey@neustar.biz Alexander Mayrhofer <alexander.mayrhofer@nic.at> WG Secretary TBD .. RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com RAI Area Advisor: Jon Peterson jon.peterson@neustar.biz Agenda Bashing. 1. Discussion of Consolidated Requirements Documents. 2. Revised ESPP documents 3. Contribution from Debbie Guyton Telcordia .. ******************************************** Approved DRINKS WG Charter : The IETF has been working on various aspects of 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. While the SPEERMINT working group has been chartered to develop requirements and best current practices among real-time application SSPs and to describe how such services may best interconnect across administrative boundaries. Specifically, DRINKS will provide details of how Session Establishment Data (SED) is collected, 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. 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. In addition DRINKS will ensure that the SED and the SIP session data 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. GOALS AND MILESTONES Nov 08 - WGLC for Requirements for Session Establishment Data (SED) data exchanges (Proposed Standard). Dec 08 - IESG Submission for Requirements for Session Establishment Data (SED) data exchanges. Jan 09 - WGLC for Exchanging of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners (Proposed standard). Feb 09 IESG Submission for Exchanging of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners. Mar 09 - WGLC for Exchange of Session Establishment Data (SED) from registries to Location Routing Function databases (Proposed Status). Apr 09 - IESG Submission for Exchange of Session Establishment Data (SED) from registries to Location Routing Function databases. 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] FIRST cut at DRINKS agenda. Richard Shockey