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

"Richard Shockey" <richard@shockey.us> Thu, 24 April 2008 13:35 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 C42393A6AC4; Thu, 24 Apr 2008 06:35: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 0A55C3A6C7B for <peppermint@core3.amsl.com>; Thu, 24 Apr 2008 06:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 nytuj-DvSNdy for <peppermint@core3.amsl.com>; Thu, 24 Apr 2008 06:35:12 -0700 (PDT)
Received: from mail.songbird.com (mail.songbird.com [208.184.79.10]) by core3.amsl.com (Postfix) with ESMTP id 737973A6B5E for <peppermint@ietf.org>; Thu, 24 Apr 2008 06:35:12 -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 m3ODY7xV017128 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 24 Apr 2008 06:34:09 -0700
From: Richard Shockey <richard@shockey.us>
To: 'Hadriel Kaplan' <HKaplan@acmepacket.com>, "'Dwight, Timothy M (Tim)'" <timothy.dwight@verizonbusiness.com>, 'Daryl Malas' <D.Malas@cablelabs.com>, 'Otmar Lendl' <lendl@nic.at>, peppermint@ietf.org
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$a! d9cd4c0$@us> <E6C2E8958 BA59A4FB960963D475F7AC30BD050391E@mail.acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30BD050391E@mail.acmepacket.com>
Date: Thu, 24 Apr 2008 09:34:55 -0400
Message-ID: <026401c8a60f$fd86a880$f893f980$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acild5bQIMI2yamUS/eNn2gBoulzzQAEsfqAAAwJVRAAFUqZ4A==
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
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)


Good very good ... cant wait to see the draft ..

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

And I'll add the sentence on or rating and billing data.

Works for me ...


>  
>  -hadriel

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