Re: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 23 April 2008 17:30 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 7608A28C339; Wed, 23 Apr 2008 10:30:36 -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 BB5C63A6AD0 for <peppermint@core3.amsl.com>; Wed, 23 Apr 2008 10:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level:
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 u-da62KKrn4z for <peppermint@core3.amsl.com>; Wed, 23 Apr 2008 10:30:34 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 658AE3A6DAF for <peppermint@ietf.org>; Wed, 23 Apr 2008 10:30:34 -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 13:30:08 -0400
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Wed, 23 Apr 2008 13:30:08 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Dwight, Timothy M (Tim)" <timothy.dwight@verizonbusiness.com>, Daryl Malas <D.Malas@cablelabs.com>, "peppermint@ietf.org" <peppermint@ietf.org>
Date: Wed, 23 Apr 2008 13:27:24 -0400
Thread-Topic: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please.
Thread-Index: Acikh2EScAYa3BvkRuqoFaN0JnBW6gAAkqtQAAKgAAAAAJ+XUAAA2ISwABUcBLAAGvG54AABAsIgAACdg7AAACqXoAAATdLAAACd5GA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30BD05032A6@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>
In-Reply-To: <092B2658AAB56A4D80836399A4C4703104526E1F@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
Yeah I'm with Tim on this - this does seem like putting the cart before the horse. I have no doubt we will get use-cases and data-types that will cause debate in the WG, but that's partly what a WG is there to decide, no? I don't think it will take too long to reject ones there isn't interest in, and we haven't needed to be able to point to a charter to say "out of scope" to do that usually in other WG's. If there are ones brought forth there *is* interest in, then we can either spend time in a WG arguing over them, or spend the same amount of time arguing about it before a WG is formed. At least with doing it in the WG, we can make progress on the ones that are less contentious. Also, I don't think the type of data we've been talking about is going to constrain much anyway. Items named "Routes", "relevant route names, identifiers, and services", and "route associations" are broad/generic enough to cover a whole lotta stuff. We'll read into them what we want to read into them. -hadriel > -----Original Message----- > From: Dwight, Timothy M (Tim) [mailto:timothy.dwight@verizonbusiness.com] > Sent: Wednesday, April 23, 2008 1:00 PM > To: Daryl Malas; Hadriel Kaplan; Richard Shockey; Otmar Lendl; > peppermint@ietf.org > Subject: RE: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please. > > Well, limiting the scope sounds good. But on what basis do we limit it? > How do we know that a proposed data model supports anything useful? > > I assume that proponents of a particular model will have some use > case(s) in mind. So why not state them explicitly? Then we can discuss > whether the resulting set of problems to be solved, is sufficient (and > sufficiently bounded). > > To me this is simply an issue of determining requirements before we > settle on an implementation. Settling on an implementation (data model) > first, will have the effect of bounding the set of requirements we might > satisfy. But doesn't that seem backward? > > Tim > > > > -----Original Message----- > > From: Daryl Malas [mailto:D.Malas@cablelabs.com] > > Sent: Wednesday, April 23, 2008 11:48 AM > > To: Dwight, Timothy M (Tim); Hadriel Kaplan; Richard Shockey; > > Otmar Lendl; peppermint@ietf.org > > Subject: RE: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please. > > > > I think the purpose here is to contain the scope of the charter. The > > subsequent use cases will then be limited to the scope of the charter. > > If you do not clearly define the scope, then the use cases can run all > > over the place. If this occurs, it just creates many years > > of debate, a > > very frustrated set of co-chairs and working group. > > > > I think this is the right approach, but we need to be careful > > to balance > > putting enough detail in to clearly contain the scope without too much > > detail as to make the charter a working group draft. > > > > --Daryl > > > > -----Original Message----- > > From: Dwight, Timothy M (Tim) > > [mailto:timothy.dwight@verizonbusiness.com] > > Sent: Wednesday, April 23, 2008 10:43 AM > > To: Hadriel Kaplan; Daryl Malas; Richard Shockey; Otmar Lendl; > > peppermint@ietf.org > > Subject: RE: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please. > > > > Do we have to determine the data model now? This seems premature when > > we've not yet considered use cases. > > > > Tim > > > > > > > -----Original Message----- > > > From: peppermint-bounces@ietf.org > > > [mailto:peppermint-bounces@ietf.org] On Behalf Of Hadriel Kaplan > > > Sent: Wednesday, April 23, 2008 11:34 AM > > > To: Daryl Malas; Richard Shockey; Otmar Lendl; peppermint@ietf.org > > > Subject: Re: [PEPPERMINT] DRINKS PROPOSED Charter ..comments please. > > > > > > > > > > > > > -----Original Message----- > > > > From: Daryl Malas [mailto:D.Malas@cablelabs.com] > > > > > > > > I recommend we further simplify: > > > > > > > > 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: > > > > > > OK, so here you're defining the minimal data needed to be > > exchanged by > > > > > DRINKS, in order for an SSP to provide SED - right? > > > > > > > > > > + Routes > > > > - Destination SIP/SIPS/TEL URI Egress and > > > Ingress Routes > > > > - Relevant route names, identifiers, and services > > > > - NAPTR context and associations > > > > > > When you exchange data, it may be in the form of a NAPTR in > > syntax and > > > > > maybe even semantics, but it's not really a "NAPTR" DNS entry - it > > > just happens to be that you chose to format the resultant route > > > information in the form of a NAPTR. So I think the word "NAPTR" > > > shouldn't be in the charter's list of data to be exchanged. We may > > > just happen to use that format in the end for the data, but there's > > > nothing about the data that demands it. (and in fact I personally > > > think it's confusing and misleading to be using that > > specific format > > > in the data exchange directly, but we can argue about that later :) > > > > > > > > > > + Service Areas > > > > - Individual, ranges, or groups of ENUMservice > > > > identifiers > > > > - Route associations > > > > > > I don't know what a "Route association" is? > > > > > > > > > > + Treatment Profiles > > > > - Priority > > > > - Location > > > > > > I note this doesn't directly include originating or source > > > information, which is fairly essential to SIP routing, afaict. Is > > > that something you'd classify under "route associations" or > > "treatment > > > > > profiles", or do you specifically not want that in the charter? > > > > > > -hadriel > > > _______________________________________________ > > > 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
- [PEPPERMINT] DRINKS PROPOSED Charter ..comments p… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Dan York
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Otmar Lendl
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Otmar Lendl
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… David Schwartz
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Otmar Lendl
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Otmar Lendl
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Dwight, Timothy M (Tim)
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Dwight, Timothy M (Tim)
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Dwight, Timothy M (Tim)
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… David Schwartz
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… PFAUTZ, PENN L, ATTCORP
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Daryl Malas
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Dwight, Timothy M (Tim)
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Guyton, Deborah A
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… PFAUTZ, PENN L, ATTCORP
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Dwight, Timothy M (Tim)
- [PEPPERMINT] DRINKS PROPOSED Charter Version 02 Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter Version … Hadriel Kaplan
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… David Schwartz
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Otmar Lendl
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Ray.Bellis
- Re: [PEPPERMINT] DRINKS PROPOSED Charter ..commen… Richard Shockey