Re: [Sipping] Alternate CLF syntax proposal

Jason Fischl <jason.fischl@gmail.com> Thu, 26 March 2009 15:35 UTC

Return-Path: <jason.fischl@gmail.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D56E3A69DE for <sipping@core3.amsl.com>; Thu, 26 Mar 2009 08:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_24=0.6]
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 aTBDNh8UDFTc for <sipping@core3.amsl.com>; Thu, 26 Mar 2009 08:35:35 -0700 (PDT)
Received: from mail-ew0-f165.google.com (mail-ew0-f165.google.com [209.85.219.165]) by core3.amsl.com (Postfix) with ESMTP id DA67A3A681C for <sipping@ietf.org>; Thu, 26 Mar 2009 08:35:34 -0700 (PDT)
Received: by ewy9 with SMTP id 9so629934ewy.37 for <sipping@ietf.org>; Thu, 26 Mar 2009 08:36:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :received:message-id:subject:from:to:cc:content-type; bh=KHZ7vcn6GMLWVdU2QDDQGx1yRdCKKuqrplgocr74Dh0=; b=h0HnkHkpwLAfHY4mYC3BLcXo+E70Te08MtPnceAN3lU1CBGf11BAWU12uPxGBXdWzA t2XnUZfCqJU+URXtjeYtbrK/1L3soGNsjJF8GOn6G/csw40rdwV63MWdkb4HGF16Bm0a NRXDZwlHSYLE5P8iS51SwZlzHI6HX4ETJM0Q8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VACBhHMW6KQ2HiPmL+OAsfz0cKfApz4q7rdXgo16xz8LAuUHtWvWUvTY/viUTisx6W LppEK2yYylYJIx6mhDT4xNCNy++JFpOoOTJjf/aBysRmOn5YWZEJXwxDxstp39verumw QnzIxH7uJLFOccFYpF23P7+gMazCgrtT9VJzY=
MIME-Version: 1.0
In-Reply-To: <49CAE21C.5060309@nostrum.com>
References: <49CAE21C.5060309@nostrum.com>
Date: Thu, 26 Mar 2009 08:36:10 -0700
Received: by 10.210.16.10 with SMTP id 10mr943ebp.21.1238081787345; Thu, 26 Mar 2009 08:36:27 -0700 (PDT)
Message-ID: <c164605b0903260836p45a8bd8eg9ad50f670ef82302@mail.gmail.com>
From: Jason Fischl <jason.fischl@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="000e0cd1ea6e237277046607615d"
Cc: sipping WG <sipping@ietf.org>, draft-gurbani-sipping-clf@tools.ietf.org
Subject: Re: [Sipping] Alternate CLF syntax proposal
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 15:35:36 -0000

On Wed, Mar 25, 2009 at 7:02 PM, Adam Roach <adam@nostrum.com> wrote:

> In the spirit of "send text," I've put together a straw-man proposal for an
> easy-to-generate and fast-to-process extensible format for saving SIP log
> messages:
>
> http://www.ietf.org/internet-drafts/draft-roach-sipping-clf-syntax-00.txt
>

I quite like this scheme. It is very simple to generate and parse and will
be blazingly fast. It would also be very simple to create a utility to
generate "human-readable" versions from it which would address that
particular concern.

Comments about the format:
- add a version number to the header
- set aside a range of tags for vendor attributes.

A few miscellaneous comments about contents:
- for sent messages: local ip:port used to send the message + transport used
+ destination ip:port
- for received messages: remote ip:port message was received from + local
ip:port + transport used
- it may be a good idea to have a predefined tag which can be used as an
index into another diagnostic file. e.g. pointer into a PCAP file or vendor
diagnostic log.
- Is there anything we want to jam in here to help debug TCP/TLS issues or
is that out of scope?

Jason