Re: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.

> -----Original Message-----
> From: peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org] On
> ************************
> DRINKS Proposed Charter
> Data for Reachability of Inter/tra-NetworK SIP
> Current Status: Proposed Working Group
>
> Mailing Lists:
> peppermint@ietf.org

We'll need a new mailing list name (or alias) for drinks@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

Typo: "(SSPs" should be "(SSPs)".

> 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.:

Remove last period, or last colon.

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

Is there only one Registry? ;)  Change "the Registry" to "a Registry".

> 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

I think you mean "Data model of SED Registries"? (I'm not really quite sure what this milestone is?)

> Provisioning of Localized Session Establishment Data (SED) caches.

I think you mean "Exchanging Session Establishment Data (SED) between Lookup Function or Location Routing Function Databases."

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