[PEPPERMINT] DRINKS Agenda planning.

["Richard Shockey" <[e-mail]>]

There have been no comments that I can see on the IETF Discuss list so I'm
presuming we are good to go for Dublin.

At this time we have a 1 hour slot blocked so I want to get a sense of what
kind of document load we might be looking at.

If you are planning or presenting documents etc let me know.

The sooner we see documents the better.

Obviously the first task will be to organize the Requirements Document etc. 


>  -----Original Message-----
>  From: [e-mail] [mailto:[e-mail]]
>  On Behalf Of IESG Secretary
>  Sent: Thursday, May 15, 2008 4:26 PM
>  To: IETF Announcement list
>  Cc: [e-mail]
>  Subject: [PEPPERMINT] WG Review: Data for Reachability of Inter/tra-
>  NetworK SIP (drinks)
>  
>  A new IETF working group has been proposed in the Real-time
>  Applications
>  and Infrastructure Area.  The IESG has not made any determination as
>  yet.
>  The following draft charter was submitted, and is provided for
>  informational purposes only.  Please send your comments to the IESG
>  mailing list ([e-mail]) by May 22, 2008.
>  
>  Data for Reachability of Inter/tra-NetworK SIP (drinks)
>  -------------------------------------------
>  Last modified: 2008-05-14
>  
>  Current Status: Proposed Working Group
>  
>  Chairs: TBD
>  
>  Area Directorate: Real Time Applications (RAI)
>  
>  RAI Director(s):
>  
>  Jon Peterson [e-mail]
>  Cullen Jennings [e-mail]
>  
>  Mailing Lists: [e-mail]
>  General information about the mailing list is at:
>  https://www1.ietf.org/mailman/listinfo/peppermint
>  
>  Description of working group:
>  
>  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.
>  
>  _______________________________________________
>  PEPPERMINT mailing list
>  [e-mail]
>  https://www.ietf.org/mailman/listinfo/peppermint

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