[PEPPERMINT] DRINKS PROPOSED Charter ..comments please.

"Richard Shockey" <richard@shockey.us> Wed, 16 April 2008 17:19 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4091E3A6F95; Wed, 16 Apr 2008 10:19:40 -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 08E863A6AAE for <peppermint@core3.amsl.com>; Wed, 16 Apr 2008 10:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.574
X-Spam-Level:
X-Spam-Status: No, score=-3.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 bJX5ucggexn8 for <peppermint@core3.amsl.com>; Wed, 16 Apr 2008 10:19:38 -0700 (PDT)
Received: from mail.songbird.com (mail.songbird.com [208.184.79.10]) by core3.amsl.com (Postfix) with ESMTP id 216A83A6939 for <peppermint@ietf.org>; Wed, 16 Apr 2008 10:19:38 -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 m3GHJ3E1011498 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <peppermint@ietf.org>; Wed, 16 Apr 2008 10:19:04 -0700
From: Richard Shockey <richard@shockey.us>
To: peppermint@ietf.org
Date: Wed, 16 Apr 2008 13:19:50 -0400
Message-ID: <125b01c89fe6$14f823c0$3ee86b40$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acif5hOzmNYlp/X0SiGV1jnC6pF21g==
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
Subject: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
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 think I have incorporated most of the comments received to date based on
Darlys first draft.

More are certainly needed.

Specifically thanks to Ken Cartwright who made excellent grammatical
suggestions.

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

DRINKS Proposed Charter 


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 SIP-enabled Multimedia
administrative domains among SIP Service Providers (SSPs. 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.  

More specifically, SPEERMINT 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), and the secure manners in which SED and the SIP session data is
exchanged between the peering functions.

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.

Typical data includes the mapping of phone numbers to URIs, policies
surrounding admission to various points of network interconnection, and
various other types of interconnect data.  In addition, there is a specific
need for the exchange of such data between the Registry and various types of
PSTN network databases.

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.
Sept 08 

Provisioning of Session Establishment Data (SED) registries.
Nov 08

Provisioning of Localized Session Establishment Data (SED) 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>



_______________________________________________
PEPPERMINT mailing list
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint