Re: [sip-clf] problem-statement and logging arbitrary SIP fields

Eric Burger <eburger@standardstrack.com> Wed, 13 April 2011 17:40 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: sip-clf@ietfc.amsl.com
Delivered-To: sip-clf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 57FD2E0869 for <sip-clf@ietfc.amsl.com>; Wed, 13 Apr 2011 10:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level:
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lNdLGimoV-A for <sip-clf@ietfc.amsl.com>; Wed, 13 Apr 2011 10:40:45 -0700 (PDT)
Received: from karma.cs.georgetown.edu (karma.cs.georgetown.edu [141.161.20.3]) by ietfc.amsl.com (Postfix) with ESMTP id 2F96AE0860 for <sip-clf@ietf.org>; Wed, 13 Apr 2011 10:40:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by karma.cs.georgetown.edu (Postfix) with ESMTP id 7FE702FCC1; Wed, 13 Apr 2011 13:40:44 -0400 (EDT)
Received: from karma.cs.georgetown.edu ([127.0.0.1]) by localhost (karma.cs.georgetown.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07647-08; Wed, 13 Apr 2011 13:40:44 -0400 (EDT)
Received: from [192.168.15.171] (ip68-100-199-8.dc.dc.cox.net [68.100.199.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by karma.cs.georgetown.edu (Postfix) with ESMTP id E7EAC2FC45; Wed, 13 Apr 2011 13:40:43 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-23-139212075; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4DA4BFD3.3070608@bell-labs.com>
Date: Wed, 13 Apr 2011 13:40:42 -0400
Message-Id: <2919F671-DDDC-40BD-BE9A-6D15896FB82E@standardstrack.com>
References: <4DA4BFD3.3070608@bell-labs.com>
To: Vijay K.Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1084)
X-Virus-Scanned: by amavisd-new at cs.georgetown.edu
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] problem-statement and logging arbitrary SIP fields
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Apr 2011 17:40:46 -0000

WFM

On Apr 12, 2011, at 5:10 PM, Vijay K. Gurbani wrote:

> Folks: In the Prague IETF, it was decided that we will allow
> the capability to log arbitrary SIP header fields and
> header elements (like the Reason-Phrase) that are not
> already part of the mandatory fields.
> 
> I am ratifying this decision on the list; pragmatically,
> what this means to the problem-statement draft is that it
> will undergo a change as follows:
> 
> OLD: (Section 8)
> 
>   The data model supports extensibility by providing the capability to
>   log "optional fields".  Optional fields are those SIP header fields
>   (or field components) that are not mandatory (see Section 8.1 for the
>   mandatory field list).  A specific representation format MAY decide
>   to explicitly maintain a representation-specific list of fields (or
>   field components) to log.  All other fields that do not appear in the
>   list of mandatory fields (Section 8.1), nor do they appear in the
>   representation-specific list of optional fields, MUST be logged using
>   a vendor-specific extension mechanism (through the use of private
>   enterprise numbers).  The specific syntax and semantics to be
>   accorded to optional fields, whether they are representation-specific
>   or use vendor-extension mechanisms MUST be defined by the specific
>   representation format used to generate the SIP CLF record.
>   Finally, [I-D.ietf-sipclf-format] is an example of a representation
>   format draft that provides an ASCII-based encoding scheme.
> 
> NEW: (Section 8)
> 
>   The data model supports extensibility by providing the capability to
>   log "optional fields".  Optional fields are those SIP header fields
>   (or field components) that are not mandatory (see Section 8.1 for the
>   mandatory field list).  Optional fields may contain SIP headers or
>   other elements present in a SIP message (for example, the Reason-
>   Phrase element from the Status-Line production rule in RFC 3261
>   [RFC3261]).  Optional fields may also contain additional information
>   that a particular vendor desires to log.  The specific syntax and
>   semantics to be accorded to optional fields MUST be defined by the
>   specific representation format used to generate the SIP CLF record.
>   Finally, [I-D.ietf-sipclf-format] is an example of a representation
>   format draft that provides an ASCII-based encoding scheme.
> 
> In the new text, I have decided to stay away from specifying private
> enterprise numbers for optional fields in the problem-statement
> draft and am leaving it to the specific representation format to
> outline this in more detail.  Clearly, to ensure the least ambiguity
> and most interoperability, it is in the best interest of a
> representation format to choose a mechanism like the private enterprise
> number (and draft-ietf-sipclf-format already does so).
> 
> Please let me know of any comments for proceeding as outlined
> above for the problem-statement draft.  This is the last open issue
> in problem-statement, and once we close this, the draft is in
> a shape to be moved ahead.
> 
> Thank you,
> 
> - 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