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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 24 April 2008 16:34 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 439FA28C245; Thu, 24 Apr 2008 09:34:44 -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 46BCD28C10A for <peppermint@core3.amsl.com>; Thu, 24 Apr 2008 09:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level:
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 yMq3E28cfTni for <peppermint@core3.amsl.com>; Thu, 24 Apr 2008 09:34:41 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 06E9528C2CA for <peppermint@ietf.org>; Thu, 24 Apr 2008 09:34:12 -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 12:33:44 -0400
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Thu, 24 Apr 2008 12:33:44 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Dwight, Timothy M (Tim)" <timothy.dwight@verizonbusiness.com>, Richard Shockey <richard@shockey.us>, "PFAUTZ, PENN L, ATTCORP" <ppfautz@att.com>, Daryl Malas <D.Malas@cablelabs.com>, Otmar Lendl <lendl@nic.at>, "peppermint@ietf.org" <peppermint@ietf.org>
Date: Thu, 24 Apr 2008 12:31:02 -0400
Thread-Topic: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
Thread-Index: Acild5bQIMI2yamUS/eNn2gBoulzzQAEsfqAAAwJVRAAEfJPwAAFPVwwAABjOUAAATE9EAAA1rogAAFSCTA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30BD0578F1A@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> <"092B265 8AAB56A4D80836399A4C47031037DD575"@ASHEVS002.mcilink.com> <100c01c8a61e$fdddf270$f999d750$@us> <092B2658AAB56A4D80836399A4C47031037DD579@ASHEVS002.mcilink.com>
In-Reply-To: <092B2658AAB56A4D80836399A4C47031037DD579@ASHEVS002.mcilink.com>
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

I agree that it is constraining the solution to some degree, but I think what Richard has said is we're going to need to do that a bit to get this past the IESG.  My guess is they're just worried we might try to take on too much or overstep the IETF's comfort zone.

The terms described so far though are fairly generic, and I think one can claim a lot of things would fall under those terms.

So to use the earlier analogy they do say "we're building a car", but that car could be a minivan or pickup - but it's not going to be a plane or boat.  If a mechanism we choose happens to be Chitty-Chitty Bang-Bang, that's ok and I'm not even sure we'd have to revisit the charter to accept that type of solution; but the current charter's just saying it's not in our scope to try to build that type of vehicle at the outset.

If we find that this scope is too constrictive, then we can always revisit and change the charter.  I don't think there will be too much disagreement to changing that if the SSP community needs something more.  And if there is disagreement to that, well... it's fairly pointless to create a mechanism that won't be used. (not that the IETF hasn't done that a hundred times :)

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