* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Drinks Status Pages

Data for Reachability of Inter/tra-NetworK SIP (Concluded WG)
Art Area: Francesca Palombini, Murray Kucherawy | 2008-Jun-13 — 2016-Apr-18 
Chairs
 


IETF-72 drinks agenda

Slides

These are also available from the materials page:
Introduction
Consolidated Provisioning Problem Statement (David Schwartz)
Key Data for a Registry Provisioning Interface (Deborah Guyton)
Data Model and Protocol Requirements (Jean-François Mulé)
Location Routing Function Requirements (Hadriel Kaplan)

Agenda

          IETF 72 DRINKS Agenda
          
          Data for Reachability of Inter/tra-NetworK SIP (drinks)
          
          
          Chair(s):
          
          Richard Shockey <richard.shockey@neustar.biz>
          
          Alexander Mayrhofer <alexander.mayrhofer@nic.at>
          
          WG Secretary
          
          TBD .
          
          RAI Director(s):
          
          Jon Peterson jon.peterson@neustar.biz
          Cullen Jennings fluffy@cisco.com
          
          
          RAI Area Advisor:
          Jon Peterson jon.peterson@neustar.biz
          
          
          Agenda Bashing.
          
          
          1. Discussion of Requirements Documents ( 4 drafts ) 25 Min.
          
          
                  Title           : Consolidated Provisioning Problem Statement
                  Author(s)       : D. Schwartz, et al.
                  Filename        : draft-ietf-drinks-cons-rqts-00.txt
                  Pages           : 12
                  Date            : 2008-07-07
          
          This document describes the type of data provisioned among Voice Service Providers and underscores the need for clearly defined structures and interfaces to facilitate this provisioning.  This work is in support of the service provider peering as defined by the SPEERMINT WG.
          
          A URL for this Internet-Draft is:
          http://www.ietf.org/internet-drafts/draft-ietf-drinks-cons-rqts-00.txt
          
          
          
          2. Title           : Provisioning Protocol Requirements for ENUM-SIP Addressing Servers
                  Author(s)       : T. Creighton, J. Mule
                  Filename        : draft-mule-peppermint-espp-requirements-01.txt
                  Pages           : 18
                  Date            : 2008-07-14
          
          This document presents use cases and protocol requirements for provisioning ENUM-SIP addressing servers.  The provisioned data is used by the addressing server to return session establishment data for SIP entities to route SIP requests to the target destinations.
          An ENUM-SIP addressing server acts as a Lookup Function in session peering to determine the target domain of a given SIP request.  It may also act as a Location Routing Function to develop the location of the SIP signaling entity in the target domain.
          
          A URL for this Internet-Draft is:
          http://www.ietf.org/internet-drafts/draft-mule-peppermint-espp-requirements-01.txt
          
          
          
          3.
          
          Title           : Key Data for a Registry Provisioning Interface draft-guyton-drinks-registry-data-00.txt
                  Author(s)       : D. Guyton
                  Filename        : draft-guyton-drinks-registry-data-00.txt
                  Pages           : 8
                  Date            : 2008-07-07
          
          This document defines data that should be included in a provisioning interface for a Registry. The provisioning interface may be used in
          (near) real time, or periodically, from a service provider's service provisioning system to establish and administer telephone number (TN) and associated routing information in the Registry after necessary validations. Based on 1) effective date/time specified for the data and 2) validation of the TN assignee, these data will be used to define selective routing views for various recipient service providers which would be reflected in ENUM-SIP address servers. In addition, the concept of multiple TNs sharing a common routing pattern simplifies the definition and administration of routing data.
          
          
          A URL for this Internet-Draft is:
          http://www.ietf.org/internet-drafts/draft-guyton-drinks-registry-data-00.txt
          
          
          4.
          
          Title           : Location Routing Function Requirements
                  Author(s)       : H. Kaplan
                  Filename        : draft-kaplan-drinks-lrf-requirements-00.txt
                  Pages           : 7
                  Date            : 2008-07-04
          
           This document describes the requirements for a Location Routing
           Function Protocol, for inter and intra-domain SIP session routing.
          
           A URL for this Internet-Draft is:
           http://www.ietf.org/internet-drafts/draft-kaplan-drinks-lrf-requiremen
           ts-00.txt
          
          
          
          General discussion of Consolidation of Requirments Documents in order to fulfill Goals and Milestones item #1.
          
          
          5. Title           : A Provisioning Protocol for ENUM-SIP Addressing Servers  (10)
                  Author(s)       : K. Cartwright, et al.
                  Filename        : draft-mule-peppermint-espp-protocol-02.txt
                  Pages           : 121
                  Date            : 2008-07-14
          
          This document defines a provisioning protocol for ENUM-SIP addressing servers.
          An ENUM-SIP addressing server is a host that acts as Lookup Function in session peering to determine the target domain of a given SIP request and it may also act as a Location Routing Function to develop the location of the SIP signaling entity in that target domain.
          This protocol allows SIP service providers to provision and manage session establishment data used by SIP network elements to route SIP sessions to the target destinations which may be served by the SIP service provider's own internal network or by a session peering partner.  The data provisioned into an ENUM-SIP addressing server is queried by SIP entities using ENUM or SIP.
          
          This version of the protocol integrates comments received on the IETF peppermint and drinks mailing lists before July 2008.  This document is an Internet-Draft and the protocol it describes is subject to technical changes that may make this version incompatible with future versions defined in Internet-Drafts.  It is expected that the authors will continue to update this protocol based on the drinks working group requirements on the session establishment data.
          
          A URL for this Internet-Draft is:
          http://www.ietf.org/internet-drafts/draft-mule-peppermint-espp-protocol-02.txt
          
          
          General Discussion ...
          
          
          ********************************************
          
          Approved DRINKS WG Charter :
          
          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.
          
          
          
          



Generated from PyHt script /wg/drinks/agenda.pyht Latest update: 24 Oct 2012 16:51 GMT -