[sip-clf] Strawman proposal to handle bodies

"Vijay K. Gurbani" <vkg@bell-labs.com> Wed, 19 January 2011 16:24 UTC

Return-Path: <vkg@bell-labs.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 5F9B83A714D for <sip-clf@core3.amsl.com>; Wed, 19 Jan 2011 08:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.276
X-Spam-Level:
X-Spam-Status: No, score=-105.276 tagged_above=-999 required=5 tests=[AWL=-0.943, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, 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 RYvKGicMjo91 for <sip-clf@core3.amsl.com>; Wed, 19 Jan 2011 08:24:19 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 0E4043A7172 for <sip-clf@ietf.org>; Wed, 19 Jan 2011 08:24:18 -0800 (PST)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p0JGQxB4016000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-clf@ietf.org>; Wed, 19 Jan 2011 10:26:59 -0600 (CST)
Received: from shoonya.ih.lucent.com (Knoppix-135185238233.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p0JGQwio023001 for <sip-clf@ietf.org>; Wed, 19 Jan 2011 10:26:59 -0600 (CST)
Message-ID: <4D371165.5030104@bell-labs.com>
Date: Wed, 19 Jan 2011 10:29:25 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: "sip-clf@ietf.org" <sip-clf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: [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: Wed, 19 Jan 2011 16:24:20 -0000

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/