Re: [PEPPERMINT] DRINKS Charter v 02

["PFAUTZ, PENN L, ATTCORP" <[e-mail]>]

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
[phone]

-----Original Message-----
From: [e-mail] [mailto:[e-mail]]
On Behalf Of Richard Shockey
Sent: Sunday, May 11, 2008 6:02 PM
To: [e-mail]
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: 

[e-mail]


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 [e-mail]
Cullen Jennings [e-mail]

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



_______________________________________________
PEPPERMINT mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/peppermint
_______________________________________________
PEPPERMINT mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/peppermint