Re: [PEPPERMINT] WG Action: Data for Reachability of Inter/tra-NetworK SIP (drinks)

["Richard Shockey" <richard at shockey.us>]

You have all seen this by now .. we have a one hour slot ready so that should show up on the draft agenda shortly.

I will arrange this week for the change of mail address from peppermint at ietf.org to drinks at ietf.org The Secretariat should be able to enroll the current list pretty automatically.

Needless to say we need to begin Agenda discussions, I have one request so far.

>  -----Original Message-----
>  From: The IESG [mailto:iesg at ietf.org]
>  Sent: Friday, June 13, 2008 5:00 PM
>  To: ietf-announce at ietf.org
>  Cc: alexander.mayrhofer at enum.at; rich.shockey at neustar.biz;
>  peppermint at ietf.org
>  Subject: WG Action: Data for Reachability of Inter/tra-NetworK SIP
>  (drinks)
>  
>  A new IETF working group has been formed in the Real-Time Applications
>  and
>  Infrastructure Area.  For additional information, please contact the
>  Area
>  Directors or the WG Chairs.
>  
>  Data for Reachability of Inter/tra-NetworK SIP (drinks)
>  ---------------------------------------------
>  Last Modified: 13 June 2008
>  
>  Current Status: Active Working Group
>  
>  Chairs:
>  
>  Richard Shockey (rich.shockey at neustar.biz)
>  Alexander Mayrhofer (alexander.mayrhofer at enum.at)
>  
>  Area Directorate: Real Time Applications (RAI)
>  
>  RAI Director(s):
>  
>  Jon Peterson (jon.peterson at neustar.biz)
>  Cullen Jennings (fluffy at cisco.com)
>  
>  RAI Area Advisor:
>  
>  Jon Peterson (jon.peterson at neustar.biz)
>  
>  Mailing Lists: peppermint at ietf.org
>  General information about the mailing list is at:
>  https://www1.ietf.org/mailman/listinfo/peppermint
>  
>  Working Group Description:
>  
>  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 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.
>  
>  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.
>  
>  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 through the use of an
>  external
>  registry to aggregate data from multiple administrative domains or
>  multiple data providers into a single view.
>  
>  The DRINKS WG 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. In addition DRINKS
>  will
>  insure that the SED and the SIP session data is 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
>  
>  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
>  
>  Requirements for Session Establishment Data (SED) data exchanges. --
>  Sept 08
>  
>  Exchanging of Session Establishment Data (SED) from data providers to
>  registries or between bi/multi-lateral partners. -- Nov 08
>  
>  Exchange of Session Establishment Data (SED) from registries to
>  Location
>  Routing Function databases. --- Feb 09

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