IETF Logo Mail Archive

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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 24 April 2008 03:48 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 ACF243A67E1; Wed, 23 Apr 2008 20:48:21 -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 8097B3A6815 for <peppermint@core3.amsl.com>; Wed, 23 Apr 2008 20:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 RSryy5WRTCoZ for <peppermint@core3.amsl.com>; Wed, 23 Apr 2008 20:48:19 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 8C9B03A67E1 for <peppermint@ietf.org>; Wed, 23 Apr 2008 20:48:19 -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; Wed, 23 Apr 2008 23:47:52 -0400
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Wed, 23 Apr 2008 23:47:52 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Richard Shockey <richard@shockey.us>, "'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: Wed, 23 Apr 2008 23:45:09 -0400
Thread-Topic: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
Thread-Index: Acild5bQIMI2yamUS/eNn2gBoulzzQAEsfqAAAwJVRA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30BD050391E@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>
In-Reply-To: <059501c8a58b$e4899c40$ad9cd4c0$@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]
>
> No one is proposing a solution. We are describing  that we do not propose
> exchanging data on Collateralized Debt Instruments and Mortgage Interest
> Swaps among SSP's

Sure, I'm all in favor of getting a charter approved post-haste.  Even if it means my ideas for "Mortgage Interest eXchanges" (MIX) will have to wait for a charter update.  (too bad too, 'cause a draft-drinks-mix would have been a recipe for success in my opinion)

But seriously, how "detailed" do we need to be in the charter regarding this data?  I think Daryl's proposed data with some minor nits is broad enough not to cause heartburn later, while not letting us get drunk in the possibilities. :)

How about this:

[begin]
The scope will be limited to defining the following criteria necessary for a SSP to respond with the necessary Session Establishment Data (SED) for both internal and external purposes:

        + Routes
                - Destination SIP/SIPS/TEL URI Egress and Ingress Routes
                - Relevant route names, identifiers, and services
                - Attributes affecting route selection
        + Service Areas
                - Individual, ranges, or groups of user-agent identifiers
                - Route-to-service-area associations
        + Treatment Profiles
                - Priority
                - Location

The mechanism(s) chosen should be extensible, in case additional criteria are deemed necessary to achieve the goals of the WG in the future.
[end]

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

v2.23.0 | Report a Bug | By Email