Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft-gurbani-sipclf-problem-statement-01)
"Spencer Dawkins" <spencer@wonderhamster.org> Tue, 02 February 2010 21:33 UTC
Return-Path: <spencer@wonderhamster.org>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA80D3A6B7D for <sip-clf@core3.amsl.com>; Tue, 2 Feb 2010 13:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 oxbjjhRqwYrK for <sip-clf@core3.amsl.com>; Tue, 2 Feb 2010 13:33:04 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 8B4DB3A6B2E for <sip-clf@ietf.org>; Tue, 2 Feb 2010 13:33:04 -0800 (PST)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MfFEA-1NNcHR1U3m-00Oztp; Tue, 02 Feb 2010 16:33:43 -0500
Message-ID: <81F3AF977ADD49E7A883F138ECCC71D0@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>, David Harrington <ietfdbh@comcast.net>, sip-clf@ietf.org
References: <7505A2C58D8F4FD88B47D10EA74649CD@china.huawei.com><00ce01caa41e$fe5a5ef0$0600a8c0@china.huawei.com> <4B68920B.5090908@alcatel-lucent.com>
Date: Tue, 02 Feb 2010 15:33:26 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19htid20n9eRU0B01g1xGydUBbhJmD07WecqEf WBDgfjfDd29rb9+tSitQusJfQoM/NX5CmjO4YHvWQwWAP3c4vR 3D3p/MPx294BA2wb238iOoJA0ZDNf5MbdRo2zNSBxc=
Subject: Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft-gurbani-sipclf-problem-statement-01)
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 21:33:05 -0000
Speaking as co-chair, this time... >> Everything is just munged together into one problem statement, as if >> everybody was in agreement about a single problem to be solved, and the >> single solution that should solve all those problems. > > My attempt at a problem statement is given in Section 3 of > the sipclf draft > (http://tools.ietf.org/html/draft-gurbani-sipclf-problem-statement-01) > If this gives you the feeling that everything is munged together, > I will be happy to work with you on any text you can contribute > that makes this more transparent. Where Spencer and Theo think we are, is that we're adopting the next version of this draft as a working group draft. We haven't seen anyone disagreeing with that. At that point - which we might as well declare to be "now", because Vijay can send in "the next version" as draft-ietf-sipclf at any time, and Theo and I will approve it - the working group becomes responsible for the text in the working group draft. That means that it's not up to Vijay and Dave to work this out, with everyone else cheering them on from the sidelines - please feel free to send text that the editor can incorporate, as we identify that we have consensus on it! Thanks, Spencer
- [sip-clf] WGLC: SIPCLF Problem Statement (draft-g… Spencer Dawkins
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… Spencer Dawkins
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… Elwell, John
- Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft… Spencer Dawkins
- Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft… Eric Burger
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… David Harrington
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… Spencer Dawkins
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… Vijay K. Gurbani
- Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft… Spencer Dawkins
- Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft… Romascanu, Dan (Dan)
- Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft… David Harrington
- Re: [sip-clf] WGLC: SIPCLF ProblemStatement(draft… Spencer Dawkins
- Re: [sip-clf] WGLC: SIPCLFProblemStatement(draft-… Rainer Gerhards
- [sip-clf] A primer on syslog. David Harrington
- Re: [sip-clf] A primer on syslog. Rainer Gerhards
- Re: [sip-clf] A primer on syslog. Spencer Dawkins
- Re: [sip-clf] A primer on syslog. Cullen Jennings
- [sip-clf] WGLC: SIPCLF Problem Statement (draft-g… Cullen Jennings
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… Rainer Gerhards
- Re: [sip-clf] A primer on syslog. Rainer Gerhards
- Re: [sip-clf] WGLC: SIPCLF Problem Statement(draf… Benoit Claise
- Re: [sip-clf] WGLC: SIPCLF Problem Statement (dra… Vijay K. Gurbani
- Re: [sip-clf] WGLC: SIPCLF Problem Statement (dra… Hadriel Kaplan
- Re: [sip-clf] WGLC: SIPCLF Problem Statement (dra… Vijay K. Gurbani