Re: [sip-clf] New CLF Syntax draft (text with index)

"Christer Holmberg" <christer.holmberg@ericsson.com> Fri, 08 May 2009 05:14 UTC

Return-Path: <christer.holmberg@ericsson.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 D09813A6922 for <sip-clf@core3.amsl.com>; Thu, 7 May 2009 22:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.865
X-Spam-Level:
X-Spam-Status: No, score=-5.865 tagged_above=-999 required=5 tests=[AWL=0.384, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 ZN0am5DR7eE4 for <sip-clf@core3.amsl.com>; Thu, 7 May 2009 22:14:46 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 3F50A3A67B4 for <sip-clf@ietf.org>; Thu, 7 May 2009 22:14:46 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b7cae000000985-14-4a03c01c139c
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 92.18.02437.C10C30A4; Fri, 8 May 2009 07:16:13 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 8 May 2009 07:16:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 8 May 2009 07:16:11 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0CD64480@esealmw113.eemea.ericsson.se>
In-Reply-To: <j2qDtydTSXrR.lyXWzQm3@nylon.softarmor.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sip-clf] New CLF Syntax draft (text with index)
Thread-Index: AcnPUPvsBMj1cIStT6SvTJQy/swE1QASmclw
References: <j2qDtydTSXrR.lyXWzQm3@nylon.softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>, "Adam Roach" <adam@nostrum.com>
X-OriginalArrivalTime: 08 May 2009 05:16:12.0734 (UTC) FILETIME=[1ABEF5E0:01C9CF9C]
X-Brightmail-Tracker: AAAAAA==
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] New CLF Syntax draft (text with index)
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: Fri, 08 May 2009 05:14:48 -0000

Hi,

I haven't followed the what-encoding-to-use discussion in detail (I
don't have any personal preference), and I appologise if the following
has already been discussed.

Have people taken into consideration the text in the body handling
draft, which says that binary data in message bodies SHOULD be
transfered using "pure" binary encoding.

I know what we are not talking about a message body type now, but do we
want SIP entities to have to support different kind of binary encodings?
They may of course have to do that anyway, if they support protocols etc
outside our control, but still...

Regards,

Christer


 

> -----Original Message-----
> From: sip-clf-bounces@ietf.org 
> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Dean Willis
> Sent: 7. toukokuuta 2009 23:18
> To: Adam Roach
> Cc: sip-clf@ietf.org
> Subject: Re: [sip-clf] New CLF Syntax draft (text with index)
> 
> Having indices and lenghts allows for aggregated fields (or 
> sub-fields if you look at it that way ). Imagine serialing 
> multiple structs, and being able to parse out a whole struct 
> or a field within a struct.
> 
> --
> Dean
> 
> -original message-
> Subject: Re: [sip-clf] New CLF Syntax draft (text with index)
> From: Adam Roach <adam@nostrum.com>
> Date: 05/07/2009 14:30
> 
> Simon Perreault wrote:
> > Adam Roach wrote, on 07/05/09 03:20 PM:
> >> I considered doing it both ways, but decided that I preferred the 
> >> slight space impact of being able to get to any fixed field by 
> >> looking at only two numbers instead of all the preceding 
> fields. I'm 
> >> open to doing just lengths if people are very sensitive to 
> the size 
> >> of each record, but have a personal preference for what's 
> in the draft currently.
> >
> > I'm sorry, I don't understand. Why would one need to look 
> at all the 
> > preceding fields?
> >
> > Let's say you want to look at field 3. You look up the 
> third pointer 
> > (p3), this gives you the start of the field. Then you look up the 
> > fourth pointer (p4), this give you the end of the field. If 
> you want the length you compute p4 - p3.
> 
> Ah, yes! That's a good point. I had considered encoding 
> *lengths* only, which would require adding all the preceding 
> fields together (and I had mis-read your suggestion to mean 
> lengths instead of pointers). You are, of course, correct -- 
> encoding only pointers gets me what I need, while cutting the 
> index size in half. Thanks! I'll try to get a revised draft 
> out reflecting this change sometime soon.
> 
> /a
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
> 
> 
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>