Re: [sip-clf] Request for Consensus: Adopt ASCII

Gonzalo Salgueiro <gsalguei@cisco.com> Wed, 01 December 2010 07:10 UTC

Return-Path: <gsalguei@cisco.com>
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 384A53A6C00 for <sip-clf@core3.amsl.com>; Tue, 30 Nov 2010 23:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 SbgsuwINdyHH for <sip-clf@core3.amsl.com>; Tue, 30 Nov 2010 23:10:41 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id B8A163A6D01 for <sip-clf@ietf.org>; Tue, 30 Nov 2010 22:49:53 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oB16lutU003374; Wed, 1 Dec 2010 01:47:56 -0500 (EST)
Received: from rtp-gsalguei-8719.cisco.com (rtp-gsalguei-8719.cisco.com [10.116.61.58]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oB16lsmH022988; Wed, 1 Dec 2010 01:47:54 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <745B2172-F6B4-4E3A-B92F-08904067354D@magorcorp.com>
Date: Wed, 01 Dec 2010 01:47:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E35576E-3B0B-41A4-BB58-81207D71E983@cisco.com>
References: <D4134C23-AC3E-48E7-BFB4-1D51C2CA51EF@magorcorp.com> <06792DB6-BD48-42C9-B12F-639EA5E6E996@acmepacket.com> <6C54CABA-5BF0-4BA3-8845-1822023FF624@magorcorp.com> <4CDAAC6B.8090707@bell-labs.com> <5319F0AA-5CDE-42F0-BDC3-1A60FA18F2CF@voxeo.com> <745B2172-F6B4-4E3A-B92F-08904067354D@magorcorp.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
X-Mailer: Apple Mail (2.1082)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] Request for Consensus: Adopt ASCII
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: Wed, 01 Dec 2010 07:10:44 -0000

Peter - 

There might be value in converging as a group on many of these lingering issues that have recently been raised before submitting the -00 version of the WG doc. 

These issues include:

- Should we use indexing at all versus tab delimited? or should we stick with just pointers? or go with do away with the indexing but still log the field lengths?
- Do we use TAB or spaceE as field separators?
- Update the presentation of optional fields from something like: <mandatory fields>	01,07,foo.bar	02,0b,hello world      to something like: <mandatory fields> 1="foo.bar" 2="hello world"
- Should we add vendor specified fields in the optionally logged portion (using enterprise numbers or related mechanism)
- What format do we use to log a field that cannot be parsed?
- How do we log a missing field? Stick with - and come up with some escape sequence for it? or do we log all fields which are interpreted/derived not use "", but all fields which are the literal string use " ?
- While we have to consensus that logging bodies (SDP and otherwise) is capped at 4k and optional, how much of of this should be specified in the Problem Statement and how much in the ASCII draft?  For something that is considered option, do we need to decide on how to represent a multi-line body in a format which tries to use a single text line?

Can we generate some productive discussion on these with the intent of getting consensus and finally get these issues resolved? Closing on these will improve our starting point and  will expedite progress on the draft

Regards,

Gonzalo


On Nov 29, 2010, at 2:55 PM, Peter Musgrave wrote:

> (as chair)
> 
> I have not seen any contrary opinions on the list. 
> 
> The WG will adopt the ASCII draft as a working doc.
> 
> Regards
> 
> Peter Musgrave
> 
> On 2010-11-10, at 9:07 PM, Dan Burnett wrote:
> 
>> +1
>> 
>> On Nov 10, 2010, at 9:30 AM, Vijay K. Gurbani wrote:
>> 
>>> On 11/09/2010 03:51 PM, Peter Musgrave wrote:
>>>> [Consensus Call] As discussed in the Beijing session, I would like
>>>> to ask for a consensus call for the sip-clf group to adopt ascii as
>>>> the format to proceed with under the present charter.
>>> 
>>> And Hadriel Kaplan asked for a clarification:
>>>> To be clear, you're asking for a consensus call on the sip-clf group
>>>> to adopt *an* ascii format, not necessarily the indexed-ascii format
>>>> as it stands right now in its draft, correct?
>>> 
>>> To which, Peter replied:
>>>> Correct
>>> 
>>> So ... yes, I support adopting an ASCII format.
>>> 
>>> Thanks,
>>> 
>>> - vijay
>>> -- 
>>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
>>> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
>>> Web:   http://ect.bell-labs.com/who/vkg/
>>> _______________________________________________
>>> sip-clf mailing list
>>> sip-clf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sip-clf
>> 
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
> 
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf