Re: [sip-clf] Open issues for the SIP CLF representation draft

Peter Musgrave <peter.musgrave@magorcorp.com> Sun, 13 February 2011 13:07 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 43BE33A6981 for <sip-clf@core3.amsl.com>; Sun, 13 Feb 2011 05:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level:
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 L0OC9L4q-oij for <sip-clf@core3.amsl.com>; Sun, 13 Feb 2011 05:07:24 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id EB3AD3A69D6 for <sip-clf@ietf.org>; Sun, 13 Feb 2011 05:07:23 -0800 (PST)
Received: by iym1 with SMTP id 1so4231729iym.31 for <sip-clf@ietf.org>; Sun, 13 Feb 2011 05:07:44 -0800 (PST)
Received: by 10.231.13.201 with SMTP id d9mr2018999iba.124.1297602464050; Sun, 13 Feb 2011 05:07:44 -0800 (PST)
Received: from [192.168.1.100] ([204.237.32.134]) by mx.google.com with ESMTPS id u9sm1631591ibe.20.2011.02.13.05.07.41 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Feb 2011 05:07:42 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-2--679803301
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <BF69FEC7-40B7-4B38-8533-D738C31697BB@cisco.com>
Date: Sun, 13 Feb 2011 08:07:40 -0500
Message-Id: <C4AE9C7C-E259-4B81-AAD8-35AFC6D9DE32@magorcorp.com>
References: <BF69FEC7-40B7-4B38-8533-D738C31697BB@cisco.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Open issues for the SIP CLF representation draft
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: Sun, 13 Feb 2011 13:07:25 -0000

Hi, 

1. I guess I favour tabs (since I expect a lot of spaces in fields) despite their drawbacks in e.g. Telnet. 

2. I would avoid the equals and quotes since this introduces two elements which could be in the data whereas the TLV introduces only one (comma)

Peter Musgrave
(as individual)

On 2011-02-10, at 1:52 AM, Gonzalo Salgueiro wrote:

> Folks -
> 
> In preparation for the -00 draft of the WG implementation draft, I need to close on a few unresolved issues that we agreed during the Virtual Interim Meeting to take to the list for further discussion. Please provide timely feedback so we minimize the number of open issues to discuss in Prague.
> 
> 1. Shall we use a TAB or a SPACE (or any LWS) as field delimiters?
> Considerations and points raised:
> 
> - TABs don’t survive Telnet or web pages very well, especially when copy/pasting.
> - spaces can appear inside fields (as can most other delimiters we choose)
> - how do TAB and SPACE delimiters interact with shell tools (rep, cut, awk)
> 
> 2. Do we need to update the syntax of the optionally logged fields from the current well known (though possibly more cryptic) TLV representation?
> 
> <mandatory fields>	01,07,foo.bar	02,0b,hello world      
> 
> to something more easily readable (like tag="value")?
> 
> <mandatory fields> 1="foo.bar" 2="hello world”
> 
> Considerations and points raised:
> 
> - some concern about adding quotes around values (since some fields will contain quotes)
> - this issue exists for almost any delimiter
> - essentially a matter of "taste"
> 
> 
> Warm Regards,
> 
> --Gonzalo
> 
> 
> 
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf