IETF Logo Mail Archive

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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 24 April 2008 15:59 UTC

Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A73228C263; Thu, 24 Apr 2008 08:59:15 -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 A6AB728C263 for <peppermint@core3.amsl.com>; Thu, 24 Apr 2008 08:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599]
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 BnHrSXfBVg9Q for <peppermint@core3.amsl.com>; Thu, 24 Apr 2008 08:59:13 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id C33E328C253 for <peppermint@ietf.org>; Thu, 24 Apr 2008 08:59:13 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.263.0; Thu, 24 Apr 2008 11:58:46 -0400
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Thu, 24 Apr 2008 11:58:46 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Richard Shockey <richard@shockey.us>, "'PFAUTZ, PENN L, ATTCORP'" <ppfautz@att.com>, "'Dwight, Timothy M (Tim)'" <timothy.dwight@verizonbusiness.com>, 'Daryl Malas' <D.Malas@cablelabs.com>, 'Otmar Lendl' <lendl@nic.at>, "peppermint@ietf.org" <peppermint@ietf.org>
Date: Thu, 24 Apr 2008 11:56:03 -0400
Thread-Topic: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
Thread-Index: Acild5bQIMI2yamUS/eNn2gBoulzzQAEsfqAAAwJVRAAEfJPwAAFPVwwAALbrRA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30BD0578E7B@mail.acmepacket.com>
References: <125b01c89fe6$14f823c0$3ee86b40$@us><20080419210654.GA30568@nic.at><E6C2E8958BA59A4FB960963D475F7AC30BD035B4EF@mail.acmepacket.com><20080420211101.GA32096@nic.at> <1a6601c8a3dd$49ca8c50$dd5fa4f0$@us><20080422144452.GA582@nic.at><E6C2E8958BA59A4FB960963D475F7AC30BD045ABC4@mail.acmepacket.com><14b501c8a495$758aeb60$60a0c220$@us><160DE07A1C4F8E4AA2715DEC577DA49193654F@srvxchg3.cablelabs.com><154801c8a49b$22fbc2b0$68f34810$@us><E6C2E8958BA59A4FB960963D475F7AC30BD045B4DE@mail.acmepacket.com><160DE07A1C4F8E4AA2715DEC577DA491936564@srvxchg3.cablelabs.com><E6C2E8958BA59A4FB960963D475F7AC30BD05031E7@mail.acmepacket.com><092B2658AAB56A4D80836399A4C4703104526DBE@ASHEVS002.mcilink.com><160DE07A1C4F8E4AA2715DEC577DA491936566@srvxchg3.cablelabs.com><092B2658AAB56A4D80836399A4C4703104526E1F@ASHEVS002.mcilink.com><160DE07A1C4F8E4AA2715DEC577DA491936569@srvxchg3.cablelabs.com><092B2658AAB56A4D80836399A4C4703104527139@ASHEVS002.mcilink.com><059501c8a58b$e4899c40$ad9cd4c0$@us> <E6C! 2E8958BA5 9A4FB960963D4 75F7AC30BD050391E@mail.acmepacket.com> <34DA635B184A644DA4588E260EC0A25A129FD159@ACCLUST02EVS1.ugd.att.com> <0e3001c8a617$c151eed0$43f5cc70$@us>
In-Reply-To: <0e3001c8a617$c151eed0$43f5cc70$@us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
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


> -----Original Message-----
> From: Richard Shockey [mailto:richard@shockey.us]
>
> **************
>
> More 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),
> and
> the secure manners in which SED and the SIP session data is exchanged
> between the peering functions.
>
>
> Typical SED data types might include:
>
> + Routes
>      - Destination SIP/SIPS/TEL URI Egress and Ingress Routes
>      - Relevant route names, identifiers, and services
>      - NAPTR context and associations
>      - PSTN database information

I think we agreed to remove the "NAPTR" line from this.  No?



> + Service Areas
>      - Individual, ranges, or groups of ENUMservice identifiers
>      - Route associations


I'm not quite sure what you mean by "ENUMservice identifiers" with regards to individual, ranges, or groups.  I mean I know what an "ENUMservice" is per RFC 3761, I just have no idea what it has to do with a "service area", or what "ranges or groups" of them would mean.
Also, "Route associations" is not a well-known term as far as I know.

I *think* what you guys mean here is:
        + Service Areas
                - Individual, ranges, or groups of user-agent identifiers
                - Route-to-service-area 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
>
> **************
>
>
_______________________________________________
PEPPERMINT mailing list
PEPPERMINT@ietf.org
https://www.ietf.org/mailman/listinfo/peppermint

v2.23.0 | Report a Bug | By Email