
From: "Richard Shockey" <richard@shockey.us>
To: <peppermint@ietf.org>
References: <20080515202605.F12DD3A6895@core3.amsl.com>
In-Reply-To: <20080515202605.F12DD3A6895@core3.amsl.com>
Date: Sat, 24 May 2008 14:15:22 -0400
Message-ID: <016f01c8bdca$28002240$780066c0$@us>
MIME-Version: 1.0
Thread-Index: Aci2yl/7LoTKjERYRcK3tdL4wFxa+AG/xnKQ
Content-Language: en-us
Subject: [PEPPERMINT] DRINKS Agenda planning.
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org

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: peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org]
>  On Behalf Of IESG Secretary
>  Sent: Thursday, May 15, 2008 4:26 PM
>  To: IETF Announcement list
>  Cc: peppermint@ietf.org
>  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 (iesg@ietf.org) 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 jon.peterson@neustar.biz
>  Cullen Jennings fluffy@cisco.com
>  
>  Mailing Lists: peppermint@ietf.org
>  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
>  PEPPERMINT@ietf.org
>  https://www.ietf.org/mailman/listinfo/peppermint

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


Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2986F3A6872; Thu, 15 May 2008 13:30:33 -0700 (PDT)
X-Original-To: peppermint@ietf.org
Delivered-To: peppermint@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id F12DD3A6895; Thu, 15 May 2008 13:26:05 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Mime-Version: 1.0
Message-Id: <20080515202605.F12DD3A6895@core3.amsl.com>
Date: Thu, 15 May 2008 13:26:05 -0700 (PDT)
X-Mailman-Approved-At: Thu, 15 May 2008 13:30:32 -0700
Cc: peppermint@ietf.org
Subject: [PEPPERMINT] WG Review: Data for Reachability of Inter/tra-NetworK SIP (drinks)
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org

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 (iesg@ietf.org) 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 jon.peterson@neustar.biz
Cullen Jennings fluffy@cisco.com

Mailing Lists: peppermint@ietf.org
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
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint


Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AF393A6954; Tue, 13 May 2008 15:04:57 -0700 (PDT)
X-Original-To: peppermint@core3.amsl.com
Delivered-To: peppermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A974D3A6968 for <peppermint@core3.amsl.com>; Tue, 13 May 2008 15:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avPH0sWAH3mT for <peppermint@core3.amsl.com>; Tue, 13 May 2008 15:04:42 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 08BEF3A695B for <peppermint@ietf.org>; Tue, 13 May 2008 15:04:41 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.2/8.14.2) with ESMTP id m4DM3ALt000944; Tue, 13 May 2008 16:03:10 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Tue, 13 May 2008 16:03:10 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 13 May 2008 16:02:58 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C60117F58B@srvxchg3.cablelabs.com>
In-Reply-To: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PEPPERMINT] DRINKS Charter v 02
Thread-Index: Acizsp2LQlJn2qAERK+lvfgFG3QLAgBjJp2g
References: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Richard Shockey" <richard@shockey.us>, <peppermint@ietf.org>
X-Approved: ondar
Subject: Re: [PEPPERMINT] DRINKS Charter v 02
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org

Rich,

   The draft charter looks ok but this attempt to limit the scope to one
of the protocols that can access or make use of this data is too
restrictive.  Said differently, the drops (data elements in DRINKS)
should be independent from the query protocol used to access it.  

   Find some comments inline to assist in the scope definition.

Jean-Francois.


> -----Original Message-----
> From: peppermint-bounces@ietf.org [mailto:peppermint-
> bounces@ietf.org] On Behalf Of Richard Shockey
> Sent: Sunday, May 11, 2008 4:02 PM
> To: peppermint@ietf.org
> 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:
> 
> peppermint@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 (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. 


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

On the one hand, this sentence does not say much given you have "with
limited exceptions". 
On the other hand, it means limiting the SED data subset to what can be
expressed or meaningful for ENUM.  Fundamentally, this seems wrong to
assume given deliverables (data exchanges between data registries, SSPs,
location functions -- not all will rely on ENUM).
I would be ok with including fields that might be provisioned for the
session establishment using ENUM and/or SIP.


> 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 securely exchanged between the peering functions.
I don't understand what is meant here.  
Is it for DRINKS to ensure that the SED data can be securely exchanged
by protocol entities?


> 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.
I would remove "potential" otherwise this is still left for further
discussion.

> 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
To limit the scope, should one of the two last deliverables be declared
out-of-scope for now?  I guess the question is: do people on the list
feel that both the data-to-registry and registry-to-location function
problems need to be solved?  This seems 2 related but distinct problems
in scope.

As I commented at the mike in IETF#71, I personally think both are
valuable to solve in parallel but may be that is too much.  There was a
draft submitted to show an example of something that could feed into the
last deliverable.  
One thought would be to start from the bottom and move up the data
chain: what is used by quering entities that use SIP/ENUM from a
location routing function? then get that data model about right, before
you look at how data providers want to structure the multiple views
based on the roles played by data owners/users/intermediates.  Can you
declare one of the 2 out-of-scope and then recharter to add the second
deliverable once we get somewhere?


> 
> 
> 
> Richard Shockey
> Director, Member of the Technical Staff
> NeuStar
> 46000 Center Oak Plaza - Sterling, VA 20166
> PSTN Office +1 571.434.5651
> PSTN Mobile: +1 703.593.2683
> <mailto:richard(at)shockey.us>
> <mailto:richard.shockey(at)neustar.biz>
> 
> 
> 
> _______________________________________________
> PEPPERMINT mailing list
> PEPPERMINT@ietf.org
> https://www.ietf.org/mailman/listinfo/peppermint
_______________________________________________
PEPPERMINT mailing list
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint


Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECD413A6B7E; Mon, 12 May 2008 07:08:04 -0700 (PDT)
X-Original-To: peppermint@core3.amsl.com
Delivered-To: peppermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EE7C3A6979 for <peppermint@core3.amsl.com>; Mon, 12 May 2008 07:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ylGBbZ4q8pma for <peppermint@core3.amsl.com>; Mon, 12 May 2008 07:08:01 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.245.115]) by core3.amsl.com (Postfix) with ESMTP id 61C7B3A68C3 for <peppermint@ietf.org>; Mon, 12 May 2008 07:08:01 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ppfautz@att.com
X-Msg-Ref: server-15.tower-121.messagelabs.com!1210601251!15003923!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 19094 invoked from network); 12 May 2008 14:07:31 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-15.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 12 May 2008 14:07:31 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m4CE79oM031792; Mon, 12 May 2008 10:07:10 -0400
Received: from ACCLUST02EVS1.ugd.att.com (acst03.ugd.att.com [135.37.16.8]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m4CE73Kr031700; Mon, 12 May 2008 10:07:04 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 May 2008 10:07:02 -0400
Message-ID: <34DA635B184A644DA4588E260EC0A25A12CCE87D@ACCLUST02EVS1.ugd.att.com>
In-Reply-To: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PEPPERMINT] DRINKS Charter v 02
Thread-Index: Acizsp2LQlJn2qAERK+lvfgFG3QLAgAgnREw
References: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
From: "PFAUTZ, PENN L, ATTCORP" <ppfautz@att.com>
To: "Richard Shockey" <richard@shockey.us>, <peppermint@ietf.org>
Subject: Re: [PEPPERMINT] DRINKS Charter v 02
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org

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
+1-732-420-4962

-----Original Message-----
From: peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org]
On Behalf Of Richard Shockey
Sent: Sunday, May 11, 2008 6:02 PM
To: peppermint@ietf.org
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: 

peppermint@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 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: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>


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


Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A15E43A698A; Sun, 11 May 2008 15:02:55 -0700 (PDT)
X-Original-To: peppermint@core3.amsl.com
Delivered-To: peppermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 714B83A6858 for <peppermint@core3.amsl.com>; Sun, 11 May 2008 15:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.185
X-Spam-Level: 
X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UN9aZxqDNzVb for <peppermint@core3.amsl.com>; Sun, 11 May 2008 15:02:51 -0700 (PDT)
Received: from mail.songbird.com (mail.songbird.com [208.184.79.10]) by core3.amsl.com (Postfix) with ESMTP id 91FDE3A67F5 for <peppermint@ietf.org>; Sun, 11 May 2008 15:02:51 -0700 (PDT)
Received: from rshockeyPC (h-68-165-240-38.mclnva23.covad.net [68.165.240.38]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id m4BM1B0j014227 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <peppermint@ietf.org>; Sun, 11 May 2008 15:01:17 -0700
From: "Richard Shockey" <richard@shockey.us>
To: <peppermint@ietf.org>
Date: Sun, 11 May 2008 18:01:51 -0400
Message-ID: <1e6901c8b3b2$a3ba1110$eb2e3330$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acizsp2LQlJn2qAERK+lvfgFG3QLAg==
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
Subject: [PEPPERMINT] DRINKS Charter v 02
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org

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: 

peppermint@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 (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. 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 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: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>


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