Re: [sip-clf] Strawman proposal to handle bodies

"Elwell, John" <john.elwell@siemens-enterprise.com> Thu, 20 January 2011 09:52 UTC

Return-Path: <john.elwell@siemens-enterprise.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 B47CE28C12F for <sip-clf@core3.amsl.com>; Thu, 20 Jan 2011 01:52:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.396
X-Spam-Level:
X-Spam-Status: No, score=-101.396 tagged_above=-999 required=5 tests=[AWL=-1.063, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, SARE_URI_EQUALS=1.666, 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 YZHZx8NvaR1i for <sip-clf@core3.amsl.com>; Thu, 20 Jan 2011 01:52:41 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 531E028C117 for <sip-clf@ietf.org>; Thu, 20 Jan 2011 01:52:41 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-3070102; Thu, 20 Jan 2011 10:55:22 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 9CC611EB82AB; Thu, 20 Jan 2011 10:55:22 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 20 Jan 2011 10:55:23 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, "sip-clf@ietf.org" <sip-clf@ietf.org>
Date: Thu, 20 Jan 2011 10:55:21 +0100
Thread-Topic: [sip-clf] Strawman proposal to handle bodies
Thread-Index: Acu39bTRXKo94stzQqW7gbajameVzgAkjMPA
Message-ID: <A444A0F8084434499206E78C106220CA05FC93F612@MCHP058A.global-ad.net>
References: <4D371165.5030104@bell-labs.com>
In-Reply-To: <4D371165.5030104@bell-labs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sip-clf] Strawman proposal to handle bodies
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: Thu, 20 Jan 2011 09:52:42 -0000

Vijay,

Don't we need 4 different tags for the 4 content types we plan to support? Otherwise you have to decode part of the value to see how the rest of the value is encoded, IIUC.

John
 

> -----Original Message-----
> From: sip-clf-bounces@ietf.org 
> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Vijay K. Gurbani
> Sent: 19 January 2011 16:29
> To: sip-clf@ietf.org
> Subject: [sip-clf] Strawman proposal to handle bodies
> 
> Folks: In the virtual meeting we had this morning, I volunteered
> to draft a proposal for handling message bodies.
> 
> As I understand it, the bounds are that logging bodies is optional
> and that bodies should not be logged as vendor extensions as that
> will hinder interoperability.
> 
> Furthermore, we are interested in logging different body types,
> or more concretely bodies containing:
> 
>    - SDP (Content-Type: application/sdp)
>    - XML payloads (Content-type: application/*+xml)
>    - binary (Content-Type: application/{isup,qsig})
>    - miscellaneous text content (Content-type: message/sipfrag,
>      message/http, text/plain, ...)
> 
> To support this, we reserve a tag field for bodies as described
> in [1], say 0x0004.  The value of this tag field would be the
> content type itself plus the body.
> 
> To take a concrete example,
> 
>     Type: 0x0004
>     Length: 160
>     Value: application/sdp v=0\r\no=alice 2890844526 2890844526 IN IP4
>      host.atlanta.example.com\r\ns=\r\nc=IN IP4
>      host.atlanta.example.com\r\nt=0 0\r\n
>      m=audio 49170 RTP/AVP 0 8 97\r\n
> 
> Couple of points to note: (a) the MIME type is saved in the Value;
> (b) the octets in Value are all logically on one line; (c) the
> Length includes the payload + length of the MIME type + LWS separator
> between the MIME type and the content.
> 
> Also note that for now let's keep aside the \r\n tokens delimiting
> the lines in the example above.  Once we agree to the proposal, we
> can work the details out on how to represent \r\n in a text-based
> body.
> 
> Binary bodies would have to be byte encoded to render them in the
> ASCII file.
> 
> Please comment on this approach so I can update the problem statement
> and Gonzalo can start thinking about the representation format for
> these in [1].
> 
> [1] http://tools.ietf.org/html/draft-salgueiro-sipclf-indexed-ascii-02
> 
> Thanks,
> 
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>