Re: [sip-clf] Changes for Problem Statement Doc

Peter Musgrave <peter.musgrave@magorcorp.com> Tue, 23 November 2010 00:46 UTC

Return-Path: <peter.musgrave@magorcorp.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 AEA2B28C17C for <sip-clf@core3.amsl.com>; Mon, 22 Nov 2010 16:46:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Y35MO8q4x71N for <sip-clf@core3.amsl.com>; Mon, 22 Nov 2010 16:45:44 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 5E20528C190 for <sip-clf@ietf.org>; Mon, 22 Nov 2010 16:45:43 -0800 (PST)
Received: by gwj17 with SMTP id 17so419554gwj.31 for <sip-clf@ietf.org>; Mon, 22 Nov 2010 16:46:39 -0800 (PST)
Received: by 10.150.143.8 with SMTP id q8mr140944ybd.321.1290473198919; Mon, 22 Nov 2010 16:46:38 -0800 (PST)
Received: from [192.168.1.105] ([204.237.32.134]) by mx.google.com with ESMTPS id k2sm2373976ybj.20.2010.11.22.16.46.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Nov 2010 16:46:37 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <4CEADCFD.3000604@bell-labs.com>
Date: Mon, 22 Nov 2010 19:46:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E3C63BD-1453-4D48-8CFE-D4043AFD3EEA@magorcorp.com>
References: <B091FA5A-F418-42C1-9BC0-0E25224E4691@magorcorp.com> <4CEADCFD.3000604@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Changes for Problem Statement Doc
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, 23 Nov 2010 00:46:06 -0000

On 2010-11-22, at 4:13 PM, Vijay K. Gurbani wrote:

> On 11/14/2010 04:42 AM, Peter Musgrave wrote:
>> 
>> 
>> Issue: There was an issue about logging bodies. I see agreement that
>> this does not need to be mandatory. I would suggest it could be
>> incorporated into the log format in a TLV manner. Does anyone want to
>> see words in the problem statement about e,g. what TLV should be used
>> to log SDP?
(as individual)
I'd welcome other opinions here. I tend to think primarily in terms of sdp bodies. I also think this raises an issue in the ascii draft about how to represent a multi-line body in a format which tries to use a single text line. Some options are:
1. allow the line breaks to happen (and use the pointer block to indicate where the next message starts) 
  - this does make simple line based scripting harder  - so I do not favour it. 
2. Have a different EOL character
3. Make each sdp line it's own TLV (or have an list-like TLV entity)

These issues may recur in other body types (e.g. the XML docs which are bodies in INFOs and NOTIFYs). So any solution should bear that in mind. 

Opinions?

Peter Musgrave

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