
From Internet-Drafts@ietf.org  Tue Mar  8 05:30:06 2011
Return-Path: <Internet-Drafts@ietf.org>
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 2B2DB3A6874; Tue,  8 Mar 2011 05:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, 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 X08ZxH06hr4B; Tue,  8 Mar 2011 05:30:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B09113A6843; Tue,  8 Mar 2011 05:30:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110308133001.7421.33648.idtracker@localhost>
Date: Tue, 08 Mar 2011 05:30:01 -0800
Cc: sip-clf@ietf.org
Subject: [sip-clf] I-D Action:draft-ietf-sipclf-format-00.txt
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: Tue, 08 Mar 2011 13:30:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP Common Log Format Working Group of the IETF.


	Title           : Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)
	Author(s)       : G. Salgueiro, et al.
	Filename        : draft-ietf-sipclf-format-00.txt
	Pages           : 18
	Date            : 2011-03-07

The SIPCLF Workgroup has defined a common log format framework for
Session Initiation Protocol (SIP) servers.  This common log format
mimics the wildly successful event logging mechanism found in well-
known web servers like Apache and web proxies like Squid.  This
document proposes an indexed text encoding format for the SIP Common
Log Format (CLF) that retains the key advantages of a text-based
format, while significantly increasing processing performance over a
purely text-based implementation.  This file format adheres to the
SIP CLF data model and provides an effective encoding scheme for all
mandatory and optional fields that appear in a SIP CLF record.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipclf-format-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-sipclf-format-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-08052935.I-D@ietf.org>


--NextPart--

From anders.nygren@gmail.com  Fri Mar 11 10:00:35 2011
Return-Path: <anders.nygren@gmail.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 0BA7B3A6A5A for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 10:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 KvxqdEtXXZ-c for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 10:00:34 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 84F2D3A6A0C for <sip-clf@ietf.org>; Fri, 11 Mar 2011 10:00:30 -0800 (PST)
Received: by wwa36 with SMTP id 36so2439529wwa.13 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 10:01:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=McnugBreA5svyD9YLFTj/hDloonC40Fpbm/QnG0al8s=; b=k/YqcpU1KYJ8UqdPO3lRq5rQ2nhJPKwC6ZhmjCrsgR25/DF47NuM0nwducCyuTF2ZY ZpVdyjfApfupaI43wTwEJrSghlrAd9Njk6VUOvZlrYIr1Bb1frXXkkYR6Sw2SHyntFva VkMH9RZMoNNUISE6CkRHLmf2g1DQqi0EcKPrM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=N5QzGsWoR2OrvyotZF3UUisMVupDVYwevj90j/1SdDFM2aR3ojxWmhtb9Qaa9KTD+B AIaN+3i69vmoBS+20lHr1qZqZjcbyvhS/vbNK9HhPbtupiEdczZKS/0lNIWxeH4dAC9E OekDG3bQ1TDvy2u/D/OtAQABM5kqWCkCN2Loo=
MIME-Version: 1.0
Received: by 10.216.79.11 with SMTP id h11mr8131022wee.77.1299866509433; Fri, 11 Mar 2011 10:01:49 -0800 (PST)
Received: by 10.216.25.17 with HTTP; Fri, 11 Mar 2011 10:01:49 -0800 (PST)
Date: Fri, 11 Mar 2011 12:01:49 -0600
Message-ID: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: sip-clf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-format-00 comments
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, 11 Mar 2011 18:00:35 -0000

Hi
I am not sure what is the correct way for commenting on the SIP-CLF spec,
so I will do it here until someone tells me that there is a better
place to do it.

I am trying to implement a log reader and writer according to
draft-ietf-sipclf-format-00 and have found a few small errors.

page 8:
   "Record Length (6 bytes):  Hexadecimal encoded total length of this
    log record, including "Flags" and "Record Length" fields, and
    terminating line-feed."

Should that include the version field as well?

page 12:
   "Length Field (2 bytes):  Indicates the length of the value coded in
    this TLV, hexadecimal encoded.  This length does NOT include the
    TLV header."

The length field is shown as 4 bytes in figure 5.

/Anders Nygren

From gsalguei@cisco.com  Fri Mar 11 11:37:37 2011
Return-Path: <gsalguei@cisco.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 3EDFB3A6867 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 11:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.411
X-Spam-Level: 
X-Spam-Status: No, score=-10.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 lYfHTJkS1ZD2 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 11:37:36 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 0F4D93A6806 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 11:37:35 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2BJcspj021447; Fri, 11 Mar 2011 14:38:54 -0500 (EST)
Received: from dhcp-64-102-154-216.cisco.com (dhcp-64-102-154-216.cisco.com [64.102.154.216]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2BJcr3g008375;  Fri, 11 Mar 2011 14:38:54 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com>
Date: Fri, 11 Mar 2011 14:38:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B116D9C8-C234-44C7-B2D4-3F2C9860A8BD@cisco.com>
References: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft-ietf-sipclf-format-00 comments
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, 11 Mar 2011 19:37:37 -0000

Anders -=20

Thanks for providing your feedback, it is much appreciated as we work =
through developing this format. =20

I'm very glad to hear you are implementing this already and would be =
willing to follow up with you offline to get some data points on how you =
decided to do this, how difficult it was, and how useful you found it, =
what you would change, etc.

Comments inline...
On Mar 11, 2011, at 1:01 PM, Anders Nygren wrote:

> Hi
> I am not sure what is the correct way for commenting on the SIP-CLF =
spec,
> so I will do it here until someone tells me that there is a better
> place to do it.
>=20
[GS] This is indeed the place.

> I am trying to implement a log reader and writer according to
> draft-ietf-sipclf-format-00 and have found a few small errors.
>=20
> page 8:
>   "Record Length (6 bytes):  Hexadecimal encoded total length of this
>    log record, including "Flags" and "Record Length" fields, and
>    terminating line-feed."
>=20
> Should that include the version field as well?

[GS] Yes this does include the Version field. It is the length of the =
ENTIRE record including all of <IndexPointers>, <MandatoryFields>, =
<OptionalFields>
The list of items in the text you have selected is not meant to be  =
complete listing of all fields, rather a representative list indicating =
that everything is included. If you think there is value in specifically =
mentioning the Version field, then I will modify the text as follows:

Hexadecimal encoded total length of this log record, including =
"Version", "Record Length", "Flags" fields, and terminating line-feed.


>=20
> page 12:
>   "Length Field (2 bytes):  Indicates the length of the value coded in
>    this TLV, hexadecimal encoded.  This length does NOT include the
>    TLV header."
>=20
> The length field is shown as 4 bytes in figure 5.

Thanks. Great catch.  This is indeed wrong. The figure is correct. I =
will change the text to 4 bytes.

Warm Regards,

Gonzalo
>=20
> /Anders Nygren
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


From vkg@bell-labs.com  Fri Mar 11 12:36:31 2011
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 AF63B3A6A3C for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 12:36:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 DAUJcd8-kFCf for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 12:36:30 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 5B5BF3A6944 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 12:36:29 -0800 (PST)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p2BKbnYC000772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-clf@ietf.org>; Fri, 11 Mar 2011 14:37:49 -0600 (CST)
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p2BKbnK6026136 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 14:37:49 -0600 (CST)
Message-ID: <4D7A8880.50008@bell-labs.com>
Date: Fri, 11 Mar 2011 14:39:28 -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.35
Subject: [sip-clf] sipclf-problem-statement-05
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, 11 Mar 2011 20:36:31 -0000

Folks: I have submitted draft-ietf-sipclf-problem-statement-05.
It is available in the archives [1].

I believe that the document is complete at this point, and will
leave it to the chair to determine the next steps.

The last few open issues we discussed in the Beijing IETF and
the follow-up in January 2011 interim meeting that impacted the
problem-statement draft have been addressed.

More specifically:

   1) Added the 4K limit on headers;
   2) Source and destination fields only have IP addresses now;
   3) Added vendor extensions for extensibility model;
   4) Allowed the logging of bodies.

The diff between -04 and -05 is available at [2].

[1] http://tools.ietf.org/html/draft-ietf-sipclf-problem-statement-05
[2] 
http://tools.ietf.org/rfcdiff?url2=draft-ietf-sipclf-problem-statement-05.txt

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/

From Internet-Drafts@ietf.org  Fri Mar 11 12:45:04 2011
Return-Path: <Internet-Drafts@ietf.org>
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 E7CC73A6A62; Fri, 11 Mar 2011 12:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, 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 y7e-8+5Oa4MB; Fri, 11 Mar 2011 12:45:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B51273A6941; Fri, 11 Mar 2011 12:45:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110311204501.23703.20890.idtracker@localhost>
Date: Fri, 11 Mar 2011 12:45:01 -0800
Cc: sip-clf@ietf.org
Subject: [sip-clf] I-D Action:draft-ietf-sipclf-problem-statement-05.txt
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, 11 Mar 2011 20:45:04 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP Common Log Format Working Group of the IETF.


	Title           : The Common Log Format (CLF) for the Session Initiation Protocol (SIP)
	Author(s)       : V. Gurbani, et al.
	Filename        : draft-ietf-sipclf-problem-statement-05.txt
	Pages           : 34
	Date            : 2011-03-11

Well-known web servers such as Apache and web proxies like Squid
support event logging using a common log format.  The logs produced
using these de-facto standard formats are invaluable to system
administrators for trouble-shooting a server and tool writers to
craft tools that mine the log files and produce reports and trends.
Furthermore, these log files can also be used to train anomaly
detection systems and feed events into a security event management
system.  The Session Initiation Protocol does not have a common log
format, and as a result, each server supports a distinct log format
that makes it unnecessarily complex to produce tools to do trend
analysis and security detection.  We propose a common log file format
for SIP servers that can be used uniformly by proxies, registrars,
redirect servers as well as back-to-back user agents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipclf-problem-statement-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-sipclf-problem-statement-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-11123100.I-D@ietf.org>


--NextPart--

From anders.nygren@gmail.com  Fri Mar 11 14:42:26 2011
Return-Path: <anders.nygren@gmail.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 CC4AF3A6A33 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 14:42:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 dAMWlUMRvB38 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 14:42:25 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 792C33A6A37 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 14:42:25 -0800 (PST)
Received: by wyb42 with SMTP id 42so3217349wyb.31 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 14:43:44 -0800 (PST)
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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=u5dKodDrejHIZDB+RcujL9h0oymx+20hStED/Wh/YY4=; b=IiOfcBoumgt+5Xq+v8KHSMle8JPJVeTECyikoDW8eDOlvQKt01OOd3gOOtZik/WlR0 /KXi+tl8igl8npM71ryzzgLNZnQkbqkESKYII7vIqI6n7KXtAgd94yyy5yvW7tp4Kx2s l1N5ySVcz9oJILR6gOD7Vb06edaHxZCddT/Ls=
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:content-transfer-encoding; b=ExKJjVu0KujO0xLbtehkcJVe4QMScqPJ4hdHSQPP64qj9AnQ7g3X//YDYcyaQUKhNp mVrTHO8sfTfBMyK2QuWcjLDijAdlAUD6SzOUL3gGsaj9jGAG1QLgTqKffFMn6b7ZIhiM zqbnTGBgWsilk/3aoS1SCYcJbPxfuk7xKxK7o=
MIME-Version: 1.0
Received: by 10.216.62.67 with SMTP id x45mr6511997wec.92.1299883424552; Fri, 11 Mar 2011 14:43:44 -0800 (PST)
Received: by 10.216.25.17 with HTTP; Fri, 11 Mar 2011 14:43:44 -0800 (PST)
In-Reply-To: <B116D9C8-C234-44C7-B2D4-3F2C9860A8BD@cisco.com>
References: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com> <B116D9C8-C234-44C7-B2D4-3F2C9860A8BD@cisco.com>
Date: Fri, 11 Mar 2011 16:43:44 -0600
Message-ID: <AANLkTi=c842r67B=BZU0Ep-_+mijeTvBw55M3qTEVvf1@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft-ietf-sipclf-format-00 comments
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, 11 Mar 2011 22:42:26 -0000

One more thing,
page 9,
The text says that fractional seconds is 6 bytes but figure 4 shows 3 bytes=
.

/Anders

On Fri, Mar 11, 2011 at 1:38 PM, Gonzalo Salgueiro <gsalguei@cisco.com> wro=
te:
> Anders -
>
> Thanks for providing your feedback, it is much appreciated as we work thr=
ough developing this format.
>
> I'm very glad to hear you are implementing this already and would be will=
ing to follow up with you offline to get some data points on how you decide=
d to do this, how difficult it was, and how useful you found it, what you w=
ould change, etc.
>
> Comments inline...
> On Mar 11, 2011, at 1:01 PM, Anders Nygren wrote:
>
>> Hi
>> I am not sure what is the correct way for commenting on the SIP-CLF spec=
,
>> so I will do it here until someone tells me that there is a better
>> place to do it.
>>
> [GS] This is indeed the place.
>
>> I am trying to implement a log reader and writer according to
>> draft-ietf-sipclf-format-00 and have found a few small errors.
>>
>> page 8:
>> =A0 "Record Length (6 bytes): =A0Hexadecimal encoded total length of thi=
s
>> =A0 =A0log record, including "Flags" and "Record Length" fields, and
>> =A0 =A0terminating line-feed."
>>
>> Should that include the version field as well?
>
> [GS] Yes this does include the Version field. It is the length of the ENT=
IRE record including all of <IndexPointers>, <MandatoryFields>, <OptionalFi=
elds>
> The list of items in the text you have selected is not meant to be =A0com=
plete listing of all fields, rather a representative list indicating that e=
verything is included. If you think there is value in specifically mentioni=
ng the Version field, then I will modify the text as follows:
>
> Hexadecimal encoded total length of this log record, including "Version",=
 "Record Length", "Flags" fields, and terminating line-feed.
>
>
>>
>> page 12:
>> =A0 "Length Field (2 bytes): =A0Indicates the length of the value coded =
in
>> =A0 =A0this TLV, hexadecimal encoded. =A0This length does NOT include th=
e
>> =A0 =A0TLV header."
>>
>> The length field is shown as 4 bytes in figure 5.
>
> Thanks. Great catch. =A0This is indeed wrong. The figure is correct. I wi=
ll change the text to 4 bytes.
>
> Warm Regards,
>
> Gonzalo
>>
>> /Anders Nygren
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>
>

From gsalguei@cisco.com  Fri Mar 11 15:06:37 2011
Return-Path: <gsalguei@cisco.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 9E8A23A6A91 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 15:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 oLbJYTvdho-3 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 15:06:36 -0800 (PST)
Received: from av-tac-sj.cisco.com (firebird.cisco.com [171.68.227.73]) by core3.amsl.com (Postfix) with ESMTP id 936363A6A58 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 15:06:36 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-sj.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2BN7rWJ003418; Fri, 11 Mar 2011 15:07:54 -0800 (PST)
Received: from dhcp-64-102-154-216.cisco.com (dhcp-64-102-154-216.cisco.com [64.102.154.216]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2BN7kPI017891;  Fri, 11 Mar 2011 18:07:46 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-76--544881130
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTi=c842r67B=BZU0Ep-_+mijeTvBw55M3qTEVvf1@mail.gmail.com>
Date: Fri, 11 Mar 2011 18:07:45 -0500
Message-Id: <7321A81E-1E05-4EBF-8250-1AF9DD09CEA4@cisco.com>
References: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com> <B116D9C8-C234-44C7-B2D4-3F2C9860A8BD@cisco.com> <AANLkTi=c842r67B=BZU0Ep-_+mijeTvBw55M3qTEVvf1@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft-ietf-sipclf-format-00 comments
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, 11 Mar 2011 23:06:37 -0000

--Apple-Mail-76--544881130
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks Anders. This reflected an earlier intent for microsecond accuracy =
that has since been rescinded. I have amended the text.

Regards,

Gonzalo

On Mar 11, 2011, at 5:43 PM, Anders Nygren wrote:

> One more thing,
> page 9,
> The text says that fractional seconds is 6 bytes but figure 4 shows 3 =
bytes.
>=20
> /Anders
>=20
> On Fri, Mar 11, 2011 at 1:38 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Anders -
>>=20
>> Thanks for providing your feedback, it is much appreciated as we work =
through developing this format.
>>=20
>> I'm very glad to hear you are implementing this already and would be =
willing to follow up with you offline to get some data points on how you =
decided to do this, how difficult it was, and how useful you found it, =
what you would change, etc.
>>=20
>> Comments inline...
>> On Mar 11, 2011, at 1:01 PM, Anders Nygren wrote:
>>=20
>>> Hi
>>> I am not sure what is the correct way for commenting on the SIP-CLF =
spec,
>>> so I will do it here until someone tells me that there is a better
>>> place to do it.
>>>=20
>> [GS] This is indeed the place.
>>=20
>>> I am trying to implement a log reader and writer according to
>>> draft-ietf-sipclf-format-00 and have found a few small errors.
>>>=20
>>> page 8:
>>>   "Record Length (6 bytes):  Hexadecimal encoded total length of =
this
>>>    log record, including "Flags" and "Record Length" fields, and
>>>    terminating line-feed."
>>>=20
>>> Should that include the version field as well?
>>=20
>> [GS] Yes this does include the Version field. It is the length of the =
ENTIRE record including all of <IndexPointers>, <MandatoryFields>, =
<OptionalFields>
>> The list of items in the text you have selected is not meant to be  =
complete listing of all fields, rather a representative list indicating =
that everything is included. If you think there is value in specifically =
mentioning the Version field, then I will modify the text as follows:
>>=20
>> Hexadecimal encoded total length of this log record, including =
"Version", "Record Length", "Flags" fields, and terminating line-feed.
>>=20
>>=20
>>>=20
>>> page 12:
>>>   "Length Field (2 bytes):  Indicates the length of the value coded =
in
>>>    this TLV, hexadecimal encoded.  This length does NOT include the
>>>    TLV header."
>>>=20
>>> The length field is shown as 4 bytes in figure 5.
>>=20
>> Thanks. Great catch.  This is indeed wrong. The figure is correct. I =
will change the text to 4 bytes.
>>=20
>> Warm Regards,
>>=20
>> Gonzalo
>>>=20
>>> /Anders Nygren
>>> _______________________________________________
>>> sip-clf mailing list
>>> sip-clf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20


--Apple-Mail-76--544881130
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Thanks Anders. This reflected an earlier intent for microsecond =
accuracy that has since been rescinded. I have amended the =
text.<div><br></div><div>Regards,</div><div><br></div><div>Gonzalo</div><d=
iv><br><div><div><div>On Mar 11, 2011, at 5:43 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>One more thing,<br>page 9,<br>The text says that =
fractional seconds is 6 bytes but figure 4 shows 3 =
bytes.<br><br>/Anders<br><br>On Fri, Mar 11, 2011 at 1:38 PM, Gonzalo =
Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Anders -<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks for =
providing your feedback, it is much appreciated as we work through =
developing this format.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I'm very glad =
to hear you are implementing this already and would be willing to follow =
up with you offline to get some data points on how you decided to do =
this, how difficult it was, and how useful you found it, what you would =
change, etc.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Comments =
inline...<br></blockquote><blockquote type=3D"cite">On Mar 11, 2011, at =
1:01 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Hi<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I am not sure what is the =
correct way for commenting on the SIP-CLF =
spec,<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">so I will do it here until someone tells me that there is =
a better<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">place to do =
it.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote type=3D"cite">[GS]=
 This is indeed the place.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">I am trying to implement a log reader and writer according =
to<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">draft-ietf-sipclf-format-00 and have found a few small =
errors.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">page =
8:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp; "Record Length (6 bytes): &nbsp;Hexadecimal encoded =
total length of this<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">&nbsp; &nbsp;log record, =
including "Flags" and "Record Length" fields, =
and<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp; &nbsp;terminating =
line-feed."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Should that include the version =
field as well?<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">[GS] Yes this =
does include the Version field. It is the length of the ENTIRE record =
including all of &lt;IndexPointers&gt;, &lt;MandatoryFields&gt;, =
&lt;OptionalFields&gt;<br></blockquote><blockquote type=3D"cite">The =
list of items in the text you have selected is not meant to be =
&nbsp;complete listing of all fields, rather a representative list =
indicating that everything is included. If you think there is value in =
specifically mentioning the Version field, then I will modify the text =
as follows:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Hexadecimal =
encoded total length of this log record, including "Version", "Record =
Length", "Flags" fields, and terminating =
line-feed.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">page =
12:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp; "Length Field (2 bytes): &nbsp;Indicates the length =
of the value coded in<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">&nbsp; &nbsp;this TLV, =
hexadecimal encoded. &nbsp;This length does NOT include =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp; &nbsp;TLV =
header."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The length field is shown as 4 =
bytes in figure 5.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks. Great =
catch. &nbsp;This is indeed wrong. The figure is correct. I will change =
the text to 4 bytes.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Warm =
Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">/Anders =
Nygren<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">sip-clf mailing =
list<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></div></=
body></html>=

--Apple-Mail-76--544881130--

From anders.nygren@gmail.com  Fri Mar 11 15:53:07 2011
Return-Path: <anders.nygren@gmail.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 133153A6AAF for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 15:53:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 VOlS5vahEioQ for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 15:53:04 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 682AE3A6A25 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 15:53:04 -0800 (PST)
Received: by wwa36 with SMTP id 36so2648455wwa.13 for <sip-clf@ietf.org>; Fri, 11 Mar 2011 15:54:23 -0800 (PST)
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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aKBxwIR5RVvCUgjzjbLuRlGOJyQeVAsk7AqTqjL+NoI=; b=hvlKJa47BfQpjKbbsMryzeIbtNxTq8u6WdVYEq09ACoFLy0tOD0MX5HQ10Tx73bbkJ 3Jiooyzg8hYlGiWewrRF2WXqX3glHXv5+BmTT6qE59i4HwODc8ffG8uiRgCjaxdcnEHy xvhyq2KNXmps9E2DEj/OXhOl69Pjg/GCBTpas=
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:content-transfer-encoding; b=nd75Vlr0XLWCt5bVeQSjeEO0W5WaTp+7t/jnlThWDklJA3UWukYZU8lKYxry8NWYU7 4mbs9JQI7gQ8FZTHl2GfYegZfV0V7m4aOj9e+2KcPnEVOKZiaJof7HEVZlnYsJYnqGWo aWxhwL+EdgYSH+CjlMv31xwG2f1fiqMI6o1LE=
MIME-Version: 1.0
Received: by 10.216.120.193 with SMTP id p43mr8284702weh.92.1299887663326; Fri, 11 Mar 2011 15:54:23 -0800 (PST)
Received: by 10.216.25.17 with HTTP; Fri, 11 Mar 2011 15:54:23 -0800 (PST)
In-Reply-To: <7321A81E-1E05-4EBF-8250-1AF9DD09CEA4@cisco.com>
References: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com> <B116D9C8-C234-44C7-B2D4-3F2C9860A8BD@cisco.com> <AANLkTi=c842r67B=BZU0Ep-_+mijeTvBw55M3qTEVvf1@mail.gmail.com> <7321A81E-1E05-4EBF-8250-1AF9DD09CEA4@cisco.com>
Date: Fri, 11 Mar 2011 17:54:23 -0600
Message-ID: <AANLkTikyir9cWQTmfQOaOYFq9yhY9QQ+Zh01zDwO4yJG@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft-ietf-sipclf-format-00 comments
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, 11 Mar 2011 23:53:07 -0000

Hi
In chapter 4.1, the text
  "The <IndexPointers> portion of the SIP CLF record is a 64-byte header
   that indicates meta-data about the record."
is repeated before and after the figure 3.

chapter 4.3 figure 5 shows a 0x0A after the TLVs. But I think that
0x0A is not part of the
optional parameters portion but is the termination of the record, and
should be included
even if there are no optional parameters in the record.

/Anders


On Fri, Mar 11, 2011 at 5:07 PM, Gonzalo Salgueiro <gsalguei@cisco.com> wro=
te:
> Thanks Anders. This reflected an earlier intent for microsecond accuracy
> that has since been rescinded. I have amended the text.
> Regards,
> Gonzalo
> On Mar 11, 2011, at 5:43 PM, Anders Nygren wrote:
>
> One more thing,
> page 9,
> The text says that fractional seconds is 6 bytes but figure 4 shows 3 byt=
es.
>
> /Anders
>
> On Fri, Mar 11, 2011 at 1:38 PM, Gonzalo Salgueiro <gsalguei@cisco.com>
> wrote:
>
> Anders -
>
> Thanks for providing your feedback, it is much appreciated as we work
> through developing this format.
>
> I'm very glad to hear you are implementing this already and would be will=
ing
> to follow up with you offline to get some data points on how you decided =
to
> do this, how difficult it was, and how useful you found it, what you woul=
d
> change, etc.
>
> Comments inline...
>
> On Mar 11, 2011, at 1:01 PM, Anders Nygren wrote:
>
> Hi
>
> I am not sure what is the correct way for commenting on the SIP-CLF spec,
>
> so I will do it here until someone tells me that there is a better
>
> place to do it.
>
> [GS] This is indeed the place.
>
> I am trying to implement a log reader and writer according to
>
> draft-ietf-sipclf-format-00 and have found a few small errors.
>
> page 8:
>
> =A0 "Record Length (6 bytes): =A0Hexadecimal encoded total length of this
>
> =A0 =A0log record, including "Flags" and "Record Length" fields, and
>
> =A0 =A0terminating line-feed."
>
> Should that include the version field as well?
>
> [GS] Yes this does include the Version field. It is the length of the ENT=
IRE
> record including all of <IndexPointers>, <MandatoryFields>, <OptionalFiel=
ds>
>
> The list of items in the text you have selected is not meant to be =A0com=
plete
> listing of all fields, rather a representative list indicating that
> everything is included. If you think there is value in specifically
> mentioning the Version field, then I will modify the text as follows:
>
> Hexadecimal encoded total length of this log record, including "Version",
> "Record Length", "Flags" fields, and terminating line-feed.
>
>
>
> page 12:
>
> =A0 "Length Field (2 bytes): =A0Indicates the length of the value coded i=
n
>
> =A0 =A0this TLV, hexadecimal encoded. =A0This length does NOT include the
>
> =A0 =A0TLV header."
>
> The length field is shown as 4 bytes in figure 5.
>
> Thanks. Great catch. =A0This is indeed wrong. The figure is correct. I wi=
ll
> change the text to 4 bytes.
>
> Warm Regards,
>
> Gonzalo
>
> /Anders Nygren
>
> _______________________________________________
>
> sip-clf mailing list
>
> sip-clf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>
>
>

From gsalguei@cisco.com  Fri Mar 11 16:29:55 2011
Return-Path: <gsalguei@cisco.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 C41DD3A6A14 for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 16:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.473
X-Spam-Level: 
X-Spam-Status: No, score=-10.473 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 hm83mGPKRivn for <sip-clf@core3.amsl.com>; Fri, 11 Mar 2011 16:29:54 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 5D26D3A6AEA for <sip-clf@ietf.org>; Fri, 11 Mar 2011 16:29:54 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2C0VDlv017532; Fri, 11 Mar 2011 19:31:13 -0500 (EST)
Received: from dhcp-64-102-154-216.cisco.com (dhcp-64-102-154-216.cisco.com [64.102.154.216]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2C0VCm8016810;  Fri, 11 Mar 2011 19:31:12 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-77--539874836
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTikyir9cWQTmfQOaOYFq9yhY9QQ+Zh01zDwO4yJG@mail.gmail.com>
Date: Fri, 11 Mar 2011 19:31:12 -0500
Message-Id: <2832080D-418A-41DD-80C9-2BA0053C1DBC@cisco.com>
References: <AANLkTimXr_8sHoUCOBkJtLR073=Z-m2A=jqbs4FXyNs+@mail.gmail.com> <B116D9C8-C234-44C7-B2D4-3F2C9860A8BD@cisco.com> <AANLkTi=c842r67B=BZU0Ep-_+mijeTvBw55M3qTEVvf1@mail.gmail.com> <7321A81E-1E05-4EBF-8250-1AF9DD09CEA4@cisco.com> <AANLkTikyir9cWQTmfQOaOYFq9yhY9QQ+Zh01zDwO4yJG@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft-ietf-sipclf-format-00 comments
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: Sat, 12 Mar 2011 00:29:55 -0000

--Apple-Mail-77--539874836
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Anders -=20

Inline..
On Mar 11, 2011, at 6:54 PM, Anders Nygren wrote:

> Hi
> In chapter 4.1, the text
>  "The <IndexPointers> portion of the SIP CLF record is a 64-byte =
header
>   that indicates meta-data about the record."
> is repeated before and after the figure 3.

[GS] Fixed.
>=20
> chapter 4.3 figure 5 shows a 0x0A after the TLVs. But I think that
> 0x0A is not part of the
> optional parameters portion but is the termination of the record, and
> should be included
> even if there are no optional parameters in the record.

[GS] In principle I agree with you. For the sake of graphical =
continuity, I'll need to get creative so that I don't need to represent =
the logical structure of the SIP CLF record as:

        <IndexPointers>
        <MandatoryFields>
        <OptionalFields>
	0x0A

I'll kick it around in my head as to how best represent that.  Great =
catch.

Regards,

Gonzalo
=20
>=20
> /Anders
>=20
>=20
> On Fri, Mar 11, 2011 at 5:07 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Thanks Anders. This reflected an earlier intent for microsecond =
accuracy
>> that has since been rescinded. I have amended the text.
>> Regards,
>> Gonzalo
>> On Mar 11, 2011, at 5:43 PM, Anders Nygren wrote:
>>=20
>> One more thing,
>> page 9,
>> The text says that fractional seconds is 6 bytes but figure 4 shows 3 =
bytes.
>>=20
>> /Anders
>>=20
>> On Fri, Mar 11, 2011 at 1:38 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com>
>> wrote:
>>=20
>> Anders -
>>=20
>> Thanks for providing your feedback, it is much appreciated as we work
>> through developing this format.
>>=20
>> I'm very glad to hear you are implementing this already and would be =
willing
>> to follow up with you offline to get some data points on how you =
decided to
>> do this, how difficult it was, and how useful you found it, what you =
would
>> change, etc.
>>=20
>> Comments inline...
>>=20
>> On Mar 11, 2011, at 1:01 PM, Anders Nygren wrote:
>>=20
>> Hi
>>=20
>> I am not sure what is the correct way for commenting on the SIP-CLF =
spec,
>>=20
>> so I will do it here until someone tells me that there is a better
>>=20
>> place to do it.
>>=20
>> [GS] This is indeed the place.
>>=20
>> I am trying to implement a log reader and writer according to
>>=20
>> draft-ietf-sipclf-format-00 and have found a few small errors.
>>=20
>> page 8:
>>=20
>>   "Record Length (6 bytes):  Hexadecimal encoded total length of this
>>=20
>>    log record, including "Flags" and "Record Length" fields, and
>>=20
>>    terminating line-feed."
>>=20
>> Should that include the version field as well?
>>=20
>> [GS] Yes this does include the Version field. It is the length of the =
ENTIRE
>> record including all of <IndexPointers>, <MandatoryFields>, =
<OptionalFields>
>>=20
>> The list of items in the text you have selected is not meant to be  =
complete
>> listing of all fields, rather a representative list indicating that
>> everything is included. If you think there is value in specifically
>> mentioning the Version field, then I will modify the text as follows:
>>=20
>> Hexadecimal encoded total length of this log record, including =
"Version",
>> "Record Length", "Flags" fields, and terminating line-feed.
>>=20
>>=20
>>=20
>> page 12:
>>=20
>>   "Length Field (2 bytes):  Indicates the length of the value coded =
in
>>=20
>>    this TLV, hexadecimal encoded.  This length does NOT include the
>>=20
>>    TLV header."
>>=20
>> The length field is shown as 4 bytes in figure 5.
>>=20
>> Thanks. Great catch.  This is indeed wrong. The figure is correct. I =
will
>> change the text to 4 bytes.
>>=20
>> Warm Regards,
>>=20
>> Gonzalo
>>=20
>> /Anders Nygren
>>=20
>> _______________________________________________
>>=20
>> sip-clf mailing list
>>=20
>> sip-clf@ietf.org
>>=20
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20
>>=20
>>=20


--Apple-Mail-77--539874836
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Anders -&nbsp;<div><br></div><div>Inline..</div><div><div><div>On Mar =
11, 2011, at 6:54 PM, Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi<br>In chapter 4.1, the text<br> &nbsp;"The =
&lt;IndexPointers&gt; portion of the SIP CLF record is a 64-byte =
header<br> &nbsp;&nbsp;that indicates meta-data about the record."<br>is =
repeated before and after the figure =
3.<br></div></blockquote><div><br></div>[GS] Fixed.<br><blockquote =
type=3D"cite"><div><br>chapter 4.3 figure 5 shows a 0x0A after the TLVs. =
But I think that<br>0x0A is not part of the<br>optional parameters =
portion but is the termination of the record, and<br>should be =
included<br>even if there are no optional parameters in the =
record.<br></div></blockquote><div><br></div>[GS] In principle I agree =
with you. For the sake of graphical continuity, I'll need to get =
creative so that I don't need to represent the logical structure of the =
SIP CLF record as:</div><div><br></div><div><div>&nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp;&lt;IndexPointers&gt;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;&lt;MandatoryFields&gt;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;&lt;OptionalFields&gt;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>0x0A</div><div><br></div><div>I'll kick it around in my head as =
to how best represent that. &nbsp;Great =
catch.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo<=
/div></div><div>&nbsp;<br><div></div><blockquote =
type=3D"cite"><div><br>/Anders<br><br><br>On Fri, Mar 11, 2011 at 5:07 =
PM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Thanks Anders. This reflected an =
earlier intent for microsecond accuracy<br></blockquote><blockquote =
type=3D"cite">that has since been rescinded. I have amended the =
text.<br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote type=3D"cite">On Mar =
11, 2011, at 5:43 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">One more =
thing,<br></blockquote><blockquote type=3D"cite">page =
9,<br></blockquote><blockquote type=3D"cite">The text says that =
fractional seconds is 6 bytes but figure 4 shows 3 =
bytes.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Fri, Mar 11, =
2011 at 1:38 PM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt;<br></blockqu=
ote><blockquote type=3D"cite">wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Anders =
-<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Thanks for providing your feedback, it is much appreciated =
as we work<br></blockquote><blockquote type=3D"cite">through developing =
this format.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I'm very glad =
to hear you are implementing this already and would be =
willing<br></blockquote><blockquote type=3D"cite">to follow up with you =
offline to get some data points on how you decided =
to<br></blockquote><blockquote type=3D"cite">do this, how difficult it =
was, and how useful you found it, what you =
would<br></blockquote><blockquote type=3D"cite">change, =
etc.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Comments =
inline...<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 11, =
2011, at 1:01 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I am not sure =
what is the correct way for commenting on the SIP-CLF =
spec,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">so I will do it =
here until someone tells me that there is a =
better<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">place to do =
it.<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">[GS] This is indeed the =
place.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I am trying to =
implement a log reader and writer according =
to<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">draft-ietf-sipclf-format-00 and have found a few small =
errors.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">page =
8:<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">&nbsp; "Record Length (6 bytes): &nbsp;Hexadecimal encoded =
total length of this<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">&nbsp; =
&nbsp;log record, including "Flags" and "Record Length" fields, =
and<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">&nbsp; &nbsp;terminating =
line-feed."<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Should that =
include the version field as well?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">[GS] Yes this =
does include the Version field. It is the length of the =
ENTIRE<br></blockquote><blockquote type=3D"cite">record including all of =
&lt;IndexPointers&gt;, &lt;MandatoryFields&gt;, =
&lt;OptionalFields&gt;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The list of =
items in the text you have selected is not meant to be =
&nbsp;complete<br></blockquote><blockquote type=3D"cite">listing of all =
fields, rather a representative list indicating =
that<br></blockquote><blockquote type=3D"cite">everything is included. =
If you think there is value in specifically<br></blockquote><blockquote =
type=3D"cite">mentioning the Version field, then I will modify the text =
as follows:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Hexadecimal =
encoded total length of this log record, including =
"Version",<br></blockquote><blockquote type=3D"cite">"Record Length", =
"Flags" fields, and terminating line-feed.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">page =
12:<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">&nbsp; "Length Field (2 bytes): &nbsp;Indicates the =
length of the value coded in<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">&nbsp; =
&nbsp;this TLV, hexadecimal encoded. &nbsp;This length does NOT include =
the<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">&nbsp; &nbsp;TLV header."<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The length =
field is shown as 4 bytes in figure 5.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks. Great =
catch. &nbsp;This is indeed wrong. The figure is correct. I =
will<br></blockquote><blockquote type=3D"cite">change the text to 4 =
bytes.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Warm =
Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">/Anders =
Nygren<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">sip-clf mailing list<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-77--539874836--

From Internet-Drafts@ietf.org  Mon Mar 14 12:45:05 2011
Return-Path: <Internet-Drafts@ietf.org>
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 21E193A6D9A; Mon, 14 Mar 2011 12:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, 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 3U33DO3qH8yr; Mon, 14 Mar 2011 12:45:04 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EEFA83A6E92; Mon, 14 Mar 2011 12:45:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314194501.5173.67472.idtracker@localhost>
Date: Mon, 14 Mar 2011 12:45:01 -0700
Cc: sip-clf@ietf.org
Subject: [sip-clf] I-D Action:draft-ietf-sipclf-format-01.txt
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: Mon, 14 Mar 2011 19:45:05 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP Common Log Format Working Group of the IETF.


	Title           : Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)
	Author(s)       : G. Salgueiro, et al.
	Filename        : draft-ietf-sipclf-format-01.txt
	Pages           : 23
	Date            : 2011-03-14

The SIPCLF Workgroup has defined a common log format framework for
Session Initiation Protocol (SIP) servers.  This common log format
mimics the wildly successful event logging mechanism found in well-
known web servers like Apache and web proxies like Squid.  This
document proposes an indexed text encoding format for the SIP Common
Log Format (CLF) that retains the key advantages of a text-based
format, while significantly increasing processing performance over a
purely text-based implementation.  This file format adheres to the
SIP CLF data model and provides an effective encoding scheme for all
mandatory and optional fields that appear in a SIP CLF record.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipclf-format-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-sipclf-format-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14124412.I-D@ietf.org>


--NextPart--

From anders.nygren@gmail.com  Mon Mar 14 19:51:48 2011
Return-Path: <anders.nygren@gmail.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 920293A6973 for <sip-clf@core3.amsl.com>; Mon, 14 Mar 2011 19:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 x-AwRRAEOdTT for <sip-clf@core3.amsl.com>; Mon, 14 Mar 2011 19:51:47 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 1FA7C3A6AD4 for <sip-clf@ietf.org>; Mon, 14 Mar 2011 19:51:46 -0700 (PDT)
Received: by wyb42 with SMTP id 42so151254wyb.31 for <sip-clf@ietf.org>; Mon, 14 Mar 2011 19:53:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=0lC8phyNX9aAd0xrHu4dMoidcNj4wRMwhoTIAKN66xU=; b=J8UG1g9Otx74TqxkSpj8YJkQ+bv5wkXBqtOlYWb2K+MYYbqktPUx+MJuxwpvUGkN/a +jxRgwAcG8mPI330B0CG6HsxWC2Hp2kzqTMxi+8Ph4AIEhHNbQgzlOPr6G7xTDGdwDpH Zzxq0O2Q2sqh+lKkiHGevErw6Hcz8VtNwpJjw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lQf1pkyBwNAjR8UrrC6URttdz5jiNsXfqvxm1583m3hT7+zMqb9alM3rGLqCNGfmyT 8zq9WW8j858jVGHGRxWh56jrpG+9b6W6kXlJoJg6aH5LawbkgsqFSTDEVT/mwtX9I/ow YfBYrRKHJAy7dxI7sUQZImMtkEDrXA+GCYvOY=
MIME-Version: 1.0
Received: by 10.216.62.137 with SMTP id y9mr2951254wec.107.1300157590916; Mon, 14 Mar 2011 19:53:10 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Mon, 14 Mar 2011 19:53:10 -0700 (PDT)
Date: Mon, 14 Mar 2011 20:53:10 -0600
Message-ID: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: sip-clf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 02:51:48 -0000

Hi
I must say that I really dislike the proposed format for vendor specific fields.
Having a variable length "tag" before the length field means that it
is necessary
to scan the tag looking for the ',' just to find the length field.

There is no simple way to tell he difference between a sip-clf
optional field and
a vendor specific optional field. So it will always be necessary to scan the
record looking for the ',' .
Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
standard optional field without a lot of work.

I think a better way to do this would be similar to diameter RFC3588, ch 4.1.
Then we could have just one format for standard optional fields and vendor
specific fields

byte 1  0x09
byte 2-5 Tag (Hex)
byte 6-9 VendorId
byte 10 0x2C
byte 11-14 Length (Hex)
byte 15 0x2C
byte 16-.. Value (variable length)

Where VendorId is the IANA assigned "SMI Network Management Private
Enterprise Codes"  [ASSIGNNO] value.
VendorId=0 is used a for the standard optional fields defined in SIP-CLF.

/Anders

From gsalguei@cisco.com  Mon Mar 14 23:18:35 2011
Return-Path: <gsalguei@cisco.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 3E18E3A68AB for <sip-clf@core3.amsl.com>; Mon, 14 Mar 2011 23:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 gD3Kot0xECGB for <sip-clf@core3.amsl.com>; Mon, 14 Mar 2011 23:18:33 -0700 (PDT)
Received: from av-tac-sj.cisco.com (firebird.cisco.com [171.68.227.73]) by core3.amsl.com (Postfix) with ESMTP id C073B3A680B for <sip-clf@ietf.org>; Mon, 14 Mar 2011 23:18:33 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-sj.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2F6Jtk3010316; Mon, 14 Mar 2011 23:19:55 -0700 (PDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2F6JmqL001309;  Tue, 15 Mar 2011 02:19:49 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--259758488
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com>
Date: Tue, 15 Mar 2011 02:19:48 -0400
Message-Id: <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 06:18:35 -0000

--Apple-Mail-3--259758488
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks for raising your concerns Anders.=20

As you know, this draft was just published today and its principal =
intent was to formulate an initial solution for SIP CLF extensibility.

A little history:
The current proposal for Vendor-specific extensions using a Syslog-like =
approach (i.e. name@<private enterprise number>) was something proposed =
over email and decided at the last SIPCLF Interim meeting in January. So =
this really is a first pass at implementing vendor-specificied optional =
fields.

That said, I'll comment inline to your points

On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:

> Hi
> I must say that I really dislike the proposed format for vendor =
specific fields.
> Having a variable length "tag" before the length field means that it
> is necessary
> to scan the tag looking for the ',' just to find the length field.
>=20
You make a valid point. I'd like others to weigh in here and comment on =
whether they think this is a serious performance limitation. I'll =
propose this as a discussion point for the upcoming meeting in Prague. =
The reason for the variable length tag is that it is based on the SD-ID =
format from Syslog, which is variable in length (i.e. the unrestricted =
name before the '@').  I think using a Vendor-ID based on a PEN is =
common sense, so I'd like to stick with that if possible. We could =
decide on a fixed length name (or number to parallel the tag from the =
Pre-Defined Optional Fields) followed by four byte PEN.

> There is no simple way to tell he difference between a sip-clf
> optional field and
> a vendor specific optional field. So it will always be necessary to =
scan the
> record looking for the ',' .
> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal
> ID, "0001,FFFF,@12345" which would be difficult to differentiate from =
a
> standard optional field without a lot of work.
>=20
Remember that that this draft restricts the scope of the syntax to the =
2nd format definition of SD-IDs in RFC5424. Thus, the above wouldn't be =
a legal vendor-specified optional field since "0001" doesn't contain an =
'@', which is mandatory for a Vendor-ID as defined in the draft. So =
there should be no confusion there as the Vendor-ID from the =
vendor-specified optional fields and the Tag from the pre-defined =
optional fields can never be the same.

> I think a better way to do this would be similar to diameter RFC3588, =
ch 4.1.
> Then we could have just one format for standard optional fields and =
vendor
> specific fields
>=20
> byte 1  0x09
> byte 2-5 Tag (Hex)
> byte 6-9 VendorId
> byte 10 0x2C
> byte 11-14 Length (Hex)
> byte 15 0x2C
> byte 16-.. Value (variable length)
>=20
> Where VendorId is the IANA assigned "SMI Network Management Private
> Enterprise Codes"  [ASSIGNNO] value.
> VendorId=3D0 is used a for the standard optional fields defined in =
SIP-CLF.

I know that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can be used in this way (as apparently DIAMETER did), then I think this =
proposal is very reasonable. This unifies both optional field types into =
a single seamless representation. I'll let others, like Chris Lonvick, =
more knowledgeable than I weigh in on this as well to confirm my =
thoughts.

Regards,

Gonzalo
>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-3--259758488
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Thanks for raising your concerns Anders.&nbsp;<div><br></div><div>As =
you know, this draft was just published today and its principal intent =
was to formulate an initial solution for SIP CLF =
extensibility.</div><div><br></div><div>A little history:</div><div>The =
current proposal for Vendor-specific extensions using a Syslog-like =
approach (i.e.&nbsp;<span class=3D"Apple-style-span" style=3D"font-family:=
 monospace; white-space: pre; ">name@&lt;private enterprise number&gt;) =
was something proposed over email and decided at the last SIPCLF Interim =
meeting in January. So this really is a first pass at implementing =
vendor-specificied optional fields.</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; white-space: =
pre; "><br></span></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;">That said, I'll comment inline to your =
points<br></span></font><div><br></div><div><div>On Mar 14, 2011, at =
10:53 PM, Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Hi<br>I=
 must say that I really dislike the proposed format for vendor specific =
fields.<br>Having a variable length "tag" before the length field means =
that it<br>is necessary<br>to scan the tag looking for the ',' just to =
find the length field.<br><br></div></blockquote>You make a valid point. =
I'd like others to weigh in here and comment on whether they think this =
is a serious performance limitation. I'll propose this as a discussion =
point for the upcoming meeting in Prague. The reason for the variable =
length tag is that it is based on the SD-ID format from Syslog, which is =
variable in length (i.e. the unrestricted name before the '@'). &nbsp;I =
think using a Vendor-ID based on a PEN is common sense, so I'd like to =
stick with that if possible. We could decide on a fixed length name (or =
number to parallel the tag from the Pre-Defined Optional Fields) =
followed by four byte PEN.</div><div><br><blockquote =
type=3D"cite"><div>There is no simple way to tell he difference between =
a sip-clf<br>optional field and<br>a vendor specific optional field. So =
it will always be necessary to scan the<br>record looking for the ',' =
.<br>Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal<br>ID, "0001,FFFF,@12345" which would be difficult to =
differentiate from a<br>standard optional field without a lot of =
work.<br><br></div></blockquote>Remember that that this draft restricts =
the scope of the syntax to the 2nd format definition of SD-IDs in =
RFC5424. Thus, the above wouldn't be a legal vendor-specified optional =
field since "0001" doesn't contain an '@', which is mandatory for a =
Vendor-ID as defined in the draft. So there should be no confusion there =
as the Vendor-ID from the vendor-specified optional fields and the Tag =
from the pre-defined optional fields can never be the =
same.</div><div><br><blockquote type=3D"cite"><div>I think a better way =
to do this would be similar to diameter RFC3588, ch 4.1.<br>Then we =
could have just one format for standard optional fields and =
vendor<br>specific fields<br><br>byte 1 &nbsp;0x09<br>byte 2-5 Tag =
(Hex)<br>byte 6-9 VendorId<br>byte 10 0x2C<br>byte 11-14 Length =
(Hex)<br>byte 15 0x2C<br>byte 16-.. Value (variable length)<br><br>Where =
VendorId is the IANA assigned "SMI Network Management =
Private<br>Enterprise Codes" &nbsp;[ASSIGNNO] value.<br>VendorId=3D0 is =
used a for the standard optional fields defined in =
SIP-CLF.<br></div></blockquote><div><br></div>I know that PEN =3D 0 is a =
Reserved value and if it is confirmed that it can be used in this way =
(as apparently DIAMETER did), then I think this proposal is very =
reasonable. This unifies both optional field types into a single =
seamless representation. I'll let others, like Chris Lonvick, more =
knowledgeable than I weigh in on this as well to confirm my =
thoughts.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonza=
lo<br><blockquote =
type=3D"cite"><div><br>/Anders<br>________________________________________=
_______<br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></div></body>=
</html>=

--Apple-Mail-3--259758488--

From anders.nygren@gmail.com  Tue Mar 15 07:37:22 2011
Return-Path: <anders.nygren@gmail.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 8D3C93A6D85 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 07:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 O14am3sse+HI for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 07:37:21 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 0755B3A6D82 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 07:37:20 -0700 (PDT)
Received: by ewy19 with SMTP id 19so235981ewy.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 07:38:45 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LzycJU/zTsG6Uh2W+byxKepzaKUunQnR91DE41asHlM=; b=K7i6CIRjRb86E+mrxSswxgRwVkuANEDdkqa7QgOOuNBm4AtjbTCZ0bZCYP2XxFKEtJ aiQ1H8tua2Fafm5H7MZ+zWTkeyGgKWm/Y+QVs7RgxoB36g4TQyZ4dWx1HK7hcinRIjLT eriLk5xJUH+fmITsySLw1NMc+grhS8vLNkuAo=
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:content-transfer-encoding; b=xFjvhU+Qr9B30jsmvIFFmovMDs8A9pei3kccAXbyMHDn7P7rQgtDoeVxCGO2z2p4jP IBibQWDhfTKl3UHBxfS9e9V4zApf//NZBtDCioAns1AFpXyT04A1Kahe2fIXLVvZOpHb CnYpHzv0xY0abtJDtA/m06clMruKpVvgJ/wY0=
MIME-Version: 1.0
Received: by 10.216.221.92 with SMTP id q70mr11761725wep.107.1300199924174; Tue, 15 Mar 2011 07:38:44 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 07:38:44 -0700 (PDT)
In-Reply-To: <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com>
Date: Tue, 15 Mar 2011 08:38:44 -0600
Message-ID: <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 14:37:22 -0000

On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wr=
ote:
> Thanks for raising your concerns Anders.
> As you know, this draft was just published today and its principal intent
> was to formulate an initial solution for SIP CLF extensibility.
> A little history:
> The current proposal for Vendor-specific extensions using a Syslog-like
> approach (i.e.=A0name@<private enterprise number>) was something proposed=
 over
> email and decided at the last SIPCLF Interim meeting in January. So this
> really is a first pass at implementing vendor-specificied optional fields=
.
> That said, I'll comment inline to your points
>
> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>
> Hi
> I must say that I really dislike the proposed format for vendor specific
> fields.
> Having a variable length "tag" before the length field means that it
> is necessary
> to scan the tag looking for the ',' just to find the length field.
>
> You make a valid point. I'd like others to weigh in here and comment on
> whether they think this is a serious performance limitation. I'll propose
> this as a discussion point for the upcoming meeting in Prague. The reason
> for the variable length tag is that it is based on the SD-ID format from
> Syslog, which is variable in length (i.e. the unrestricted name before th=
e
> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so I'd=
 like
> to stick with that if possible. We could decide on a fixed length name (o=
r
> number to parallel the tag from the Pre-Defined Optional Fields) followed=
 by
> four byte PEN.
>
> There is no simple way to tell he difference between a sip-clf
> optional field and
> a vendor specific optional field. So it will always be necessary to scan =
the
> record looking for the ',' .
> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
> standard optional field without a lot of work.
>
> Remember that that this draft restricts the scope of the syntax to the 2n=
d
> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a leg=
al
> vendor-specified optional field since "0001" doesn't contain an '@', whic=
h
> is mandatory for a Vendor-ID as defined in the draft. So there should be =
no
> confusion there as the Vendor-ID from the vendor-specified optional field=
s
> and the Tag from the pre-defined optional fields can never be the same.
>

I think that You did not understand the point I was trying to make.
As I understand the specification in the 2nd format definition of SD-IDs in
RFC5424, comma "," is allowed in the name part. So
"0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficult=
 to
differentiate from a standard optional field with tag=3D"0001", length=3D"F=
FFF" and
a value starting with "@<Vendor-ID>"

> I think a better way to do this would be similar to diameter RFC3588, ch
> 4.1.
> Then we could have just one format for standard optional fields and vendo=
r
> specific fields
>
> byte 1 =A00x09
> byte 2-5 Tag (Hex)
> byte 6-9 VendorId
> byte 10 0x2C
> byte 11-14 Length (Hex)
> byte 15 0x2C
> byte 16-.. Value (variable length)
>
> Where VendorId is the IANA assigned "SMI Network Management Private
> Enterprise Codes" =A0[ASSIGNNO] value.
> VendorId=3D0 is used a for the standard optional fields defined in SIP-CL=
F.
>
> I know that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can
> be used in this way (as apparently DIAMETER did), then I think this propo=
sal
> is very reasonable. This unifies both optional field types into a single
> seamless representation. I'll let others, like Chris Lonvick, more
> knowledgeable than I weigh in on this as well to confirm my thoughts.
> Regards,
> Gonzalo
>
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>

From gsalguei@cisco.com  Tue Mar 15 07:53:51 2011
Return-Path: <gsalguei@cisco.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 EF04D3A6D91 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 07:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.354
X-Spam-Level: 
X-Spam-Status: No, score=-9.354 tagged_above=-999 required=5 tests=[AWL=-1.056, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8]
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 8thtHc2M6xbz for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 07:53:49 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id DE8333A6DDC for <sip-clf@ietf.org>; Tue, 15 Mar 2011 07:53:48 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FEtCtM022525; Tue, 15 Mar 2011 10:55:12 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FEtBg6021193;  Tue, 15 Mar 2011 10:55:12 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-8--228835721
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com>
Date: Tue, 15 Mar 2011 10:55:11 -0400
Message-Id: <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 14:53:51 -0000

--Apple-Mail-8--228835721
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Anders -=20

You are absolutely right, I did misunderstand your point the first time =
around. I thought you were saying '001' was the Vendor-ID, when in fact =
you were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name =
in front of the '@' is only restricted in the following way:

- MUST be printable US-ASCII strings
- MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF %d61), a closing brace (']', ABNF %d93), a quote-character ('"', =
ABNF %d34), whitespace, or control characters.

it indeed means your example is a valid Vendor-ID and could cause =
confusion. While this would be very unlikely to happen in practice [I =
can't imagine an implementer intentionally doing this], it is undesired. =
I think this fact makes your original proposal that much more elegant =
than the existing one.

Regards,=20

Gonzalo


On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:

> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Thanks for raising your concerns Anders.
>> As you know, this draft was just published today and its principal =
intent
>> was to formulate an initial solution for SIP CLF extensibility.
>> A little history:
>> The current proposal for Vendor-specific extensions using a =
Syslog-like
>> approach (i.e. name@<private enterprise number>) was something =
proposed over
>> email and decided at the last SIPCLF Interim meeting in January. So =
this
>> really is a first pass at implementing vendor-specificied optional =
fields.
>> That said, I'll comment inline to your points
>>=20
>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>=20
>> Hi
>> I must say that I really dislike the proposed format for vendor =
specific
>> fields.
>> Having a variable length "tag" before the length field means that it
>> is necessary
>> to scan the tag looking for the ',' just to find the length field.
>>=20
>> You make a valid point. I'd like others to weigh in here and comment =
on
>> whether they think this is a serious performance limitation. I'll =
propose
>> this as a discussion point for the upcoming meeting in Prague. The =
reason
>> for the variable length tag is that it is based on the SD-ID format =
from
>> Syslog, which is variable in length (i.e. the unrestricted name =
before the
>> '@').  I think using a Vendor-ID based on a PEN is common sense, so =
I'd like
>> to stick with that if possible. We could decide on a fixed length =
name (or
>> number to parallel the tag from the Pre-Defined Optional Fields) =
followed by
>> four byte PEN.
>>=20
>> There is no simple way to tell he difference between a sip-clf
>> optional field and
>> a vendor specific optional field. So it will always be necessary to =
scan the
>> record looking for the ',' .
>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal
>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from =
a
>> standard optional field without a lot of work.
>>=20
>> Remember that that this draft restricts the scope of the syntax to =
the 2nd
>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a =
legal
>> vendor-specified optional field since "0001" doesn't contain an '@', =
which
>> is mandatory for a Vendor-ID as defined in the draft. So there should =
be no
>> confusion there as the Vendor-ID from the vendor-specified optional =
fields
>> and the Tag from the pre-defined optional fields can never be the =
same.
>>=20
>=20
> I think that You did not understand the point I was trying to make.
> As I understand the specification in the 2nd format definition of =
SD-IDs in
> RFC5424, comma "," is allowed in the name part. So
> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very =
difficult to
> differentiate from a standard optional field with tag=3D"0001", =
length=3D"FFFF" and
> a value starting with "@<Vendor-ID>"
>=20
>> I think a better way to do this would be similar to diameter RFC3588, =
ch
>> 4.1.
>> Then we could have just one format for standard optional fields and =
vendor
>> specific fields
>>=20
>> byte 1  0x09
>> byte 2-5 Tag (Hex)
>> byte 6-9 VendorId
>> byte 10 0x2C
>> byte 11-14 Length (Hex)
>> byte 15 0x2C
>> byte 16-.. Value (variable length)
>>=20
>> Where VendorId is the IANA assigned "SMI Network Management Private
>> Enterprise Codes"  [ASSIGNNO] value.
>> VendorId=3D0 is used a for the standard optional fields defined in =
SIP-CLF.
>>=20
>> I know that PEN =3D 0 is a Reserved value and if it is confirmed that =
it can
>> be used in this way (as apparently DIAMETER did), then I think this =
proposal
>> is very reasonable. This unifies both optional field types into a =
single
>> seamless representation. I'll let others, like Chris Lonvick, more
>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>> Regards,
>> Gonzalo
>>=20
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20


--Apple-Mail-8--228835721
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Anders -&nbsp;<div><br></div><div>You are absolutely right, I did =
misunderstand your point the first time around. I thought you were =
saying '001' was the Vendor-ID, when in fact you were saying =
that&nbsp;"0001,FFFF,@&lt;PEN&gt;" is the Vendor-ID. Since the name in =
front of the '@' is only restricted in the following =
way:</div><div><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; white-space: pre; "><br></span></div><div>-&nbsp;<span =
class=3D"Apple-style-span" style=3D"font-family: monospace; white-space: =
pre; ">MUST be printable US-ASCII strings</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; white-space: =
pre; ">- MUST </span><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; white-space: pre; ">NOT contain an =
at-sign ('@', ABNF %d64), an equal-sign ('=3D', ABNF </span><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; white-space: =
pre; ">%d61), a closing brace (']', ABNF %d93), a quote-character ('"', =
</span><span class=3D"Apple-style-span" style=3D"font-family: monospace; =
white-space: pre; ">ABNF %d34), whitespace, or control =
characters.</span></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; white-space: pre; =
"><br></span></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;">it indeed means your example is a valid Vendor-ID and could cause =
confusion. While this would be very unlikely to happen in practice [I =
can't imagine an implementer intentionally doing this], it is undesired. =
I think this fact makes your original proposal that much more elegant =
than the existing one.</span></font></div><div><font =
class=3D"Apple-style-span" face=3D"monospace"><span =
class=3D"Apple-style-span" style=3D"white-space: =
pre;"><br></span></font></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;">Regards, </span></font></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;"><br></span></font></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;">Gonzalo</span></font></div><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;"><br></span></font></div><div><div><br></div><div><div>On Mar 15, =
2011, at 10:38 AM, Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Thanks for raising your concerns =
Anders.<br></blockquote><blockquote type=3D"cite">As you know, this =
draft was just published today and its principal =
intent<br></blockquote><blockquote type=3D"cite">was to formulate an =
initial solution for SIP CLF extensibility.<br></blockquote><blockquote =
type=3D"cite">A little history:<br></blockquote><blockquote =
type=3D"cite">The current proposal for Vendor-specific extensions using =
a Syslog-like<br></blockquote><blockquote type=3D"cite">approach =
(i.e.&nbsp;name@&lt;private enterprise number&gt;) was something =
proposed over<br></blockquote><blockquote type=3D"cite">email and =
decided at the last SIPCLF Interim meeting in January. So =
this<br></blockquote><blockquote type=3D"cite">really is a first pass at =
implementing vendor-specificied optional =
fields.<br></blockquote><blockquote type=3D"cite">That said, I'll =
comment inline to your points<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 14, =
2011, at 10:53 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">I must say =
that I really dislike the proposed format for vendor =
specific<br></blockquote><blockquote =
type=3D"cite">fields.<br></blockquote><blockquote type=3D"cite">Having a =
variable length "tag" before the length field means that =
it<br></blockquote><blockquote type=3D"cite">is =
necessary<br></blockquote><blockquote type=3D"cite">to scan the tag =
looking for the ',' just to find the length =
field.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">You make a =
valid point. I'd like others to weigh in here and comment =
on<br></blockquote><blockquote type=3D"cite">whether they think this is =
a serious performance limitation. I'll =
propose<br></blockquote><blockquote type=3D"cite">this as a discussion =
point for the upcoming meeting in Prague. The =
reason<br></blockquote><blockquote type=3D"cite">for the variable length =
tag is that it is based on the SD-ID format =
from<br></blockquote><blockquote type=3D"cite">Syslog, which is variable =
in length (i.e. the unrestricted name before =
the<br></blockquote><blockquote type=3D"cite">'@'). &nbsp;I think using =
a Vendor-ID based on a PEN is common sense, so I'd =
like<br></blockquote><blockquote type=3D"cite">to stick with that if =
possible. We could decide on a fixed length name =
(or<br></blockquote><blockquote type=3D"cite">number to parallel the tag =
from the Pre-Defined Optional Fields) followed =
by<br></blockquote><blockquote type=3D"cite">four byte =
PEN.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">There is no =
simple way to tell he difference between a =
sip-clf<br></blockquote><blockquote type=3D"cite">optional field =
and<br></blockquote><blockquote type=3D"cite">a vendor specific optional =
field. So it will always be necessary to scan =
the<br></blockquote><blockquote type=3D"cite">record looking for the ',' =
.<br></blockquote><blockquote type=3D"cite">Actually looking at RFC 5424 =
ch 4.3.2 it looks like this would be a legal<br></blockquote><blockquote =
type=3D"cite">ID, "0001,FFFF,@12345" which would be difficult to =
differentiate from a<br></blockquote><blockquote type=3D"cite">standard =
optional field without a lot of work.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Remember that =
that this draft restricts the scope of the syntax to the =
2nd<br></blockquote><blockquote type=3D"cite">format definition of =
SD-IDs in RFC5424. Thus, the above wouldn't be a =
legal<br></blockquote><blockquote type=3D"cite">vendor-specified =
optional field since "0001" doesn't contain an '@', =
which<br></blockquote><blockquote type=3D"cite">is mandatory for a =
Vendor-ID as defined in the draft. So there should be =
no<br></blockquote><blockquote type=3D"cite">confusion there as the =
Vendor-ID from the vendor-specified optional =
fields<br></blockquote><blockquote type=3D"cite">and the Tag from the =
pre-defined optional fields can never be the =
same.<br></blockquote><blockquote type=3D"cite"><br></blockquote><br>I =
think that You did not understand the point I was trying to make.<br>As =
I understand the specification in the 2nd format definition of SD-IDs =
in<br>RFC5424, comma "," is allowed in the name part. =
So<br>"0001,FFFF,@&lt;Vendor-ID&gt;" would be a legal tag, that would be =
very difficult to<br>differentiate from a standard optional field with =
tag=3D"0001", length=3D"FFFF" and<br>a value starting with =
"@&lt;Vendor-ID&gt;"<br><br><blockquote type=3D"cite">I think a better =
way to do this would be similar to diameter RFC3588, =
ch<br></blockquote><blockquote =
type=3D"cite">4.1.<br></blockquote><blockquote type=3D"cite">Then we =
could have just one format for standard optional fields and =
vendor<br></blockquote><blockquote type=3D"cite">specific =
fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 1 =
&nbsp;0x09<br></blockquote><blockquote type=3D"cite">byte 2-5 Tag =
(Hex)<br></blockquote><blockquote type=3D"cite">byte 6-9 =
VendorId<br></blockquote><blockquote type=3D"cite">byte 10 =
0x2C<br></blockquote><blockquote type=3D"cite">byte 11-14 Length =
(Hex)<br></blockquote><blockquote type=3D"cite">byte 15 =
0x2C<br></blockquote><blockquote type=3D"cite">byte 16-.. Value =
(variable length)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Where VendorId =
is the IANA assigned "SMI Network Management =
Private<br></blockquote><blockquote type=3D"cite">Enterprise Codes" =
&nbsp;[ASSIGNNO] value.<br></blockquote><blockquote =
type=3D"cite">VendorId=3D0 is used a for the standard optional fields =
defined in SIP-CLF.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I know that PEN =
=3D 0 is a Reserved value and if it is confirmed that it =
can<br></blockquote><blockquote type=3D"cite">be used in this way (as =
apparently DIAMETER did), then I think this =
proposal<br></blockquote><blockquote type=3D"cite">is very reasonable. =
This unifies both optional field types into a =
single<br></blockquote><blockquote type=3D"cite">seamless =
representation. I'll let others, like Chris Lonvick, =
more<br></blockquote><blockquote type=3D"cite">knowledgeable than I =
weigh in on this as well to confirm my =
thoughts.<br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-8--228835721--

From anders.nygren@gmail.com  Tue Mar 15 09:43:51 2011
Return-Path: <anders.nygren@gmail.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 B7F1A3A6D52 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 09:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_LOW=-1]
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 I4I2EGGsNHQy for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 09:43:50 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 37B0B3A690F for <sip-clf@ietf.org>; Tue, 15 Mar 2011 09:43:50 -0700 (PDT)
Received: by wyb42 with SMTP id 42so809555wyb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 09:45:15 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=AGw5M99X+t9nWiw5twIJeZ/2KLoQDdWvynNA+aKnk5o=; b=rP9JUXhILHAUexc/UXMqB+n/iJMakczQzcsb5BgPeXasRCmp7B6QUwfE8bL6zlrjD/ IXAYoAVVtuqd9cZcmIimw2bZeljLXHTcl4qdfrJ6sJ+kHx4MRkDkiQ9sloGVestWIeie 4zXYo6ZJ9HVnJh9CbLb2af3GNU5dsEuzAtZ40=
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:content-transfer-encoding; b=klZ84ShuYiAdRvji/2X0nw41FglhdVeaEbACAd6Mj3zX1dRzS3pdj5vPELPy/jsV8E LGU6oiJTD9L/svsVmSOZMmgrG9G/tsHucDx2AMGnMHrwgnyvkFmmjjZ3exK15E4VRpR/ rORCeXFTM35q51ed0p6NV/1RrWC7eOBYBvqpI=
MIME-Version: 1.0
Received: by 10.216.62.137 with SMTP id y9mr3715787wec.107.1300207514753; Tue, 15 Mar 2011 09:45:14 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 09:45:14 -0700 (PDT)
In-Reply-To: <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com>
Date: Tue, 15 Mar 2011 10:45:14 -0600
Message-ID: <AANLkTi=Cj3urLqDZW9MCzzJGauWMPKgiATGo3_z4sa_z@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 16:43:51 -0000

I would like to modify/extend my original proposal with the following
two alternatives.

1, Two TLV pointers.
Background:
The current draft-01 contains only one TLV pointer, "TLV Start
Pointer", that points
to the optional parameters block. This block contains both the standard opt=
ional
parameters and the vendor extensions.

Change:
Add a new pointer "Vendor Extensions Pointer". So "TLV Start Pointer" point=
s to
the standard optional parameters. And "Vendor Extensions Pointer" points to
the vendor extensions block.
The contents of the Standard optional parameters have the format
proposed in draft-01,
and the contents of the Vendor extension block have the format I
proposed earlier.

byte 1  0x09
byte 2-5 Tag (Hex)
byte 6-9 VendorId
byte 10 0x2C
byte 11-14 Length (Hex)
byte 15 0x2C
byte 16-.. Value (variable length)

2, Common format
Keep one common format for both standard optional parameters and
vendor extensions
more in line with diameter, RFC3588, ch 4.1

0x09                1 byte
vendor flag        1 byte     "s" =3D standard or "v" =3D vendor
Tag (Hex)          4 bytes
0x2C                1 byte
Length (Hex)     4 bytes
[VendorId          4 bytes]  Only present if vendor flag=3D"v"
0x2C
Value (variable length)

/Anders

On Tue, Mar 15, 2011 at 8:55 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wro=
te:
> Anders -
> You are absolutely right, I did misunderstand your point the first time
> around. I thought you were saying '001' was the Vendor-ID, when in fact y=
ou
> were saying that=A0"0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in
> front of the '@' is only restricted in the following way:
> -=A0MUST be printable US-ASCII strings
> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', ABN=
F
> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d3=
4),
> whitespace, or control characters.
> it indeed means your example is a valid Vendor-ID and could cause confusi=
on.
> While this would be very unlikely to happen in practice [I can't imagine =
an
> implementer intentionally doing this], it is undesired. I think this fact
> makes your original proposal that much more elegant than the existing one=
.
> Regards,
> Gonzalo
>
> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>
> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com>
> wrote:
>
> Thanks for raising your concerns Anders.
>
> As you know, this draft was just published today and its principal intent
>
> was to formulate an initial solution for SIP CLF extensibility.
>
> A little history:
>
> The current proposal for Vendor-specific extensions using a Syslog-like
>
> approach (i.e.=A0name@<private enterprise number>) was something proposed=
 over
>
> email and decided at the last SIPCLF Interim meeting in January. So this
>
> really is a first pass at implementing vendor-specificied optional fields=
.
>
> That said, I'll comment inline to your points
>
> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>
> Hi
>
> I must say that I really dislike the proposed format for vendor specific
>
> fields.
>
> Having a variable length "tag" before the length field means that it
>
> is necessary
>
> to scan the tag looking for the ',' just to find the length field.
>
> You make a valid point. I'd like others to weigh in here and comment on
>
> whether they think this is a serious performance limitation. I'll propose
>
> this as a discussion point for the upcoming meeting in Prague. The reason
>
> for the variable length tag is that it is based on the SD-ID format from
>
> Syslog, which is variable in length (i.e. the unrestricted name before th=
e
>
> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so I'd=
 like
>
> to stick with that if possible. We could decide on a fixed length name (o=
r
>
> number to parallel the tag from the Pre-Defined Optional Fields) followed=
 by
>
> four byte PEN.
>
> There is no simple way to tell he difference between a sip-clf
>
> optional field and
>
> a vendor specific optional field. So it will always be necessary to scan =
the
>
> record looking for the ',' .
>
> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
>
> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>
> standard optional field without a lot of work.
>
> Remember that that this draft restricts the scope of the syntax to the 2n=
d
>
> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a leg=
al
>
> vendor-specified optional field since "0001" doesn't contain an '@', whic=
h
>
> is mandatory for a Vendor-ID as defined in the draft. So there should be =
no
>
> confusion there as the Vendor-ID from the vendor-specified optional field=
s
>
> and the Tag from the pre-defined optional fields can never be the same.
>
>
> I think that You did not understand the point I was trying to make.
> As I understand the specification in the 2nd format definition of SD-IDs =
in
> RFC5424, comma "," is allowed in the name part. So
> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficu=
lt
> to
> differentiate from a standard optional field with tag=3D"0001", length=3D=
"FFFF"
> and
> a value starting with "@<Vendor-ID>"
>
> I think a better way to do this would be similar to diameter RFC3588, ch
>
> 4.1.
>
> Then we could have just one format for standard optional fields and vendo=
r
>
> specific fields
>
> byte 1 =A00x09
>
> byte 2-5 Tag (Hex)
>
> byte 6-9 VendorId
>
> byte 10 0x2C
>
> byte 11-14 Length (Hex)
>
> byte 15 0x2C
>
> byte 16-.. Value (variable length)
>
> Where VendorId is the IANA assigned "SMI Network Management Private
>
> Enterprise Codes" =A0[ASSIGNNO] value.
>
> VendorId=3D0 is used a for the standard optional fields defined in SIP-CL=
F.
>
> I know that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can
>
> be used in this way (as apparently DIAMETER did), then I think this propo=
sal
>
> is very reasonable. This unifies both optional field types into a single
>
> seamless representation. I'll let others, like Chris Lonvick, more
>
> knowledgeable than I weigh in on this as well to confirm my thoughts.
>
> Regards,
>
> Gonzalo
>
> /Anders
>
> _______________________________________________
>
> sip-clf mailing list
>
> sip-clf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>
>
>

From gsalguei@cisco.com  Tue Mar 15 10:13:03 2011
Return-Path: <gsalguei@cisco.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 757373A6DD2 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 10:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.237
X-Spam-Level: 
X-Spam-Status: No, score=-9.237 tagged_above=-999 required=5 tests=[AWL=-0.939, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8]
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 inZR2YPflY-S for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 10:13:01 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 4840B3A6BE3 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 10:12:59 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FHEM7v006265; Tue, 15 Mar 2011 13:14:22 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FHEJCs018999;  Tue, 15 Mar 2011 13:14:19 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-11--220487783
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTi=Cj3urLqDZW9MCzzJGauWMPKgiATGo3_z4sa_z@mail.gmail.com>
Date: Tue, 15 Mar 2011 13:14:19 -0400
Message-Id: <BCF3AE7B-DA85-476C-AC61-3383D8D6D6DF@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <AANLkTi=Cj3urLqDZW9MCzzJGauWMPKgiATGo3_z4sa_z@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 17:13:03 -0000

--Apple-Mail-11--220487783
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Anders -=20

This would make good fodder for discussion by the group on the list as =
well as in Prague.  It would be my preference not to further overload =
the current Flags field in <IndexPointers> with additional and =
additional flag with pre-defined, vendor-specified, and both settings. I =
think the most elegant solution is:
=20
1. The single format you proposed for both Pre-Defined and =
Vendor-Specific optional fields (where, if allowed, PEN=3D0 signifies =
Pre-Defined optional field).
2. Based on group consensus, decide whether (a) we stick with a single =
pointer is needed in <IndexPointers> to indicate the beginning of the =
optional fields (i.e. both pre-defined and vendor-specified) or whether =
(b) there is value in adding an additional pointer added to =
<IndexPointers>, where one pointer points to the start of the =
Pre-Defined optional fields and the other points to the start of =
Vendor-specified fields.

Sound reasonable?

Regards,

Gonzalo
On Mar 15, 2011, at 12:45 PM, Anders Nygren wrote:

> I would like to modify/extend my original proposal with the following
> two alternatives.
>=20
> 1, Two TLV pointers.
> Background:
> The current draft-01 contains only one TLV pointer, "TLV Start
> Pointer", that points
> to the optional parameters block. This block contains both the =
standard optional
> parameters and the vendor extensions.
>=20
> Change:
> Add a new pointer "Vendor Extensions Pointer". So "TLV Start Pointer" =
points to
> the standard optional parameters. And "Vendor Extensions Pointer" =
points to
> the vendor extensions block.
> The contents of the Standard optional parameters have the format
> proposed in draft-01,
> and the contents of the Vendor extension block have the format I
> proposed earlier.
>=20
> byte 1  0x09
> byte 2-5 Tag (Hex)
> byte 6-9 VendorId
> byte 10 0x2C
> byte 11-14 Length (Hex)
> byte 15 0x2C
> byte 16-.. Value (variable length)
>=20
> 2, Common format
> Keep one common format for both standard optional parameters and
> vendor extensions
> more in line with diameter, RFC3588, ch 4.1
>=20
> 0x09                1 byte
> vendor flag        1 byte     "s" =3D standard or "v" =3D vendor
> Tag (Hex)          4 bytes
> 0x2C                1 byte
> Length (Hex)     4 bytes
> [VendorId          4 bytes]  Only present if vendor flag=3D"v"
> 0x2C
> Value (variable length)
>=20
> /Anders
>=20
> On Tue, Mar 15, 2011 at 8:55 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Anders -
>> You are absolutely right, I did misunderstand your point the first =
time
>> around. I thought you were saying '001' was the Vendor-ID, when in =
fact you
>> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name =
in
>> front of the '@' is only restricted in the following way:
>> - MUST be printable US-ASCII strings
>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF
>> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF =
%d34),
>> whitespace, or control characters.
>> it indeed means your example is a valid Vendor-ID and could cause =
confusion.
>> While this would be very unlikely to happen in practice [I can't =
imagine an
>> implementer intentionally doing this], it is undesired. I think this =
fact
>> makes your original proposal that much more elegant than the existing =
one.
>> Regards,
>> Gonzalo
>>=20
>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>=20
>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com>
>> wrote:
>>=20
>> Thanks for raising your concerns Anders.
>>=20
>> As you know, this draft was just published today and its principal =
intent
>>=20
>> was to formulate an initial solution for SIP CLF extensibility.
>>=20
>> A little history:
>>=20
>> The current proposal for Vendor-specific extensions using a =
Syslog-like
>>=20
>> approach (i.e. name@<private enterprise number>) was something =
proposed over
>>=20
>> email and decided at the last SIPCLF Interim meeting in January. So =
this
>>=20
>> really is a first pass at implementing vendor-specificied optional =
fields.
>>=20
>> That said, I'll comment inline to your points
>>=20
>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>=20
>> Hi
>>=20
>> I must say that I really dislike the proposed format for vendor =
specific
>>=20
>> fields.
>>=20
>> Having a variable length "tag" before the length field means that it
>>=20
>> is necessary
>>=20
>> to scan the tag looking for the ',' just to find the length field.
>>=20
>> You make a valid point. I'd like others to weigh in here and comment =
on
>>=20
>> whether they think this is a serious performance limitation. I'll =
propose
>>=20
>> this as a discussion point for the upcoming meeting in Prague. The =
reason
>>=20
>> for the variable length tag is that it is based on the SD-ID format =
from
>>=20
>> Syslog, which is variable in length (i.e. the unrestricted name =
before the
>>=20
>> '@').  I think using a Vendor-ID based on a PEN is common sense, so =
I'd like
>>=20
>> to stick with that if possible. We could decide on a fixed length =
name (or
>>=20
>> number to parallel the tag from the Pre-Defined Optional Fields) =
followed by
>>=20
>> four byte PEN.
>>=20
>> There is no simple way to tell he difference between a sip-clf
>>=20
>> optional field and
>>=20
>> a vendor specific optional field. So it will always be necessary to =
scan the
>>=20
>> record looking for the ',' .
>>=20
>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal
>>=20
>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from =
a
>>=20
>> standard optional field without a lot of work.
>>=20
>> Remember that that this draft restricts the scope of the syntax to =
the 2nd
>>=20
>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a =
legal
>>=20
>> vendor-specified optional field since "0001" doesn't contain an '@', =
which
>>=20
>> is mandatory for a Vendor-ID as defined in the draft. So there should =
be no
>>=20
>> confusion there as the Vendor-ID from the vendor-specified optional =
fields
>>=20
>> and the Tag from the pre-defined optional fields can never be the =
same.
>>=20
>>=20
>> I think that You did not understand the point I was trying to make.
>> As I understand the specification in the 2nd format definition of =
SD-IDs in
>> RFC5424, comma "," is allowed in the name part. So
>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very =
difficult
>> to
>> differentiate from a standard optional field with tag=3D"0001", =
length=3D"FFFF"
>> and
>> a value starting with "@<Vendor-ID>"
>>=20
>> I think a better way to do this would be similar to diameter RFC3588, =
ch
>>=20
>> 4.1.
>>=20
>> Then we could have just one format for standard optional fields and =
vendor
>>=20
>> specific fields
>>=20
>> byte 1  0x09
>>=20
>> byte 2-5 Tag (Hex)
>>=20
>> byte 6-9 VendorId
>>=20
>> byte 10 0x2C
>>=20
>> byte 11-14 Length (Hex)
>>=20
>> byte 15 0x2C
>>=20
>> byte 16-.. Value (variable length)
>>=20
>> Where VendorId is the IANA assigned "SMI Network Management Private
>>=20
>> Enterprise Codes"  [ASSIGNNO] value.
>>=20
>> VendorId=3D0 is used a for the standard optional fields defined in =
SIP-CLF.
>>=20
>> I know that PEN =3D 0 is a Reserved value and if it is confirmed that =
it can
>>=20
>> be used in this way (as apparently DIAMETER did), then I think this =
proposal
>>=20
>> is very reasonable. This unifies both optional field types into a =
single
>>=20
>> seamless representation. I'll let others, like Chris Lonvick, more
>>=20
>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>> /Anders
>>=20
>> _______________________________________________
>>=20
>> sip-clf mailing list
>>=20
>> sip-clf@ietf.org
>>=20
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20
>>=20
>>=20


--Apple-Mail-11--220487783
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Anders -&nbsp;<div><br></div><div>This would make good fodder for =
discussion by the group on the list as well as in Prague. &nbsp;It would =
be my preference not to further overload the current Flags field in =
&lt;IndexPointers&gt; with additional and additional flag with =
pre-defined, vendor-specified, and both settings. I think the most =
elegant solution is:</div><div>&nbsp;</div><div>1. The single format you =
proposed for both Pre-Defined and Vendor-Specific optional fields =
(where, if allowed, PEN=3D0 signifies Pre-Defined optional =
field).</div><div>2. Based on group consensus, decide whether (a) we =
stick with a single pointer is needed in &lt;IndexPointers&gt; to =
indicate the beginning of the optional fields (i.e. both pre-defined and =
vendor-specified) or whether (b) there is value in adding an additional =
pointer added to &lt;IndexPointers&gt;, where one pointer points to the =
start of the Pre-Defined optional fields and the other points to the =
start of Vendor-specified fields.</div><div><br></div><div>Sound =
reasonable?</div><div><br></div><div>Regards,</div><div><br></div><div>Gon=
zalo<br><div><div>On Mar 15, 2011, at 12:45 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>I would like to modify/extend my original proposal =
with the following<br>two alternatives.<br><br>1, Two TLV =
pointers.<br>Background:<br>The current draft-01 contains only one TLV =
pointer, "TLV Start<br>Pointer", that points<br>to the optional =
parameters block. This block contains both the standard =
optional<br>parameters and the vendor extensions.<br><br>Change:<br>Add =
a new pointer "Vendor Extensions Pointer". So "TLV Start Pointer" points =
to<br>the standard optional parameters. And "Vendor Extensions Pointer" =
points to<br>the vendor extensions block.<br>The contents of the =
Standard optional parameters have the format<br>proposed in =
draft-01,<br>and the contents of the Vendor extension block have the =
format I<br>proposed earlier.<br><br>byte 1 &nbsp;0x09<br>byte 2-5 Tag =
(Hex)<br>byte 6-9 VendorId<br>byte 10 0x2C<br>byte 11-14 Length =
(Hex)<br>byte 15 0x2C<br>byte 16-.. Value (variable length)<br><br>2, =
Common format<br>Keep one common format for both standard optional =
parameters and<br>vendor extensions<br>more in line with diameter, =
RFC3588, ch 4.1<br><br>0x09 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;1 byte<br>vendor flag =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1 byte =
&nbsp;&nbsp;&nbsp;&nbsp;"s" =3D standard or "v" =3D vendor<br>Tag (Hex) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4 bytes<br>0x2C =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;1 byte<br>Length (Hex) &nbsp;&nbsp;&nbsp;&nbsp;4 =
bytes<br>[VendorId =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4 bytes] =
&nbsp;Only present if vendor flag=3D"v"<br>0x2C<br>Value (variable =
length)<br><br>/Anders<br><br>On Tue, Mar 15, 2011 at 8:55 AM, Gonzalo =
Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Anders -<br></blockquote><blockquote =
type=3D"cite">You are absolutely right, I did misunderstand your point =
the first time<br></blockquote><blockquote type=3D"cite">around. I =
thought you were saying '001' was the Vendor-ID, when in fact =
you<br></blockquote><blockquote type=3D"cite">were saying =
that&nbsp;"0001,FFFF,@&lt;PEN&gt;" is the Vendor-ID. Since the name =
in<br></blockquote><blockquote type=3D"cite">front of the '@' is only =
restricted in the following way:<br></blockquote><blockquote =
type=3D"cite">-&nbsp;MUST be printable US-ASCII =
strings<br></blockquote><blockquote type=3D"cite">- MUST NOT contain an =
at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF<br></blockquote><blockquote type=3D"cite">%d61), a closing brace =
(']', ABNF %d93), a quote-character ('"', ABNF =
%d34),<br></blockquote><blockquote type=3D"cite">whitespace, or control =
characters.<br></blockquote><blockquote type=3D"cite">it indeed means =
your example is a valid Vendor-ID and could cause =
confusion.<br></blockquote><blockquote type=3D"cite">While this would be =
very unlikely to happen in practice [I can't imagine =
an<br></blockquote><blockquote type=3D"cite">implementer intentionally =
doing this], it is undesired. I think this =
fact<br></blockquote><blockquote type=3D"cite">makes your original =
proposal that much more elegant than the existing =
one.<br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 15, =
2011, at 10:38 AM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Tue, Mar 15, =
2011 at 12:19 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt;<br></blockqu=
ote><blockquote type=3D"cite">wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks for =
raising your concerns Anders.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">As you know, =
this draft was just published today and its principal =
intent<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">was to =
formulate an initial solution for SIP CLF =
extensibility.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">A little =
history:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The current =
proposal for Vendor-specific extensions using a =
Syslog-like<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">approach =
(i.e.&nbsp;name@&lt;private enterprise number&gt;) was something =
proposed over<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">email and =
decided at the last SIPCLF Interim meeting in January. So =
this<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">really is a =
first pass at implementing vendor-specificied optional =
fields.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">That said, I'll =
comment inline to your points<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 14, =
2011, at 10:53 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I must say that =
I really dislike the proposed format for vendor =
specific<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">fields.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Having a =
variable length "tag" before the length field means that =
it<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">is necessary<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">to scan the tag =
looking for the ',' just to find the length =
field.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">You make a =
valid point. I'd like others to weigh in here and comment =
on<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">whether they think this is a serious performance =
limitation. I'll propose<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">this as a =
discussion point for the upcoming meeting in Prague. The =
reason<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">for the =
variable length tag is that it is based on the SD-ID format =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Syslog, which =
is variable in length (i.e. the unrestricted name before =
the<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">'@'). &nbsp;I think using a Vendor-ID based on a PEN is =
common sense, so I'd like<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">to stick with =
that if possible. We could decide on a fixed length name =
(or<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">number to parallel the tag from the Pre-Defined Optional =
Fields) followed by<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">four byte =
PEN.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">There is no =
simple way to tell he difference between a =
sip-clf<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">optional field =
and<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">a vendor specific optional field. So it will always be =
necessary to scan the<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">record looking =
for the ',' .<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Actually =
looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">ID, =
"0001,FFFF,@12345" which would be difficult to differentiate from =
a<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">standard optional field without a lot of =
work.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Remember that =
that this draft restricts the scope of the syntax to the =
2nd<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">format definition of SD-IDs in RFC5424. Thus, the above =
wouldn't be a legal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">vendor-specified =
optional field since "0001" doesn't contain an '@', =
which<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is mandatory =
for a Vendor-ID as defined in the draft. So there should be =
no<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">confusion there as the Vendor-ID from the vendor-specified =
optional fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">and the Tag =
from the pre-defined optional fields can never be the =
same.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think that =
You did not understand the point I was trying to =
make.<br></blockquote><blockquote type=3D"cite">As I understand the =
specification in the 2nd format definition of SD-IDs =
in<br></blockquote><blockquote type=3D"cite">RFC5424, comma "," is =
allowed in the name part. So<br></blockquote><blockquote =
type=3D"cite">"0001,FFFF,@&lt;Vendor-ID&gt;" would be a legal tag, that =
would be very difficult<br></blockquote><blockquote =
type=3D"cite">to<br></blockquote><blockquote type=3D"cite">differentiate =
from a standard optional field with tag=3D"0001", =
length=3D"FFFF"<br></blockquote><blockquote =
type=3D"cite">and<br></blockquote><blockquote type=3D"cite">a value =
starting with "@&lt;Vendor-ID&gt;"<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think a =
better way to do this would be similar to diameter RFC3588, =
ch<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">4.1.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Then we could =
have just one format for standard optional fields and =
vendor<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">specific =
fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 1 =
&nbsp;0x09<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 2-5 Tag =
(Hex)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 6-9 =
VendorId<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 10 =
0x2C<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 11-14 =
Length (Hex)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 15 =
0x2C<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 16-.. =
Value (variable length)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Where VendorId =
is the IANA assigned "SMI Network Management =
Private<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Enterprise =
Codes" &nbsp;[ASSIGNNO] value.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VendorId=3D0 is =
used a for the standard optional fields defined in =
SIP-CLF.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I know that PEN =
=3D 0 is a Reserved value and if it is confirmed that it =
can<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">be used in this way (as apparently DIAMETER did), then I =
think this proposal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is very =
reasonable. This unifies both optional field types into a =
single<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">seamless =
representation. I'll let others, like Chris Lonvick, =
more<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">knowledgeable =
than I weigh in on this as well to confirm my =
thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">sip-clf mailing list<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-11--220487783--

From anders.nygren@gmail.com  Tue Mar 15 10:39:32 2011
Return-Path: <anders.nygren@gmail.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 4AE173A6DFB for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 10:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[AWL=-0.920, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_LOW=-1]
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 1m2B0zKxzkPe for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 10:39:31 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 52F803A6D21 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 10:39:30 -0700 (PDT)
Received: by wyb42 with SMTP id 42so872993wyb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 10:40:55 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=GYLygb/8KLCsVcDBMT59zngQ7tDfqGj7cmviwaFlP+U=; b=mxFb1GwhEARePNSIxel535Aqh4jQ0PXlciB6khsPvyGTJAkekth5x2uDBYDZzm06Jl zUALSLebdfqyfV++eLsiJQHYneN2U5375Si0V6zL9c9wU1PWL4bHIN4wnbNNX1eGJ4Nk KrAuI3Hms9Vlc0EwZwx0mI7pjlfooHowFDzO0=
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:content-transfer-encoding; b=ilUpdK079jNrnYhOVIJaiexN9XgCi8VcKBvEucH5HJfMAUYCFCuqhr3WflJUHwTwxK DK/dz4o6k4L/cyklZxZZ7Ko6M26MWw1XV9kneWVjsJBaxhQQwioS19/RHuI1f6sh0AFQ 9tPSmbqt05JKhOnzn0WAEH9mixkI5+HoXhYrw=
MIME-Version: 1.0
Received: by 10.216.79.11 with SMTP id h11mr12068220wee.77.1300210854940; Tue, 15 Mar 2011 10:40:54 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 10:40:54 -0700 (PDT)
In-Reply-To: <BCF3AE7B-DA85-476C-AC61-3383D8D6D6DF@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <AANLkTi=Cj3urLqDZW9MCzzJGauWMPKgiATGo3_z4sa_z@mail.gmail.com> <BCF3AE7B-DA85-476C-AC61-3383D8D6D6DF@cisco.com>
Date: Tue, 15 Mar 2011 11:40:54 -0600
Message-ID: <AANLkTi=vBdqoxuRRdSQp6TvaAVfYwEEbiNk3kH6JC2tW@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 17:39:32 -0000

On Tue, Mar 15, 2011 at 11:14 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wr=
ote:
> Anders -
> This would make good fodder for discussion by the group on the list as we=
ll
> as in Prague. =A0It would be my preference not to further overload the cu=
rrent
> Flags field in <IndexPointers> with additional and additional flag with
> pre-defined, vendor-specified, and both settings.

The vendor flag I mentioned would not be in the Flags field in <IndexPointe=
rs>.
It would be in the TLV structure. So that PEN=3D0 would not  need to be use=
d
to indicate that it is a standard optional parameter.


> I think the most elegant
> solution is:
>
> 1. The single format you proposed for both Pre-Defined and Vendor-Specifi=
c
> optional fields (where, if allowed, PEN=3D0 signifies Pre-Defined optiona=
l
> field).
> 2. Based on group consensus, decide whether (a) we stick with a single
> pointer is needed in <IndexPointers> to indicate the beginning of the
> optional fields (i.e. both pre-defined and vendor-specified) or whether (=
b)
> there is value in adding an additional pointer added to <IndexPointers>,
> where one pointer points to the start of the Pre-Defined optional fields =
and
> the other points to the start of Vendor-specified fields.
> Sound reasonable?

Yes.
The purpose of the extra pointer was to make parsing simpler in the case wh=
ere
there are two different formats for the standard optional parameters and th=
e
vendor extensions. If they have the same format I see no reason for the ext=
ra
pointer.

/Anders


> Regards,
> Gonzalo
> On Mar 15, 2011, at 12:45 PM, Anders Nygren wrote:
>
> I would like to modify/extend my original proposal with the following
> two alternatives.
>
> 1, Two TLV pointers.
> Background:
> The current draft-01 contains only one TLV pointer, "TLV Start
> Pointer", that points
> to the optional parameters block. This block contains both the standard
> optional
> parameters and the vendor extensions.
>
> Change:
> Add a new pointer "Vendor Extensions Pointer". So "TLV Start Pointer" poi=
nts
> to
> the standard optional parameters. And "Vendor Extensions Pointer" points =
to
> the vendor extensions block.
> The contents of the Standard optional parameters have the format
> proposed in draft-01,
> and the contents of the Vendor extension block have the format I
> proposed earlier.
>
> byte 1 =A00x09
> byte 2-5 Tag (Hex)
> byte 6-9 VendorId
> byte 10 0x2C
> byte 11-14 Length (Hex)
> byte 15 0x2C
> byte 16-.. Value (variable length)
>
> 2, Common format
> Keep one common format for both standard optional parameters and
> vendor extensions
> more in line with diameter, RFC3588, ch 4.1
>
> 0x09 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A01 byte
> vendor flag =A0=A0=A0=A0=A0=A0=A01 byte =A0=A0=A0=A0"s" =3D standard or "=
v" =3D vendor
> Tag (Hex) =A0=A0=A0=A0=A0=A0=A0=A0=A04 bytes
> 0x2C =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A01 byte
> Length (Hex) =A0=A0=A0=A04 bytes
> [VendorId =A0=A0=A0=A0=A0=A0=A0=A0=A04 bytes] =A0Only present if vendor f=
lag=3D"v"
> 0x2C
> Value (variable length)
>
> /Anders
>
> On Tue, Mar 15, 2011 at 8:55 AM, Gonzalo Salgueiro <gsalguei@cisco.com>
> wrote:
>
> Anders -
>
> You are absolutely right, I did misunderstand your point the first time
>
> around. I thought you were saying '001' was the Vendor-ID, when in fact y=
ou
>
> were saying that=A0"0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in
>
> front of the '@' is only restricted in the following way:
>
> -=A0MUST be printable US-ASCII strings
>
> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', ABN=
F
>
> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d3=
4),
>
> whitespace, or control characters.
>
> it indeed means your example is a valid Vendor-ID and could cause confusi=
on.
>
> While this would be very unlikely to happen in practice [I can't imagine =
an
>
> implementer intentionally doing this], it is undesired. I think this fact
>
> makes your original proposal that much more elegant than the existing one=
.
>
> Regards,
>
> Gonzalo
>
> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>
> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com>
>
> wrote:
>
> Thanks for raising your concerns Anders.
>
> As you know, this draft was just published today and its principal intent
>
> was to formulate an initial solution for SIP CLF extensibility.
>
> A little history:
>
> The current proposal for Vendor-specific extensions using a Syslog-like
>
> approach (i.e.=A0name@<private enterprise number>) was something proposed=
 over
>
> email and decided at the last SIPCLF Interim meeting in January. So this
>
> really is a first pass at implementing vendor-specificied optional fields=
.
>
> That said, I'll comment inline to your points
>
> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>
> Hi
>
> I must say that I really dislike the proposed format for vendor specific
>
> fields.
>
> Having a variable length "tag" before the length field means that it
>
> is necessary
>
> to scan the tag looking for the ',' just to find the length field.
>
> You make a valid point. I'd like others to weigh in here and comment on
>
> whether they think this is a serious performance limitation. I'll propose
>
> this as a discussion point for the upcoming meeting in Prague. The reason
>
> for the variable length tag is that it is based on the SD-ID format from
>
> Syslog, which is variable in length (i.e. the unrestricted name before th=
e
>
> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so I'd=
 like
>
> to stick with that if possible. We could decide on a fixed length name (o=
r
>
> number to parallel the tag from the Pre-Defined Optional Fields) followed=
 by
>
> four byte PEN.
>
> There is no simple way to tell he difference between a sip-clf
>
> optional field and
>
> a vendor specific optional field. So it will always be necessary to scan =
the
>
> record looking for the ',' .
>
> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
>
> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>
> standard optional field without a lot of work.
>
> Remember that that this draft restricts the scope of the syntax to the 2n=
d
>
> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a leg=
al
>
> vendor-specified optional field since "0001" doesn't contain an '@', whic=
h
>
> is mandatory for a Vendor-ID as defined in the draft. So there should be =
no
>
> confusion there as the Vendor-ID from the vendor-specified optional field=
s
>
> and the Tag from the pre-defined optional fields can never be the same.
>
>
> I think that You did not understand the point I was trying to make.
>
> As I understand the specification in the 2nd format definition of SD-IDs =
in
>
> RFC5424, comma "," is allowed in the name part. So
>
> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficu=
lt
>
> to
>
> differentiate from a standard optional field with tag=3D"0001", length=3D=
"FFFF"
>
> and
>
> a value starting with "@<Vendor-ID>"
>
> I think a better way to do this would be similar to diameter RFC3588, ch
>
> 4.1.
>
> Then we could have just one format for standard optional fields and vendo=
r
>
> specific fields
>
> byte 1 =A00x09
>
> byte 2-5 Tag (Hex)
>
> byte 6-9 VendorId
>
> byte 10 0x2C
>
> byte 11-14 Length (Hex)
>
> byte 15 0x2C
>
> byte 16-.. Value (variable length)
>
> Where VendorId is the IANA assigned "SMI Network Management Private
>
> Enterprise Codes" =A0[ASSIGNNO] value.
>
> VendorId=3D0 is used a for the standard optional fields defined in SIP-CL=
F.
>
> I know that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can
>
> be used in this way (as apparently DIAMETER did), then I think this propo=
sal
>
> is very reasonable. This unifies both optional field types into a single
>
> seamless representation. I'll let others, like Chris Lonvick, more
>
> knowledgeable than I weigh in on this as well to confirm my thoughts.
>
> Regards,
>
> Gonzalo
>
> /Anders
>
> _______________________________________________
>
> sip-clf mailing list
>
> sip-clf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>
>
>
>
>

From anders.nygren@gmail.com  Tue Mar 15 10:48:02 2011
Return-Path: <anders.nygren@gmail.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 E2B693A6A24 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 10:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level: 
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 tTVd+iYbSphn for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 10:48:02 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id DFE0A3A6971 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 10:48:01 -0700 (PDT)
Received: by wyb42 with SMTP id 42so882372wyb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 10:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=Z/YZ/bOUDsduzDqHJEq5DonDve2VMpa1kiKSXqEI+ZY=; b=sYaUbabUUJFk0LgXBm2U+dB3ZF64RZOyeljkE5uj20aE1HX5KW3yge0IYO5YtzeIfe R1yvTLvtoxDnBQvSwbk19rJKRYPgZ5QEh8Z4QSV0D2FcGOmJdZkvG+456GcCkJjbUnzC 4otfRLUyF77HTtG1l9DTfLN777A/ul2jh5pCI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dVNiSvnssIJR93NMY4u8Ox3ZLtoGopBikGXdizalTtRJoeKtbGVPyqCT4lJavZ3kFT RDr/trmoBV4XMTib1KDycDPZuAIzqNt1xume0fZPZMDlta7i92zCT6YVK9pWM2egMHQK 3MsOBCxnjGNm+nhMxhco4+cN6HYiZhGkF98CI=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr3803744wej.77.1300211366528; Tue, 15 Mar 2011 10:49:26 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 10:49:26 -0700 (PDT)
Date: Tue, 15 Mar 2011 11:49:26 -0600
Message-ID: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 17:48:03 -0000

Hi
I will start writing one email for each issue in order to make it
easier to track the different discussions.

I would like to propose that the Flag Field is moved from the
<IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
will be pure metadata that can be ignored if wanted and all interesting
data about the message is in the second line of the record.

Also I think it would be good to change the Sent/Received flag from

Sent/Received flag

         u = received UDP mesage
         t = received TCP mesage
         l = received TLS mesage
         U = sent UDP mesage
         T = sent TCP mesage
         L = sent TLS mesage

To
Sent/Received flag [1 byte]
         r = received message
         s = sent message

And add
Protocol [1 byte]
         u = UDP
         t = TCP
         l = TLS

Since the proposed CLF already requires quite a lot of space there is
little reason to
try to pack different parameters into the same byte.

/Anders

From anders.nygren@gmail.com  Tue Mar 15 11:01:21 2011
Return-Path: <anders.nygren@gmail.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 542793A6DE3 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 11:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.27
X-Spam-Level: 
X-Spam-Status: No, score=-3.27 tagged_above=-999 required=5 tests=[AWL=0.329,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WhFQRyuvVKqt for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 11:01:20 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 5C3743A6971 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 11:01:20 -0700 (PDT)
Received: by wyb42 with SMTP id 42so896213wyb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 11:02:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ssMeXtAXVU+WY2/dxALFVjX464Tm6+PrzWH39ETLX10=; b=Y9FDg44sn2Mo6ByaA8HQRAk2iyekmJxnuPkIX6nNcSAlsGSMYsOa/UOfVHWie4T51K VHJ7F3GKetj+mDZLwezGesFkJagGjQhOacR7m/FKYrjpc5pFmZUAbyjqkAZNUl4HZSIO TW7/FUYSQSNH8NbQswvQnQ43Xhji7xjTYNbzc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=UeLkzUg9faR+2mgIxU3VIY5TCp6kXC/lBih/JfLm76bnnjokGihMikT3JcopjLub3x SlS1jPtbQmq8lFLgk61VrPNw06X9bPV1t0mnYEUTYfeSDcsZ4z06ltdi27Y+NV15CKwE Y/gwrQv2XW7t5eBuK/gJo/JoKUOQyfMFhPstU=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr3818204wej.77.1300212161213; Tue, 15 Mar 2011 11:02:41 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 11:02:41 -0700 (PDT)
Date: Tue, 15 Mar 2011 12:02:41 -0600
Message-ID: <AANLkTinS_FpcdNohB_rtGdJXqr=P3_3gWg4TgHCNY+1T@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-format-01, TLV Start Pointer
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: Tue, 15 Mar 2011 18:01:21 -0000

Hi
When extracting the mandatory fields the length of one parameter can normally be
calculated by
Length = <Pointer To Next Parameter> - <Pointer To This Parameter> -1

However if there are no optional fields
"If the OPTIONAL TLV groups are not implemented, then the "TLV Start Pointer"
field MUST be set to zero (0x0000)."

But to calculate the length of <Client-Txn> You first have to check if
<TLV Start Pointer> = 0x0000 in which case the <Client-Txn> length
is
Length = <Record Length> - <Pointer To Client-Txn> -1

Similarly when extracting the TLVs it is necessary to do an extra test if
the <TLV Start Pointer> = 0x0000.

I would like to propose that in the case when there are no optional fields that
the <TLV Start Pointer> points to the 0x0A at the end of the record.

It is not a big complication but it will remove a couple of tests in a parser.

/Anders

From gsalguei@cisco.com  Tue Mar 15 11:25:16 2011
Return-Path: <gsalguei@cisco.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 89B623A6D78 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 11:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.143
X-Spam-Level: 
X-Spam-Status: No, score=-9.143 tagged_above=-999 required=5 tests=[AWL=-0.845, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8]
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 PPzy+QNyo+5k for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 11:25:14 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 53F3A3A6B10 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 11:25:14 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FIQbCE013234; Tue, 15 Mar 2011 14:26:37 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FIQavX002665;  Tue, 15 Mar 2011 14:26:36 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-12--216150443
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTi=vBdqoxuRRdSQp6TvaAVfYwEEbiNk3kH6JC2tW@mail.gmail.com>
Date: Tue, 15 Mar 2011 14:26:36 -0400
Message-Id: <8751A616-4A9C-43B5-B7EE-66FA5AD0DA75@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <AANLkTi=Cj3urLqDZW9MCzzJGauWMPKgiATGo3_z4sa_z@mail.gmail.com> <BCF3AE7B-DA85-476C-AC61-3383D8D6D6DF@cisco.com> <AANLkTi=vBdqoxuRRdSQp6TvaAVfYwEEbiNk3kH6JC2tW@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Tue, 15 Mar 2011 18:25:16 -0000

--Apple-Mail-12--216150443
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Sounds like we are converging.

On Mar 15, 2011, at 1:40 PM, Anders Nygren wrote:

> On Tue, Mar 15, 2011 at 11:14 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Anders -
>> This would make good fodder for discussion by the group on the list =
as well
>> as in Prague.  It would be my preference not to further overload the =
current
>> Flags field in <IndexPointers> with additional and additional flag =
with
>> pre-defined, vendor-specified, and both settings.
>=20
> The vendor flag I mentioned would not be in the Flags field in =
<IndexPointers>.
> It would be in the TLV structure. So that PEN=3D0 would not  need to =
be used
> to indicate that it is a standard optional parameter.
>=20
Do you know of any issues with using PEN=3D0 in this manner?  I don't. =
It appears that DIAMETER does it, so I suspect it is fine.

>=20
>> I think the most elegant
>> solution is:
>>=20
>> 1. The single format you proposed for both Pre-Defined and =
Vendor-Specific
>> optional fields (where, if allowed, PEN=3D0 signifies Pre-Defined =
optional
>> field).
>> 2. Based on group consensus, decide whether (a) we stick with a =
single
>> pointer is needed in <IndexPointers> to indicate the beginning of the
>> optional fields (i.e. both pre-defined and vendor-specified) or =
whether (b)
>> there is value in adding an additional pointer added to =
<IndexPointers>,
>> where one pointer points to the start of the Pre-Defined optional =
fields and
>> the other points to the start of Vendor-specified fields.
>> Sound reasonable?
>=20
> Yes.
> The purpose of the extra pointer was to make parsing simpler in the =
case where
> there are two different formats for the standard optional parameters =
and the
> vendor extensions. If they have the same format I see no reason for =
the extra
> pointer.

OK. So just to confirm, as an implementer, you don't see any added value =
in specifically being able to identify the beginning of the =
vendor-specified optional fields (if present)? Knowing the beginning of =
the combined optional fields is fine (provided they use the same general =
syntax)?

Regards,

Gonzalo

>=20
> /Anders
>=20
>=20
>> Regards,
>> Gonzalo
>> On Mar 15, 2011, at 12:45 PM, Anders Nygren wrote:
>>=20
>> I would like to modify/extend my original proposal with the following
>> two alternatives.
>>=20
>> 1, Two TLV pointers.
>> Background:
>> The current draft-01 contains only one TLV pointer, "TLV Start
>> Pointer", that points
>> to the optional parameters block. This block contains both the =
standard
>> optional
>> parameters and the vendor extensions.
>>=20
>> Change:
>> Add a new pointer "Vendor Extensions Pointer". So "TLV Start Pointer" =
points
>> to
>> the standard optional parameters. And "Vendor Extensions Pointer" =
points to
>> the vendor extensions block.
>> The contents of the Standard optional parameters have the format
>> proposed in draft-01,
>> and the contents of the Vendor extension block have the format I
>> proposed earlier.
>>=20
>> byte 1  0x09
>> byte 2-5 Tag (Hex)
>> byte 6-9 VendorId
>> byte 10 0x2C
>> byte 11-14 Length (Hex)
>> byte 15 0x2C
>> byte 16-.. Value (variable length)
>>=20
>> 2, Common format
>> Keep one common format for both standard optional parameters and
>> vendor extensions
>> more in line with diameter, RFC3588, ch 4.1
>>=20
>> 0x09                1 byte
>> vendor flag        1 byte     "s" =3D standard or "v" =3D vendor
>> Tag (Hex)          4 bytes
>> 0x2C                1 byte
>> Length (Hex)     4 bytes
>> [VendorId          4 bytes]  Only present if vendor flag=3D"v"
>> 0x2C
>> Value (variable length)
>>=20
>> /Anders
>>=20
>> On Tue, Mar 15, 2011 at 8:55 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com>
>> wrote:
>>=20
>> Anders -
>>=20
>> You are absolutely right, I did misunderstand your point the first =
time
>>=20
>> around. I thought you were saying '001' was the Vendor-ID, when in =
fact you
>>=20
>> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name =
in
>>=20
>> front of the '@' is only restricted in the following way:
>>=20
>> - MUST be printable US-ASCII strings
>>=20
>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF
>>=20
>> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF =
%d34),
>>=20
>> whitespace, or control characters.
>>=20
>> it indeed means your example is a valid Vendor-ID and could cause =
confusion.
>>=20
>> While this would be very unlikely to happen in practice [I can't =
imagine an
>>=20
>> implementer intentionally doing this], it is undesired. I think this =
fact
>>=20
>> makes your original proposal that much more elegant than the existing =
one.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>=20
>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com>
>>=20
>> wrote:
>>=20
>> Thanks for raising your concerns Anders.
>>=20
>> As you know, this draft was just published today and its principal =
intent
>>=20
>> was to formulate an initial solution for SIP CLF extensibility.
>>=20
>> A little history:
>>=20
>> The current proposal for Vendor-specific extensions using a =
Syslog-like
>>=20
>> approach (i.e. name@<private enterprise number>) was something =
proposed over
>>=20
>> email and decided at the last SIPCLF Interim meeting in January. So =
this
>>=20
>> really is a first pass at implementing vendor-specificied optional =
fields.
>>=20
>> That said, I'll comment inline to your points
>>=20
>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>=20
>> Hi
>>=20
>> I must say that I really dislike the proposed format for vendor =
specific
>>=20
>> fields.
>>=20
>> Having a variable length "tag" before the length field means that it
>>=20
>> is necessary
>>=20
>> to scan the tag looking for the ',' just to find the length field.
>>=20
>> You make a valid point. I'd like others to weigh in here and comment =
on
>>=20
>> whether they think this is a serious performance limitation. I'll =
propose
>>=20
>> this as a discussion point for the upcoming meeting in Prague. The =
reason
>>=20
>> for the variable length tag is that it is based on the SD-ID format =
from
>>=20
>> Syslog, which is variable in length (i.e. the unrestricted name =
before the
>>=20
>> '@').  I think using a Vendor-ID based on a PEN is common sense, so =
I'd like
>>=20
>> to stick with that if possible. We could decide on a fixed length =
name (or
>>=20
>> number to parallel the tag from the Pre-Defined Optional Fields) =
followed by
>>=20
>> four byte PEN.
>>=20
>> There is no simple way to tell he difference between a sip-clf
>>=20
>> optional field and
>>=20
>> a vendor specific optional field. So it will always be necessary to =
scan the
>>=20
>> record looking for the ',' .
>>=20
>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal
>>=20
>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from =
a
>>=20
>> standard optional field without a lot of work.
>>=20
>> Remember that that this draft restricts the scope of the syntax to =
the 2nd
>>=20
>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a =
legal
>>=20
>> vendor-specified optional field since "0001" doesn't contain an '@', =
which
>>=20
>> is mandatory for a Vendor-ID as defined in the draft. So there should =
be no
>>=20
>> confusion there as the Vendor-ID from the vendor-specified optional =
fields
>>=20
>> and the Tag from the pre-defined optional fields can never be the =
same.
>>=20
>>=20
>> I think that You did not understand the point I was trying to make.
>>=20
>> As I understand the specification in the 2nd format definition of =
SD-IDs in
>>=20
>> RFC5424, comma "," is allowed in the name part. So
>>=20
>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very =
difficult
>>=20
>> to
>>=20
>> differentiate from a standard optional field with tag=3D"0001", =
length=3D"FFFF"
>>=20
>> and
>>=20
>> a value starting with "@<Vendor-ID>"
>>=20
>> I think a better way to do this would be similar to diameter RFC3588, =
ch
>>=20
>> 4.1.
>>=20
>> Then we could have just one format for standard optional fields and =
vendor
>>=20
>> specific fields
>>=20
>> byte 1  0x09
>>=20
>> byte 2-5 Tag (Hex)
>>=20
>> byte 6-9 VendorId
>>=20
>> byte 10 0x2C
>>=20
>> byte 11-14 Length (Hex)
>>=20
>> byte 15 0x2C
>>=20
>> byte 16-.. Value (variable length)
>>=20
>> Where VendorId is the IANA assigned "SMI Network Management Private
>>=20
>> Enterprise Codes"  [ASSIGNNO] value.
>>=20
>> VendorId=3D0 is used a for the standard optional fields defined in =
SIP-CLF.
>>=20
>> I know that PEN =3D 0 is a Reserved value and if it is confirmed that =
it can
>>=20
>> be used in this way (as apparently DIAMETER did), then I think this =
proposal
>>=20
>> is very reasonable. This unifies both optional field types into a =
single
>>=20
>> seamless representation. I'll let others, like Chris Lonvick, more
>>=20
>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>> /Anders
>>=20
>> _______________________________________________
>>=20
>> sip-clf mailing list
>>=20
>> sip-clf@ietf.org
>>=20
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20


--Apple-Mail-12--216150443
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Sounds like we are converging.<div><br><div><div>On Mar 15, 2011, at =
1:40 PM, Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Tue, Mar 15, 2011 at 11:14 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Anders -<br></blockquote><blockquote =
type=3D"cite">This would make good fodder for discussion by the group on =
the list as well<br></blockquote><blockquote type=3D"cite">as in Prague. =
&nbsp;It would be my preference not to further overload the =
current<br></blockquote><blockquote type=3D"cite">Flags field in =
&lt;IndexPointers&gt; with additional and additional flag =
with<br></blockquote><blockquote type=3D"cite">pre-defined, =
vendor-specified, and both settings.<br></blockquote><br>The vendor flag =
I mentioned would not be in the Flags field in =
&lt;IndexPointers&gt;.<br>It would be in the TLV structure. So that =
PEN=3D0 would not &nbsp;need to be used<br>to indicate that it is a =
standard optional parameter.<br><br></div></blockquote>Do you know of =
any issues with using PEN=3D0 in this manner? &nbsp;I don't. It appears =
that DIAMETER does it, so I suspect it is =
fine.</div><div><br></div><div><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite">I think the most =
elegant<br></blockquote><blockquote type=3D"cite">solution =
is:<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">1. The single format you proposed for both Pre-Defined =
and Vendor-Specific<br></blockquote><blockquote type=3D"cite">optional =
fields (where, if allowed, PEN=3D0 signifies Pre-Defined =
optional<br></blockquote><blockquote =
type=3D"cite">field).<br></blockquote><blockquote type=3D"cite">2. Based =
on group consensus, decide whether (a) we stick with a =
single<br></blockquote><blockquote type=3D"cite">pointer is needed in =
&lt;IndexPointers&gt; to indicate the beginning of =
the<br></blockquote><blockquote type=3D"cite">optional fields (i.e. both =
pre-defined and vendor-specified) or whether =
(b)<br></blockquote><blockquote type=3D"cite">there is value in adding =
an additional pointer added to =
&lt;IndexPointers&gt;,<br></blockquote><blockquote type=3D"cite">where =
one pointer points to the start of the Pre-Defined optional fields =
and<br></blockquote><blockquote type=3D"cite">the other points to the =
start of Vendor-specified fields.<br></blockquote><blockquote =
type=3D"cite">Sound reasonable?<br></blockquote><br>Yes.<br>The purpose =
of the extra pointer was to make parsing simpler in the case =
where<br>there are two different formats for the standard optional =
parameters and the<br>vendor extensions. If they have the same format I =
see no reason for the =
extra<br>pointer.<br></div></blockquote><div><br></div>OK. So just to =
confirm, as an implementer, you don't see any added value in =
specifically being able to identify the beginning of the =
vendor-specified optional fields (if present)? Knowing the beginning of =
the combined optional fields is fine (provided they use the same general =
syntax)?</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzal=
o</div><div><br><blockquote =
type=3D"cite"><div><br>/Anders<br><br><br><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote type=3D"cite">On Mar =
15, 2011, at 12:45 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would like to =
modify/extend my original proposal with the =
following<br></blockquote><blockquote type=3D"cite">two =
alternatives.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">1, Two TLV =
pointers.<br></blockquote><blockquote =
type=3D"cite">Background:<br></blockquote><blockquote type=3D"cite">The =
current draft-01 contains only one TLV pointer, "TLV =
Start<br></blockquote><blockquote type=3D"cite">Pointer", that =
points<br></blockquote><blockquote type=3D"cite">to the optional =
parameters block. This block contains both the =
standard<br></blockquote><blockquote =
type=3D"cite">optional<br></blockquote><blockquote =
type=3D"cite">parameters and the vendor =
extensions.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Change:<br></blockquote><blockquote type=3D"cite">Add a =
new pointer "Vendor Extensions Pointer". So "TLV Start Pointer" =
points<br></blockquote><blockquote =
type=3D"cite">to<br></blockquote><blockquote type=3D"cite">the standard =
optional parameters. And "Vendor Extensions Pointer" points =
to<br></blockquote><blockquote type=3D"cite">the vendor extensions =
block.<br></blockquote><blockquote type=3D"cite">The contents of the =
Standard optional parameters have the format<br></blockquote><blockquote =
type=3D"cite">proposed in draft-01,<br></blockquote><blockquote =
type=3D"cite">and the contents of the Vendor extension block have the =
format I<br></blockquote><blockquote type=3D"cite">proposed =
earlier.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 1 =
&nbsp;0x09<br></blockquote><blockquote type=3D"cite">byte 2-5 Tag =
(Hex)<br></blockquote><blockquote type=3D"cite">byte 6-9 =
VendorId<br></blockquote><blockquote type=3D"cite">byte 10 =
0x2C<br></blockquote><blockquote type=3D"cite">byte 11-14 Length =
(Hex)<br></blockquote><blockquote type=3D"cite">byte 15 =
0x2C<br></blockquote><blockquote type=3D"cite">byte 16-.. Value =
(variable length)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">2, Common =
format<br></blockquote><blockquote type=3D"cite">Keep one common format =
for both standard optional parameters and<br></blockquote><blockquote =
type=3D"cite">vendor extensions<br></blockquote><blockquote =
type=3D"cite">more in line with diameter, RFC3588, ch =
4.1<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">0x09 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;1 byte<br></blockquote><blockquote type=3D"cite">vendor =
flag &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1 byte =
&nbsp;&nbsp;&nbsp;&nbsp;"s" =3D standard or "v" =3D =
vendor<br></blockquote><blockquote type=3D"cite">Tag (Hex) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4 =
bytes<br></blockquote><blockquote type=3D"cite">0x2C =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;1 byte<br></blockquote><blockquote type=3D"cite">Length =
(Hex) &nbsp;&nbsp;&nbsp;&nbsp;4 bytes<br></blockquote><blockquote =
type=3D"cite">[VendorId =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4 bytes] =
&nbsp;Only present if vendor flag=3D"v"<br></blockquote><blockquote =
type=3D"cite">0x2C<br></blockquote><blockquote type=3D"cite">Value =
(variable length)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Tue, Mar 15, =
2011 at 8:55 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt;<br></blockqu=
ote><blockquote type=3D"cite">wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Anders =
-<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">You are absolutely right, I did misunderstand your point =
the first time<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">around. I =
thought you were saying '001' was the Vendor-ID, when in fact =
you<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">were saying that&nbsp;"0001,FFFF,@&lt;PEN&gt;" is the =
Vendor-ID. Since the name in<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">front of the =
'@' is only restricted in the following way:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">-&nbsp;MUST be =
printable US-ASCII strings<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- MUST NOT =
contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">%d61), a =
closing brace (']', ABNF %d93), a quote-character ('"', ABNF =
%d34),<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">whitespace, or =
control characters.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">it indeed means =
your example is a valid Vendor-ID and could cause =
confusion.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">While this =
would be very unlikely to happen in practice [I can't imagine =
an<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">implementer intentionally doing this], it is undesired. I =
think this fact<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">makes your =
original proposal that much more elegant than the existing =
one.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 15, =
2011, at 10:38 AM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Tue, Mar 15, =
2011 at 12:19 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt;<br></blockqu=
ote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks for =
raising your concerns Anders.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">As you know, =
this draft was just published today and its principal =
intent<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">was to =
formulate an initial solution for SIP CLF =
extensibility.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">A little =
history:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The current =
proposal for Vendor-specific extensions using a =
Syslog-like<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">approach =
(i.e.&nbsp;name@&lt;private enterprise number&gt;) was something =
proposed over<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">email and =
decided at the last SIPCLF Interim meeting in January. So =
this<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">really is a =
first pass at implementing vendor-specificied optional =
fields.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">That said, I'll =
comment inline to your points<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 14, =
2011, at 10:53 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I must say that =
I really dislike the proposed format for vendor =
specific<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">fields.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Having a =
variable length "tag" before the length field means that =
it<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">is necessary<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">to scan the tag =
looking for the ',' just to find the length =
field.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">You make a =
valid point. I'd like others to weigh in here and comment =
on<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">whether they think this is a serious performance =
limitation. I'll propose<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">this as a =
discussion point for the upcoming meeting in Prague. The =
reason<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">for the =
variable length tag is that it is based on the SD-ID format =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Syslog, which =
is variable in length (i.e. the unrestricted name before =
the<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">'@'). &nbsp;I think using a Vendor-ID based on a PEN is =
common sense, so I'd like<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">to stick with =
that if possible. We could decide on a fixed length name =
(or<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">number to parallel the tag from the Pre-Defined Optional =
Fields) followed by<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">four byte =
PEN.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">There is no =
simple way to tell he difference between a =
sip-clf<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">optional field =
and<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">a vendor specific optional field. So it will always be =
necessary to scan the<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">record looking =
for the ',' .<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Actually =
looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">ID, =
"0001,FFFF,@12345" which would be difficult to differentiate from =
a<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">standard optional field without a lot of =
work.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Remember that =
that this draft restricts the scope of the syntax to the =
2nd<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">format definition of SD-IDs in RFC5424. Thus, the above =
wouldn't be a legal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">vendor-specified =
optional field since "0001" doesn't contain an '@', =
which<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is mandatory =
for a Vendor-ID as defined in the draft. So there should be =
no<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">confusion there as the Vendor-ID from the vendor-specified =
optional fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">and the Tag =
from the pre-defined optional fields can never be the =
same.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think that =
You did not understand the point I was trying to =
make.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">As I understand =
the specification in the 2nd format definition of SD-IDs =
in<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">RFC5424, comma "," is allowed in the name part. =
So<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">"0001,FFFF,@&lt;Vendor-ID&gt;" would be a legal tag, that =
would be very difficult<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">to<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">differentiate =
from a standard optional field with tag=3D"0001", =
length=3D"FFFF"<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">and<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">a value =
starting with "@&lt;Vendor-ID&gt;"<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think a =
better way to do this would be similar to diameter RFC3588, =
ch<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">4.1.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Then we could =
have just one format for standard optional fields and =
vendor<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">specific =
fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 1 =
&nbsp;0x09<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 2-5 Tag =
(Hex)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 6-9 =
VendorId<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 10 =
0x2C<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 11-14 =
Length (Hex)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 15 =
0x2C<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 16-.. =
Value (variable length)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Where VendorId =
is the IANA assigned "SMI Network Management =
Private<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Enterprise =
Codes" &nbsp;[ASSIGNNO] value.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VendorId=3D0 is =
used a for the standard optional fields defined in =
SIP-CLF.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I know that PEN =
=3D 0 is a Reserved value and if it is confirmed that it =
can<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">be used in this way (as apparently DIAMETER did), then I =
think this proposal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is very =
reasonable. This unifies both optional field types into a =
single<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">seamless =
representation. I'll let others, like Chris Lonvick, =
more<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">knowledgeable =
than I weigh in on this as well to confirm my =
thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">sip-clf mailing list<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-12--216150443--

From gsalguei@cisco.com  Tue Mar 15 11:36:44 2011
Return-Path: <gsalguei@cisco.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 524993A6B1D for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 11:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.216
X-Spam-Level: 
X-Spam-Status: No, score=-10.216 tagged_above=-999 required=5 tests=[AWL=0.382, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 uhLPnM5mFMYK for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 11:36:43 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 212013A6B1C for <sip-clf@ietf.org>; Tue, 15 Mar 2011 11:36:43 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FIc77b014373; Tue, 15 Mar 2011 14:38:07 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FIc6bi017482;  Tue, 15 Mar 2011 14:38:06 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-14--215460632
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com>
Date: Tue, 15 Mar 2011 14:38:06 -0400
Message-Id: <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 18:36:44 -0000

--Apple-Mail-14--215460632
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:

> Hi
> I will start writing one email for each issue in order to make it
> easier to track the different discussions.
>=20
Thanks. That should help.

> I would like to propose that the Flag Field is moved from the
> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
> will be pure metadata that can be ignored if wanted and all =
interesting
> data about the message is in the second line of the record.
>=20
I have no real preference on this one. I'll let others weigh in with =
their thoughts.

> Also I think it would be good to change the Sent/Received flag from
>=20
> Sent/Received flag
>=20
>         u =3D received UDP mesage
>         t =3D received TCP mesage
>         l =3D received TLS mesage
>         U =3D sent UDP mesage
>         T =3D sent TCP mesage
>         L =3D sent TLS mesage
>=20
> To
> Sent/Received flag [1 byte]
>         r =3D received message
>         s =3D sent message
>=20
> And add
> Protocol [1 byte]
>         u =3D UDP
>         t =3D TCP
>         l =3D TLS
>=20
> Since the proposed CLF already requires quite a lot of space there is
> little reason to
> try to pack different parameters into the same byte.

This is what was proposed early on, but the group decided on =
consolidating the two. I'm not violently opposed or in favor of either, =
but I don't see any real benefit to separating the two out since all =
permutations are covered in a single easy byte.

Regards,

Gonzalo
>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-14--215460632
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 15, 2011, at 1:49 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi<br>I will start writing one email for each issue =
in order to make it<br>easier to track the different =
discussions.<br><br></div></blockquote>Thanks. That should =
help.</div><div><br><blockquote type=3D"cite"><div>I would like to =
propose that the Flag Field is moved from the<br>&lt;IndexPointers&gt; =
to &lt;MandatoryFields&gt;. That way the &lt;IndexPointers&gt;<br>will =
be pure metadata that can be ignored if wanted and all =
interesting<br>data about the message is in the second line of the =
record.<br><br></div></blockquote>I have no real preference on this one. =
I'll let others weigh in with their thoughts.</div><div><br><blockquote =
type=3D"cite"><div>Also I think it would be good to change the =
Sent/Received flag from<br><br>Sent/Received flag<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D received UDP =
mesage<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
received TCP mesage<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D received TLS =
mesage<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;U =3D sent =
UDP mesage<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T =3D =
sent TCP mesage<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L =3D =
sent TLS mesage<br><br>To<br>Sent/Received flag [1 byte]<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;r =3D received =
message<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s =3D sent =
message<br><br>And add<br>Protocol [1 byte]<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D UDP<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D TCP<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D TLS<br><br>Since =
the proposed CLF already requires quite a lot of space there =
is<br>little reason to<br>try to pack different parameters into the same =
byte.<br></div></blockquote><div><br></div>This is what was proposed =
early on, but the group decided on consolidating the two. I'm not =
violently opposed or in favor of either, but I don't see any real =
benefit to separating the two out since all permutations are covered in =
a single easy =
byte.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo<b=
r><blockquote =
type=3D"cite"><div><br>/Anders<br>________________________________________=
_______<br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></body></html=
>=

--Apple-Mail-14--215460632--

From anders.nygren@gmail.com  Tue Mar 15 12:11:56 2011
Return-Path: <anders.nygren@gmail.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 E39903A6E72 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.312
X-Spam-Level: 
X-Spam-Status: No, score=-3.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 G-RBO3ZZqPDb for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:11:55 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 396F23A6E5F for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:11:55 -0700 (PDT)
Received: by wyb42 with SMTP id 42so970241wyb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:13:19 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=X/UCfzJxdjneqsr0GizHqRBBcM3MXyZs0pwr5hPnWcs=; b=vW6ZG6mW2Kd4oiyoWGxB7En31YT7bFNNXEBmzb/h0AhQNSCFNALxP6udwlncArRSgW 2f5E6cKMCCq0DzL2tqzd+s7jZ6s5y4oAaEIpPIeRTtSy1fB3eDbkby18+vnEHXYkeUIb K4UrkFlAb2jm9Uwi2oXD+a6ZBZrpFgB/clQls=
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:content-transfer-encoding; b=X+z9+4GevMYRRbV+sIl8cFqpfIk9jR9RVR+0d6A0A1x3P2UXQxFRen+8lukHyf9sHV r6GLROy7rUG6eB5pH/20xJ1GziZoeZQeNdsT5csdYMaR0WnCnhB3fo3EUL6gSFt0P9F1 GmRPTqUxsXfHu6p7IiMQOriigWDUUTZnvjN3o=
MIME-Version: 1.0
Received: by 10.216.190.15 with SMTP id d15mr12107159wen.62.1300216399676; Tue, 15 Mar 2011 12:13:19 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 12:13:19 -0700 (PDT)
In-Reply-To: <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com>
Date: Tue, 15 Mar 2011 13:13:19 -0600
Message-ID: <AANLkTi=RvWTVaaqBZwY1vEjZHU-smbXr3u-bMxLtSYG5@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 19:11:57 -0000

On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro <gsalguei@cisco.com> wr=
ote:
>
> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>
> Hi
> I will start writing one email for each issue in order to make it
> easier to track the different discussions.
>
> Thanks. That should help.
>
> I would like to propose that the Flag Field is moved from the
> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
> will be pure metadata that can be ignored if wanted and all interesting
> data about the message is in the second line of the record.
>
> I have no real preference on this one. I'll let others weigh in with thei=
r
> thoughts.
>
> Also I think it would be good to change the Sent/Received flag from
>
> Sent/Received flag
>
> =A0=A0=A0=A0=A0=A0=A0=A0u =3D received UDP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0t =3D received TCP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0l =3D received TLS mesage
> =A0=A0=A0=A0=A0=A0=A0=A0U =3D sent UDP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0T =3D sent TCP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0L =3D sent TLS mesage
>
> To
> Sent/Received flag [1 byte]
> =A0=A0=A0=A0=A0=A0=A0=A0r =3D received message
> =A0=A0=A0=A0=A0=A0=A0=A0s =3D sent message
>
> And add
> Protocol [1 byte]
> =A0=A0=A0=A0=A0=A0=A0=A0u =3D UDP
> =A0=A0=A0=A0=A0=A0=A0=A0t =3D TCP
> =A0=A0=A0=A0=A0=A0=A0=A0l =3D TLS
>
> Since the proposed CLF already requires quite a lot of space there is
> little reason to
> try to pack different parameters into the same byte.
>
> This is what was proposed early on, but the group decided on consolidatin=
g
> the two. I'm not violently opposed or in favor of either, but I don't see
> any real benefit to separating the two out since all permutations are
> covered in a single easy byte.

It is not a big deal but for instance if You want to find all sent messages=
 it
is 3 tests instead of one for each record, (and if we add SCTP, see below),
then it would be 4. And when searching for all messages on a specific proto=
col
it is 2 tests instead of one.

A quick check found RFC 4168, "The Stream Control Transmission
Protocol (SCTP) as a Transport for the Session Initiation Protocol
(SIP)"

So maybe SCTP should be added as a protocol. I do not know if there is some=
thing
similar to TLS over SCTP, but I suspect things may get messy with a lot of
permutations in the future.

So maybe we should consider 3 parameters
send/receive    sent, received
protocol           tcp, udp, sctp
secure             encrypted, plain text

/Anders

> Regards,
> Gonzalo
>
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>

From gsalguei@cisco.com  Tue Mar 15 12:13:40 2011
Return-Path: <gsalguei@cisco.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 A33123A6B35 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.248
X-Spam-Level: 
X-Spam-Status: No, score=-10.248 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 d0P38hJliJlh for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:13:39 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id AE9993A6A40 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:13:39 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FJF3Bi017926; Tue, 15 Mar 2011 15:15:03 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FJF3bw005838;  Tue, 15 Mar 2011 15:15:03 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-16--213244198
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTinS_FpcdNohB_rtGdJXqr=P3_3gWg4TgHCNY+1T@mail.gmail.com>
Date: Tue, 15 Mar 2011 15:15:02 -0400
Message-Id: <A7D4B0A0-B9FE-4A66-9440-88B40CC96D74@cisco.com>
References: <AANLkTinS_FpcdNohB_rtGdJXqr=P3_3gWg4TgHCNY+1T@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, TLV Start Pointer
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: Tue, 15 Mar 2011 19:13:40 -0000

--Apple-Mail-16--213244198
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


If this simplifies getting the length of the final mandatory field (i.e =
Client-Txn), then I'm not opposed to having "TLV Start Pointer" point to =
the terminating line feed, rather than being set to all zeroes in the =
case of no optional fields.

Are others OK with this logic?

Gonzalo



On Mar 15, 2011, at 2:02 PM, Anders Nygren wrote:

> Hi
> When extracting the mandatory fields the length of one parameter can =
normally be
> calculated by
> Length =3D <Pointer To Next Parameter> - <Pointer To This Parameter> =
-1
>=20
> However if there are no optional fields
> "If the OPTIONAL TLV groups are not implemented, then the "TLV Start =
Pointer"
> field MUST be set to zero (0x0000)."
>=20
> But to calculate the length of <Client-Txn> You first have to check if
> <TLV Start Pointer> =3D 0x0000 in which case the <Client-Txn> length
> is
> Length =3D <Record Length> - <Pointer To Client-Txn> -1
>=20
> Similarly when extracting the TLVs it is necessary to do an extra test =
if
> the <TLV Start Pointer> =3D 0x0000.
>=20
> I would like to propose that in the case when there are no optional =
fields that
> the <TLV Start Pointer> points to the 0x0A at the end of the record.
>=20
> It is not a big complication but it will remove a couple of tests in a =
parser.
>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-16--213244198
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>If this simplifies getting the length of the final =
mandatory field (i.e Client-Txn), then I'm not opposed to having "TLV =
Start Pointer" point to the terminating line feed, rather than being set =
to all zeroes in the case of no optional =
fields.</div><div><br></div><div>Are others OK with this =
logic?</div><div><br></div><div>Gonzalo</div><div><br></div><div><br></div=
><div><br></div><div>On Mar 15, 2011, at 2:02 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi<br>When extracting the mandatory fields the length =
of one parameter can normally be<br>calculated by<br>Length =3D =
&lt;Pointer To Next Parameter&gt; - &lt;Pointer To This Parameter&gt; =
-1<br><br>However if there are no optional fields<br>"If the OPTIONAL =
TLV groups are not implemented, then the "TLV Start Pointer"<br>field =
MUST be set to zero (0x0000)."<br><br>But to calculate the length of =
&lt;Client-Txn&gt; You first have to check if<br>&lt;TLV Start =
Pointer&gt; =3D 0x0000 in which case the &lt;Client-Txn&gt; =
length<br>is<br>Length =3D &lt;Record Length&gt; - &lt;Pointer To =
Client-Txn&gt; -1<br><br>Similarly when extracting the TLVs it is =
necessary to do an extra test if<br>the &lt;TLV Start Pointer&gt; =3D =
0x0000.<br><br>I would like to propose that in the case when there are =
no optional fields that<br>the &lt;TLV Start Pointer&gt; points to the =
0x0A at the end of the record.<br><br>It is not a big complication but =
it will remove a couple of tests in a =
parser.<br><br>/Anders<br>_______________________________________________<=
br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></body></html=
>=

--Apple-Mail-16--213244198--

From anders.nygren@gmail.com  Tue Mar 15 12:40:59 2011
Return-Path: <anders.nygren@gmail.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 4E77C3A6979 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.343
X-Spam-Level: 
X-Spam-Status: No, score=-3.343 tagged_above=-999 required=5 tests=[AWL=0.256,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 CFN2xO2aXyQo for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:40:58 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id DE2333A6E34 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:40:57 -0700 (PDT)
Received: by wyb42 with SMTP id 42so1000616wyb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:42:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=7tTVneKGx7AITkrE0R/Z/gAXis9QzkLZZb9AbT2yhXk=; b=lYPe1PMeWpcR5HQOUSEyXI3iOYYY+UmhCBX0Fc0/IlFAJ+wyAd2RkOGTwwFBCcBXra V+nC5+vr65Akr3qYGbsmYHyZtcHy5+I3aKRLDPICJstZdVCy6YzZm9zYhTEVpnJ0fKXq S/lmaoZn35VLO43qkv73KRm35dPjC9IwYlID4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iw4J5g41A3vy4wxQU+WEU2+AOn0tXhsm1Pykrt4JPuZqOWvfwkelg92/v2ycI2I915 LUn0s+dnjTTmlujTTM+dAp7agPJzxC08xDVCN1k0eL/QZQh/0m3HkHxdf2cRej44iucC DfyC8hHZdTr6gYZtmgEx7iSL41dSkLUCgu2iY=
MIME-Version: 1.0
Received: by 10.216.221.92 with SMTP id q70mr12084169wep.107.1300218142684; Tue, 15 Mar 2011 12:42:22 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 12:42:22 -0700 (PDT)
Date: Tue, 15 Mar 2011 13:42:22 -0600
Message-ID: <AANLkTimg71pj4uF6=ew9Ga2TJvePVfTdnbTHa916VNDs@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-format-01, example missing client-tx
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: Tue, 15 Mar 2011 19:40:59 -0000

Hi
The example in ch 5, is missing <client-tx>.

/Anders

From gsalguei@cisco.com  Tue Mar 15 12:48:36 2011
Return-Path: <gsalguei@cisco.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 ACBAB3A6B30 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.275
X-Spam-Level: 
X-Spam-Status: No, score=-10.275 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 thLG8TFlZJD4 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:48:36 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id C30D03A6A8B for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:48:35 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FJo0Do021205; Tue, 15 Mar 2011 15:50:00 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FJnxgJ021485;  Tue, 15 Mar 2011 15:49:59 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-19--211149429
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTimg71pj4uF6=ew9Ga2TJvePVfTdnbTHa916VNDs@mail.gmail.com>
Date: Tue, 15 Mar 2011 15:49:57 -0400
Message-Id: <D5EBA3E9-10EC-40B4-8AC0-F63F97F113BE@cisco.com>
References: <AANLkTimg71pj4uF6=ew9Ga2TJvePVfTdnbTHa916VNDs@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, example missing client-tx
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: Tue, 15 Mar 2011 19:48:36 -0000

--Apple-Mail-19--211149429
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks Anders.  It inadvertently got dropped from the =
draft-salgueiro-sipclf-indexed-ascii-03 version to the =
draft-ietf-sipclf-format-00 when all of the ip addresses and dns names =
were made "documentation friendly". I have already fixed it and the =
revised example will appear in the -02 draft.

Regards,

Gonzalo

On Mar 15, 2011, at 3:42 PM, Anders Nygren wrote:

> Hi
> The example in ch 5, is missing <client-tx>.
>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-19--211149429
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks Anders. &nbsp;It inadvertently got dropped from the draft-salgueiro-sipclf-indexed-ascii-03 version to the&nbsp;draft-ietf-sipclf-format-00 when all of the ip addresses and dns names were made "documentation friendly". I have already fixed it and the revised example will appear in the -02 draft.<div><br></div><div>Regards,</div><div><br></div><div>Gonzalo</div><div><br><div><div>On Mar 15, 2011, at 3:42 PM, Anders Nygren wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi<br>The example in ch 5, is missing &lt;client-tx&gt;.<br><br>/Anders<br>_______________________________________________<br>sip-clf mailing list<br><a href="mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></div></body></html>
--Apple-Mail-19--211149429--

From gsalguei@cisco.com  Tue Mar 15 12:57:21 2011
Return-Path: <gsalguei@cisco.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 B2A7A3A6E17 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.298
X-Spam-Level: 
X-Spam-Status: No, score=-11.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  RCVD_IN_DNSWL_HI=-8]
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 1PVKRb0p9iQd for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 12:57:18 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 3D9173A6B49 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 12:57:18 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FJweh4022077; Tue, 15 Mar 2011 15:58:41 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FJwejh001158;  Tue, 15 Mar 2011 15:58:40 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-20--210627528
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTi=RvWTVaaqBZwY1vEjZHU-smbXr3u-bMxLtSYG5@mail.gmail.com>
Date: Tue, 15 Mar 2011 15:58:39 -0400
Message-Id: <4CDB9960-FC4E-4197-AB64-C708BBE27D80@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com> <AANLkTi=RvWTVaaqBZwY1vEjZHU-smbXr3u-bMxLtSYG5@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 19:57:21 -0000

--Apple-Mail-20--210627528
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Anders -=20

The notion of adding both SCTP and TLS the flag was brought up on the =
list back in October and it went unreplied to (far as I can tell). Here =
is the snippet:

Although, given that TLS can ride on top of UDP or TCP, we may want to =
think of a second letter added to "L" to
denote TLS-over-TCP and TLS-over-UDP (I doubt any implementations are =
using TLS-over-UDP for signaling only, but given that SCTP is starting
to appear in kernels, maybe our flags ought to be "u, t, s, lu, lt, ls, =
U, T, S, LU, LT, LS").

The fact that this is the second time this has been raised leads me to =
believe there is a need. I will raise this as a discussion topic in the =
upcoming meeting Prague.

Regards,

Gonzalo


On Mar 15, 2011, at 3:13 PM, Anders Nygren wrote:

> On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>>=20
>> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>>=20
>> Hi
>> I will start writing one email for each issue in order to make it
>> easier to track the different discussions.
>>=20
>> Thanks. That should help.
>>=20
>> I would like to propose that the Flag Field is moved from the
>> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
>> will be pure metadata that can be ignored if wanted and all =
interesting
>> data about the message is in the second line of the record.
>>=20
>> I have no real preference on this one. I'll let others weigh in with =
their
>> thoughts.
>>=20
>> Also I think it would be good to change the Sent/Received flag from
>>=20
>> Sent/Received flag
>>=20
>>         u =3D received UDP mesage
>>         t =3D received TCP mesage
>>         l =3D received TLS mesage
>>         U =3D sent UDP mesage
>>         T =3D sent TCP mesage
>>         L =3D sent TLS mesage
>>=20
>> To
>> Sent/Received flag [1 byte]
>>         r =3D received message
>>         s =3D sent message
>>=20
>> And add
>> Protocol [1 byte]
>>         u =3D UDP
>>         t =3D TCP
>>         l =3D TLS
>>=20
>> Since the proposed CLF already requires quite a lot of space there is
>> little reason to
>> try to pack different parameters into the same byte.
>>=20
>> This is what was proposed early on, but the group decided on =
consolidating
>> the two. I'm not violently opposed or in favor of either, but I don't =
see
>> any real benefit to separating the two out since all permutations are
>> covered in a single easy byte.
>=20
> It is not a big deal but for instance if You want to find all sent =
messages it
> is 3 tests instead of one for each record, (and if we add SCTP, see =
below),
> then it would be 4. And when searching for all messages on a specific =
protocol
> it is 2 tests instead of one.
>=20
> A quick check found RFC 4168, "The Stream Control Transmission
> Protocol (SCTP) as a Transport for the Session Initiation Protocol
> (SIP)"
>=20
> So maybe SCTP should be added as a protocol. I do not know if there is =
something
> similar to TLS over SCTP, but I suspect things may get messy with a =
lot of
> permutations in the future.
>=20
> So maybe we should consider 3 parameters
> send/receive    sent, received
> protocol           tcp, udp, sctp
> secure             encrypted, plain text
>=20
> /Anders
>=20
>> Regards,
>> Gonzalo
>>=20
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20


--Apple-Mail-20--210627528
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Anders -&nbsp;<div><br></div><div>The notion of adding both SCTP and =
TLS the flag was brought up on the list back in October and it went =
unreplied to (far as I can tell). Here is the =
snippet:</div><div><br></div><div>Although, given that TLS can ride on =
top&nbsp;of UDP or TCP, we may want to think of a second letter added to =
"L" to<br>denote TLS-over-TCP and TLS-over-UDP (I doubt any =
implementations are&nbsp;using TLS-over-UDP for signaling only, but =
given that SCTP is starting<br>to appear in kernels, maybe our flags =
ought to be "u, t, s, lu, lt, ls,&nbsp;U, T, S, LU, LT, =
LS").</div><div><br></div><div>The fact that this is the second time =
this has been raised leads me to believe there is a need. I will raise =
this as a discussion topic in the upcoming meeting =
Prague.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo=
</div><div><br></div><div><br><div><div>On Mar 15, 2011, at 3:13 PM, =
Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">On Mar 15, 2011, at 1:49 PM, Anders Nygren =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">I will start =
writing one email for each issue in order to make =
it<br></blockquote><blockquote type=3D"cite">easier to track the =
different discussions.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks. That =
should help.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would like to =
propose that the Flag Field is moved from =
the<br></blockquote><blockquote type=3D"cite">&lt;IndexPointers&gt; to =
&lt;MandatoryFields&gt;. That way the =
&lt;IndexPointers&gt;<br></blockquote><blockquote type=3D"cite">will be =
pure metadata that can be ignored if wanted and all =
interesting<br></blockquote><blockquote type=3D"cite">data about the =
message is in the second line of the record.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I have no real =
preference on this one. I'll let others weigh in with =
their<br></blockquote><blockquote =
type=3D"cite">thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Also I think it =
would be good to change the Sent/Received flag =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Sent/Received =
flag<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
received UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
received TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
received TLS mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;U =3D sent =
UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T =3D sent =
TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L =3D sent =
TLS mesage<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">To<br></blockquote><blockquote type=3D"cite">Sent/Received =
flag [1 byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;r =3D =
received message<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s =3D sent =
message<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">And =
add<br></blockquote><blockquote type=3D"cite">Protocol [1 =
byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
UDP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
TCP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
TLS<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">Since the proposed CLF already requires quite a lot of =
space there is<br></blockquote><blockquote type=3D"cite">little reason =
to<br></blockquote><blockquote type=3D"cite">try to pack different =
parameters into the same byte.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This is what =
was proposed early on, but the group decided on =
consolidating<br></blockquote><blockquote type=3D"cite">the two. I'm not =
violently opposed or in favor of either, but I don't =
see<br></blockquote><blockquote type=3D"cite">any real benefit to =
separating the two out since all permutations =
are<br></blockquote><blockquote type=3D"cite">covered in a single easy =
byte.<br></blockquote><br>It is not a big deal but for instance if You =
want to find all sent messages it<br>is 3 tests instead of one for each =
record, (and if we add SCTP, see below),<br>then it would be 4. And when =
searching for all messages on a specific protocol<br>it is 2 tests =
instead of one.<br><br>A quick check found RFC 4168, "The Stream Control =
Transmission<br>Protocol (SCTP) as a Transport for the Session =
Initiation Protocol<br>(SIP)"<br><br>So maybe SCTP should be added as a =
protocol. I do not know if there is something<br>similar to TLS over =
SCTP, but I suspect things may get messy with a lot of<br>permutations =
in the future.<br><br>So maybe we should consider 3 =
parameters<br>send/receive &nbsp;&nbsp;&nbsp;sent, received<br>protocol =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;tcp, udp, =
sctp<br>secure =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;en=
crypted, plain text<br><br>/Anders<br><br><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-20--210627528--

From peter.musgrave@magorcorp.com  Tue Mar 15 13:56:09 2011
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 A35763A6B45 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 13:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=0.999, BAYES_00=-2.599, GB_I_LETTER=-2, 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 IWqBYW47Fbn9 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 13:56:08 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 0DDE33A6B44 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 13:56:07 -0700 (PDT)
Received: by yxk30 with SMTP id 30so486523yxk.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 13:57:33 -0700 (PDT)
Received: by 10.91.195.22 with SMTP id x22mr515549agp.158.1300222651433; Tue, 15 Mar 2011 13:57:31 -0700 (PDT)
Received: from [192.168.1.119] (cpe-173-170-70-85.tampabay.res.rr.com [173.170.70.85]) by mx.google.com with ESMTPS id r8sm220938ane.19.2011.03.15.13.57.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Mar 2011 13:57:30 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-11--207099518
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <4CDB9960-FC4E-4197-AB64-C708BBE27D80@cisco.com>
Date: Tue, 15 Mar 2011 16:57:27 -0400
Message-Id: <33E31883-E842-46C6-A849-748452FDED3A@magorcorp.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com> <AANLkTi=RvWTVaaqBZwY1vEjZHU-smbXr3u-bMxLtSYG5@mail.gmail.com> <4CDB9960-FC4E-4197-AB64-C708BBE27D80@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] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 20:56:09 -0000

--Apple-Mail-11--207099518
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,=20

I am a fan of keeping separate things separate. So I agree transport and =
send/receive would benefit from being untangled (IIRC, I may be the one =
responsible for entangling them).

The transport field was intended to match the SIP transport protocol - =
so I think one byte for UDP, TCP, TLS, SCTP is ok.=20

I don't see the need to have a separate security field (since we already =
have TCP/TLS sharing a byte) - so I would continue in the same vein. =
It's not a biggie for me - so if others want a secure/not secure byte =
that would be okay.=20

Peter Musgrave
(as individual)

On 2011-03-15, at 3:58 PM, Gonzalo Salgueiro wrote:

> Anders -=20
>=20
> The notion of adding both SCTP and TLS the flag was brought up on the =
list back in October and it went unreplied to (far as I can tell). Here =
is the snippet:
>=20
> Although, given that TLS can ride on top of UDP or TCP, we may want to =
think of a second letter added to "L" to
> denote TLS-over-TCP and TLS-over-UDP (I doubt any implementations are =
using TLS-over-UDP for signaling only, but given that SCTP is starting
> to appear in kernels, maybe our flags ought to be "u, t, s, lu, lt, =
ls, U, T, S, LU, LT, LS").
>=20
> The fact that this is the second time this has been raised leads me to =
believe there is a need. I will raise this as a discussion topic in the =
upcoming meeting Prague.
>=20
> Regards,
>=20
> Gonzalo
>=20
>=20
> On Mar 15, 2011, at 3:13 PM, Anders Nygren wrote:
>=20
>> On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>>>=20
>>> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>>>=20
>>> Hi
>>> I will start writing one email for each issue in order to make it
>>> easier to track the different discussions.
>>>=20
>>> Thanks. That should help.
>>>=20
>>> I would like to propose that the Flag Field is moved from the
>>> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
>>> will be pure metadata that can be ignored if wanted and all =
interesting
>>> data about the message is in the second line of the record.
>>>=20
>>> I have no real preference on this one. I'll let others weigh in with =
their
>>> thoughts.
>>>=20
>>> Also I think it would be good to change the Sent/Received flag from
>>>=20
>>> Sent/Received flag
>>>=20
>>>         u =3D received UDP mesage
>>>         t =3D received TCP mesage
>>>         l =3D received TLS mesage
>>>         U =3D sent UDP mesage
>>>         T =3D sent TCP mesage
>>>         L =3D sent TLS mesage
>>>=20
>>> To
>>> Sent/Received flag [1 byte]
>>>         r =3D received message
>>>         s =3D sent message
>>>=20
>>> And add
>>> Protocol [1 byte]
>>>         u =3D UDP
>>>         t =3D TCP
>>>         l =3D TLS
>>>=20
>>> Since the proposed CLF already requires quite a lot of space there =
is
>>> little reason to
>>> try to pack different parameters into the same byte.
>>>=20
>>> This is what was proposed early on, but the group decided on =
consolidating
>>> the two. I'm not violently opposed or in favor of either, but I =
don't see
>>> any real benefit to separating the two out since all permutations =
are
>>> covered in a single easy byte.
>>=20
>> It is not a big deal but for instance if You want to find all sent =
messages it
>> is 3 tests instead of one for each record, (and if we add SCTP, see =
below),
>> then it would be 4. And when searching for all messages on a specific =
protocol
>> it is 2 tests instead of one.
>>=20
>> A quick check found RFC 4168, "The Stream Control Transmission
>> Protocol (SCTP) as a Transport for the Session Initiation Protocol
>> (SIP)"
>>=20
>> So maybe SCTP should be added as a protocol. I do not know if there =
is something
>> similar to TLS over SCTP, but I suspect things may get messy with a =
lot of
>> permutations in the future.
>>=20
>> So maybe we should consider 3 parameters
>> send/receive    sent, received
>> protocol           tcp, udp, sctp
>> secure             encrypted, plain text
>>=20
>> /Anders
>>=20
>>> Regards,
>>> Gonzalo
>>>=20
>>> /Anders
>>> _______________________________________________
>>> sip-clf mailing list
>>> sip-clf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>>=20
>>>=20
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-11--207099518
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,&nbsp;<div><br></div><div><div><div><div>I am a fan of keeping =
separate things separate. So I agree transport and send/receive would =
benefit from being untangled (IIRC, I may be the one responsible for =
entangling them).</div><div><br></div><div>The transport field was =
intended to match the SIP transport protocol - so I think one byte for =
UDP, TCP, TLS, SCTP is ok.&nbsp;</div><div><br></div><div>I don't see =
the need to have a separate security field (since we already have =
TCP/TLS sharing a byte) - so I would continue in the same vein. It's not =
a biggie for me - so if others want a secure/not secure byte that would =
be okay.&nbsp;</div><div><br></div><div>Peter Musgrave</div><div>(as =
individual)</div><div><br></div><div>On 2011-03-15, at 3:58 PM, Gonzalo =
Salgueiro wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Anders =
-&nbsp;<div><br></div><div>The notion of adding both SCTP and TLS the =
flag was brought up on the list back in October and it went unreplied to =
(far as I can tell). Here is the =
snippet:</div><div><br></div><div>Although, given that TLS can ride on =
top&nbsp;of UDP or TCP, we may want to think of a second letter added to =
"L" to<br>denote TLS-over-TCP and TLS-over-UDP (I doubt any =
implementations are&nbsp;using TLS-over-UDP for signaling only, but =
given that SCTP is starting<br>to appear in kernels, maybe our flags =
ought to be "u, t, s, lu, lt, ls,&nbsp;U, T, S, LU, LT, =
LS").</div><div><br></div><div>The fact that this is the second time =
this has been raised leads me to believe there is a need. I will raise =
this as a discussion topic in the upcoming meeting =
Prague.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo=
</div><div><br></div><div><br><div><div>On Mar 15, 2011, at 3:13 PM, =
Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">On Mar 15, 2011, at 1:49 PM, Anders Nygren =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">I will start =
writing one email for each issue in order to make =
it<br></blockquote><blockquote type=3D"cite">easier to track the =
different discussions.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks. That =
should help.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would like to =
propose that the Flag Field is moved from =
the<br></blockquote><blockquote type=3D"cite">&lt;IndexPointers&gt; to =
&lt;MandatoryFields&gt;. That way the =
&lt;IndexPointers&gt;<br></blockquote><blockquote type=3D"cite">will be =
pure metadata that can be ignored if wanted and all =
interesting<br></blockquote><blockquote type=3D"cite">data about the =
message is in the second line of the record.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I have no real =
preference on this one. I'll let others weigh in with =
their<br></blockquote><blockquote =
type=3D"cite">thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Also I think it =
would be good to change the Sent/Received flag =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Sent/Received =
flag<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
received UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
received TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
received TLS mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;U =3D sent =
UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T =3D sent =
TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L =3D sent =
TLS mesage<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">To<br></blockquote><blockquote type=3D"cite">Sent/Received =
flag [1 byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;r =3D =
received message<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s =3D sent =
message<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">And =
add<br></blockquote><blockquote type=3D"cite">Protocol [1 =
byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
UDP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
TCP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
TLS<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">Since the proposed CLF already requires quite a lot of =
space there is<br></blockquote><blockquote type=3D"cite">little reason =
to<br></blockquote><blockquote type=3D"cite">try to pack different =
parameters into the same byte.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This is what =
was proposed early on, but the group decided on =
consolidating<br></blockquote><blockquote type=3D"cite">the two. I'm not =
violently opposed or in favor of either, but I don't =
see<br></blockquote><blockquote type=3D"cite">any real benefit to =
separating the two out since all permutations =
are<br></blockquote><blockquote type=3D"cite">covered in a single easy =
byte.<br></blockquote><br>It is not a big deal but for instance if You =
want to find all sent messages it<br>is 3 tests instead of one for each =
record, (and if we add SCTP, see below),<br>then it would be 4. And when =
searching for all messages on a specific protocol<br>it is 2 tests =
instead of one.<br><br>A quick check found RFC 4168, "The Stream Control =
Transmission<br>Protocol (SCTP) as a Transport for the Session =
Initiation Protocol<br>(SIP)"<br><br>So maybe SCTP should be added as a =
protocol. I do not know if there is something<br>similar to TLS over =
SCTP, but I suspect things may get messy with a lot of<br>permutations =
in the future.<br><br>So maybe we should consider 3 =
parameters<br>send/receive &nbsp;&nbsp;&nbsp;sent, received<br>protocol =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;tcp, udp, =
sctp<br>secure =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;en=
crypted, plain text<br><br>/Anders<br><br><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></div>__=
_____________________________________________<br>sip-clf mailing =
list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></blockquote></div><br></div></div></body>=
</html>=

--Apple-Mail-11--207099518--

From peter.musgrave@magorcorp.com  Tue Mar 15 13:57:04 2011
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 A22B03A6EBA for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 13:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.098
X-Spam-Level: 
X-Spam-Status: No, score=-104.098 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 JXexC5K8ASOd for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 13:57:03 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 6F0AD3A6EB5 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 13:57:03 -0700 (PDT)
Received: by ywi6 with SMTP id 6so487023ywi.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 13:58:28 -0700 (PDT)
Received: by 10.90.16.37 with SMTP id 37mr500727agp.203.1300222708122; Tue, 15 Mar 2011 13:58:28 -0700 (PDT)
Received: from [192.168.1.119] (cpe-173-170-70-85.tampabay.res.rr.com [173.170.70.85]) by mx.google.com with ESMTPS id r8sm220938ane.19.2011.03.15.13.58.26 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Mar 2011 13:58:27 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-12--207040684
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <A7D4B0A0-B9FE-4A66-9440-88B40CC96D74@cisco.com>
Date: Tue, 15 Mar 2011 16:58:26 -0400
Message-Id: <D8C64806-F7C4-4992-8D8B-1756AB10EE0B@magorcorp.com>
References: <AANLkTinS_FpcdNohB_rtGdJXqr=P3_3gWg4TgHCNY+1T@mail.gmail.com> <A7D4B0A0-B9FE-4A66-9440-88B40CC96D74@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] draft-ietf-sipclf-format-01, TLV Start Pointer
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: Tue, 15 Mar 2011 20:57:04 -0000

--Apple-Mail-12--207040684
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Works for me

Peter Musgrave
(as individual)

On 2011-03-15, at 3:15 PM, Gonzalo Salgueiro wrote:

>=20
> If this simplifies getting the length of the final mandatory field =
(i.e Client-Txn), then I'm not opposed to having "TLV Start Pointer" =
point to the terminating line feed, rather than being set to all zeroes =
in the case of no optional fields.
>=20
> Are others OK with this logic?
>=20
> Gonzalo
>=20
>=20
>=20
> On Mar 15, 2011, at 2:02 PM, Anders Nygren wrote:
>=20
>> Hi
>> When extracting the mandatory fields the length of one parameter can =
normally be
>> calculated by
>> Length =3D <Pointer To Next Parameter> - <Pointer To This Parameter> =
-1
>>=20
>> However if there are no optional fields
>> "If the OPTIONAL TLV groups are not implemented, then the "TLV Start =
Pointer"
>> field MUST be set to zero (0x0000)."
>>=20
>> But to calculate the length of <Client-Txn> You first have to check =
if
>> <TLV Start Pointer> =3D 0x0000 in which case the <Client-Txn> length
>> is
>> Length =3D <Record Length> - <Pointer To Client-Txn> -1
>>=20
>> Similarly when extracting the TLVs it is necessary to do an extra =
test if
>> the <TLV Start Pointer> =3D 0x0000.
>>=20
>> I would like to propose that in the case when there are no optional =
fields that
>> the <TLV Start Pointer> points to the 0x0A at the end of the record.
>>=20
>> It is not a big complication but it will remove a couple of tests in =
a parser.
>>=20
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-12--207040684
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Works =
for me<div><br></div><div>Peter Musgrave</div><div>(as =
individual)</div><div><br><div><div>On 2011-03-15, at 3:15 PM, Gonzalo =
Salgueiro wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><br><div><div>If this =
simplifies getting the length of the final mandatory field (i.e =
Client-Txn), then I'm not opposed to having "TLV Start Pointer" point to =
the terminating line feed, rather than being set to all zeroes in the =
case of no optional fields.</div><div><br></div><div>Are others OK with =
this =
logic?</div><div><br></div><div>Gonzalo</div><div><br></div><div><br></div=
><div><br></div><div>On Mar 15, 2011, at 2:02 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi<br>When extracting the mandatory fields the length =
of one parameter can normally be<br>calculated by<br>Length =3D =
&lt;Pointer To Next Parameter&gt; - &lt;Pointer To This Parameter&gt; =
-1<br><br>However if there are no optional fields<br>"If the OPTIONAL =
TLV groups are not implemented, then the "TLV Start Pointer"<br>field =
MUST be set to zero (0x0000)."<br><br>But to calculate the length of =
&lt;Client-Txn&gt; You first have to check if<br>&lt;TLV Start =
Pointer&gt; =3D 0x0000 in which case the &lt;Client-Txn&gt; =
length<br>is<br>Length =3D &lt;Record Length&gt; - &lt;Pointer To =
Client-Txn&gt; -1<br><br>Similarly when extracting the TLVs it is =
necessary to do an extra test if<br>the &lt;TLV Start Pointer&gt; =3D =
0x0000.<br><br>I would like to propose that in the case when there are =
no optional fields that<br>the &lt;TLV Start Pointer&gt; points to the =
0x0A at the end of the record.<br><br>It is not a big complication but =
it will remove a couple of tests in a =
parser.<br><br>/Anders<br>_______________________________________________<=
br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></div></blockquote></div><br></div>_____=
__________________________________________<br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></blockquote></div><br></div></body></html=
>=

--Apple-Mail-12--207040684--

From anders.nygren@gmail.com  Tue Mar 15 14:09:01 2011
Return-Path: <anders.nygren@gmail.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 2C31E3A6EC4 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.369
X-Spam-Level: 
X-Spam-Status: No, score=-3.369 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 xdseS-SuBUZe for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:09:00 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 390353A6808 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:08:59 -0700 (PDT)
Received: by wwa36 with SMTP id 36so853851wwa.13 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:10:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=nxzkVKmIryMgR5cHYiKTw0ZnyofCBhUwJJoMqGl5IbM=; b=vfHCdDEXuDpjcjGkDfze+5LC7OeeU+cDlkINEHkOpkHPUwKEoR3Y2URmT0T6Vrsfku ga+IV4b3py4g/aK1iWQUrZJuGq5Z5p4GVEXLn/InZoa8mvPUdJrW99M/u6SK2yIpWzOv lYMmnTJmypWEGrZMbOtmef8OjZCg2kF0lSmzQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=p496BOiVeGD+fY/80O9mkQMNdTqpl6UQrqEhJXjlBeL0NGlsiPktMyxCD1b2xgNUfc VrRTjWOIyGPc6Apg/8dAbuTukSxijyh53UHfZK4Kloc8kNQus+pFPr3ObceuyfPz3Ypd /n8O6lS8Jv2oxp7oqDodeTjRRShKmhZfuLUJ0=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr4000249wej.77.1300223425023; Tue, 15 Mar 2011 14:10:25 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 14:10:24 -0700 (PDT)
Date: Tue, 15 Mar 2011 15:10:24 -0600
Message-ID: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
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: Tue, 15 Mar 2011 21:09:01 -0000

Hi
The list of mandatory fields includes Status-Code but not Reason-Phrase.
Wouldn't it be useful to have Reason-Phrase also since RFC3261

21.1.5 183 Session Progress

   The 183 (Session Progress) response is used to convey information
   about the progress of the call that is not otherwise classified.  The
   Reason-Phrase, header fields, or message body MAY be used to convey
   more details about the call progress.

21.4.1 400 Bad Request

   The request could not be understood due to malformed syntax.  The
   Reason-Phrase SHOULD identify the syntax problem in more detail, for
   example, "Missing Call-ID header field".

So at times Reason-Phrase gives some additional information that can not be
obtained from just the Status-Code. Maybe as an optional field.

/Anders

From peter.musgrave@magorcorp.com  Tue Mar 15 14:22:06 2011
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 38CAF3A6EC0 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, 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 Sdcj7wh1k0zd for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:22:04 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id C830D3A6E9B for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:22:04 -0700 (PDT)
Received: by gwb20 with SMTP id 20so491948gwb.31 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:23:30 -0700 (PDT)
Received: by 10.236.109.70 with SMTP id r46mr2048097yhg.31.1300224209179; Tue, 15 Mar 2011 14:23:29 -0700 (PDT)
Received: from [192.168.1.119] (cpe-173-170-70-85.tampabay.res.rr.com [173.170.70.85]) by mx.google.com with ESMTPS id 57sm138136yhl.20.2011.03.15.14.23.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Mar 2011 14:23:28 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com>
Date: Tue, 15 Mar 2011 17:23:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
References: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
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: Tue, 15 Mar 2011 21:22:06 -0000

I think as a predefined option field Reason Phrase makes sense.

It may be worth thinking about other optional header fields people might =
want...Refer, History-Info, Session-ID - might become a bit of a long =
list. Would this be viewed as useful?

Peter (as individual)

On 2011-03-15, at 5:10 PM, Anders Nygren wrote:

> Hi
> The list of mandatory fields includes Status-Code but not =
Reason-Phrase.
> Wouldn't it be useful to have Reason-Phrase also since RFC3261
>=20
> 21.1.5 183 Session Progress
>=20
>   The 183 (Session Progress) response is used to convey information
>   about the progress of the call that is not otherwise classified.  =
The
>   Reason-Phrase, header fields, or message body MAY be used to convey
>   more details about the call progress.
>=20
> 21.4.1 400 Bad Request
>=20
>   The request could not be understood due to malformed syntax.  The
>   Reason-Phrase SHOULD identify the syntax problem in more detail, for
>   example, "Missing Call-ID header field".
>=20
> So at times Reason-Phrase gives some additional information that can =
not be
> obtained from just the Status-Code. Maybe as an optional field.
>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


From anders.nygren@gmail.com  Tue Mar 15 14:30:38 2011
Return-Path: <anders.nygren@gmail.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 44AE93A6D54 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.39
X-Spam-Level: 
X-Spam-Status: No, score=-3.39 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 cxuGNu-0V5yU for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:30:37 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 2A4D53A6C81 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:30:37 -0700 (PDT)
Received: by wwa36 with SMTP id 36so870483wwa.13 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:32:02 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WCZnNzR1PAPtyQIj/BOvNkrA0x5Jcl4x/27tFIhk3mg=; b=UcTJ0FnAN/PbW1hlE6xsHBWoWSkquVjyIAD6UImitkTlbA0IKs+xY9kp3cE6WbWOvY yzzhsNOA/SnzUnTVfF+/0r5oZ62GT7VaJrzSUuiZygomINKUf6Gdeps1WtyRxWLn/DnF Qhi0Z52HFcesCMoAYDipGBnJUHr6EqbWfAUfA=
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:content-transfer-encoding; b=be9Ys8zz0efu+yoYJz8FU2BwwcGMK/dHtfQFurye02jZY4hU3BLAheiRVsZzL2Ru6j aMYUh7oFJ8ohkpW55/R4bTq/TNN2zVzYHcLwa/gNxsJ6czbxxgRCR7uCuR0F9NpB6/31 ed3SEMvO7Rnn4VKkbq3mE7bc1ikBF5dTkAmTI=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr4021612wej.77.1300224721883; Tue, 15 Mar 2011 14:32:01 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 14:32:01 -0700 (PDT)
In-Reply-To: <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
References: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com> <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
Date: Tue, 15 Mar 2011 15:32:01 -0600
Message-ID: <AANLkTi=HDJkBphTg6jGCrZaWKi8M16M+n_Mz5rY10Ubx@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
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: Tue, 15 Mar 2011 21:30:38 -0000

On Tue, Mar 15, 2011 at 3:23 PM, Peter Musgrave
<peter.musgrave@magorcorp.com> wrote:
> I think as a predefined option field Reason Phrase makes sense.
>
> It may be worth thinking about other optional header fields people might =
want...Refer, History-Info, Session-ID - might become a bit of a long list.=
 Would this be viewed as useful?
>

I don't have a list of header fields that I want to add, but I think
it may be good
to define most SIP headers as optional field just to prevent too many
vendors from
defining their own extensions for standard sip headers.

/Anders

> Peter (as individual)
>
> On 2011-03-15, at 5:10 PM, Anders Nygren wrote:
>
>> Hi
>> The list of mandatory fields includes Status-Code but not Reason-Phrase.
>> Wouldn't it be useful to have Reason-Phrase also since RFC3261
>>
>> 21.1.5 183 Session Progress
>>
>> =A0 The 183 (Session Progress) response is used to convey information
>> =A0 about the progress of the call that is not otherwise classified. =A0=
The
>> =A0 Reason-Phrase, header fields, or message body MAY be used to convey
>> =A0 more details about the call progress.
>>
>> 21.4.1 400 Bad Request
>>
>> =A0 The request could not be understood due to malformed syntax. =A0The
>> =A0 Reason-Phrase SHOULD identify the syntax problem in more detail, for
>> =A0 example, "Missing Call-ID header field".
>>
>> So at times Reason-Phrase gives some additional information that can not=
 be
>> obtained from just the Status-Code. Maybe as an optional field.
>>
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>
>

From vkg@bell-labs.com  Tue Mar 15 14:38:21 2011
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 6934E3A6EBB for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.594
X-Spam-Level: 
X-Spam-Status: No, score=-106.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 JRblZdxWE7PK for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:38:20 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 29C9A3A6E9D for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:38:19 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p2FLdjwM004723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-clf@ietf.org>; Tue, 15 Mar 2011 16:39:45 -0500 (CDT)
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p2FLdiBE021829 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 16:39:45 -0500 (CDT)
Message-ID: <4D7FDD06.3080501@bell-labs.com>
Date: Tue, 15 Mar 2011 16:41:26 -0500
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
References: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com>
In-Reply-To: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
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: Tue, 15 Mar 2011 21:38:21 -0000

On 03/15/2011 04:10 PM, Anders Nygren wrote:
> Hi
> The list of mandatory fields includes Status-Code but not Reason-Phrase.
> Wouldn't it be useful to have Reason-Phrase also since RFC3261
[...]
> So at times Reason-Phrase gives some additional information that can not be
> obtained from just the Status-Code. Maybe as an optional field.

Anders: I believe for the vast majority of the uses, a status-code
suffices (it gives you an accurate idea where in the transaction
machine a certain transaction is).

Reason-phrase is additional information, for sure, but it does
not detract from the knowledge gained earlier.

At this point, I don't see the need for it as an optional field
simply for the reason that this list could grow without bounds.

If an implementation wanted to produce a reason-phrase, the
vendor extension may be the best.  At least it will be visible and
a tool can parse and use the extension as intended.

If this is not agreeable, then we will have to rethink the
optional field logging to make it extensible to handle any SIP
header that an implementation may want to log instead of
picking and choosing some fields like Reason-phrase.

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/

From gsalguei@cisco.com  Tue Mar 15 14:43:40 2011
Return-Path: <gsalguei@cisco.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 A05F63A6EC6 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.385
X-Spam-Level: 
X-Spam-Status: No, score=-11.385 tagged_above=-999 required=5 tests=[AWL=1.213, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  RCVD_IN_DNSWL_HI=-8]
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 VmnWfsackuVQ for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 14:43:39 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 19C703A6B57 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 14:43:39 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FLbWKW001211; Tue, 15 Mar 2011 17:37:32 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FLbVEV015554;  Tue, 15 Mar 2011 17:37:31 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-25--204695844
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <33E31883-E842-46C6-A849-748452FDED3A@magorcorp.com>
Date: Tue, 15 Mar 2011 17:37:31 -0400
Message-Id: <1143C00C-3085-42FE-B6FE-C4E66DAA83C8@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com> <AANLkTi=RvWTVaaqBZwY1vEjZHU-smbXr3u-bMxLtSYG5@mail.gmail.com> <4CDB9960-FC4E-4197-AB64-C708BBE27D80@cisco.com> <33E31883-E842-46C6-A849-748452FDED3A@magorcorp.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 21:43:40 -0000

--Apple-Mail-25--204695844
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I agree Peter. Based on Ander's search example and some further thought =
on the matter has led me to the conclusion that we really do need to =
have these two separated. As far as the separate security field, I think =
it comes down to whether it is descriptive enough to say it is using TLS =
versus TLS over <blah>.

Gonzalo

On Mar 15, 2011, at 4:57 PM, Peter Musgrave wrote:

> Hi,=20
>=20
> I am a fan of keeping separate things separate. So I agree transport =
and send/receive would benefit from being untangled (IIRC, I may be the =
one responsible for entangling them).
>=20
> The transport field was intended to match the SIP transport protocol - =
so I think one byte for UDP, TCP, TLS, SCTP is ok.=20
>=20
> I don't see the need to have a separate security field (since we =
already have TCP/TLS sharing a byte) - so I would continue in the same =
vein. It's not a biggie for me - so if others want a secure/not secure =
byte that would be okay.=20
>=20
> Peter Musgrave
> (as individual)
>=20
> On 2011-03-15, at 3:58 PM, Gonzalo Salgueiro wrote:
>=20
>> Anders -=20
>>=20
>> The notion of adding both SCTP and TLS the flag was brought up on the =
list back in October and it went unreplied to (far as I can tell). Here =
is the snippet:
>>=20
>> Although, given that TLS can ride on top of UDP or TCP, we may want =
to think of a second letter added to "L" to
>> denote TLS-over-TCP and TLS-over-UDP (I doubt any implementations are =
using TLS-over-UDP for signaling only, but given that SCTP is starting
>> to appear in kernels, maybe our flags ought to be "u, t, s, lu, lt, =
ls, U, T, S, LU, LT, LS").
>>=20
>> The fact that this is the second time this has been raised leads me =
to believe there is a need. I will raise this as a discussion topic in =
the upcoming meeting Prague.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>>=20
>> On Mar 15, 2011, at 3:13 PM, Anders Nygren wrote:
>>=20
>>> On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>>>>=20
>>>> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>>>>=20
>>>> Hi
>>>> I will start writing one email for each issue in order to make it
>>>> easier to track the different discussions.
>>>>=20
>>>> Thanks. That should help.
>>>>=20
>>>> I would like to propose that the Flag Field is moved from the
>>>> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
>>>> will be pure metadata that can be ignored if wanted and all =
interesting
>>>> data about the message is in the second line of the record.
>>>>=20
>>>> I have no real preference on this one. I'll let others weigh in =
with their
>>>> thoughts.
>>>>=20
>>>> Also I think it would be good to change the Sent/Received flag from
>>>>=20
>>>> Sent/Received flag
>>>>=20
>>>>         u =3D received UDP mesage
>>>>         t =3D received TCP mesage
>>>>         l =3D received TLS mesage
>>>>         U =3D sent UDP mesage
>>>>         T =3D sent TCP mesage
>>>>         L =3D sent TLS mesage
>>>>=20
>>>> To
>>>> Sent/Received flag [1 byte]
>>>>         r =3D received message
>>>>         s =3D sent message
>>>>=20
>>>> And add
>>>> Protocol [1 byte]
>>>>         u =3D UDP
>>>>         t =3D TCP
>>>>         l =3D TLS
>>>>=20
>>>> Since the proposed CLF already requires quite a lot of space there =
is
>>>> little reason to
>>>> try to pack different parameters into the same byte.
>>>>=20
>>>> This is what was proposed early on, but the group decided on =
consolidating
>>>> the two. I'm not violently opposed or in favor of either, but I =
don't see
>>>> any real benefit to separating the two out since all permutations =
are
>>>> covered in a single easy byte.
>>>=20
>>> It is not a big deal but for instance if You want to find all sent =
messages it
>>> is 3 tests instead of one for each record, (and if we add SCTP, see =
below),
>>> then it would be 4. And when searching for all messages on a =
specific protocol
>>> it is 2 tests instead of one.
>>>=20
>>> A quick check found RFC 4168, "The Stream Control Transmission
>>> Protocol (SCTP) as a Transport for the Session Initiation Protocol
>>> (SIP)"
>>>=20
>>> So maybe SCTP should be added as a protocol. I do not know if there =
is something
>>> similar to TLS over SCTP, but I suspect things may get messy with a =
lot of
>>> permutations in the future.
>>>=20
>>> So maybe we should consider 3 parameters
>>> send/receive    sent, received
>>> protocol           tcp, udp, sctp
>>> secure             encrypted, plain text
>>>=20
>>> /Anders
>>>=20
>>>> Regards,
>>>> Gonzalo
>>>>=20
>>>> /Anders
>>>> _______________________________________________
>>>> sip-clf mailing list
>>>> sip-clf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>>>=20
>>>>=20
>>=20
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>=20


--Apple-Mail-25--204695844
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
agree Peter. Based on Ander's search example and some further thought on =
the matter has led me to the conclusion that we really do need to have =
these two separated. As far as the separate security field, I think it =
comes down to whether it is descriptive enough to say it is using TLS =
versus TLS over =
&lt;blah&gt;.<div><br></div><div>Gonzalo</div><div><br><div><div>On Mar =
15, 2011, at 4:57 PM, Peter Musgrave wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">Hi,&nbsp;<div><br></div><div><div><div><div>I am a fan of keeping =
separate things separate. So I agree transport and send/receive would =
benefit from being untangled (IIRC, I may be the one responsible for =
entangling them).</div><div><br></div><div>The transport field was =
intended to match the SIP transport protocol - so I think one byte for =
UDP, TCP, TLS, SCTP is ok.&nbsp;</div><div><br></div><div>I don't see =
the need to have a separate security field (since we already have =
TCP/TLS sharing a byte) - so I would continue in the same vein. It's not =
a biggie for me - so if others want a secure/not secure byte that would =
be okay.&nbsp;</div><div><br></div><div>Peter Musgrave</div><div>(as =
individual)</div><div><br></div><div>On 2011-03-15, at 3:58 PM, Gonzalo =
Salgueiro wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Anders =
-&nbsp;<div><br></div><div>The notion of adding both SCTP and TLS the =
flag was brought up on the list back in October and it went unreplied to =
(far as I can tell). Here is the =
snippet:</div><div><br></div><div>Although, given that TLS can ride on =
top&nbsp;of UDP or TCP, we may want to think of a second letter added to =
"L" to<br>denote TLS-over-TCP and TLS-over-UDP (I doubt any =
implementations are&nbsp;using TLS-over-UDP for signaling only, but =
given that SCTP is starting<br>to appear in kernels, maybe our flags =
ought to be "u, t, s, lu, lt, ls,&nbsp;U, T, S, LU, LT, =
LS").</div><div><br></div><div>The fact that this is the second time =
this has been raised leads me to believe there is a need. I will raise =
this as a discussion topic in the upcoming meeting =
Prague.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo=
</div><div><br></div><div><br><div><div>On Mar 15, 2011, at 3:13 PM, =
Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">On Mar 15, 2011, at 1:49 PM, Anders Nygren =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">I will start =
writing one email for each issue in order to make =
it<br></blockquote><blockquote type=3D"cite">easier to track the =
different discussions.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks. That =
should help.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would like to =
propose that the Flag Field is moved from =
the<br></blockquote><blockquote type=3D"cite">&lt;IndexPointers&gt; to =
&lt;MandatoryFields&gt;. That way the =
&lt;IndexPointers&gt;<br></blockquote><blockquote type=3D"cite">will be =
pure metadata that can be ignored if wanted and all =
interesting<br></blockquote><blockquote type=3D"cite">data about the =
message is in the second line of the record.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I have no real =
preference on this one. I'll let others weigh in with =
their<br></blockquote><blockquote =
type=3D"cite">thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Also I think it =
would be good to change the Sent/Received flag =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Sent/Received =
flag<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
received UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
received TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
received TLS mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;U =3D sent =
UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T =3D sent =
TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L =3D sent =
TLS mesage<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">To<br></blockquote><blockquote type=3D"cite">Sent/Received =
flag [1 byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;r =3D =
received message<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s =3D sent =
message<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">And =
add<br></blockquote><blockquote type=3D"cite">Protocol [1 =
byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
UDP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
TCP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
TLS<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">Since the proposed CLF already requires quite a lot of =
space there is<br></blockquote><blockquote type=3D"cite">little reason =
to<br></blockquote><blockquote type=3D"cite">try to pack different =
parameters into the same byte.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This is what =
was proposed early on, but the group decided on =
consolidating<br></blockquote><blockquote type=3D"cite">the two. I'm not =
violently opposed or in favor of either, but I don't =
see<br></blockquote><blockquote type=3D"cite">any real benefit to =
separating the two out since all permutations =
are<br></blockquote><blockquote type=3D"cite">covered in a single easy =
byte.<br></blockquote><br>It is not a big deal but for instance if You =
want to find all sent messages it<br>is 3 tests instead of one for each =
record, (and if we add SCTP, see below),<br>then it would be 4. And when =
searching for all messages on a specific protocol<br>it is 2 tests =
instead of one.<br><br>A quick check found RFC 4168, "The Stream Control =
Transmission<br>Protocol (SCTP) as a Transport for the Session =
Initiation Protocol<br>(SIP)"<br><br>So maybe SCTP should be added as a =
protocol. I do not know if there is something<br>similar to TLS over =
SCTP, but I suspect things may get messy with a lot of<br>permutations =
in the future.<br><br>So maybe we should consider 3 =
parameters<br>send/receive &nbsp;&nbsp;&nbsp;sent, received<br>protocol =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;tcp, udp, =
sctp<br>secure =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;en=
crypted, plain text<br><br>/Anders<br><br><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></div>__=
_____________________________________________<br>sip-clf mailing =
list<br><a href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote></div><br></div></div></div=
></blockquote></div><br></div></body></html>=

--Apple-Mail-25--204695844--

From anders.nygren@gmail.com  Tue Mar 15 15:00:11 2011
Return-Path: <anders.nygren@gmail.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 46FE93A6E24 for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 15:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.407
X-Spam-Level: 
X-Spam-Status: No, score=-4.407 tagged_above=-999 required=5 tests=[AWL=1.192,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 ZOtr26gDfunW for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 15:00:08 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 73EEE3A6EEB for <sip-clf@ietf.org>; Tue, 15 Mar 2011 15:00:07 -0700 (PDT)
Received: by wwa36 with SMTP id 36so891916wwa.13 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 15:01:32 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ImlKCPLHLjm5ltlcmIpOY1xfOwtI+JT7eFk0+5DomAc=; b=PMtHIvxLovcuZ6jecsHgf1h5xxd/QLr4VJavqsFR2PCWiTkvNV62NfnBctKE8DtUq8 yCbFwRH3i0IR5d6Y48+nNCpstfUkIdP2UPE5jsFLBOEuOsy9aTOGUwRTOXXFxC8DyIYT IIfpKlB+a6/yxml1jmvTz+nVcuSe68ArL7dX8=
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:content-transfer-encoding; b=BkLZ3yEoxgL3ETZphqHGQWB5wCE1hFR2cYlYdgAveqAFmju4DHZdIP/vk/UuhVlE90 UQQP+ypIPfMWNBf7y8UECjfipYQvxZFVGhA8AcIUGjn32JV5RkabMDKqDsUuUSyRGeMN ok5wiEDZe5QcyrQcJuBwmvi/nsGVU8RAANezs=
MIME-Version: 1.0
Received: by 10.216.221.92 with SMTP id q70mr12211738wep.107.1300226492330; Tue, 15 Mar 2011 15:01:32 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Tue, 15 Mar 2011 15:01:32 -0700 (PDT)
In-Reply-To: <1143C00C-3085-42FE-B6FE-C4E66DAA83C8@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com> <AANLkTi=RvWTVaaqBZwY1vEjZHU-smbXr3u-bMxLtSYG5@mail.gmail.com> <4CDB9960-FC4E-4197-AB64-C708BBE27D80@cisco.com> <33E31883-E842-46C6-A849-748452FDED3A@magorcorp.com> <1143C00C-3085-42FE-B6FE-C4E66DAA83C8@cisco.com>
Date: Tue, 15 Mar 2011 16:01:32 -0600
Message-ID: <AANLkTiknCiZGLWMCg8CacGb3xDbFEbH9hgqqoSutKXx_@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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: Tue, 15 Mar 2011 22:00:11 -0000

On Tue, Mar 15, 2011 at 3:37 PM, Gonzalo Salgueiro <gsalguei@cisco.com> wro=
te:
> I agree Peter. Based on Ander's search example and some further thought o=
n
> the matter has led me to the conclusion that we really do need to have th=
ese
> two separated. As far as the separate security field, I think it comes do=
wn
> to whether it is descriptive enough to say it is using TLS versus TLS ove=
r
> <blah>.

Since TLS can be run over TCP, UDP or SCTP, (I don't know if all alternativ=
es
apply for SIP), I think it may be useful to separate the transport protocol=
 from
the encryption. It is not something I feel very strongly about but I
prefer to keep
things separate and orthogonal.

/Anders

> Gonzalo
> On Mar 15, 2011, at 4:57 PM, Peter Musgrave wrote:
>
> Hi,
> I am a fan of keeping separate things separate. So I agree transport and
> send/receive would benefit from being untangled (IIRC, I may be the one
> responsible for entangling them).
> The transport field was intended to match the SIP transport protocol - so=
 I
> think one byte for UDP, TCP, TLS, SCTP is ok.
> I don't see the need to have a separate security field (since we already
> have TCP/TLS sharing a byte) - so I would continue in the same vein. It's
> not a biggie for me - so if others want a secure/not secure byte that wou=
ld
> be okay.
> Peter Musgrave
> (as individual)
> On 2011-03-15, at 3:58 PM, Gonzalo Salgueiro wrote:
>
> Anders -
> The notion of adding both SCTP and TLS the flag was brought up on the lis=
t
> back in October and it went unreplied to (far as I can tell). Here is the
> snippet:
> Although, given that TLS can ride on top=A0of UDP or TCP, we may want to =
think
> of a second letter added to "L" to
> denote TLS-over-TCP and TLS-over-UDP (I doubt any implementations are=A0u=
sing
> TLS-over-UDP for signaling only, but given that SCTP is starting
> to appear in kernels, maybe our flags ought to be "u, t, s, lu, lt, ls,=
=A0U,
> T, S, LU, LT, LS").
> The fact that this is the second time this has been raised leads me to
> believe there is a need. I will raise this as a discussion topic in the
> upcoming meeting Prague.
> Regards,
> Gonzalo
>
> On Mar 15, 2011, at 3:13 PM, Anders Nygren wrote:
>
> On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro <gsalguei@cisco.com>
> wrote:
>
> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>
> Hi
>
> I will start writing one email for each issue in order to make it
>
> easier to track the different discussions.
>
> Thanks. That should help.
>
> I would like to propose that the Flag Field is moved from the
>
> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
>
> will be pure metadata that can be ignored if wanted and all interesting
>
> data about the message is in the second line of the record.
>
> I have no real preference on this one. I'll let others weigh in with thei=
r
>
> thoughts.
>
> Also I think it would be good to change the Sent/Received flag from
>
> Sent/Received flag
>
> =A0=A0=A0=A0=A0=A0=A0=A0u =3D received UDP mesage
>
> =A0=A0=A0=A0=A0=A0=A0=A0t =3D received TCP mesage
>
> =A0=A0=A0=A0=A0=A0=A0=A0l =3D received TLS mesage
>
> =A0=A0=A0=A0=A0=A0=A0=A0U =3D sent UDP mesage
>
> =A0=A0=A0=A0=A0=A0=A0=A0T =3D sent TCP mesage
>
> =A0=A0=A0=A0=A0=A0=A0=A0L =3D sent TLS mesage
>
> To
>
> Sent/Received flag [1 byte]
>
> =A0=A0=A0=A0=A0=A0=A0=A0r =3D received message
>
> =A0=A0=A0=A0=A0=A0=A0=A0s =3D sent message
>
> And add
>
> Protocol [1 byte]
>
> =A0=A0=A0=A0=A0=A0=A0=A0u =3D UDP
>
> =A0=A0=A0=A0=A0=A0=A0=A0t =3D TCP
>
> =A0=A0=A0=A0=A0=A0=A0=A0l =3D TLS
>
> Since the proposed CLF already requires quite a lot of space there is
>
> little reason to
>
> try to pack different parameters into the same byte.
>
> This is what was proposed early on, but the group decided on consolidatin=
g
>
> the two. I'm not violently opposed or in favor of either, but I don't see
>
> any real benefit to separating the two out since all permutations are
>
> covered in a single easy byte.
>
> It is not a big deal but for instance if You want to find all sent messag=
es
> it
> is 3 tests instead of one for each record, (and if we add SCTP, see below=
),
> then it would be 4. And when searching for all messages on a specific
> protocol
> it is 2 tests instead of one.
>
> A quick check found RFC 4168, "The Stream Control Transmission
> Protocol (SCTP) as a Transport for the Session Initiation Protocol
> (SIP)"
>
> So maybe SCTP should be added as a protocol. I do not know if there is
> something
> similar to TLS over SCTP, but I suspect things may get messy with a lot o=
f
> permutations in the future.
>
> So maybe we should consider 3 parameters
> send/receive =A0=A0=A0sent, received
> protocol =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0tcp, udp, sctp
> secure =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0encrypted, plain text
>
> /Anders
>
> Regards,
>
> Gonzalo
>
> /Anders
>
> _______________________________________________
>
> 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
>
>
>

From gsalguei@cisco.com  Tue Mar 15 15:01:39 2011
Return-Path: <gsalguei@cisco.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 ED2DA3A6E9E for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 15:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.461
X-Spam-Level: 
X-Spam-Status: No, score=-10.461 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 JNuQKH-ezEVF for <sip-clf@core3.amsl.com>; Tue, 15 Mar 2011 15:01:39 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 9C85A3A6E24 for <sip-clf@ietf.org>; Tue, 15 Mar 2011 15:01:38 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FLtWw4002801; Tue, 15 Mar 2011 17:55:32 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2FLtSJ4001728;  Tue, 15 Mar 2011 17:55:29 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-26--203618655
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
Date: Tue, 15 Mar 2011 17:55:28 -0400
Message-Id: <7DB6DBE8-760E-4C32-B4C2-7EFD0A09FF89@cisco.com>
References: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com> <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
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: Tue, 15 Mar 2011 22:01:40 -0000

--Apple-Mail-26--203618655
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Mar 15, 2011, at 5:23 PM, Peter Musgrave wrote:

> I think as a predefined option field Reason Phrase makes sense.
>=20
> It may be worth thinking about other optional header fields people =
might want...Refer, History-Info, Session-ID - might become a bit of a =
long list. Would this be viewed as useful?

I had it as one of the discussion topics for Prague. I think we =
fundamentally need to decide what fields we want as Pre-defined Optional =
Fields IF that list a reasonable one. If we want to open it up (as =
Anders suggest) to ALL SIP fields, then this would likely require a =
different mechanism entirely.

Gonzalo

>=20
> Peter (as individual)
>=20
> On 2011-03-15, at 5:10 PM, Anders Nygren wrote:
>=20
>> Hi
>> The list of mandatory fields includes Status-Code but not =
Reason-Phrase.
>> Wouldn't it be useful to have Reason-Phrase also since RFC3261
>>=20
>> 21.1.5 183 Session Progress
>>=20
>>  The 183 (Session Progress) response is used to convey information
>>  about the progress of the call that is not otherwise classified.  =
The
>>  Reason-Phrase, header fields, or message body MAY be used to convey
>>  more details about the call progress.
>>=20
>> 21.4.1 400 Bad Request
>>=20
>>  The request could not be understood due to malformed syntax.  The
>>  Reason-Phrase SHOULD identify the syntax problem in more detail, for
>>  example, "Missing Call-ID header field".
>>=20
>> So at times Reason-Phrase gives some additional information that can =
not be
>> obtained from just the Status-Code. Maybe as an optional field.
>>=20
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-26--203618655
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 15, 2011, at 5:23 PM, Peter Musgrave =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>I think as a predefined option field Reason Phrase =
makes sense.<br><br>It may be worth thinking about other optional header =
fields people might want...Refer, History-Info, Session-ID - might =
become a bit of a long list. Would this be viewed as =
useful?<br></div></blockquote><div><br></div>I had it as one of the =
discussion topics for Prague. I think we fundamentally need to decide =
what fields we want as Pre-defined Optional Fields IF that list a =
reasonable one. If we want to open it up (as Anders suggest) to ALL SIP =
fields, then this would likely require a different mechanism =
entirely.</div><div><br></div><div>Gonzalo</div><div><br><blockquote =
type=3D"cite"><div><br>Peter (as individual)<br><br>On 2011-03-15, at =
5:10 PM, Anders Nygren wrote:<br><br><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">The list of =
mandatory fields includes Status-Code but not =
Reason-Phrase.<br></blockquote><blockquote type=3D"cite">Wouldn't it be =
useful to have Reason-Phrase also since =
RFC3261<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">21.1.5 183 =
Session Progress<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> &nbsp;The 183 =
(Session Progress) response is used to convey =
information<br></blockquote><blockquote type=3D"cite"> &nbsp;about the =
progress of the call that is not otherwise classified. =
&nbsp;The<br></blockquote><blockquote type=3D"cite"> =
&nbsp;Reason-Phrase, header fields, or message body MAY be used to =
convey<br></blockquote><blockquote type=3D"cite"> &nbsp;more details =
about the call progress.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">21.4.1 400 Bad =
Request<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> &nbsp;The =
request could not be understood due to malformed syntax. =
&nbsp;The<br></blockquote><blockquote type=3D"cite"> &nbsp;Reason-Phrase =
SHOULD identify the syntax problem in more detail, =
for<br></blockquote><blockquote type=3D"cite"> &nbsp;example, "Missing =
Call-ID header field".<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">So at times =
Reason-Phrase gives some additional information that can not =
be<br></blockquote><blockquote type=3D"cite">obtained from just the =
Status-Code. Maybe as an optional field.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><br>_______________________=
________________________<br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></body></html=
>=

--Apple-Mail-26--203618655--

From anders.nygren@gmail.com  Wed Mar 16 09:15:32 2011
Return-Path: <anders.nygren@gmail.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 D35D73A69C7 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 09:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 W-knyzsDx6HV for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 09:15:32 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id B27073A69AD for <sip-clf@ietf.org>; Wed, 16 Mar 2011 09:15:31 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1556041wwa.13 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 09:16:57 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=qOhuPyjmsbBn+6AWSj8SbAxBADb9vQzKhZJFWSJR12o=; b=SQNm+HXoTLfpedBeHTX2R9lWwKXGdN/nG0gt20fJiuHBCwEQQU7DDRObuX+ZRJp5Yd ocP0c3MxGJI/MN1jMbUPeQvUGI23NIiUSnTRp4xM35/A/pqulebbG9ZDOuAJ2hNTphbu qxaveRXz6BBVrrTaJXCuQCIyJvnaoWFztszJg=
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:content-transfer-encoding; b=P0hpquCeSEhivEsW4SbXmKp7TnZsvfYqMjWTFhgQjlmIYU9LxKwcacjcFZ16a1iRni GDC0QxxF2gle3Pf8wy1Y94eJhoY5a7ONaWhO04CWVg8A2h71/5cvDnmA1klaAx4A1I05 hvlMAFUahjvHXAT8spn4YZxRIlrB/hW/PY0jE=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr270541wej.77.1300292217780; Wed, 16 Mar 2011 09:16:57 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Wed, 16 Mar 2011 09:16:57 -0700 (PDT)
In-Reply-To: <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com>
Date: Wed, 16 Mar 2011 10:16:57 -0600
Message-ID: <AANLkTinbpTkkYQrA7hQnvCULq2Hud-N6Pd3Du0Gh-4yB@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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, 16 Mar 2011 16:15:32 -0000

On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro <gsalguei@cisco.com> wr=
ote:
>
> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>
> Hi
> I will start writing one email for each issue in order to make it
> easier to track the different discussions.
>
> Thanks. That should help.
>
> I would like to propose that the Flag Field is moved from the
> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
> will be pure metadata that can be ignored if wanted and all interesting
> data about the message is in the second line of the record.
>
> I have no real preference on this one. I'll let others weigh in with thei=
r
> thoughts.
>

Just one more comment on this. In draft-01 ch. 4 it says

  "1.  Index Pointers - The first 64-bytes of this format.  This
      portion is primarily composed of a list of pointers that indicate
      the beginning of both the variable length mandatory and optional
      fields that are logged as part of this record.  These pointers are
      implemented as a mechanism to improve processing of these records
      and to allow a reader to expeditiously skip right to the desired
      field without unnecessarily going through the entire record."

and ch 4.1.  Index Pointers

   "The <IndexPointers> portion of the SIP CLF record (shown in Figure 3)
   is a 64-byte header that indicates meta-data about the record."

And finally ch 6.  Text Tool Considerations

"Index lines may be rapidly discarded by checking the first character
 of the line: index lines will always start with an alphabetical character.=
.."

All these sections together gives the impression that the  <IndexPointers>
portion only contains meta data and can safely ignored if wanted.

So I would prefer that the flags field is moved to the <MandatoryFields>
part. And if not then I think that the descriptions in ch 4, ch 4.1 and ch =
6
should be updated.

/Anders

> Also I think it would be good to change the Sent/Received flag from
>
> Sent/Received flag
>
> =A0=A0=A0=A0=A0=A0=A0=A0u =3D received UDP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0t =3D received TCP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0l =3D received TLS mesage
> =A0=A0=A0=A0=A0=A0=A0=A0U =3D sent UDP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0T =3D sent TCP mesage
> =A0=A0=A0=A0=A0=A0=A0=A0L =3D sent TLS mesage
>
> To
> Sent/Received flag [1 byte]
> =A0=A0=A0=A0=A0=A0=A0=A0r =3D received message
> =A0=A0=A0=A0=A0=A0=A0=A0s =3D sent message
>
> And add
> Protocol [1 byte]
> =A0=A0=A0=A0=A0=A0=A0=A0u =3D UDP
> =A0=A0=A0=A0=A0=A0=A0=A0t =3D TCP
> =A0=A0=A0=A0=A0=A0=A0=A0l =3D TLS
>
> Since the proposed CLF already requires quite a lot of space there is
> little reason to
> try to pack different parameters into the same byte.
>
> This is what was proposed early on, but the group decided on consolidatin=
g
> the two. I'm not violently opposed or in favor of either, but I don't see
> any real benefit to separating the two out since all permutations are
> covered in a single easy byte.
> Regards,
> Gonzalo
>
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>

From anders.nygren@gmail.com  Wed Mar 16 09:30:43 2011
Return-Path: <anders.nygren@gmail.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 D08A23A69C6 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 09:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.506
X-Spam-Level: 
X-Spam-Status: No, score=-3.506 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 auEkCjU0voYU for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 09:30:43 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 0A17E3A69D0 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 09:30:41 -0700 (PDT)
Received: by wyb42 with SMTP id 42so2002905wyb.31 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 09:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=5jcasxLfHOaG8YE6y7we5OOa4Xe10idyd0LNXMnVM7c=; b=Y53zH+tEvKfbaPplY7z2nqNnnTyvrUfLxznPlZwKGrbmUN2E6vbadSEHVt5D0wftSO ITFho8B9l7E+DrFnS0/omwRirz/33LEz7HK+2gCHTOPX3nhJrLxdXQ+cGebgtbyXmWlj hjo+of9ZzZ3k+eWHADxbExQ6QR8/NZloH8FGE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=eKHLuoAaX/Ex8PBe6jDo7VWlhMV/ph4naQw75ILHBsNxVTslzZIpI/nYbpXj/MHUAe rlZuZackkUg9X6mRD4q97ZDkhuS1p8dF1Uiiz7mdMvcI9IRWV9lVJoaDavcpGmEtgNIW 6JIIm0mzQY6OwLJyRWIagqRWgCI4LgxB3vBX8=
MIME-Version: 1.0
Received: by 10.216.221.92 with SMTP id q70mr143008wep.107.1300293128148; Wed, 16 Mar 2011 09:32:08 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Wed, 16 Mar 2011 09:32:08 -0700 (PDT)
Date: Wed, 16 Mar 2011 10:32:08 -0600
Message-ID: <AANLkTinQA6Ve2GQo1BpwRtgZaci7SXpOMhr4cmv6t_fG@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-format-01, optional fields
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, 16 Mar 2011 16:30:43 -0000

Hi
I hope this is the last from me for this version.

In the descriptions of the optional fields I think that there some things
that should be clarified.

- Can the optional fields be in any order, or do they have to be sorted
by increasing tag values?

- If an optional field represents a SIP header, e.g. Contact, can appear
several times in a SIP message how are they logged, as several optional
fields with the same tag, or does the all the Contact headers have to be
concatenated in the value of one optional field. (I think that draft-00
explicitly stated that the contact optional field could be repeated, but that
seems to have disappeared in draft-01.)

-If an optional field can be present several times, do they have to be adjacent
or can they be mixed with other optional fields?

- figure 1 shows that the optional fields are before the vendor extensions.
If we have the same format for standard optional fields and vendor extensions
is it still a requirement that they be separate, or can they be mixed.

/Anders

From gsalguei@cisco.com  Wed Mar 16 10:07:13 2011
Return-Path: <gsalguei@cisco.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 BEC893A69E6 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 10:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.469
X-Spam-Level: 
X-Spam-Status: No, score=-10.469 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 elA7EAwB1f45 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 10:07:12 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 9B6EF3A6941 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 10:07:12 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GH8c7G015919; Wed, 16 Mar 2011 13:08:38 -0400 (EDT)
Received: from dhcp-64-102-211-8.cisco.com (dhcp-64-102-211-8.cisco.com [64.102.211.8]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GH8bph020394;  Wed, 16 Mar 2011 13:08:37 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-40--134429490
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTinQA6Ve2GQo1BpwRtgZaci7SXpOMhr4cmv6t_fG@mail.gmail.com>
Date: Wed, 16 Mar 2011 13:08:37 -0400
Message-Id: <44188993-8A2D-486A-9DAC-9F155CAD0957@cisco.com>
References: <AANLkTinQA6Ve2GQo1BpwRtgZaci7SXpOMhr4cmv6t_fG@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, optional fields
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, 16 Mar 2011 17:07:13 -0000

--Apple-Mail-40--134429490
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Inline...

On Mar 16, 2011, at 12:32 PM, Anders Nygren wrote:

> Hi
> I hope this is the last from me for this version.
>=20
> In the descriptions of the optional fields I think that there some =
things
> that should be clarified.
>=20
> - Can the optional fields be in any order, or do they have to be =
sorted
> by increasing tag values?

They can be specified in any order, though I suppose most people would =
logically do it based on increasing tag number (assuming pre-defined =
optional field). Do you think this should be further restricted so that =
implementers MUST implement the pre-defined optional fields in ascending =
tag number order?
>=20
> - If an optional field represents a SIP header, e.g. Contact, can =
appear
> several times in a SIP message how are they logged, as several =
optional
> fields with the same tag, or does the all the Contact headers have to =
be
> concatenated in the value of one optional field. (I think that =
draft-00
> explicitly stated that the contact optional field could be repeated, =
but that
> seems to have disappeared in draft-01.)
>=20
This bit of text from -00 was removed as this is one of the areas =
requiring further discussion. For the Contact header (tag =3D0x0000) " =
the text in -00 states "(can be repeated)" but this is unclear as to =
whether this is logged as a single optional field entry with multiple =
instances of the Contact header in the Value field or as multiple =
entries (i.e. one for each Contact) with the same 0x0000 tag. I'm not =
sure which is better. This is something I hope to have more clarity on =
coming out of Prague, but maybe we can get a few folks to weigh in on =
this here on the alias.
=20

> -If an optional field can be present several times, do they have to be =
adjacent
> or can they be mixed with other optional fields?

This obviously depends upon what we decide for the above issue as far as =
whether we allow more more than one optional field entry with the same =
tag number, but there are no restrictions on this now. Do you have a =
preference.
>=20
> - figure 1 shows that the optional fields are before the vendor =
extensions.
> If we have the same format for standard optional fields and vendor =
extensions
> is it still a requirement that they be separate, or can they be mixed.

I don't want to speculate on where the conversations in Prague will lead =
us, but I would think we should stick with laying out the pre-defined =
optional elements first and the vendor-specified elements next.

Regards,

Gonzalo

>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-40--134429490
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Inline...<div><br><div><div>On Mar 16, 2011, at 12:32 PM, Anders =
Nygren wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi<br>I hope this is the last from me for this =
version.<br><br>In the descriptions of the optional fields I think that =
there some things<br>that should be clarified.<br><br>- Can the optional =
fields be in any order, or do they have to be sorted<br>by increasing =
tag values?<br></div></blockquote><div><br></div>They can be specified =
in any order, though I suppose most people would logically do it based =
on increasing tag number (assuming pre-defined optional field). Do you =
think this should be further restricted so that implementers MUST =
implement the pre-defined optional fields in ascending tag number =
order?<br><blockquote type=3D"cite"><div><br>- If an optional field =
represents a SIP header, e.g. Contact, can appear<br>several times in a =
SIP message how are they logged, as several optional<br>fields with the =
same tag, or does the all the Contact headers have to be<br>concatenated =
in the value of one optional field. (I think that draft-00<br>explicitly =
stated that the contact optional field could be repeated, but =
that<br>seems to have disappeared in =
draft-01.)<br><br></div></blockquote>This bit of text from -00 was =
removed as this is one of the areas requiring further discussion. For =
the Contact header (tag =3D0x0000) " the text in -00 states "<span =
class=3D"Apple-style-span" style=3D"font-family: monospace; white-space: =
pre; ">(can be repeated)" but this is unclear as to whether this is =
logged as a single optional field entry with multiple instances of the =
Contact header in the Value field or as multiple entries (i.e. one for =
each Contact) with the same 0x0000 tag. I'm not sure which is better. =
This is something I hope to have more clarity on coming out of Prague, =
but maybe we can get a few folks to weigh in on this here on the =
alias.</span></div><div>&nbsp;</div><div><br><blockquote =
type=3D"cite"><div>-If an optional field can be present several times, =
do they have to be adjacent<br>or can they be mixed with other optional =
fields?<br></div></blockquote><div><br></div>This obviously depends upon =
what we decide for the above issue as far as whether we allow more more =
than one optional field entry with the same tag number, but there are no =
restrictions on this now. Do you have a preference.<br><blockquote =
type=3D"cite"><div><br>- figure 1 shows that the optional fields are =
before the vendor extensions.<br>If we have the same format for standard =
optional fields and vendor extensions<br>is it still a requirement that =
they be separate, or can they be =
mixed.<br></div></blockquote><div><br></div>I don't want to speculate on =
where the conversations in Prague will lead us, but I would think we =
should stick with laying out the pre-defined optional elements first and =
the vendor-specified elements =
next.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo</=
div><div><br><blockquote =
type=3D"cite"><div><br>/Anders<br>________________________________________=
_______<br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></div></body>=
</html>=

--Apple-Mail-40--134429490--

From gsalguei@cisco.com  Wed Mar 16 10:15:20 2011
Return-Path: <gsalguei@cisco.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 6B3AC3A69E6 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 10:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.476
X-Spam-Level: 
X-Spam-Status: No, score=-10.476 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 CDopCiGcI7Y5 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 10:15:19 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 2B3C43A6941 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 10:15:19 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GHGiRm016670; Wed, 16 Mar 2011 13:16:44 -0400 (EDT)
Received: from dhcp-64-102-211-8.cisco.com (dhcp-64-102-211-8.cisco.com [64.102.211.8]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GHGitY029765;  Wed, 16 Mar 2011 13:16:44 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-42--133942962
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTinbpTkkYQrA7hQnvCULq2Hud-N6Pd3Du0Gh-4yB@mail.gmail.com>
Date: Wed, 16 Mar 2011 13:16:44 -0400
Message-Id: <491E79D5-4285-4979-8A47-ADC4D56E5999@cisco.com>
References: <AANLkTinaDKurSgbz3m5A2GV0k-zf21VAsRJzZXKTfH26@mail.gmail.com> <C664DEB6-88D5-44F1-88BC-C9FC123D72FE@cisco.com> <AANLkTinbpTkkYQrA7hQnvCULq2Hud-N6Pd3Du0Gh-4yB@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, Flag field
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, 16 Mar 2011 17:15:20 -0000

--Apple-Mail-42--133942962
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This is first time this has been raised and is a valid point. I see =
value in moving it to <MandatoryFields>. Let's let others chime in as =
well.

If we don't get some critical mass on this issue, I'll add it to the =
discussion agenda for Prague.

Regards,

Gonzalo

On Mar 16, 2011, at 12:16 PM, Anders Nygren wrote:

> On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>>=20
>> On Mar 15, 2011, at 1:49 PM, Anders Nygren wrote:
>>=20
>> Hi
>> I will start writing one email for each issue in order to make it
>> easier to track the different discussions.
>>=20
>> Thanks. That should help.
>>=20
>> I would like to propose that the Flag Field is moved from the
>> <IndexPointers> to <MandatoryFields>. That way the <IndexPointers>
>> will be pure metadata that can be ignored if wanted and all =
interesting
>> data about the message is in the second line of the record.
>>=20
>> I have no real preference on this one. I'll let others weigh in with =
their
>> thoughts.
>>=20
>=20
> Just one more comment on this. In draft-01 ch. 4 it says
>=20
>  "1.  Index Pointers - The first 64-bytes of this format.  This
>      portion is primarily composed of a list of pointers that indicate
>      the beginning of both the variable length mandatory and optional
>      fields that are logged as part of this record.  These pointers =
are
>      implemented as a mechanism to improve processing of these records
>      and to allow a reader to expeditiously skip right to the desired
>      field without unnecessarily going through the entire record."
>=20
> and ch 4.1.  Index Pointers
>=20
>   "The <IndexPointers> portion of the SIP CLF record (shown in Figure =
3)
>   is a 64-byte header that indicates meta-data about the record."
>=20
> And finally ch 6.  Text Tool Considerations
>=20
> "Index lines may be rapidly discarded by checking the first character
> of the line: index lines will always start with an alphabetical =
character..."
>=20
> All these sections together gives the impression that the  =
<IndexPointers>
> portion only contains meta data and can safely ignored if wanted.
>=20
> So I would prefer that the flags field is moved to the =
<MandatoryFields>
> part. And if not then I think that the descriptions in ch 4, ch 4.1 =
and ch 6
> should be updated.
>=20
> /Anders
>=20
>> Also I think it would be good to change the Sent/Received flag from
>>=20
>> Sent/Received flag
>>=20
>>         u =3D received UDP mesage
>>         t =3D received TCP mesage
>>         l =3D received TLS mesage
>>         U =3D sent UDP mesage
>>         T =3D sent TCP mesage
>>         L =3D sent TLS mesage
>>=20
>> To
>> Sent/Received flag [1 byte]
>>         r =3D received message
>>         s =3D sent message
>>=20
>> And add
>> Protocol [1 byte]
>>         u =3D UDP
>>         t =3D TCP
>>         l =3D TLS
>>=20
>> Since the proposed CLF already requires quite a lot of space there is
>> little reason to
>> try to pack different parameters into the same byte.
>>=20
>> This is what was proposed early on, but the group decided on =
consolidating
>> the two. I'm not violently opposed or in favor of either, but I don't =
see
>> any real benefit to separating the two out since all permutations are
>> covered in a single easy byte.
>> Regards,
>> Gonzalo
>>=20
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20


--Apple-Mail-42--133942962
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This =
is first time this has been raised and is a valid point. I see value in =
moving it to &lt;MandatoryFields&gt;. Let's let others chime in as =
well.<div><br></div><div>If we don't get some critical mass on this =
issue, I'll add it to the discussion agenda for =
Prague.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzalo=
</div><div><br><div><div>On Mar 16, 2011, at 12:16 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>On Tue, Mar 15, 2011 at 12:38 PM, Gonzalo Salgueiro =
&lt;<a href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">On Mar 15, 2011, at 1:49 PM, Anders Nygren =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">I will start =
writing one email for each issue in order to make =
it<br></blockquote><blockquote type=3D"cite">easier to track the =
different discussions.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks. That =
should help.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I would like to =
propose that the Flag Field is moved from =
the<br></blockquote><blockquote type=3D"cite">&lt;IndexPointers&gt; to =
&lt;MandatoryFields&gt;. That way the =
&lt;IndexPointers&gt;<br></blockquote><blockquote type=3D"cite">will be =
pure metadata that can be ignored if wanted and all =
interesting<br></blockquote><blockquote type=3D"cite">data about the =
message is in the second line of the record.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I have no real =
preference on this one. I'll let others weigh in with =
their<br></blockquote><blockquote =
type=3D"cite">thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>Just one more comment on this. In =
draft-01 ch. 4 it says<br><br> &nbsp;"1. &nbsp;Index Pointers - The =
first 64-bytes of this format. &nbsp;This<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;portion is primarily composed of a list of =
pointers that indicate<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the beginning =
of both the variable length mandatory and optional<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;fields that are logged as part of this =
record. &nbsp;These pointers are<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;implemented as a mechanism to improve =
processing of these records<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and to =
allow a reader to expeditiously skip right to the desired<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;field without unnecessarily going through =
the entire record."<br><br>and ch 4.1. &nbsp;Index Pointers<br><br> =
&nbsp;&nbsp;"The &lt;IndexPointers&gt; portion of the SIP CLF record =
(shown in Figure 3)<br> &nbsp;&nbsp;is a 64-byte header that indicates =
meta-data about the record."<br><br>And finally ch 6. &nbsp;Text Tool =
Considerations<br><br>"Index lines may be rapidly discarded by checking =
the first character<br> of the line: index lines will always start with =
an alphabetical character..."<br><br>All these sections together gives =
the impression that the &nbsp;&lt;IndexPointers&gt;<br>portion only =
contains meta data and can safely ignored if wanted.<br><br>So I would =
prefer that the flags field is moved to the =
&lt;MandatoryFields&gt;<br>part. And if not then I think that the =
descriptions in ch 4, ch 4.1 and ch 6<br>should be =
updated.<br><br>/Anders<br><br><blockquote type=3D"cite">Also I think it =
would be good to change the Sent/Received flag =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Sent/Received =
flag<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
received UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
received TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
received TLS mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;U =3D sent =
UDP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T =3D sent =
TCP mesage<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;L =3D sent =
TLS mesage<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">To<br></blockquote><blockquote type=3D"cite">Sent/Received =
flag [1 byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;r =3D =
received message<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s =3D sent =
message<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">And =
add<br></blockquote><blockquote type=3D"cite">Protocol [1 =
byte]<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;u =3D =
UDP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t =3D =
TCP<br></blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;l =3D =
TLS<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">Since the proposed CLF already requires quite a lot of =
space there is<br></blockquote><blockquote type=3D"cite">little reason =
to<br></blockquote><blockquote type=3D"cite">try to pack different =
parameters into the same byte.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This is what =
was proposed early on, but the group decided on =
consolidating<br></blockquote><blockquote type=3D"cite">the two. I'm not =
violently opposed or in favor of either, but I don't =
see<br></blockquote><blockquote type=3D"cite">any real benefit to =
separating the two out since all permutations =
are<br></blockquote><blockquote type=3D"cite">covered in a single easy =
byte.<br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-42--133942962--

From anders.nygren@gmail.com  Wed Mar 16 10:33:25 2011
Return-Path: <anders.nygren@gmail.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 A101A3A69FB for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 10:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.512
X-Spam-Level: 
X-Spam-Status: No, score=-3.512 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 mOa4OA6T8Yhr for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 10:33:24 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id D94733A69F2 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 10:33:23 -0700 (PDT)
Received: by wyb42 with SMTP id 42so2068437wyb.31 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 10:34:49 -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 :message-id:subject:from:to:cc:content-type; bh=MiyUOXPGBDEGNf4qOZd94INb1JtyiC8Lw9xb/dLO7aQ=; b=GZexWpcP/k4Rwf/qsg0uEFRCcJuC/T6rWIZN61nXwLaLf4gofZaWbLsuLeIiqaBUlI 3VVrZijagrLeAoIH1rSiwNeSoOqYUTK08aqXBm9RRfSuQDCzf689PeS80rpSQUZ5peZ8 THAn4ydU9/B3Xz81Ap34figTBdh0U+GgzBohQ=
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=iiWFdc/zH3P8gnXvoclNXLP8u1t56Le2ATSaLdAHnn8BvXy1Ddvg5jYw+TcfDPjy7G 30gw3+EmbBMVwTeNnCLGB1DZn2UJVLXQ77TgHxuVeA03lYCHEnrJvKCHZcyxHxS40GKW vWiGspi3sZycvmHUFXd2qwyCkiYHUaSqztQi0=
MIME-Version: 1.0
Received: by 10.216.62.67 with SMTP id x45mr343399wec.92.1300296889822; Wed, 16 Mar 2011 10:34:49 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Wed, 16 Mar 2011 10:34:49 -0700 (PDT)
In-Reply-To: <44188993-8A2D-486A-9DAC-9F155CAD0957@cisco.com>
References: <AANLkTinQA6Ve2GQo1BpwRtgZaci7SXpOMhr4cmv6t_fG@mail.gmail.com> <44188993-8A2D-486A-9DAC-9F155CAD0957@cisco.com>
Date: Wed, 16 Mar 2011 11:34:49 -0600
Message-ID: <AANLkTinpBOMN8W1K1trV2jPK-00KRTh=qBmF2F9c6P92@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, optional fields
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, 16 Mar 2011 17:33:25 -0000

On Wed, Mar 16, 2011 at 11:08 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wrote:
> Inline...
> On Mar 16, 2011, at 12:32 PM, Anders Nygren wrote:
>
> Hi
> I hope this is the last from me for this version.
>
> In the descriptions of the optional fields I think that there some things
> that should be clarified.
>
> - Can the optional fields be in any order, or do they have to be sorted
> by increasing tag values?
>
> They can be specified in any order, though I suppose most people would
> logically do it based on increasing tag number (assuming pre-defined
> optional field). Do you think this should be further restricted so that
> implementers MUST implement the pre-defined optional fields in ascending tag
> number order?

I think it is OK to allow any order.
But I do think that it is important to mention in the spec whatever is
decided.

>
> - If an optional field represents a SIP header, e.g. Contact, can appear
> several times in a SIP message how are they logged, as several optional
> fields with the same tag, or does the all the Contact headers have to be
> concatenated in the value of one optional field. (I think that draft-00
> explicitly stated that the contact optional field could be repeated, but
> that
> seems to have disappeared in draft-01.)
>
> This bit of text from -00 was removed as this is one of the areas requiring
> further discussion. For the Contact header (tag =0x0000) " the text in -00
> states "(can be repeated)" but this is unclear as to whether this is logged
> as a single optional field entry with multiple instances of the Contact
> header in the Value field or as multiple entries (i.e. one for each Contact)
> with the same 0x0000 tag. I'm not sure which is better. This is something I
> hope to have more clarity on coming out of Prague, but maybe we can get a
> few folks to weigh in on this here on the alias.
>
>
> -If an optional field can be present several times, do they have to be
> adjacent
> or can they be mixed with other optional fields?
>
> This obviously depends upon what we decide for the above issue as far as
> whether we allow more more than one optional field entry with the same tag
> number, but there are no restrictions on this now. Do you have a preference.

I would prefer to have several TLVs with the same tag.
With the addition that if it is a SIP header that is logged they should be in
the same order as in the original SIP message.

>
> - figure 1 shows that the optional fields are before the vendor extensions.
> If we have the same format for standard optional fields and vendor
> extensions
> is it still a requirement that they be separate, or can they be mixed.
>
> I don't want to speculate on where the conversations in Prague will lead us,
> but I would think we should stick with laying out the pre-defined optional
> elements first and the vendor-specified elements next.

Fine with me.

The real point of this email was just to point out some things that were not
explicitly specified in the draft.

Another thing I noticed is that in the problem-statement it says that the length
limit for all fields are 4096 bytes per field. And currently there is
no mention of the
max field lengths for the mandatory fields and up to 65535 bytes for
each optional
field. I think this is something that should be clarified.

/Anders


> Regards,
> Gonzalo
>
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>

From clonvick@cisco.com  Wed Mar 16 12:35:17 2011
Return-Path: <clonvick@cisco.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 EA49B3A6A85 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 12:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.449
X-Spam-Level: 
X-Spam-Status: No, score=-109.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8, 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 V1+mHFHx3pkm for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 12:35:09 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 50E353A6A76 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 12:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=clonvick@cisco.com; l=6345; q=dns/txt; s=iport; t=1300304192; x=1301513792; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=qTmbM1i7a3PXciLJ1Tt97okI4rWTV2RBtY8tUC4DtqI=; b=Czbuk12/OaYgFeXyW/uk9uBrFGMhVaLPXyZSDsl1qP89iLBlDTONt4x9 YDb85lt3cSeMUdIolh9ffIXuntWbDwqzBRLFD42R4JII0kN/GRfZSb2pP t6EJg6nHuY7Tu+5f8TOtCAw2Nxiao6HdTMHqwoH9NFAbFUsmhQt+m3gt7 k=;
X-IronPort-AV: E=Sophos;i="4.63,195,1299456000"; d="scan'208";a="667818584"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-6.cisco.com with ESMTP; 16 Mar 2011 19:36:32 +0000
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.16.68]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2GJaVKe005825;  Wed, 16 Mar 2011 19:36:31 GMT
Date: Wed, 16 Mar 2011 12:36:31 -0700 (PDT)
From: Chris Lonvick <clonvick@cisco.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com>
Message-ID: <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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, 16 Mar 2011 19:35:17 -0000

Hi,

Sorry for the delay in responding - busy with the day job.  :-)

I see where you're going with this.  You could preclude the 0x2C character 
from the VendorID, and you could establish a fixed length for the 
VendorID, but even with that you're still going to have to do a search 
ahead to see if there is a 0x40 (@) in the field to determine if it's a 
vendor specific optional field, or a pre-defined optional field.  As 
Anders says, not the best way to quickly process.

I also saw Anders' proposal for inserting a new 1-byte field in the 
Optional Fields container.  Using a full byte for two options just seems 
wasteful to me, but that's probably just me.  :-)  A good option for that 
is to tell the IANA that the field currently has two options ("s" and "v") 
but may be expanded at a later time.  In SSH we usually carved out three 
options: standard, vendor, and experimental.  For experimental, we said 
that if you come up with something new and want others to try it out 
(without having to use a single PEN [sort'a]) then have everone agree upon 
a value in the experimental range.  See the last bullet in section 5.1 of 
RFC 4254 for an example.

Regards,
Chris

On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:

> Anders -
>
> You are absolutely right, I did misunderstand your point the first time around. I thought you were saying '001' was the Vendor-ID, when in fact you were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in front of the '@' is only restricted in the following way:
>
> - MUST be printable US-ASCII strings
> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=', ABNF %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d34), whitespace, or control characters.
>
> it indeed means your example is a valid Vendor-ID and could cause confusion. While this would be very unlikely to happen in practice [I can't imagine an implementer intentionally doing this], it is undesired. I think this fact makes your original proposal that much more elegant than the existing one.
>
> Regards,
>
> Gonzalo
>
>
> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>
>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wrote:
>>> Thanks for raising your concerns Anders.
>>> As you know, this draft was just published today and its principal intent
>>> was to formulate an initial solution for SIP CLF extensibility.
>>> A little history:
>>> The current proposal for Vendor-specific extensions using a Syslog-like
>>> approach (i.e. name@<private enterprise number>) was something proposed over
>>> email and decided at the last SIPCLF Interim meeting in January. So this
>>> really is a first pass at implementing vendor-specificied optional fields.
>>> That said, I'll comment inline to your points
>>>
>>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>>
>>> Hi
>>> I must say that I really dislike the proposed format for vendor specific
>>> fields.
>>> Having a variable length "tag" before the length field means that it
>>> is necessary
>>> to scan the tag looking for the ',' just to find the length field.
>>>
>>> You make a valid point. I'd like others to weigh in here and comment on
>>> whether they think this is a serious performance limitation. I'll propose
>>> this as a discussion point for the upcoming meeting in Prague. The reason
>>> for the variable length tag is that it is based on the SD-ID format from
>>> Syslog, which is variable in length (i.e. the unrestricted name before the
>>> '@').  I think using a Vendor-ID based on a PEN is common sense, so I'd like
>>> to stick with that if possible. We could decide on a fixed length name (or
>>> number to parallel the tag from the Pre-Defined Optional Fields) followed by
>>> four byte PEN.
>>>
>>> There is no simple way to tell he difference between a sip-clf
>>> optional field and
>>> a vendor specific optional field. So it will always be necessary to scan the
>>> record looking for the ',' .
>>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
>>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>>> standard optional field without a lot of work.
>>>
>>> Remember that that this draft restricts the scope of the syntax to the 2nd
>>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a legal
>>> vendor-specified optional field since "0001" doesn't contain an '@', which
>>> is mandatory for a Vendor-ID as defined in the draft. So there should be no
>>> confusion there as the Vendor-ID from the vendor-specified optional fields
>>> and the Tag from the pre-defined optional fields can never be the same.
>>>
>>
>> I think that You did not understand the point I was trying to make.
>> As I understand the specification in the 2nd format definition of SD-IDs in
>> RFC5424, comma "," is allowed in the name part. So
>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficult to
>> differentiate from a standard optional field with tag="0001", length="FFFF" and
>> a value starting with "@<Vendor-ID>"
>>
>>> I think a better way to do this would be similar to diameter RFC3588, ch
>>> 4.1.
>>> Then we could have just one format for standard optional fields and vendor
>>> specific fields
>>>
>>> byte 1  0x09
>>> byte 2-5 Tag (Hex)
>>> byte 6-9 VendorId
>>> byte 10 0x2C
>>> byte 11-14 Length (Hex)
>>> byte 15 0x2C
>>> byte 16-.. Value (variable length)
>>>
>>> Where VendorId is the IANA assigned "SMI Network Management Private
>>> Enterprise Codes"  [ASSIGNNO] value.
>>> VendorId=0 is used a for the standard optional fields defined in SIP-CLF.
>>>
>>> I know that PEN = 0 is a Reserved value and if it is confirmed that it can
>>> be used in this way (as apparently DIAMETER did), then I think this proposal
>>> is very reasonable. This unifies both optional field types into a single
>>> seamless representation. I'll let others, like Chris Lonvick, more
>>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>> Regards,
>>> Gonzalo
>>>
>>> /Anders
>>> _______________________________________________
>>> sip-clf mailing list
>>> sip-clf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>>
>>>
>
>

From anders.nygren@gmail.com  Wed Mar 16 13:00:47 2011
Return-Path: <anders.nygren@gmail.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 EE2603A6AAC for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 13:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[AWL=-1.069, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_LOW=-1]
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 LfStlJ5QdTv8 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 13:00:47 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 851273A6AB2 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 13:00:46 -0700 (PDT)
Received: by wyb42 with SMTP id 42so2230781wyb.31 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 13:02:12 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pl6zlHMRfYZWezjPpoURXGYJDaEOMwKFg1d9lSOJRos=; b=GE9p41LSaY0yZ1HuxdvBsFArnovvo6UIVf5xHsyIPEjIccNiNaw1lYs1dyz5PktUwZ 6QDS4wf8KFrhd59RmmEExUgFTczGipVKhOLuhBHpiNW1Pw1A8CfetaStL6X8+vq1/GBT fp5sXHC30dKqMyKCRKJgzkX7a001Vaqp4Nd50=
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:content-transfer-encoding; b=q9aN0W/9bgAk+0+na7Gu2D3Qm2So0tUQDZlCbH7FOhiXCf2oJbVI5zXyATaqTVKcAk w+gXpKH3jF1hfdTNVSH2K8L3MxXpvbzlrv7tFws60XkWRC6MAGSGmfjFyByu7mVTh+dy Dh8qoVPOTL/Gf5eq0hVHiVkMoqkHd+LK2dqvU=
MIME-Version: 1.0
Received: by 10.216.145.90 with SMTP id o68mr493605wej.77.1300305732689; Wed, 16 Mar 2011 13:02:12 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Wed, 16 Mar 2011 13:02:12 -0700 (PDT)
In-Reply-To: <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com>
Date: Wed, 16 Mar 2011 14:02:12 -0600
Message-ID: <AANLkTikS5cOpx4L_C6pQeEqD-qGojKAo9+1gddyPKw=q@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Chris Lonvick <clonvick@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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, 16 Mar 2011 20:00:48 -0000

On Wed, Mar 16, 2011 at 1:36 PM, Chris Lonvick <clonvick@cisco.com> wrote:
> Hi,
>
> Sorry for the delay in responding - busy with the day job. =A0:-)
>
> I see where you're going with this. =A0You could preclude the 0x2C charac=
ter
> from the VendorID, and you could establish a fixed length for the VendorI=
D,
> but even with that you're still going to have to do a search ahead to see=
 if
> there is a 0x40 (@) in the field to determine if it's a vendor specific
> optional field, or a pre-defined optional field. =A0As Anders says, not t=
he
> best way to quickly process.
>
> I also saw Anders' proposal for inserting a new 1-byte field in the Optio=
nal
> Fields container. =A0Using a full byte for two options just seems wastefu=
l to
> me, but that's probably just me. =A0:-)

Since this is a text format I assumed it was the right thing to to.
(And if we should start worrying about one byte, I think there are some
commas "," that we could remove instead.)

But an alternative could be
tag 0x0000-0x7FFF   standard
tag 0x8000-0xFFFF   vendor

Or as Bill Gates almost said "Nobody needs more than 32K tags" :)

/Anders

> A good option for that is to tell the
> IANA that the field currently has two options ("s" and "v") but may be
> expanded at a later time. =A0In SSH we usually carved out three options:
> standard, vendor, and experimental. =A0For experimental, we said that if =
you
> come up with something new and want others to try it out (without having =
to
> use a single PEN [sort'a]) then have everone agree upon a value in the
> experimental range. =A0See the last bullet in section 5.1 of RFC 4254 for=
 an
> example.
>
> Regards,
> Chris
>
> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>
>> Anders -
>>
>> You are absolutely right, I did misunderstand your point the first time
>> around. I thought you were saying '001' was the Vendor-ID, when in fact =
you
>> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in
>> front of the '@' is only restricted in the following way:
>>
>> - MUST be printable US-ASCII strings
>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', AB=
NF
>> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d=
34),
>> whitespace, or control characters.
>>
>> it indeed means your example is a valid Vendor-ID and could cause
>> confusion. While this would be very unlikely to happen in practice [I ca=
n't
>> imagine an implementer intentionally doing this], it is undesired. I thi=
nk
>> this fact makes your original proposal that much more elegant than the
>> existing one.
>>
>> Regards,
>>
>> Gonzalo
>>
>>
>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>
>>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com=
>
>>> wrote:
>>>>
>>>> Thanks for raising your concerns Anders.
>>>> As you know, this draft was just published today and its principal
>>>> intent
>>>> was to formulate an initial solution for SIP CLF extensibility.
>>>> A little history:
>>>> The current proposal for Vendor-specific extensions using a Syslog-lik=
e
>>>> approach (i.e. name@<private enterprise number>) was something propose=
d
>>>> over
>>>> email and decided at the last SIPCLF Interim meeting in January. So th=
is
>>>> really is a first pass at implementing vendor-specificied optional
>>>> fields.
>>>> That said, I'll comment inline to your points
>>>>
>>>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>>>
>>>> Hi
>>>> I must say that I really dislike the proposed format for vendor specif=
ic
>>>> fields.
>>>> Having a variable length "tag" before the length field means that it
>>>> is necessary
>>>> to scan the tag looking for the ',' just to find the length field.
>>>>
>>>> You make a valid point. I'd like others to weigh in here and comment o=
n
>>>> whether they think this is a serious performance limitation. I'll
>>>> propose
>>>> this as a discussion point for the upcoming meeting in Prague. The
>>>> reason
>>>> for the variable length tag is that it is based on the SD-ID format fr=
om
>>>> Syslog, which is variable in length (i.e. the unrestricted name before
>>>> the
>>>> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so =
I'd
>>>> like
>>>> to stick with that if possible. We could decide on a fixed length name
>>>> (or
>>>> number to parallel the tag from the Pre-Defined Optional Fields)
>>>> followed by
>>>> four byte PEN.
>>>>
>>>> There is no simple way to tell he difference between a sip-clf
>>>> optional field and
>>>> a vendor specific optional field. So it will always be necessary to sc=
an
>>>> the
>>>> record looking for the ',' .
>>>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a
>>>> legal
>>>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from =
a
>>>> standard optional field without a lot of work.
>>>>
>>>> Remember that that this draft restricts the scope of the syntax to the
>>>> 2nd
>>>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a
>>>> legal
>>>> vendor-specified optional field since "0001" doesn't contain an '@',
>>>> which
>>>> is mandatory for a Vendor-ID as defined in the draft. So there should =
be
>>>> no
>>>> confusion there as the Vendor-ID from the vendor-specified optional
>>>> fields
>>>> and the Tag from the pre-defined optional fields can never be the same=
.
>>>>
>>>
>>> I think that You did not understand the point I was trying to make.
>>> As I understand the specification in the 2nd format definition of SD-ID=
s
>>> in
>>> RFC5424, comma "," is allowed in the name part. So
>>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very
>>> difficult to
>>> differentiate from a standard optional field with tag=3D"0001",
>>> length=3D"FFFF" and
>>> a value starting with "@<Vendor-ID>"
>>>
>>>> I think a better way to do this would be similar to diameter RFC3588, =
ch
>>>> 4.1.
>>>> Then we could have just one format for standard optional fields and
>>>> vendor
>>>> specific fields
>>>>
>>>> byte 1 =A00x09
>>>> byte 2-5 Tag (Hex)
>>>> byte 6-9 VendorId
>>>> byte 10 0x2C
>>>> byte 11-14 Length (Hex)
>>>> byte 15 0x2C
>>>> byte 16-.. Value (variable length)
>>>>
>>>> Where VendorId is the IANA assigned "SMI Network Management Private
>>>> Enterprise Codes" =A0[ASSIGNNO] value.
>>>> VendorId=3D0 is used a for the standard optional fields defined in
>>>> SIP-CLF.
>>>>
>>>> I know that PEN =3D 0 is a Reserved value and if it is confirmed that =
it
>>>> can
>>>> be used in this way (as apparently DIAMETER did), then I think this
>>>> proposal
>>>> is very reasonable. This unifies both optional field types into a sing=
le
>>>> seamless representation. I'll let others, like Chris Lonvick, more
>>>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>>> Regards,
>>>> Gonzalo
>>>>
>>>> /Anders
>>>> _______________________________________________
>>>> sip-clf mailing list
>>>> sip-clf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>>>
>>>>
>>
>>
>

From gsalguei@cisco.com  Wed Mar 16 13:23:17 2011
Return-Path: <gsalguei@cisco.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 4FCBA3A68DE for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 13:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.332
X-Spam-Level: 
X-Spam-Status: No, score=-9.332 tagged_above=-999 required=5 tests=[AWL=-1.034, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8]
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 xrweexqqH7hc for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 13:23:15 -0700 (PDT)
Received: from av-tac-sj.cisco.com (firebird.cisco.com [171.68.227.73]) by core3.amsl.com (Postfix) with ESMTP id 8600E3A6909 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 13:23:15 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-sj.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GKOcvb025124; Wed, 16 Mar 2011 13:24:39 -0700 (PDT)
Received: from dhcp-64-102-154-252.cisco.com (dhcp-64-102-154-252.cisco.com [64.102.154.252]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GKOWr0008811;  Wed, 16 Mar 2011 16:24:33 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-43--122674520
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com>
Date: Wed, 16 Mar 2011 16:24:32 -0400
Message-Id: <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com>
To: Chris Lonvick <clonvick@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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, 16 Mar 2011 20:23:17 -0000

--Apple-Mail-43--122674520
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Chris -

Thanks for the response. One very simple proposal I was offering that =
would clean up the convoluted syntax and avoid having to look ahead for =
the '@' is :

- A single format for both pre-defined and vendor-specified optional =
fields based on TLV format
- This single format is based on syslog-like tag@PEN is used is used as =
the "Tag" in TLV and where PEN=3D0 if it is not vendor-specified.

This eliminates any need for a V bit to specify standard, vendor, =
experimental. Can you confirm that using the Reserved PEN=3D0 in this =
manner is valid?

This seems to me a simple and elegant solution to this problem. =
Thoughts?

Regards,

Gonzalo



On Mar 16, 2011, at 3:36 PM, Chris Lonvick wrote:

> Hi,
>=20
> Sorry for the delay in responding - busy with the day job.  :-)
>=20
> I see where you're going with this.  You could preclude the 0x2C =
character from the VendorID, and you could establish a fixed length for =
the VendorID, but even with that you're still going to have to do a =
search ahead to see if there is a 0x40 (@) in the field to determine if =
it's a vendor specific optional field, or a pre-defined optional field.  =
As Anders says, not the best way to quickly process.
>=20
> I also saw Anders' proposal for inserting a new 1-byte field in the =
Optional Fields container.  Using a full byte for two options just seems =
wasteful to me, but that's probably just me.  :-)  A good option for =
that is to tell the IANA that the field currently has two options ("s" =
and "v") but may be expanded at a later time.  In SSH we usually carved =
out three options: standard, vendor, and experimental.  For =
experimental, we said that if you come up with something new and want =
others to try it out (without having to use a single PEN [sort'a]) then =
have everone agree upon a value in the experimental range.  See the last =
bullet in section 5.1 of RFC 4254 for an example.
>=20
> Regards,
> Chris
>=20
> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>=20
>> Anders -
>>=20
>> You are absolutely right, I did misunderstand your point the first =
time around. I thought you were saying '001' was the Vendor-ID, when in =
fact you were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the =
name in front of the '@' is only restricted in the following way:
>>=20
>> - MUST be printable US-ASCII strings
>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF %d61), a closing brace (']', ABNF %d93), a quote-character ('"', =
ABNF %d34), whitespace, or control characters.
>>=20
>> it indeed means your example is a valid Vendor-ID and could cause =
confusion. While this would be very unlikely to happen in practice [I =
can't imagine an implementer intentionally doing this], it is undesired. =
I think this fact makes your original proposal that much more elegant =
than the existing one.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>>=20
>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>=20
>>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>>>> Thanks for raising your concerns Anders.
>>>> As you know, this draft was just published today and its principal =
intent
>>>> was to formulate an initial solution for SIP CLF extensibility.
>>>> A little history:
>>>> The current proposal for Vendor-specific extensions using a =
Syslog-like
>>>> approach (i.e. name@<private enterprise number>) was something =
proposed over
>>>> email and decided at the last SIPCLF Interim meeting in January. So =
this
>>>> really is a first pass at implementing vendor-specificied optional =
fields.
>>>> That said, I'll comment inline to your points
>>>>=20
>>>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>>>=20
>>>> Hi
>>>> I must say that I really dislike the proposed format for vendor =
specific
>>>> fields.
>>>> Having a variable length "tag" before the length field means that =
it
>>>> is necessary
>>>> to scan the tag looking for the ',' just to find the length field.
>>>>=20
>>>> You make a valid point. I'd like others to weigh in here and =
comment on
>>>> whether they think this is a serious performance limitation. I'll =
propose
>>>> this as a discussion point for the upcoming meeting in Prague. The =
reason
>>>> for the variable length tag is that it is based on the SD-ID format =
from
>>>> Syslog, which is variable in length (i.e. the unrestricted name =
before the
>>>> '@').  I think using a Vendor-ID based on a PEN is common sense, so =
I'd like
>>>> to stick with that if possible. We could decide on a fixed length =
name (or
>>>> number to parallel the tag from the Pre-Defined Optional Fields) =
followed by
>>>> four byte PEN.
>>>>=20
>>>> There is no simple way to tell he difference between a sip-clf
>>>> optional field and
>>>> a vendor specific optional field. So it will always be necessary to =
scan the
>>>> record looking for the ',' .
>>>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal
>>>> ID, "0001,FFFF,@12345" which would be difficult to differentiate =
from a
>>>> standard optional field without a lot of work.
>>>>=20
>>>> Remember that that this draft restricts the scope of the syntax to =
the 2nd
>>>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be =
a legal
>>>> vendor-specified optional field since "0001" doesn't contain an =
'@', which
>>>> is mandatory for a Vendor-ID as defined in the draft. So there =
should be no
>>>> confusion there as the Vendor-ID from the vendor-specified optional =
fields
>>>> and the Tag from the pre-defined optional fields can never be the =
same.
>>>>=20
>>>=20
>>> I think that You did not understand the point I was trying to make.
>>> As I understand the specification in the 2nd format definition of =
SD-IDs in
>>> RFC5424, comma "," is allowed in the name part. So
>>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very =
difficult to
>>> differentiate from a standard optional field with tag=3D"0001", =
length=3D"FFFF" and
>>> a value starting with "@<Vendor-ID>"
>>>=20
>>>> I think a better way to do this would be similar to diameter =
RFC3588, ch
>>>> 4.1.
>>>> Then we could have just one format for standard optional fields and =
vendor
>>>> specific fields
>>>>=20
>>>> byte 1  0x09
>>>> byte 2-5 Tag (Hex)
>>>> byte 6-9 VendorId
>>>> byte 10 0x2C
>>>> byte 11-14 Length (Hex)
>>>> byte 15 0x2C
>>>> byte 16-.. Value (variable length)
>>>>=20
>>>> Where VendorId is the IANA assigned "SMI Network Management Private
>>>> Enterprise Codes"  [ASSIGNNO] value.
>>>> VendorId=3D0 is used a for the standard optional fields defined in =
SIP-CLF.
>>>>=20
>>>> I know that PEN =3D 0 is a Reserved value and if it is confirmed =
that it can
>>>> be used in this way (as apparently DIAMETER did), then I think this =
proposal
>>>> is very reasonable. This unifies both optional field types into a =
single
>>>> seamless representation. I'll let others, like Chris Lonvick, more
>>>> knowledgeable than I weigh in on this as well to confirm my =
thoughts.
>>>> Regards,
>>>> Gonzalo
>>>>=20
>>>> /Anders
>>>> _______________________________________________
>>>> sip-clf mailing list
>>>> sip-clf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>>>=20
>>>>=20
>>=20
>>=20


--Apple-Mail-43--122674520
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Chris =
-<div><br></div><div>Thanks for the response. One very simple proposal I =
was offering that would clean up the convoluted syntax and avoid having =
to look ahead for the '@' is :</div><div><br></div><div>- A single =
format for both pre-defined and vendor-specified optional fields based =
on TLV format</div><div>- This single format is based on =
syslog-like&nbsp;tag@PEN is used is used as the "Tag" in TLV and where =
PEN=3D0 if it is not vendor-specified.</div><div><br></div><div>This =
eliminates any need for a V bit to specify standard, vendor, =
experimental. Can you confirm that using the Reserved PEN=3D0 in this =
manner is valid?</div><div><br></div><div>This seems to me a simple and =
elegant solution to this problem. =
Thoughts?</div><div><br></div><div>Regards,</div><div><br></div><div>Gonza=
lo</div><div><br></div><div><br></div><div><br><div><div>On Mar 16, =
2011, at 3:36 PM, Chris Lonvick wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi,<br><br>Sorry for the delay in responding - busy =
with the day job. &nbsp;:-)<br><br>I see where you're going with this. =
&nbsp;You could preclude the 0x2C character from the VendorID, and you =
could establish a fixed length for the VendorID, but even with that =
you're still going to have to do a search ahead to see if there is a =
0x40 (@) in the field to determine if it's a vendor specific optional =
field, or a pre-defined optional field. &nbsp;As Anders says, not the =
best way to quickly process.<br><br>I also saw Anders' proposal for =
inserting a new 1-byte field in the Optional Fields container. =
&nbsp;Using a full byte for two options just seems wasteful to me, but =
that's probably just me. &nbsp;:-) &nbsp;A good option for that is to =
tell the IANA that the field currently has two options ("s" and "v") but =
may be expanded at a later time. &nbsp;In SSH we usually carved out =
three options: standard, vendor, and experimental. &nbsp;For =
experimental, we said that if you come up with something new and want =
others to try it out (without having to use a single PEN [sort'a]) then =
have everone agree upon a value in the experimental range. &nbsp;See the =
last bullet in section 5.1 of RFC 4254 for an =
example.<br><br>Regards,<br>Chris<br><br>On Tue, 15 Mar 2011, Gonzalo =
Salgueiro wrote:<br><br><blockquote type=3D"cite">Anders =
-<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">You are absolutely right, I did misunderstand your point =
the first time around. I thought you were saying '001' was the =
Vendor-ID, when in fact you were saying that "0001,FFFF,@&lt;PEN&gt;" is =
the Vendor-ID. Since the name in front of the '@' is only restricted in =
the following way:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- MUST be =
printable US-ASCII strings<br></blockquote><blockquote type=3D"cite">- =
MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', ABNF =
%d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF =
%d34), whitespace, or control characters.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">it indeed means =
your example is a valid Vendor-ID and could cause confusion. While this =
would be very unlikely to happen in practice [I can't imagine an =
implementer intentionally doing this], it is undesired. I think this =
fact makes your original proposal that much more elegant than the =
existing one.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 15, =
2011, at 10:38 AM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Thanks for raising your concerns =
Anders.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">As you =
know, this draft was just published today and its principal =
intent<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">was to =
formulate an initial solution for SIP CLF =
extensibility.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">A =
little history:<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">The =
current proposal for Vendor-specific extensions using a =
Syslog-like<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">approach=
 (i.e. name@&lt;private enterprise number&gt;) was something proposed =
over<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">email =
and decided at the last SIPCLF Interim meeting in January. So =
this<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">really =
is a first pass at implementing vendor-specificied optional =
fields.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">That =
said, I'll comment inline to your =
points<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">On Mar =
14, 2011, at 10:53 PM, Anders Nygren =
wrote:<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Hi<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">I must =
say that I really dislike the proposed format for vendor =
specific<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">fields.<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Having=
 a variable length "tag" before the length field means that =
it<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">is =
necessary<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">to =
scan the tag looking for the ',' just to find the length =
field.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">You =
make a valid point. I'd like others to weigh in here and comment =
on<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">whether =
they think this is a serious performance limitation. I'll =
propose<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">this =
as a discussion point for the upcoming meeting in Prague. The =
reason<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">for =
the variable length tag is that it is based on the SD-ID format =
from<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Syslog, =
which is variable in length (i.e. the unrestricted name before =
the<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">'@'). =
&nbsp;I think using a Vendor-ID based on a PEN is common sense, so I'd =
like<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">to =
stick with that if possible. We could decide on a fixed length name =
(or<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">number =
to parallel the tag from the Pre-Defined Optional Fields) followed =
by<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">four =
byte PEN.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">There =
is no simple way to tell he difference between a =
sip-clf<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">optional=
 field and<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">a =
vendor specific optional field. So it will always be necessary to scan =
the<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">record =
looking for the ',' =
.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Actually=
 looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">ID, =
"0001,FFFF,@12345" which would be difficult to differentiate from =
a<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">standard=
 optional field without a lot of =
work.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Remember=
 that that this draft restricts the scope of the syntax to the =
2nd<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">format =
definition of SD-IDs in RFC5424. Thus, the above wouldn't be a =
legal<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">vendor-specified optional field since "0001" doesn't =
contain an '@', =
which<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">is =
mandatory for a Vendor-ID as defined in the draft. So there should be =
no<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">confusion there as the Vendor-ID from the vendor-specified =
optional fields<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">and =
the Tag from the pre-defined optional fields can never be the =
same.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I think that You did not =
understand the point I was trying to =
make.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">As I understand the specification in the 2nd format =
definition of SD-IDs in<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">RFC5424, comma "," is allowed in =
the name part. So<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">"0001,FFFF,@&lt;Vendor-ID&gt;" =
would be a legal tag, that would be very difficult =
to<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">differentiate from a standard optional field with =
tag=3D"0001", length=3D"FFFF" =
and<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">a value starting with =
"@&lt;Vendor-ID&gt;"<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">I =
think a better way to do this would be similar to diameter RFC3588, =
ch<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">4.1.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Then =
we could have just one format for standard optional fields and =
vendor<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">specific=
 fields<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte 1 =
&nbsp;0x09<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte =
2-5 Tag (Hex)<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte =
6-9 VendorId<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte =
10 0x2C<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte =
11-14 Length (Hex)<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte =
15 0x2C<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">byte =
16-.. Value (variable =
length)<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Where =
VendorId is the IANA assigned "SMI Network Management =
Private<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Enterprise Codes" &nbsp;[ASSIGNNO] =
value.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">VendorId=3D0 is used a for the standard optional fields =
defined in =
SIP-CLF.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">I know =
that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">be =
used in this way (as apparently DIAMETER did), then I think this =
proposal<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">is =
very reasonable. This unifies both optional field types into a =
single<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">seamless=
 representation. I'll let others, like Chris Lonvick, =
more<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">knowledgeable than I weigh in on this as well to confirm =
my thoughts.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Regards,<br></blockquote></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Gonzalo<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">/Anders<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote></bl=
ockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote></blockquote></blockquote><=
blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></body><=
/html>=

--Apple-Mail-43--122674520--

From gsalguei@cisco.com  Wed Mar 16 13:41:16 2011
Return-Path: <gsalguei@cisco.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 CEB973A6A1D for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 13:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.431
X-Spam-Level: 
X-Spam-Status: No, score=-10.431 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 bONd9t2uUnCQ for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 13:41:15 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 854EE3A6A0C for <sip-clf@ietf.org>; Wed, 16 Mar 2011 13:41:15 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GKgdbm006192; Wed, 16 Mar 2011 16:42:39 -0400 (EDT)
Received: from dhcp-64-102-154-252.cisco.com (dhcp-64-102-154-252.cisco.com [64.102.154.252]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2GKgdHd029722;  Wed, 16 Mar 2011 16:42:39 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-45--121587791
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTinpBOMN8W1K1trV2jPK-00KRTh=qBmF2F9c6P92@mail.gmail.com>
Date: Wed, 16 Mar 2011 16:42:39 -0400
Message-Id: <7C93D69F-AA6C-4030-B5E2-E8E2C2699DC0@cisco.com>
References: <AANLkTinQA6Ve2GQo1BpwRtgZaci7SXpOMhr4cmv6t_fG@mail.gmail.com> <44188993-8A2D-486A-9DAC-9F155CAD0957@cisco.com> <AANLkTinpBOMN8W1K1trV2jPK-00KRTh=qBmF2F9c6P92@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>, "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, optional fields
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, 16 Mar 2011 20:41:16 -0000

--Apple-Mail-45--121587791
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Mar 16, 2011, at 1:34 PM, Anders Nygren wrote:

> On Wed, Mar 16, 2011 at 11:08 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Inline...
>> On Mar 16, 2011, at 12:32 PM, Anders Nygren wrote:
>>=20
>> Hi
>> I hope this is the last from me for this version.
>>=20
>> In the descriptions of the optional fields I think that there some =
things
>> that should be clarified.
>>=20
>> - Can the optional fields be in any order, or do they have to be =
sorted
>> by increasing tag values?
>>=20
>> They can be specified in any order, though I suppose most people =
would
>> logically do it based on increasing tag number (assuming pre-defined
>> optional field). Do you think this should be further restricted so =
that
>> implementers MUST implement the pre-defined optional fields in =
ascending tag
>> number order?
>=20
> I think it is OK to allow any order.
> But I do think that it is important to mention in the spec whatever is
> decided.
>=20
>>=20
>> - If an optional field represents a SIP header, e.g. Contact, can =
appear
>> several times in a SIP message how are they logged, as several =
optional
>> fields with the same tag, or does the all the Contact headers have to =
be
>> concatenated in the value of one optional field. (I think that =
draft-00
>> explicitly stated that the contact optional field could be repeated, =
but
>> that
>> seems to have disappeared in draft-01.)
>>=20
>> This bit of text from -00 was removed as this is one of the areas =
requiring
>> further discussion. For the Contact header (tag =3D0x0000) " the text =
in -00
>> states "(can be repeated)" but this is unclear as to whether this is =
logged
>> as a single optional field entry with multiple instances of the =
Contact
>> header in the Value field or as multiple entries (i.e. one for each =
Contact)
>> with the same 0x0000 tag. I'm not sure which is better. This is =
something I
>> hope to have more clarity on coming out of Prague, but maybe we can =
get a
>> few folks to weigh in on this here on the alias.
>>=20
>>=20
>> -If an optional field can be present several times, do they have to =
be
>> adjacent
>> or can they be mixed with other optional fields?
>>=20
>> This obviously depends upon what we decide for the above issue as far =
as
>> whether we allow more more than one optional field entry with the =
same tag
>> number, but there are no restrictions on this now. Do you have a =
preference.
>=20
> I would prefer to have several TLVs with the same tag.
> With the addition that if it is a SIP header that is logged they =
should be in
> the same order as in the original SIP message.
>=20
>>=20
>> - figure 1 shows that the optional fields are before the vendor =
extensions.
>> If we have the same format for standard optional fields and vendor
>> extensions
>> is it still a requirement that they be separate, or can they be =
mixed.
>>=20
>> I don't want to speculate on where the conversations in Prague will =
lead us,
>> but I would think we should stick with laying out the pre-defined =
optional
>> elements first and the vendor-specified elements next.
>=20
> Fine with me.
>=20
> The real point of this email was just to point out some things that =
were not
> explicitly specified in the draft.
>=20
Duly noted.

> Another thing I noticed is that in the problem-statement it says that =
the length
> limit for all fields are 4096 bytes per field. And currently there is
> no mention of the
> max field lengths for the mandatory fields and up to 65535 bytes for
> each optional
> field. I think this is something that should be clarified.

I'll probably add some text deferring to the Problem Statement.  I'm =
copying Vijay on this so he is aware and can update the text in the =
Problem Statement around the field limits for mandatory vs. optional.

Regards,

Gonzalo
>=20
> /Anders
>=20
>=20
>> Regards,
>> Gonzalo
>>=20
>> /Anders
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20


--Apple-Mail-45--121587791
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 16, 2011, at 1:34 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>On Wed, Mar 16, 2011 at 11:08 AM, Gonzalo Salgueiro =
&lt;<a href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Inline...<br></blockquote><blockquote =
type=3D"cite">On Mar 16, 2011, at 12:32 PM, Anders Nygren =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote type=3D"cite">I hope this =
is the last from me for this version.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In the =
descriptions of the optional fields I think that there some =
things<br></blockquote><blockquote type=3D"cite">that should be =
clarified.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- Can the =
optional fields be in any order, or do they have to be =
sorted<br></blockquote><blockquote type=3D"cite">by increasing tag =
values?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">They can be =
specified in any order, though I suppose most people =
would<br></blockquote><blockquote type=3D"cite">logically do it based on =
increasing tag number (assuming pre-defined<br></blockquote><blockquote =
type=3D"cite">optional field). Do you think this should be further =
restricted so that<br></blockquote><blockquote type=3D"cite">implementers =
MUST implement the pre-defined optional fields in ascending =
tag<br></blockquote><blockquote type=3D"cite">number =
order?<br></blockquote><br>I think it is OK to allow any order.<br>But I =
do think that it is important to mention in the spec whatever =
is<br>decided.<br><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- If an =
optional field represents a SIP header, e.g. Contact, can =
appear<br></blockquote><blockquote type=3D"cite">several times in a SIP =
message how are they logged, as several =
optional<br></blockquote><blockquote type=3D"cite">fields with the same =
tag, or does the all the Contact headers have to =
be<br></blockquote><blockquote type=3D"cite">concatenated in the value =
of one optional field. (I think that =
draft-00<br></blockquote><blockquote type=3D"cite">explicitly stated =
that the contact optional field could be repeated, =
but<br></blockquote><blockquote =
type=3D"cite">that<br></blockquote><blockquote type=3D"cite">seems to =
have disappeared in draft-01.)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This bit of =
text from -00 was removed as this is one of the areas =
requiring<br></blockquote><blockquote type=3D"cite">further discussion. =
For the Contact header (tag =3D0x0000) " the text in =
-00<br></blockquote><blockquote type=3D"cite">states "(can be repeated)" =
but this is unclear as to whether this is =
logged<br></blockquote><blockquote type=3D"cite">as a single optional =
field entry with multiple instances of the =
Contact<br></blockquote><blockquote type=3D"cite">header in the Value =
field or as multiple entries (i.e. one for each =
Contact)<br></blockquote><blockquote type=3D"cite">with the same 0x0000 =
tag. I'm not sure which is better. This is something =
I<br></blockquote><blockquote type=3D"cite">hope to have more clarity on =
coming out of Prague, but maybe we can get a<br></blockquote><blockquote =
type=3D"cite">few folks to weigh in on this here on the =
alias.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">-If an optional =
field can be present several times, do they have to =
be<br></blockquote><blockquote =
type=3D"cite">adjacent<br></blockquote><blockquote type=3D"cite">or can =
they be mixed with other optional fields?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This obviously =
depends upon what we decide for the above issue as far =
as<br></blockquote><blockquote type=3D"cite">whether we allow more more =
than one optional field entry with the same =
tag<br></blockquote><blockquote type=3D"cite">number, but there are no =
restrictions on this now. Do you have a =
preference.<br></blockquote><br>I would prefer to have several TLVs with =
the same tag.<br>With the addition that if it is a SIP header that is =
logged they should be in<br>the same order as in the original SIP =
message.<br><br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">- figure 1 shows that the optional fields are before the =
vendor extensions.<br></blockquote><blockquote type=3D"cite">If we have =
the same format for standard optional fields and =
vendor<br></blockquote><blockquote =
type=3D"cite">extensions<br></blockquote><blockquote type=3D"cite">is it =
still a requirement that they be separate, or can they be =
mixed.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I don't want to =
speculate on where the conversations in Prague will lead =
us,<br></blockquote><blockquote type=3D"cite">but I would think we =
should stick with laying out the pre-defined =
optional<br></blockquote><blockquote type=3D"cite">elements first and =
the vendor-specified elements next.<br></blockquote><br>Fine with =
me.<br><br>The real point of this email was just to point out some =
things that were not<br>explicitly specified in the =
draft.<br><br></div></blockquote>Duly noted.</div><div><br><blockquote =
type=3D"cite"><div>Another thing I noticed is that in the =
problem-statement it says that the length<br>limit for all fields are =
4096 bytes per field. And currently there is<br>no mention of the<br>max =
field lengths for the mandatory fields and up to 65535 bytes for<br>each =
optional<br>field. I think this is something that should be =
clarified.<br></div></blockquote><div><br></div>I'll probably add some =
text deferring to the Problem Statement. &nbsp;I'm copying Vijay on this =
so he is aware and can update the text in the Problem Statement around =
the field limits for mandatory vs. =
optional.</div><div><br></div><div>Regards,</div><div><br></div><div>Gonza=
lo<br><blockquote type=3D"cite"><div><br>/Anders<br><br><br><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">sip-clf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></body></html>=

--Apple-Mail-45--121587791--

From anders.nygren@gmail.com  Wed Mar 16 15:56:26 2011
Return-Path: <anders.nygren@gmail.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 C607D3A6A77 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 15:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.855
X-Spam-Level: 
X-Spam-Status: No, score=-2.855 tagged_above=-999 required=5 tests=[AWL=-0.456, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1]
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 NOwjccJfIPLa for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 15:56:26 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id B0AEB3A6974 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 15:56:25 -0700 (PDT)
Received: by wyb42 with SMTP id 42so2383301wyb.31 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 15:57:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=otwkTY/oV70WKgGb/dSqUtysLh4mC8uNLyyHgHACTtI=; b=d4gQL6RieP2IJEMOyhttyPcb8PW6Ja4unMysktU2nrVrCKV0MWU552hKCSX1DtcjAx 5HFh72gm0cOSc1at2J1C+iOJ0xGJDIRpNnmHKd3s76oETucroOboj/0BCKC67L+g5ewS 43vgqap2EOHJSpUfFp3LRPxo0AVSL7Iikvkgo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JXLNVbioY+w2T2PadZ++mkZtSscDrcseaJ0qrkZygmC5+b31j0muNmantu75JytKuh k1nEnKt2t4phY2OEb8TzWKn0roABiNMjtHeIKuTh7zwVjo8kX/g1fPM9YY/2JGL6kIGr z3JDv7h8OfFkX7ItXFWPXaWNG54+ijMjybK94=
MIME-Version: 1.0
Received: by 10.216.120.193 with SMTP id p43mr499190weh.92.1300316272169; Wed, 16 Mar 2011 15:57:52 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Wed, 16 Mar 2011 15:57:52 -0700 (PDT)
Date: Wed, 16 Mar 2011 16:57:52 -0600
Message-ID: <AANLkTimewCMhf06foUJeSKW0vwbPQJqymErnc9NFyxEG@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sip-clf] draft-ietf-sipclf-format-01, IPv6 format
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, 16 Mar 2011 22:56:26 -0000

Hi
For Destination IP address:port and Source IP address:port it only specifies
that "The port number MUST be separated from the IP address by a single ':'"
It does not say anything about how IPv6 addresses should be represented.

But according to "A Recommendation for IPv6 Address Text Representation",
RFC 5952, IPv6Address':'port is ambiguous. Because of this RFC 5952 ch.6 says
    "The [] style as expressed in [RFC3986] SHOULD be employed, and is
      the default unless otherwise specified"

This also seems to be the same format as specified by the SIP ABNF for
host:port.

I think it would be useful to add that to the descriptions of
Destination IP address:port and Source IP address:port.
If not RFC 5952 then at least some other comment about allowed/recommended
formats for IPv6 addresses.

/Anders

From clonvick@cisco.com  Wed Mar 16 16:37:17 2011
Return-Path: <clonvick@cisco.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 2C3473A6A7A for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 16:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.162
X-Spam-Level: 
X-Spam-Status: No, score=-109.162 tagged_above=-999 required=5 tests=[AWL=-0.862, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8, 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 Z-zX1irZbdHY for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 16:37:15 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 96D7A3A6944 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 16:37:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=clonvick@cisco.com; l=7964; q=dns/txt; s=iport; t=1300318723; x=1301528323; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=HAydtS819mPPMixRXir12HF4kTuKuyo0uiMWWcUtJGk=; b=GudQEnC+rFxTDdFXogZxk3gaTjkZhEFfCibRJFQ4LO4aGw4VqlO7DqlG Mq1VpTP9+zl00Ha7yvxom2OrVjdakLRcVv8GnqOFWvdmtv3mbWAhOk9nk 2xNAIfeesUJNMxWplXzlmFdikMvYAlNYVM4wO0JwQWO7V+74filsltEuS c=;
X-IronPort-AV: E=Sophos;i="4.63,196,1299456000"; d="scan'208";a="347969587"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-5.cisco.com with ESMTP; 16 Mar 2011 23:38:42 +0000
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.16.68]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2GNcg3G019021;  Wed, 16 Mar 2011 23:38:42 GMT
Date: Wed, 16 Mar 2011 16:38:41 -0700 (PDT)
From: Chris Lonvick <clonvick@cisco.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com>
Message-ID: <Pine.GSO.4.63.1103161631290.29866@sjc-cde-011.cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com> <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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, 16 Mar 2011 23:37:17 -0000

Hi Gonzalo,

I do like that proposal.  It does keep things simple and clean.  (I must 
have missed it earlier.)

I don't think that there will be any problem in using PEN=0 in this manner 
in this application.  I'll check with some people to see if they can think 
of anything.

If there is a problem in using PEN=0, the alternative would be for the 
IETF to register a PEN specifically for this application.  In that case, 
using PEN=<new assigned number> would mean that the TAG is pre-defined, 
and using any other number would mean that the TAG is vendor specified.

Best regards,
Chris

On Wed, 16 Mar 2011, Gonzalo Salgueiro wrote:

> Chris -
>
> Thanks for the response. One very simple proposal I was offering that would clean up the convoluted syntax and avoid having to look ahead for the '@' is :
>
> - A single format for both pre-defined and vendor-specified optional fields based on TLV format
> - This single format is based on syslog-like tag@PEN is used is used as the "Tag" in TLV and where PEN=0 if it is not vendor-specified.
>
> This eliminates any need for a V bit to specify standard, vendor, experimental. Can you confirm that using the Reserved PEN=0 in this manner is valid?
>
> This seems to me a simple and elegant solution to this problem. Thoughts?
>
> Regards,
>
> Gonzalo
>
>
>
> On Mar 16, 2011, at 3:36 PM, Chris Lonvick wrote:
>
>> Hi,
>>
>> Sorry for the delay in responding - busy with the day job.  :-)
>>
>> I see where you're going with this.  You could preclude the 0x2C character from the VendorID, and you could establish a fixed length for the VendorID, but even with that you're still going to have to do a search ahead to see if there is a 0x40 (@) in the field to determine if it's a vendor specific optional field, or a pre-defined optional field.  As Anders says, not the best way to quickly process.
>>
>> I also saw Anders' proposal for inserting a new 1-byte field in the Optional Fields container.  Using a full byte for two options just seems wasteful to me, but that's probably just me.  :-)  A good option for that is to tell the IANA that the field currently has two options ("s" and "v") but may be expanded at a later time.  In SSH we usually carved out three options: standard, vendor, and experimental.  For experimental, we said that if you come up with something new and want others to try it out (without having to use a single PEN [sort'a]) then have everone agree upon a value in the experimental range.  See the last bullet in section 5.1 of RFC 4254 for an example.
>>
>> Regards,
>> Chris
>>
>> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>>
>>> Anders -
>>>
>>> You are absolutely right, I did misunderstand your point the first time around. I thought you were saying '001' was the Vendor-ID, when in fact you were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in front of the '@' is only restricted in the following way:
>>>
>>> - MUST be printable US-ASCII strings
>>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=', ABNF %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d34), whitespace, or control characters.
>>>
>>> it indeed means your example is a valid Vendor-ID and could cause confusion. While this would be very unlikely to happen in practice [I can't imagine an implementer intentionally doing this], it is undesired. I think this fact makes your original proposal that much more elegant than the existing one.
>>>
>>> Regards,
>>>
>>> Gonzalo
>>>
>>>
>>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>>
>>>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wrote:
>>>>> Thanks for raising your concerns Anders.
>>>>> As you know, this draft was just published today and its principal intent
>>>>> was to formulate an initial solution for SIP CLF extensibility.
>>>>> A little history:
>>>>> The current proposal for Vendor-specific extensions using a Syslog-like
>>>>> approach (i.e. name@<private enterprise number>) was something proposed over
>>>>> email and decided at the last SIPCLF Interim meeting in January. So this
>>>>> really is a first pass at implementing vendor-specificied optional fields.
>>>>> That said, I'll comment inline to your points
>>>>>
>>>>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>>>>
>>>>> Hi
>>>>> I must say that I really dislike the proposed format for vendor specific
>>>>> fields.
>>>>> Having a variable length "tag" before the length field means that it
>>>>> is necessary
>>>>> to scan the tag looking for the ',' just to find the length field.
>>>>>
>>>>> You make a valid point. I'd like others to weigh in here and comment on
>>>>> whether they think this is a serious performance limitation. I'll propose
>>>>> this as a discussion point for the upcoming meeting in Prague. The reason
>>>>> for the variable length tag is that it is based on the SD-ID format from
>>>>> Syslog, which is variable in length (i.e. the unrestricted name before the
>>>>> '@').  I think using a Vendor-ID based on a PEN is common sense, so I'd like
>>>>> to stick with that if possible. We could decide on a fixed length name (or
>>>>> number to parallel the tag from the Pre-Defined Optional Fields) followed by
>>>>> four byte PEN.
>>>>>
>>>>> There is no simple way to tell he difference between a sip-clf
>>>>> optional field and
>>>>> a vendor specific optional field. So it will always be necessary to scan the
>>>>> record looking for the ',' .
>>>>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
>>>>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>>>>> standard optional field without a lot of work.
>>>>>
>>>>> Remember that that this draft restricts the scope of the syntax to the 2nd
>>>>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a legal
>>>>> vendor-specified optional field since "0001" doesn't contain an '@', which
>>>>> is mandatory for a Vendor-ID as defined in the draft. So there should be no
>>>>> confusion there as the Vendor-ID from the vendor-specified optional fields
>>>>> and the Tag from the pre-defined optional fields can never be the same.
>>>>>
>>>>
>>>> I think that You did not understand the point I was trying to make.
>>>> As I understand the specification in the 2nd format definition of SD-IDs in
>>>> RFC5424, comma "," is allowed in the name part. So
>>>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficult to
>>>> differentiate from a standard optional field with tag="0001", length="FFFF" and
>>>> a value starting with "@<Vendor-ID>"
>>>>
>>>>> I think a better way to do this would be similar to diameter RFC3588, ch
>>>>> 4.1.
>>>>> Then we could have just one format for standard optional fields and vendor
>>>>> specific fields
>>>>>
>>>>> byte 1  0x09
>>>>> byte 2-5 Tag (Hex)
>>>>> byte 6-9 VendorId
>>>>> byte 10 0x2C
>>>>> byte 11-14 Length (Hex)
>>>>> byte 15 0x2C
>>>>> byte 16-.. Value (variable length)
>>>>>
>>>>> Where VendorId is the IANA assigned "SMI Network Management Private
>>>>> Enterprise Codes"  [ASSIGNNO] value.
>>>>> VendorId=0 is used a for the standard optional fields defined in SIP-CLF.
>>>>>
>>>>> I know that PEN = 0 is a Reserved value and if it is confirmed that it can
>>>>> be used in this way (as apparently DIAMETER did), then I think this proposal
>>>>> is very reasonable. This unifies both optional field types into a single
>>>>> seamless representation. I'll let others, like Chris Lonvick, more
>>>>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>>>> Regards,
>>>>> Gonzalo
>>>>>
>>>>> /Anders
>>>>> _______________________________________________
>>>>> sip-clf mailing list
>>>>> sip-clf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>>>>
>>>>>
>>>
>>>
>
>

From gsalguei@cisco.com  Wed Mar 16 21:02:44 2011
Return-Path: <gsalguei@cisco.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 4C4643A6A15 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 21:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.838
X-Spam-Level: 
X-Spam-Status: No, score=-9.838 tagged_above=-999 required=5 tests=[AWL=-0.441, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_37=0.6, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-8]
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 48T7V4KFlk13 for <sip-clf@core3.amsl.com>; Wed, 16 Mar 2011 21:02:43 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 44BA93A69A5 for <sip-clf@ietf.org>; Wed, 16 Mar 2011 21:02:43 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2H449In014555; Thu, 17 Mar 2011 00:04:09 -0400 (EDT)
Received: from rtp-gsalguei-8714.cisco.com (rtp-gsalguei-8714.cisco.com [10.116.61.53]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2H446n7020194;  Thu, 17 Mar 2011 00:04:06 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-61--95100995
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTimewCMhf06foUJeSKW0vwbPQJqymErnc9NFyxEG@mail.gmail.com>
Date: Thu, 17 Mar 2011 00:04:06 -0400
Message-Id: <27D2855F-3F16-444E-A851-1BEE44435681@cisco.com>
References: <AANLkTimewCMhf06foUJeSKW0vwbPQJqymErnc9NFyxEG@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft-ietf-sipclf-format-01, IPv6 format
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: Thu, 17 Mar 2011 04:02:44 -0000

--Apple-Mail-61--95100995
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks Anders. There are two reasonable possibilities here:

1) I'll add some text to explain that the address:port is a general =
representation. While purely having address:port is appropriate for =
IPv4, the more appropriate square brackets syntax [address]:port should =
be used for IPv6

2) Use the syntax [address]:port SHALL be used for both IPv4 and IPv6

I prefer option #2 for its broad-based usage and simplicity. Hopefully =
folks will weigh in with their preference.

Regards,

Gonzalo

On Mar 16, 2011, at 6:57 PM, Anders Nygren wrote:

> Hi
> For Destination IP address:port and Source IP address:port it only =
specifies
> that "The port number MUST be separated from the IP address by a =
single ':'"
> It does not say anything about how IPv6 addresses should be =
represented.
>=20
> But according to "A Recommendation for IPv6 Address Text =
Representation",
> RFC 5952, IPv6Address':'port is ambiguous. Because of this RFC 5952 =
ch.6 says
>    "The [] style as expressed in [RFC3986] SHOULD be employed, and is
>      the default unless otherwise specified"
>=20
> This also seems to be the same format as specified by the SIP ABNF for
> host:port.
>=20
> I think it would be useful to add that to the descriptions of
> Destination IP address:port and Source IP address:port.
> If not RFC 5952 then at least some other comment about =
allowed/recommended
> formats for IPv6 addresses.
>=20
> /Anders
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-61--95100995
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Thanks Anders. There are two reasonable possibilities =
here:<div><br></div><div>1) I'll add some text to explain that the =
address:port is a general representation. While purely having =
address:port is appropriate for IPv4, the more appropriate square =
brackets syntax [address]:port should be used for =
IPv6</div><div><br></div><div>2) Use the syntax [address]:port SHALL be =
used for both IPv4 and IPv6</div><div><br></div><div>I prefer option #2 =
for its broad-based usage and simplicity. Hopefully folks will weigh in =
with their =
preference.</div><div><br></div><div>Regards,</div><div><br></div><div>Gon=
zalo</div><div><br><div><div>On Mar 16, 2011, at 6:57 PM, Anders Nygren =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi<br>For Destination IP address:port and Source IP =
address:port it only specifies<br>that "The port number MUST be =
separated from the IP address by a single ':'"<br>It does not say =
anything about how IPv6 addresses should be represented.<br><br>But =
according to "A Recommendation for IPv6 Address Text =
Representation",<br>RFC 5952, IPv6Address':'port is ambiguous. Because =
of this RFC 5952 ch.6 says<br> &nbsp;&nbsp;&nbsp;"The [] style as =
expressed in [RFC3986] SHOULD be employed, and is<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the default unless otherwise =
specified"<br><br>This also seems to be the same format as specified by =
the SIP ABNF for<br>host:port.<br><br>I think it would be useful to add =
that to the descriptions of<br>Destination IP address:port and Source IP =
address:port.<br>If not RFC 5952 then at least some other comment about =
allowed/recommended<br>formats for IPv6 =
addresses.<br><br>/Anders<br>_____________________________________________=
__<br>sip-clf mailing list<br><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/sip-clf<br></div></blockquote></div><br></div></body>=
</html>=

--Apple-Mail-61--95100995--

From anders.nygren@gmail.com  Thu Mar 17 10:03:12 2011
Return-Path: <anders.nygren@gmail.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 1339B3A6ACC for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 10:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.28
X-Spam-Level: 
X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=-0.981,  BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_LOW=-1]
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 T31MyCmD9hhm for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 10:03:10 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 633443A6A25 for <sip-clf@ietf.org>; Thu, 17 Mar 2011 10:03:10 -0700 (PDT)
Received: by wwa36 with SMTP id 36so2543124wwa.13 for <sip-clf@ietf.org>; Thu, 17 Mar 2011 10:04:37 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ZdKPlflMQJ0rUkCf3FKexf3Aja/YpIoPMIK5NOy3UWA=; b=xOVkuHPs7uhQDhROPIVGIYegJ8BCgvUiN19IgxaeCePVuUJnQVeH+o/4dHdnOptZv3 /jdaWsgprdBDEN6F2uBs/cQ/rmE1Jbx+cx3jNyCyf0O8mAOolsdkk9nhVqhYBp0/mRFu xStPGO1pwjTu4QJVJCTups/vl4WefnHx6HhJU=
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:content-transfer-encoding; b=lh9LfCE6g2sllwJh6U1H53nBTzwXn7Vk5CcIgFIS4+Od2PFWQV7pf0u/VR2Dqf8vXU 7mi6HdavdyZGC86xqDbW8kte4il8jFy9kULBhDa5W7nHU38OCqM4kMPZ/3roLsCs70pl RHPeBX06NnOnzUbh7hHs3K8BUBvtMytlxJo2s=
MIME-Version: 1.0
Received: by 10.216.178.132 with SMTP id f4mr1118661wem.62.1300381477751; Thu, 17 Mar 2011 10:04:37 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Thu, 17 Mar 2011 10:04:37 -0700 (PDT)
In-Reply-To: <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com> <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com>
Date: Thu, 17 Mar 2011 11:04:37 -0600
Message-ID: <AANLkTinLcJsFtNMp=egPJs_oSejiKMVYnUyYhttLwk4u@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Thu, 17 Mar 2011 17:03:12 -0000

On Wed, Mar 16, 2011 at 2:24 PM, Gonzalo Salgueiro <gsalguei@cisco.com> wro=
te:
> Chris -
> Thanks for the response. One very simple proposal I was offering that wou=
ld
> clean up the convoluted syntax and avoid having to look ahead for the '@'=
 is
> :
> - A single format for both pre-defined and vendor-specified optional fiel=
ds
> based on TLV format
> - This single format is based on syslog-like=A0tag@PEN is used is used as=
 the
> "Tag" in TLV and where PEN=3D0 if it is not vendor-specified.
> This eliminates any need for a V bit to specify standard, vendor,
> experimental. Can you confirm that using the Reserved PEN=3D0 in this man=
ner
> is valid?
> This seems to me a simple and elegant solution to this problem. Thoughts?
> Regards,
> Gonzalo
>

Yes, that is fine with me.
Or to expand it and still keeping in line with syslog, (using a variants of
both formats in RFC5424 ch 6.3.2. SD-ID, and not just the second format),
and my previous proposals but avoids the vendor flag.
It is still easy to parse, (if byte 5=3D"," it is a standard field and
if byte 5=3D"@"
it is a vendor extension), and it saves 5 bytes per optional field.
And You don't have to worry about if PEN =3D 0 is allowed or not.

In ABNF

optional    =3D standard | vendor
tag           =3D 4HEXDIG
vendorID   =3D 4HEXDIG
length      =3D 4HEXDIG
standard   =3D tag "," length "," value
vendor      =3D tag "@" vendorID ","  length "," value

/Anders

>
> On Mar 16, 2011, at 3:36 PM, Chris Lonvick wrote:
>
> Hi,
>
> Sorry for the delay in responding - busy with the day job. =A0:-)
>
> I see where you're going with this. =A0You could preclude the 0x2C charac=
ter
> from the VendorID, and you could establish a fixed length for the VendorI=
D,
> but even with that you're still going to have to do a search ahead to see=
 if
> there is a 0x40 (@) in the field to determine if it's a vendor specific
> optional field, or a pre-defined optional field. =A0As Anders says, not t=
he
> best way to quickly process.
>
> I also saw Anders' proposal for inserting a new 1-byte field in the Optio=
nal
> Fields container. =A0Using a full byte for two options just seems wastefu=
l to
> me, but that's probably just me. =A0:-) =A0A good option for that is to t=
ell the
> IANA that the field currently has two options ("s" and "v") but may be
> expanded at a later time. =A0In SSH we usually carved out three options:
> standard, vendor, and experimental. =A0For experimental, we said that if =
you
> come up with something new and want others to try it out (without having =
to
> use a single PEN [sort'a]) then have everone agree upon a value in the
> experimental range. =A0See the last bullet in section 5.1 of RFC 4254 for=
 an
> example.
>
> Regards,
> Chris
>
> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>
> Anders -
>
> You are absolutely right, I did misunderstand your point the first time
> around. I thought you were saying '001' was the Vendor-ID, when in fact y=
ou
> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in
> front of the '@' is only restricted in the following way:
>
> - MUST be printable US-ASCII strings
>
> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', ABN=
F
> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d3=
4),
> whitespace, or control characters.
>
> it indeed means your example is a valid Vendor-ID and could cause confusi=
on.
> While this would be very unlikely to happen in practice [I can't imagine =
an
> implementer intentionally doing this], it is undesired. I think this fact
> makes your original proposal that much more elegant than the existing one=
.
>
> Regards,
>
> Gonzalo
>
>
> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>
> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com>
> wrote:
>
> Thanks for raising your concerns Anders.
>
> As you know, this draft was just published today and its principal intent
>
> was to formulate an initial solution for SIP CLF extensibility.
>
> A little history:
>
> The current proposal for Vendor-specific extensions using a Syslog-like
>
> approach (i.e. name@<private enterprise number>) was something proposed o=
ver
>
> email and decided at the last SIPCLF Interim meeting in January. So this
>
> really is a first pass at implementing vendor-specificied optional fields=
.
>
> That said, I'll comment inline to your points
>
> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>
> Hi
>
> I must say that I really dislike the proposed format for vendor specific
>
> fields.
>
> Having a variable length "tag" before the length field means that it
>
> is necessary
>
> to scan the tag looking for the ',' just to find the length field.
>
> You make a valid point. I'd like others to weigh in here and comment on
>
> whether they think this is a serious performance limitation. I'll propose
>
> this as a discussion point for the upcoming meeting in Prague. The reason
>
> for the variable length tag is that it is based on the SD-ID format from
>
> Syslog, which is variable in length (i.e. the unrestricted name before th=
e
>
> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so I'd=
 like
>
> to stick with that if possible. We could decide on a fixed length name (o=
r
>
> number to parallel the tag from the Pre-Defined Optional Fields) followed=
 by
>
> four byte PEN.
>
> There is no simple way to tell he difference between a sip-clf
>
> optional field and
>
> a vendor specific optional field. So it will always be necessary to scan =
the
>
> record looking for the ',' .
>
> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
>
> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>
> standard optional field without a lot of work.
>
> Remember that that this draft restricts the scope of the syntax to the 2n=
d
>
> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a leg=
al
>
> vendor-specified optional field since "0001" doesn't contain an '@', whic=
h
>
> is mandatory for a Vendor-ID as defined in the draft. So there should be =
no
>
> confusion there as the Vendor-ID from the vendor-specified optional field=
s
>
> and the Tag from the pre-defined optional fields can never be the same.
>
>
> I think that You did not understand the point I was trying to make.
>
> As I understand the specification in the 2nd format definition of SD-IDs =
in
>
> RFC5424, comma "," is allowed in the name part. So
>
> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficu=
lt
> to
>
> differentiate from a standard optional field with tag=3D"0001", length=3D=
"FFFF"
> and
>
> a value starting with "@<Vendor-ID>"
>
> I think a better way to do this would be similar to diameter RFC3588, ch
>
> 4.1.
>
> Then we could have just one format for standard optional fields and vendo=
r
>
> specific fields
>
> byte 1 =A00x09
>
> byte 2-5 Tag (Hex)
>
> byte 6-9 VendorId
>
> byte 10 0x2C
>
> byte 11-14 Length (Hex)
>
> byte 15 0x2C
>
> byte 16-.. Value (variable length)
>
> Where VendorId is the IANA assigned "SMI Network Management Private
>
> Enterprise Codes" =A0[ASSIGNNO] value.
>
> VendorId=3D0 is used a for the standard optional fields defined in SIP-CL=
F.
>
> I know that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can
>
> be used in this way (as apparently DIAMETER did), then I think this propo=
sal
>
> is very reasonable. This unifies both optional field types into a single
>
> seamless representation. I'll let others, like Chris Lonvick, more
>
> knowledgeable than I weigh in on this as well to confirm my thoughts.
>
> Regards,
>
> Gonzalo
>
> /Anders
>
> _______________________________________________
>
> sip-clf mailing list
>
> sip-clf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>
>
>
>
>

From gsalguei@cisco.com  Thu Mar 17 10:26:46 2011
Return-Path: <gsalguei@cisco.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 8A8C43A69EE for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 10:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.276
X-Spam-Level: 
X-Spam-Status: No, score=-9.276 tagged_above=-999 required=5 tests=[AWL=-0.978, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8]
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 Q07IUbIuHvpf for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 10:26:44 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 5F4473A69EB for <sip-clf@ietf.org>; Thu, 17 Mar 2011 10:26:44 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2HHS9Gi027378; Thu, 17 Mar 2011 13:28:09 -0400 (EDT)
Received: from dhcp-64-102-211-8.cisco.com (dhcp-64-102-211-8.cisco.com [64.102.211.8]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2HHS4SB014891;  Thu, 17 Mar 2011 13:28:06 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-76--46863264
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <AANLkTinLcJsFtNMp=egPJs_oSejiKMVYnUyYhttLwk4u@mail.gmail.com>
Date: Thu, 17 Mar 2011 13:28:03 -0400
Message-Id: <60755913-FF54-4FBC-B999-17E8A958DF83@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com> <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com> <AANLkTinLcJsFtNMp=egPJs_oSejiKMVYnUyYhttLwk4u@mail.gmail.com>
To: Anders Nygren <anders.nygren@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Thu, 17 Mar 2011 17:26:46 -0000

--Apple-Mail-76--46863264
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I like this proposal as well. Despite the extra 5 bytes for =
vendor-specified optional fields, I think I prefer my proposal only from =
the point of view that it lines up nicely for both optional field types =
(and I think there is value in that). I could be easily swayed though... =
;-)

My ordered preference list is:

1. My proposal with PEN=3D0 for pre-defined optional fields
2. Chris Lonvick's proposal of using my proposal with a newly =
registered/reserved PEN for pre-defined optional fields
3. This proposal

Regards,

Gonzalo


On Mar 17, 2011, at 1:04 PM, Anders Nygren wrote:

> On Wed, Mar 16, 2011 at 2:24 PM, Gonzalo Salgueiro =
<gsalguei@cisco.com> wrote:
>> Chris -
>> Thanks for the response. One very simple proposal I was offering that =
would
>> clean up the convoluted syntax and avoid having to look ahead for the =
'@' is
>> :
>> - A single format for both pre-defined and vendor-specified optional =
fields
>> based on TLV format
>> - This single format is based on syslog-like tag@PEN is used is used =
as the
>> "Tag" in TLV and where PEN=3D0 if it is not vendor-specified.
>> This eliminates any need for a V bit to specify standard, vendor,
>> experimental. Can you confirm that using the Reserved PEN=3D0 in this =
manner
>> is valid?
>> This seems to me a simple and elegant solution to this problem. =
Thoughts?
>> Regards,
>> Gonzalo
>>=20
>=20
> Yes, that is fine with me.
> Or to expand it and still keeping in line with syslog, (using a =
variants of
> both formats in RFC5424 ch 6.3.2. SD-ID, and not just the second =
format),
> and my previous proposals but avoids the vendor flag.
> It is still easy to parse, (if byte 5=3D"," it is a standard field and
> if byte 5=3D"@"
> it is a vendor extension), and it saves 5 bytes per optional field.
> And You don't have to worry about if PEN =3D 0 is allowed or not.
>=20
> In ABNF
>=20
> optional    =3D standard | vendor
> tag           =3D 4HEXDIG
> vendorID   =3D 4HEXDIG
> length      =3D 4HEXDIG
> standard   =3D tag "," length "," value
> vendor      =3D tag "@" vendorID ","  length "," value
>=20
> /Anders
>=20
>>=20
>> On Mar 16, 2011, at 3:36 PM, Chris Lonvick wrote:
>>=20
>> Hi,
>>=20
>> Sorry for the delay in responding - busy with the day job.  :-)
>>=20
>> I see where you're going with this.  You could preclude the 0x2C =
character
>> from the VendorID, and you could establish a fixed length for the =
VendorID,
>> but even with that you're still going to have to do a search ahead to =
see if
>> there is a 0x40 (@) in the field to determine if it's a vendor =
specific
>> optional field, or a pre-defined optional field.  As Anders says, not =
the
>> best way to quickly process.
>>=20
>> I also saw Anders' proposal for inserting a new 1-byte field in the =
Optional
>> Fields container.  Using a full byte for two options just seems =
wasteful to
>> me, but that's probably just me.  :-)  A good option for that is to =
tell the
>> IANA that the field currently has two options ("s" and "v") but may =
be
>> expanded at a later time.  In SSH we usually carved out three =
options:
>> standard, vendor, and experimental.  For experimental, we said that =
if you
>> come up with something new and want others to try it out (without =
having to
>> use a single PEN [sort'a]) then have everone agree upon a value in =
the
>> experimental range.  See the last bullet in section 5.1 of RFC 4254 =
for an
>> example.
>>=20
>> Regards,
>> Chris
>>=20
>> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>>=20
>> Anders -
>>=20
>> You are absolutely right, I did misunderstand your point the first =
time
>> around. I thought you were saying '001' was the Vendor-ID, when in =
fact you
>> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name =
in
>> front of the '@' is only restricted in the following way:
>>=20
>> - MUST be printable US-ASCII strings
>>=20
>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF
>> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF =
%d34),
>> whitespace, or control characters.
>>=20
>> it indeed means your example is a valid Vendor-ID and could cause =
confusion.
>> While this would be very unlikely to happen in practice [I can't =
imagine an
>> implementer intentionally doing this], it is undesired. I think this =
fact
>> makes your original proposal that much more elegant than the existing =
one.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>>=20
>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>=20
>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro =
<gsalguei@cisco.com>
>> wrote:
>>=20
>> Thanks for raising your concerns Anders.
>>=20
>> As you know, this draft was just published today and its principal =
intent
>>=20
>> was to formulate an initial solution for SIP CLF extensibility.
>>=20
>> A little history:
>>=20
>> The current proposal for Vendor-specific extensions using a =
Syslog-like
>>=20
>> approach (i.e. name@<private enterprise number>) was something =
proposed over
>>=20
>> email and decided at the last SIPCLF Interim meeting in January. So =
this
>>=20
>> really is a first pass at implementing vendor-specificied optional =
fields.
>>=20
>> That said, I'll comment inline to your points
>>=20
>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>=20
>> Hi
>>=20
>> I must say that I really dislike the proposed format for vendor =
specific
>>=20
>> fields.
>>=20
>> Having a variable length "tag" before the length field means that it
>>=20
>> is necessary
>>=20
>> to scan the tag looking for the ',' just to find the length field.
>>=20
>> You make a valid point. I'd like others to weigh in here and comment =
on
>>=20
>> whether they think this is a serious performance limitation. I'll =
propose
>>=20
>> this as a discussion point for the upcoming meeting in Prague. The =
reason
>>=20
>> for the variable length tag is that it is based on the SD-ID format =
from
>>=20
>> Syslog, which is variable in length (i.e. the unrestricted name =
before the
>>=20
>> '@').  I think using a Vendor-ID based on a PEN is common sense, so =
I'd like
>>=20
>> to stick with that if possible. We could decide on a fixed length =
name (or
>>=20
>> number to parallel the tag from the Pre-Defined Optional Fields) =
followed by
>>=20
>> four byte PEN.
>>=20
>> There is no simple way to tell he difference between a sip-clf
>>=20
>> optional field and
>>=20
>> a vendor specific optional field. So it will always be necessary to =
scan the
>>=20
>> record looking for the ',' .
>>=20
>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal
>>=20
>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from =
a
>>=20
>> standard optional field without a lot of work.
>>=20
>> Remember that that this draft restricts the scope of the syntax to =
the 2nd
>>=20
>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a =
legal
>>=20
>> vendor-specified optional field since "0001" doesn't contain an '@', =
which
>>=20
>> is mandatory for a Vendor-ID as defined in the draft. So there should =
be no
>>=20
>> confusion there as the Vendor-ID from the vendor-specified optional =
fields
>>=20
>> and the Tag from the pre-defined optional fields can never be the =
same.
>>=20
>>=20
>> I think that You did not understand the point I was trying to make.
>>=20
>> As I understand the specification in the 2nd format definition of =
SD-IDs in
>>=20
>> RFC5424, comma "," is allowed in the name part. So
>>=20
>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very =
difficult
>> to
>>=20
>> differentiate from a standard optional field with tag=3D"0001", =
length=3D"FFFF"
>> and
>>=20
>> a value starting with "@<Vendor-ID>"
>>=20
>> I think a better way to do this would be similar to diameter RFC3588, =
ch
>>=20
>> 4.1.
>>=20
>> Then we could have just one format for standard optional fields and =
vendor
>>=20
>> specific fields
>>=20
>> byte 1  0x09
>>=20
>> byte 2-5 Tag (Hex)
>>=20
>> byte 6-9 VendorId
>>=20
>> byte 10 0x2C
>>=20
>> byte 11-14 Length (Hex)
>>=20
>> byte 15 0x2C
>>=20
>> byte 16-.. Value (variable length)
>>=20
>> Where VendorId is the IANA assigned "SMI Network Management Private
>>=20
>> Enterprise Codes"  [ASSIGNNO] value.
>>=20
>> VendorId=3D0 is used a for the standard optional fields defined in =
SIP-CLF.
>>=20
>> I know that PEN =3D 0 is a Reserved value and if it is confirmed that =
it can
>>=20
>> be used in this way (as apparently DIAMETER did), then I think this =
proposal
>>=20
>> is very reasonable. This unifies both optional field types into a =
single
>>=20
>> seamless representation. I'll let others, like Chris Lonvick, more
>>=20
>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>=20
>> Regards,
>>=20
>> Gonzalo
>>=20
>> /Anders
>>=20
>> _______________________________________________
>>=20
>> sip-clf mailing list
>>=20
>> sip-clf@ietf.org
>>=20
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20


--Apple-Mail-76--46863264
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
like this proposal as well. Despite the extra 5 bytes for =
vendor-specified optional fields, I think I prefer my proposal only from =
the point of view that it lines up nicely for both optional field types =
(and I think there is value in that). I could be easily swayed though... =
;-)<div><br></div><div>My ordered preference list =
is:<div><br></div><div>1. My proposal with PEN=3D0 for pre-defined =
optional fields</div><div>2. Chris Lonvick's proposal of using my =
proposal with a newly registered/reserved PEN for&nbsp;pre-defined =
optional fields</div><div>3. This =
proposal</div><div><br></div><div>Regards,</div><div><br></div><div>Gonzal=
o</div><div><br></div><div><br><div><div>On Mar 17, 2011, at 1:04 PM, =
Anders Nygren wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Wed, Mar 16, 2011 at 2:24 PM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Chris -<br></blockquote><blockquote =
type=3D"cite">Thanks for the response. One very simple proposal I was =
offering that would<br></blockquote><blockquote type=3D"cite">clean up =
the convoluted syntax and avoid having to look ahead for the '@' =
is<br></blockquote><blockquote type=3D"cite">:<br></blockquote><blockquote=
 type=3D"cite">- A single format for both pre-defined and =
vendor-specified optional fields<br></blockquote><blockquote =
type=3D"cite">based on TLV format<br></blockquote><blockquote =
type=3D"cite">- This single format is based on syslog-like&nbsp;tag@PEN =
is used is used as the<br></blockquote><blockquote type=3D"cite">"Tag" =
in TLV and where PEN=3D0 if it is not =
vendor-specified.<br></blockquote><blockquote type=3D"cite">This =
eliminates any need for a V bit to specify standard, =
vendor,<br></blockquote><blockquote type=3D"cite">experimental. Can you =
confirm that using the Reserved PEN=3D0 in this =
manner<br></blockquote><blockquote type=3D"cite">is =
valid?<br></blockquote><blockquote type=3D"cite">This seems to me a =
simple and elegant solution to this problem. =
Thoughts?<br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>Yes, that is fine with me.<br>Or to =
expand it and still keeping in line with syslog, (using a variants =
of<br>both formats in RFC5424 ch 6.3.2. SD-ID, and not just the second =
format),<br>and my previous proposals but avoids the vendor flag.<br>It =
is still easy to parse, (if byte 5=3D"," it is a standard field =
and<br>if byte 5=3D"@"<br>it is a vendor extension), and it saves 5 =
bytes per optional field.<br>And You don't have to worry about if PEN =3D =
0 is allowed or not.<br><br>In ABNF<br><br>optional &nbsp;&nbsp;&nbsp;=3D =
standard | vendor<br>tag =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D =
4HEXDIG<br>vendorID &nbsp;&nbsp;=3D 4HEXDIG<br>length =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D 4HEXDIG<br>standard &nbsp;&nbsp;=3D =
tag "," length "," value<br>vendor &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D tag =
"@" vendorID "," &nbsp;length "," =
value<br><br>/Anders<br><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 16, =
2011, at 3:36 PM, Chris Lonvick wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Sorry for the =
delay in responding - busy with the day job. =
&nbsp;:-)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I see where =
you're going with this. &nbsp;You could preclude the 0x2C =
character<br></blockquote><blockquote type=3D"cite">from the VendorID, =
and you could establish a fixed length for the =
VendorID,<br></blockquote><blockquote type=3D"cite">but even with that =
you're still going to have to do a search ahead to see =
if<br></blockquote><blockquote type=3D"cite">there is a 0x40 (@) in the =
field to determine if it's a vendor specific<br></blockquote><blockquote =
type=3D"cite">optional field, or a pre-defined optional field. &nbsp;As =
Anders says, not the<br></blockquote><blockquote type=3D"cite">best way =
to quickly process.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I also saw =
Anders' proposal for inserting a new 1-byte field in the =
Optional<br></blockquote><blockquote type=3D"cite">Fields container. =
&nbsp;Using a full byte for two options just seems wasteful =
to<br></blockquote><blockquote type=3D"cite">me, but that's probably =
just me. &nbsp;:-) &nbsp;A good option for that is to tell =
the<br></blockquote><blockquote type=3D"cite">IANA that the field =
currently has two options ("s" and "v") but may =
be<br></blockquote><blockquote type=3D"cite">expanded at a later time. =
&nbsp;In SSH we usually carved out three =
options:<br></blockquote><blockquote type=3D"cite">standard, vendor, and =
experimental. &nbsp;For experimental, we said that if =
you<br></blockquote><blockquote type=3D"cite">come up with something new =
and want others to try it out (without having =
to<br></blockquote><blockquote type=3D"cite">use a single PEN [sort'a]) =
then have everone agree upon a value in the<br></blockquote><blockquote =
type=3D"cite">experimental range. &nbsp;See the last bullet in section =
5.1 of RFC 4254 for an<br></blockquote><blockquote =
type=3D"cite">example.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Chris<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Tue, 15 Mar =
2011, Gonzalo Salgueiro wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Anders =
-<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">You are absolutely right, I did misunderstand your point =
the first time<br></blockquote><blockquote type=3D"cite">around. I =
thought you were saying '001' was the Vendor-ID, when in fact =
you<br></blockquote><blockquote type=3D"cite">were saying that =
"0001,FFFF,@&lt;PEN&gt;" is the Vendor-ID. Since the name =
in<br></blockquote><blockquote type=3D"cite">front of the '@' is only =
restricted in the following way:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- MUST be =
printable US-ASCII strings<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- MUST NOT =
contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', =
ABNF<br></blockquote><blockquote type=3D"cite">%d61), a closing brace =
(']', ABNF %d93), a quote-character ('"', ABNF =
%d34),<br></blockquote><blockquote type=3D"cite">whitespace, or control =
characters.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">it indeed means =
your example is a valid Vendor-ID and could cause =
confusion.<br></blockquote><blockquote type=3D"cite">While this would be =
very unlikely to happen in practice [I can't imagine =
an<br></blockquote><blockquote type=3D"cite">implementer intentionally =
doing this], it is undesired. I think this =
fact<br></blockquote><blockquote type=3D"cite">makes your original =
proposal that much more elegant than the existing =
one.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 15, =
2011, at 10:38 AM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Tue, Mar 15, =
2011 at 12:19 AM, Gonzalo Salgueiro &lt;<a =
href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt;<br></blockqu=
ote><blockquote type=3D"cite">wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thanks for =
raising your concerns Anders.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">As you know, =
this draft was just published today and its principal =
intent<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">was to =
formulate an initial solution for SIP CLF =
extensibility.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">A little =
history:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The current =
proposal for Vendor-specific extensions using a =
Syslog-like<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">approach (i.e. =
name@&lt;private enterprise number&gt;) was something proposed =
over<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">email and =
decided at the last SIPCLF Interim meeting in January. So =
this<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">really is a =
first pass at implementing vendor-specificied optional =
fields.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">That said, I'll =
comment inline to your points<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Mar 14, =
2011, at 10:53 PM, Anders Nygren wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Hi<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I must say that =
I really dislike the proposed format for vendor =
specific<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">fields.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Having a =
variable length "tag" before the length field means that =
it<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">is necessary<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">to scan the tag =
looking for the ',' just to find the length =
field.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">You make a =
valid point. I'd like others to weigh in here and comment =
on<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">whether they think this is a serious performance =
limitation. I'll propose<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">this as a =
discussion point for the upcoming meeting in Prague. The =
reason<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">for the =
variable length tag is that it is based on the SD-ID format =
from<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Syslog, which =
is variable in length (i.e. the unrestricted name before =
the<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">'@'). &nbsp;I think using a Vendor-ID based on a PEN is =
common sense, so I'd like<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">to stick with =
that if possible. We could decide on a fixed length name =
(or<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">number to parallel the tag from the Pre-Defined Optional =
Fields) followed by<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">four byte =
PEN.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">There is no =
simple way to tell he difference between a =
sip-clf<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">optional field =
and<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">a vendor specific optional field. So it will always be =
necessary to scan the<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">record looking =
for the ',' .<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Actually =
looking at RFC 5424 ch 4.3.2 it looks like this would be a =
legal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">ID, =
"0001,FFFF,@12345" which would be difficult to differentiate from =
a<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">standard optional field without a lot of =
work.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Remember that =
that this draft restricts the scope of the syntax to the =
2nd<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">format definition of SD-IDs in RFC5424. Thus, the above =
wouldn't be a legal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">vendor-specified =
optional field since "0001" doesn't contain an '@', =
which<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is mandatory =
for a Vendor-ID as defined in the draft. So there should be =
no<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">confusion there as the Vendor-ID from the vendor-specified =
optional fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">and the Tag =
from the pre-defined optional fields can never be the =
same.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think that =
You did not understand the point I was trying to =
make.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">As I understand =
the specification in the 2nd format definition of SD-IDs =
in<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">RFC5424, comma "," is allowed in the name part. =
So<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">"0001,FFFF,@&lt;Vendor-ID&gt;" would be a legal tag, that =
would be very difficult<br></blockquote><blockquote =
type=3D"cite">to<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">differentiate =
from a standard optional field with tag=3D"0001", =
length=3D"FFFF"<br></blockquote><blockquote =
type=3D"cite">and<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">a value =
starting with "@&lt;Vendor-ID&gt;"<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think a =
better way to do this would be similar to diameter RFC3588, =
ch<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">4.1.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Then we could =
have just one format for standard optional fields and =
vendor<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">specific =
fields<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 1 =
&nbsp;0x09<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 2-5 Tag =
(Hex)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 6-9 =
VendorId<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 10 =
0x2C<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 11-14 =
Length (Hex)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 15 =
0x2C<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">byte 16-.. =
Value (variable length)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Where VendorId =
is the IANA assigned "SMI Network Management =
Private<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Enterprise =
Codes" &nbsp;[ASSIGNNO] value.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">VendorId=3D0 is =
used a for the standard optional fields defined in =
SIP-CLF.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I know that PEN =
=3D 0 is a Reserved value and if it is confirmed that it =
can<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">be used in this way (as apparently DIAMETER did), then I =
think this proposal<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is very =
reasonable. This unifies both optional field types into a =
single<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">seamless =
representation. I'll let others, like Chris Lonvick, =
more<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">knowledgeable =
than I weigh in on this as well to confirm my =
thoughts.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Gonzalo<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">/Anders<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">sip-clf mailing list<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:sip-clf@ietf.org">sip-clf@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/sip-clf">https://www.ietf.or=
g/mailman/listinfo/sip-clf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote></div></blockquote></div><br></div></div></=
body></html>=

--Apple-Mail-76--46863264--

From anders.nygren@gmail.com  Thu Mar 17 10:43:46 2011
Return-Path: <anders.nygren@gmail.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 380C43A6A25 for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 10:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.228
X-Spam-Level: 
X-Spam-Status: No, score=-2.228 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_LOW=-1]
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 v+kxITWPIN4O for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 10:43:45 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 9B75C3A69F3 for <sip-clf@ietf.org>; Thu, 17 Mar 2011 10:43:44 -0700 (PDT)
Received: by wwa36 with SMTP id 36so2580641wwa.13 for <sip-clf@ietf.org>; Thu, 17 Mar 2011 10:45:12 -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 :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EqRV4yvFVHjopodlVB38mahNCNn7foPL2Qm9dK/i2HU=; b=DuIlG41hAdJYpJjiNcV+A5LTR4Hg5ve+4AHk0CcKXEiRSnCfhBI7iK3lcuVYhv3xdo aLC9+6W6QqclCFEq3M/p1h/XuIIMYJUkHwTcr7pnMG4CcdZD/U+cgHGZfkJ2abYqc+nB FC9vd8mmdqnScLUDDvWofJIVFMHsDrfc7fFJc=
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:content-transfer-encoding; b=KLZHTufrFcoH0H+0gap7/88sOSTybXKoh1R11/A6Fx8KyGhKL9Ur2IIFTegZzHlsoK lrUKEV/q0nIbV8CggFgplMAneTH9AEuHoOSQmGJrk7nv/wnxBXf3MdjoF5ihRoaUq1hG oJDmtxfhzk4oAPJr5hsDDTV67Ul3HmYBRf/cs=
MIME-Version: 1.0
Received: by 10.216.79.11 with SMTP id h11mr29975wee.77.1300383912232; Thu, 17 Mar 2011 10:45:12 -0700 (PDT)
Received: by 10.216.25.17 with HTTP; Thu, 17 Mar 2011 10:45:12 -0700 (PDT)
In-Reply-To: <60755913-FF54-4FBC-B999-17E8A958DF83@cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com> <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com> <AANLkTinLcJsFtNMp=egPJs_oSejiKMVYnUyYhttLwk4u@mail.gmail.com> <60755913-FF54-4FBC-B999-17E8A958DF83@cisco.com>
Date: Thu, 17 Mar 2011 11:45:12 -0600
Message-ID: <AANLkTimCsc19X_Fe=f0p77=gOmtrPazKfzpu5etHLwwe@mail.gmail.com>
From: Anders Nygren <anders.nygren@gmail.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Thu, 17 Mar 2011 17:43:46 -0000

I will not argue this any further. All 3 alternatives are fine with me.

/Anders

On Thu, Mar 17, 2011 at 11:28 AM, Gonzalo Salgueiro <gsalguei@cisco.com> wr=
ote:
> I like this proposal as well. Despite the extra 5 bytes for vendor-specif=
ied
> optional fields, I think I prefer my proposal only from the point of view
> that it lines up nicely for both optional field types (and I think there =
is
> value in that). I could be easily swayed though... ;-)
> My ordered preference list is:
> 1. My proposal with PEN=3D0 for pre-defined optional fields
> 2. Chris Lonvick's proposal of using my proposal with a newly
> registered/reserved PEN for=A0pre-defined optional fields
> 3. This proposal
> Regards,
> Gonzalo
>
> On Mar 17, 2011, at 1:04 PM, Anders Nygren wrote:
>
> On Wed, Mar 16, 2011 at 2:24 PM, Gonzalo Salgueiro <gsalguei@cisco.com>
> wrote:
>
> Chris -
>
> Thanks for the response. One very simple proposal I was offering that wou=
ld
>
> clean up the convoluted syntax and avoid having to look ahead for the '@'=
 is
>
> :
>
> - A single format for both pre-defined and vendor-specified optional fiel=
ds
>
> based on TLV format
>
> - This single format is based on syslog-like=A0tag@PEN is used is used as=
 the
>
> "Tag" in TLV and where PEN=3D0 if it is not vendor-specified.
>
> This eliminates any need for a V bit to specify standard, vendor,
>
> experimental. Can you confirm that using the Reserved PEN=3D0 in this man=
ner
>
> is valid?
>
> This seems to me a simple and elegant solution to this problem. Thoughts?
>
> Regards,
>
> Gonzalo
>
>
> Yes, that is fine with me.
> Or to expand it and still keeping in line with syslog, (using a variants =
of
> both formats in RFC5424 ch 6.3.2. SD-ID, and not just the second format),
> and my previous proposals but avoids the vendor flag.
> It is still easy to parse, (if byte 5=3D"," it is a standard field and
> if byte 5=3D"@"
> it is a vendor extension), and it saves 5 bytes per optional field.
> And You don't have to worry about if PEN =3D 0 is allowed or not.
>
> In ABNF
>
> optional =A0=A0=A0=3D standard | vendor
> tag =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=3D 4HEXDIG
> vendorID =A0=A0=3D 4HEXDIG
> length =A0=A0=A0=A0=A0=3D 4HEXDIG
> standard =A0=A0=3D tag "," length "," value
> vendor =A0=A0=A0=A0=A0=3D tag "@" vendorID "," =A0length "," value
>
> /Anders
>
>
> On Mar 16, 2011, at 3:36 PM, Chris Lonvick wrote:
>
> Hi,
>
> Sorry for the delay in responding - busy with the day job. =A0:-)
>
> I see where you're going with this. =A0You could preclude the 0x2C charac=
ter
>
> from the VendorID, and you could establish a fixed length for the VendorI=
D,
>
> but even with that you're still going to have to do a search ahead to see=
 if
>
> there is a 0x40 (@) in the field to determine if it's a vendor specific
>
> optional field, or a pre-defined optional field. =A0As Anders says, not t=
he
>
> best way to quickly process.
>
> I also saw Anders' proposal for inserting a new 1-byte field in the Optio=
nal
>
> Fields container. =A0Using a full byte for two options just seems wastefu=
l to
>
> me, but that's probably just me. =A0:-) =A0A good option for that is to t=
ell the
>
> IANA that the field currently has two options ("s" and "v") but may be
>
> expanded at a later time. =A0In SSH we usually carved out three options:
>
> standard, vendor, and experimental. =A0For experimental, we said that if =
you
>
> come up with something new and want others to try it out (without having =
to
>
> use a single PEN [sort'a]) then have everone agree upon a value in the
>
> experimental range. =A0See the last bullet in section 5.1 of RFC 4254 for=
 an
>
> example.
>
> Regards,
>
> Chris
>
> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>
> Anders -
>
> You are absolutely right, I did misunderstand your point the first time
>
> around. I thought you were saying '001' was the Vendor-ID, when in fact y=
ou
>
> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in
>
> front of the '@' is only restricted in the following way:
>
> - MUST be printable US-ASCII strings
>
> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', ABN=
F
>
> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d3=
4),
>
> whitespace, or control characters.
>
> it indeed means your example is a valid Vendor-ID and could cause confusi=
on.
>
> While this would be very unlikely to happen in practice [I can't imagine =
an
>
> implementer intentionally doing this], it is undesired. I think this fact
>
> makes your original proposal that much more elegant than the existing one=
.
>
> Regards,
>
> Gonzalo
>
>
> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>
> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com>
>
> wrote:
>
> Thanks for raising your concerns Anders.
>
> As you know, this draft was just published today and its principal intent
>
> was to formulate an initial solution for SIP CLF extensibility.
>
> A little history:
>
> The current proposal for Vendor-specific extensions using a Syslog-like
>
> approach (i.e. name@<private enterprise number>) was something proposed o=
ver
>
> email and decided at the last SIPCLF Interim meeting in January. So this
>
> really is a first pass at implementing vendor-specificied optional fields=
.
>
> That said, I'll comment inline to your points
>
> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>
> Hi
>
> I must say that I really dislike the proposed format for vendor specific
>
> fields.
>
> Having a variable length "tag" before the length field means that it
>
> is necessary
>
> to scan the tag looking for the ',' just to find the length field.
>
> You make a valid point. I'd like others to weigh in here and comment on
>
> whether they think this is a serious performance limitation. I'll propose
>
> this as a discussion point for the upcoming meeting in Prague. The reason
>
> for the variable length tag is that it is based on the SD-ID format from
>
> Syslog, which is variable in length (i.e. the unrestricted name before th=
e
>
> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so I'd=
 like
>
> to stick with that if possible. We could decide on a fixed length name (o=
r
>
> number to parallel the tag from the Pre-Defined Optional Fields) followed=
 by
>
> four byte PEN.
>
> There is no simple way to tell he difference between a sip-clf
>
> optional field and
>
> a vendor specific optional field. So it will always be necessary to scan =
the
>
> record looking for the ',' .
>
> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a legal
>
> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>
> standard optional field without a lot of work.
>
> Remember that that this draft restricts the scope of the syntax to the 2n=
d
>
> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a leg=
al
>
> vendor-specified optional field since "0001" doesn't contain an '@', whic=
h
>
> is mandatory for a Vendor-ID as defined in the draft. So there should be =
no
>
> confusion there as the Vendor-ID from the vendor-specified optional field=
s
>
> and the Tag from the pre-defined optional fields can never be the same.
>
>
> I think that You did not understand the point I was trying to make.
>
> As I understand the specification in the 2nd format definition of SD-IDs =
in
>
> RFC5424, comma "," is allowed in the name part. So
>
> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very difficu=
lt
>
> to
>
> differentiate from a standard optional field with tag=3D"0001", length=3D=
"FFFF"
>
> and
>
> a value starting with "@<Vendor-ID>"
>
> I think a better way to do this would be similar to diameter RFC3588, ch
>
> 4.1.
>
> Then we could have just one format for standard optional fields and vendo=
r
>
> specific fields
>
> byte 1 =A00x09
>
> byte 2-5 Tag (Hex)
>
> byte 6-9 VendorId
>
> byte 10 0x2C
>
> byte 11-14 Length (Hex)
>
> byte 15 0x2C
>
> byte 16-.. Value (variable length)
>
> Where VendorId is the IANA assigned "SMI Network Management Private
>
> Enterprise Codes" =A0[ASSIGNNO] value.
>
> VendorId=3D0 is used a for the standard optional fields defined in SIP-CL=
F.
>
> I know that PEN =3D 0 is a Reserved value and if it is confirmed that it =
can
>
> be used in this way (as apparently DIAMETER did), then I think this propo=
sal
>
> is very reasonable. This unifies both optional field types into a single
>
> seamless representation. I'll let others, like Chris Lonvick, more
>
> knowledgeable than I weigh in on this as well to confirm my thoughts.
>
> Regards,
>
> Gonzalo
>
> /Anders
>
> _______________________________________________
>
> sip-clf mailing list
>
> sip-clf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/sip-clf
>
>
>
>
>
>
>
>

From clonvick@cisco.com  Thu Mar 17 12:06:34 2011
Return-Path: <clonvick@cisco.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 05D3A3A6AED for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 12:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.989
X-Spam-Level: 
X-Spam-Status: No, score=-108.989 tagged_above=-999 required=5 tests=[AWL=-0.690, BAYES_00=-2.599, MANGLED_PENIS=2.3, RCVD_IN_DNSWL_HI=-8, 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 cCNipXld1jFy for <sip-clf@core3.amsl.com>; Thu, 17 Mar 2011 12:06:32 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 5F4083A694D for <sip-clf@ietf.org>; Thu, 17 Mar 2011 12:06:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=clonvick@cisco.com; l=8910; q=dns/txt; s=iport; t=1300388880; x=1301598480; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=3a213Lc+kA0wAsSO2d/CdwSU9ihLakT9EsVYZfS62J8=; b=fNGKaHQ3D3tJAw2LxHIoxH9l89O5WhxLNp7s9yyjUUF7zjNd6wzIjRKE zhtxLijKc/Ck1Hd98Bkrr4ArwwCK+jiv8hc2zLTQID3kxgR72p4JCn148 h4kKYLmTkk7S1JwRu1v0Em7yH6W2mzOhMCUCUPtKL4BBvF2zdPvKAuJ4z o=;
X-IronPort-AV: E=Sophos;i="4.63,200,1299456000"; d="scan'208";a="321511095"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by sj-iport-2.cisco.com with ESMTP; 17 Mar 2011 19:08:00 +0000
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.16.68]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2HJ7xoI026601;  Thu, 17 Mar 2011 19:08:00 GMT
Date: Thu, 17 Mar 2011 12:07:59 -0700 (PDT)
From: Chris Lonvick <clonvick@cisco.com>
To: Anders Nygren <anders.nygren@gmail.com>
In-Reply-To: <AANLkTinLcJsFtNMp=egPJs_oSejiKMVYnUyYhttLwk4u@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.1103171207170.26318@sjc-cde-011.cisco.com>
References: <AANLkTi=4NSXhgqAg75EUkWt6K0jdg4Kgcy6B37vyTMit@mail.gmail.com> <75DCC5B8-DB67-42AD-A6F2-F972FCFD5AB3@cisco.com> <AANLkTi=4d+uJ5kVXjiT-8eUzO_-5xWw3Lr23vo5cHiLH@mail.gmail.com> <E7D0A5D2-07B2-40DD-A7C8-2DF9FFC35CB4@cisco.com> <Pine.GSO.4.63.1103150805050.29330@sjc-cde-011.cisco.com> <29F0AE59-74D6-45D7-9FD0-9F3F88BA259A@cisco.com> <AANLkTinLcJsFtNMp=egPJs_oSejiKMVYnUyYhttLwk4u@mail.gmail.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1902445306-1300388879=:26318"
Cc: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Vendor extensions in draft-ietf-sipclf-format-01.txt
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: Thu, 17 Mar 2011 19:06:34 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-1902445306-1300388879=:26318
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi,

I like this one as well.  Unfortunately I won't be in Prague for the=20
discussion.

Thanks,
Chris

On Thu, 17 Mar 2011, Anders Nygren wrote:

> On Wed, Mar 16, 2011 at 2:24 PM, Gonzalo Salgueiro <gsalguei@cisco.com> w=
rote:
>> Chris -
>> Thanks for the response. One very simple proposal I was offering that wo=
uld
>> clean up the convoluted syntax and avoid having to look ahead for the '@=
' is
>> :
>> - A single format for both pre-defined and vendor-specified optional fie=
lds
>> based on TLV format
>> - This single format is based on syslog-like=A0tag@PEN is used is used a=
s the
>> "Tag" in TLV and where PEN=3D0 if it is not vendor-specified.
>> This eliminates any need for a V bit to specify standard, vendor,
>> experimental. Can you confirm that using the Reserved PEN=3D0 in this ma=
nner
>> is valid?
>> This seems to me a simple and elegant solution to this problem. Thoughts=
?
>> Regards,
>> Gonzalo
>>
>
> Yes, that is fine with me.
> Or to expand it and still keeping in line with syslog, (using a variants =
of
> both formats in RFC5424 ch 6.3.2. SD-ID, and not just the second format),
> and my previous proposals but avoids the vendor flag.
> It is still easy to parse, (if byte 5=3D"," it is a standard field and
> if byte 5=3D"@"
> it is a vendor extension), and it saves 5 bytes per optional field.
> And You don't have to worry about if PEN =3D 0 is allowed or not.
>
> In ABNF
>
> optional    =3D standard | vendor
> tag           =3D 4HEXDIG
> vendorID   =3D 4HEXDIG
> length      =3D 4HEXDIG
> standard   =3D tag "," length "," value
> vendor      =3D tag "@" vendorID ","  length "," value
>
> /Anders
>
>>
>> On Mar 16, 2011, at 3:36 PM, Chris Lonvick wrote:
>>
>> Hi,
>>
>> Sorry for the delay in responding - busy with the day job. =A0:-)
>>
>> I see where you're going with this. =A0You could preclude the 0x2C chara=
cter
>> from the VendorID, and you could establish a fixed length for the Vendor=
ID,
>> but even with that you're still going to have to do a search ahead to se=
e if
>> there is a 0x40 (@) in the field to determine if it's a vendor specific
>> optional field, or a pre-defined optional field. =A0As Anders says, not =
the
>> best way to quickly process.
>>
>> I also saw Anders' proposal for inserting a new 1-byte field in the Opti=
onal
>> Fields container. =A0Using a full byte for two options just seems wastef=
ul to
>> me, but that's probably just me. =A0:-) =A0A good option for that is to =
tell the
>> IANA that the field currently has two options ("s" and "v") but may be
>> expanded at a later time. =A0In SSH we usually carved out three options:
>> standard, vendor, and experimental. =A0For experimental, we said that if=
 you
>> come up with something new and want others to try it out (without having=
 to
>> use a single PEN [sort'a]) then have everone agree upon a value in the
>> experimental range. =A0See the last bullet in section 5.1 of RFC 4254 fo=
r an
>> example.
>>
>> Regards,
>> Chris
>>
>> On Tue, 15 Mar 2011, Gonzalo Salgueiro wrote:
>>
>> Anders -
>>
>> You are absolutely right, I did misunderstand your point the first time
>> around. I thought you were saying '001' was the Vendor-ID, when in fact =
you
>> were saying that "0001,FFFF,@<PEN>" is the Vendor-ID. Since the name in
>> front of the '@' is only restricted in the following way:
>>
>> - MUST be printable US-ASCII strings
>>
>> - MUST NOT contain an at-sign ('@', ABNF %d64), an equal-sign ('=3D', AB=
NF
>> %d61), a closing brace (']', ABNF %d93), a quote-character ('"', ABNF %d=
34),
>> whitespace, or control characters.
>>
>> it indeed means your example is a valid Vendor-ID and could cause confus=
ion.
>> While this would be very unlikely to happen in practice [I can't imagine=
 an
>> implementer intentionally doing this], it is undesired. I think this fac=
t
>> makes your original proposal that much more elegant than the existing on=
e.
>>
>> Regards,
>>
>> Gonzalo
>>
>>
>> On Mar 15, 2011, at 10:38 AM, Anders Nygren wrote:
>>
>> On Tue, Mar 15, 2011 at 12:19 AM, Gonzalo Salgueiro <gsalguei@cisco.com>
>> wrote:
>>
>> Thanks for raising your concerns Anders.
>>
>> As you know, this draft was just published today and its principal inten=
t
>>
>> was to formulate an initial solution for SIP CLF extensibility.
>>
>> A little history:
>>
>> The current proposal for Vendor-specific extensions using a Syslog-like
>>
>> approach (i.e. name@<private enterprise number>) was something proposed =
over
>>
>> email and decided at the last SIPCLF Interim meeting in January. So this
>>
>> really is a first pass at implementing vendor-specificied optional field=
s.
>>
>> That said, I'll comment inline to your points
>>
>> On Mar 14, 2011, at 10:53 PM, Anders Nygren wrote:
>>
>> Hi
>>
>> I must say that I really dislike the proposed format for vendor specific
>>
>> fields.
>>
>> Having a variable length "tag" before the length field means that it
>>
>> is necessary
>>
>> to scan the tag looking for the ',' just to find the length field.
>>
>> You make a valid point. I'd like others to weigh in here and comment on
>>
>> whether they think this is a serious performance limitation. I'll propos=
e
>>
>> this as a discussion point for the upcoming meeting in Prague. The reaso=
n
>>
>> for the variable length tag is that it is based on the SD-ID format from
>>
>> Syslog, which is variable in length (i.e. the unrestricted name before t=
he
>>
>> '@'). =A0I think using a Vendor-ID based on a PEN is common sense, so I'=
d like
>>
>> to stick with that if possible. We could decide on a fixed length name (=
or
>>
>> number to parallel the tag from the Pre-Defined Optional Fields) followe=
d by
>>
>> four byte PEN.
>>
>> There is no simple way to tell he difference between a sip-clf
>>
>> optional field and
>>
>> a vendor specific optional field. So it will always be necessary to scan=
 the
>>
>> record looking for the ',' .
>>
>> Actually looking at RFC 5424 ch 4.3.2 it looks like this would be a lega=
l
>>
>> ID, "0001,FFFF,@12345" which would be difficult to differentiate from a
>>
>> standard optional field without a lot of work.
>>
>> Remember that that this draft restricts the scope of the syntax to the 2=
nd
>>
>> format definition of SD-IDs in RFC5424. Thus, the above wouldn't be a le=
gal
>>
>> vendor-specified optional field since "0001" doesn't contain an '@', whi=
ch
>>
>> is mandatory for a Vendor-ID as defined in the draft. So there should be=
 no
>>
>> confusion there as the Vendor-ID from the vendor-specified optional fiel=
ds
>>
>> and the Tag from the pre-defined optional fields can never be the same.
>>
>>
>> I think that You did not understand the point I was trying to make.
>>
>> As I understand the specification in the 2nd format definition of SD-IDs=
 in
>>
>> RFC5424, comma "," is allowed in the name part. So
>>
>> "0001,FFFF,@<Vendor-ID>" would be a legal tag, that would be very diffic=
ult
>> to
>>
>> differentiate from a standard optional field with tag=3D"0001", length=
=3D"FFFF"
>> and
>>
>> a value starting with "@<Vendor-ID>"
>>
>> I think a better way to do this would be similar to diameter RFC3588, ch
>>
>> 4.1.
>>
>> Then we could have just one format for standard optional fields and vend=
or
>>
>> specific fields
>>
>> byte 1 =A00x09
>>
>> byte 2-5 Tag (Hex)
>>
>> byte 6-9 VendorId
>>
>> byte 10 0x2C
>>
>> byte 11-14 Length (Hex)
>>
>> byte 15 0x2C
>>
>> byte 16-.. Value (variable length)
>>
>> Where VendorId is the IANA assigned "SMI Network Management Private
>>
>> Enterprise Codes" =A0[ASSIGNNO] value.
>>
>> VendorId=3D0 is used a for the standard optional fields defined in SIP-C=
LF.
>>
>> I know that PEN =3D 0 is a Reserved value and if it is confirmed that it=
 can
>>
>> be used in this way (as apparently DIAMETER did), then I think this prop=
osal
>>
>> is very reasonable. This unifies both optional field types into a single
>>
>> seamless representation. I'll let others, like Chris Lonvick, more
>>
>> knowledgeable than I weigh in on this as well to confirm my thoughts.
>>
>> Regards,
>>
>> Gonzalo
>>
>> /Anders
>>
>> _______________________________________________
>>
>> sip-clf mailing list
>>
>> sip-clf@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>
>>
>>
>>
>>
>>
>
---559023410-1902445306-1300388879=:26318--

From eburger@standardstrack.com  Fri Mar 18 11:31:46 2011
Return-Path: <eburger@standardstrack.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 A9C333A6A29 for <sip-clf@core3.amsl.com>; Fri, 18 Mar 2011 11:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ZPWE0HKRxU3d for <sip-clf@core3.amsl.com>; Fri, 18 Mar 2011 11:31:45 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.249.249]) by core3.amsl.com (Postfix) with ESMTP id 61FE43A69B7 for <sip-clf@ietf.org>; Fri, 18 Mar 2011 11:31:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=1e+ANFixd2jDWi8zBYJVVTRybx31arV9mPV1UAl6LppQ99lttOTqBvd22gfhtLjSGIamS4MGuIl46bFakACdnV9K3AamaEzHicFrf0689ZQoHd1miDIWzvKb+wnx0SCi;
Received: from [64.134.242.62] (helo=[192.168.5.137]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Q0eQS-00006Y-Hp for sip-clf@ietf.org; Fri, 18 Mar 2011 11:29:29 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-133-43442135; protocol="application/pkcs7-signature"; micalg=sha1
Date: Fri, 18 Mar 2011 14:33:09 -0400
In-Reply-To: <7DB6DBE8-760E-4C32-B4C2-7EFD0A09FF89@cisco.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
References: <AANLkTinnyWJ1wDzZdsW9PzyO+xTSSiy_pjm+JLs9ADyi@mail.gmail.com> <41DAD933-6D4A-43EE-B817-23B6795748B8@magorcorp.com> <7DB6DBE8-760E-4C32-B4C2-7EFD0A09FF89@cisco.com>
Message-Id: <23C4D4B6-47FB-4C79-AA5B-62F160867183@standardstrack.com>
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
Subject: Re: [sip-clf] draft-ietf-sipclf-problem-statement-05 Reason-Phrase
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, 18 Mar 2011 18:31:46 -0000

--Apple-Mail-133-43442135
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Smells like an IANA registry...

On Mar 15, 2011, at 5:55 PM, Gonzalo Salgueiro wrote:

>=20
> On Mar 15, 2011, at 5:23 PM, Peter Musgrave wrote:
>=20
>> I think as a predefined option field Reason Phrase makes sense.
>>=20
>> It may be worth thinking about other optional header fields people =
might want...Refer, History-Info, Session-ID - might become a bit of a =
long list. Would this be viewed as useful?
>=20
> I had it as one of the discussion topics for Prague. I think we =
fundamentally need to decide what fields we want as Pre-defined Optional =
Fields IF that list a reasonable one. If we want to open it up (as =
Anders suggest) to ALL SIP fields, then this would likely require a =
different mechanism entirely.
>=20
> Gonzalo
>=20
>>=20
>> Peter (as individual)
>>=20
>> On 2011-03-15, at 5:10 PM, Anders Nygren wrote:
>>=20
>>> Hi
>>> The list of mandatory fields includes Status-Code but not =
Reason-Phrase.
>>> Wouldn't it be useful to have Reason-Phrase also since RFC3261
>>>=20
>>> 21.1.5 183 Session Progress
>>>=20
>>>  The 183 (Session Progress) response is used to convey information
>>>  about the progress of the call that is not otherwise classified.  =
The
>>>  Reason-Phrase, header fields, or message body MAY be used to convey
>>>  more details about the call progress.
>>>=20
>>> 21.4.1 400 Bad Request
>>>=20
>>>  The request could not be understood due to malformed syntax.  The
>>>  Reason-Phrase SHOULD identify the syntax problem in more detail, =
for
>>>  example, "Missing Call-ID header field".
>>>=20
>>> So at times Reason-Phrase gives some additional information that can =
not be
>>> obtained from just the Status-Code. Maybe as an optional field.
>>>=20
>>> /Anders
>>> _______________________________________________
>>> sip-clf mailing list
>>> sip-clf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sip-clf
>>=20
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-133-43442135
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggY6MIIFIqAD
AgECAhEAxcM7lN0zgrA71mfq+sG6xjANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMDA5MDgwMDAw
MDBaFw0xMTA5MDgyMzU5NTlaMIHhMTUwMwYDVQQLEyxDb21vZG8gVHJ1c3QgTmV0d29yayAtIFBF
UlNPTkEgTk9UIFZBTElEQVRFRDFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNl
OiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMyBDb21v
ZG8gTGltaXRlZDEUMBIGA1UEAxMLRXJpYyBCdXJnZXIxKTAnBgkqhkiG9w0BCQEWGmVidXJnZXJA
c3RhbmRhcmRzdHJhY2suY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqeauFkEq
5Pj7AIAaDRbUWIpoblTKyrjcSfXRaHvjk0jWBTsBPe6oOZjudMK0Vo9A1Sl52BixDgf1/qb2Z+PT
7M0mqSOOsSucEBid48IMvGi79xmKKAVf5jiyFNNAaTZWn76dwNLMkKd/+Ki0fn8kEbb2zG+gGKyZ
MNHiNX+GQfPpHyzo2MTwnb16lXMfGJrGv4uLZS/pY9PENdFQnwV0ASZoqX+ArtLY2xeuC+rYG9xQ
Cz7qiLbJhCJzWsEGETyHLDjE5bN4HB9DsJKtGFLQuOdTanwGigNz9cVH9pLFNQxiotavAouXgqS4
wGvcq4mGP9w9zTychoUqIKsEg9OD1wIDAQABo4ICHDCCAhgwHwYDVR0jBBgwFoAUiYJnfcSdJnAA
S7RQSHzePa4Ebn0wHQYDVR0OBBYEFAlgEOVj6Hl0La8sPRP388HEMiWvMA4GA1UdDwEB/wQEAwIF
oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB
hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0
cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwgaUGA1UdHwSBnTCBmjBMoEqgSIZGaHR0cDovL2Ny
bC5jb21vZG9jYS5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls
LmNybDBKoEigRoZEaHR0cDovL2NybC5jb21vZG8ubmV0L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0
aGVudGljYXRpb25hbmRFbWFpbC5jcmwwbAYIKwYBBQUHAQEEYDBeMDYGCCsGAQUFBzAChipodHRw
Oi8vY3J0LmNvbW9kb2NhLmNvbS9VVE5BQUFDbGllbnRDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6
Ly9vY3NwLmNvbW9kb2NhLmNvbTAlBgNVHREEHjAcgRplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNv
bTANBgkqhkiG9w0BAQUFAAOCAQEACRTppSEc5DMYn8YXcbfX36iTaNBGw1gUvTNam0U8pXH0E7H3
2d4cTq6DEMu5ifEvxMGBqhUyv0sKxQ7+UvtDwrk7Kiy2L6TUC4zNEklZbtDqY7+Wd7EQZkN4k/zx
kMLlz2VIIRL/Cg48NrBKP5bo1la78NTJx8m4+VForLseEBabxMQoWB/GOVC7WpO/+RCgd93gz6H/
RzW1hnK0Uvu5H3Kz7HEC3R1Qk/sE9nXVzTfoJOMJRnyMS5Ut61mgoWSm/kUtczAlRRYh6IBOhzAl
awoXz+yk9hMCheYRAWx0EamBBpSzvqXj0N2vXYc62v3e3ddcLZncjiB0pYIfCE3s4DGCA/8wggP7
AgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBD
aXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cu
dXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIEVtYWlsAhEAxcM7lN0zgrA71mfq+sG6xjAJBgUrDgMCGgUAoIICDzAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTAzMTgxODMzMDlaMCMGCSqGSIb3DQEJ
BDEWBBQUwvurvRSBazRSK5PlIHpbeAntCzCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBABw5Tl+MuJewvm/lU8zdQa0FyXh0seZTGNghT56RIs21JgBZ
dzg9dX8obTGzBTv7IZUnG983B2a4QoWBhnur8InkXUcRp2ONCEwWSpckTKBP0GESYb+EKEz1bXU/
0iDzvEnCoIj47pxTpL6e6mJuJyTPIgtaUp5S0ikrnaVD/cUM42DuJgmj1u8kpDtqgP+M49D32eAx
Ea4iIhB21IvjEOOqj3LYJ+JAhq/o3ppkaCKdk5NAPOpvWQgVTj0eciM83XirKuzILUN44tl4OO10
ZULs14qkctEyfKhOEpoMkULnfgGOAOpSGa7Cu9CHwgRiNeBGRnQduxW3f3GpnUinL/0AAAAAAAA=

--Apple-Mail-133-43442135--

From clonvick@cisco.com  Mon Mar 28 10:36:38 2011
Return-Path: <clonvick@cisco.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 14E6328C122 for <sip-clf@core3.amsl.com>; Mon, 28 Mar 2011 10:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.024
X-Spam-Level: 
X-Spam-Status: No, score=-110.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 6gQew0HueMaa for <sip-clf@core3.amsl.com>; Mon, 28 Mar 2011 10:36:37 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id F216F28C11C for <sip-clf@ietf.org>; Mon, 28 Mar 2011 10:36:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=clonvick@cisco.com; l=891; q=dns/txt; s=iport; t=1301333894; x=1302543494; h=date:from:to:subject:message-id:mime-version; bh=BNIpshbAmrb76f2P/6ZWbziZl5WH23COBlzWvXyaab8=; b=jm5b2y49yL3yVDahpQ3w66otWKLVKBdVfV65w33/WUCeDLknzVdZ89Rd OlJ10u8yzywcvq3jSPEWxLIchhGlHRrA55BjjCyG803TOye9yVer+1QAU IBFSg0UlUWoh2SUrohzmOAGHndtPtKf8kmLufzoeOS7//7jkfPxXaO355 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgIANvGkE2rRDoH/2dsb2JhbACYQgEBjQF3pzycDoJ8gm0EhTo
X-IronPort-AV: E=Sophos;i="4.63,256,1299456000"; d="scan'208";a="419600276"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 28 Mar 2011 17:38:13 +0000
Received: from sjc-cde-013.cisco.com (sjc-cde-013.cisco.com [171.69.29.170]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2SHcDun009308 for <sip-clf@ietf.org>; Mon, 28 Mar 2011 17:38:13 GMT
Date: Mon, 28 Mar 2011 10:38:13 -0700 (PDT)
From: Chris Lonvick <clonvick@cisco.com>
To: sip-clf@ietf.org
Message-ID: <Pine.GSO.4.63.1103261921470.11931@sjc-cde-013.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: [sip-clf] Using the PEN
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: Mon, 28 Mar 2011 17:36:38 -0000

Hi,

I ran the question of using PEN=0 and PEN=<vendor id> past a few people.

IANA did not have an opinion.

David Harrington, the author of RFC5612 thinks that it would be good.
http://www.rfc-editor.org/rfc/rfc5612.txt

The best response I got was from Dan Romascanu who wrote:
>> PENs are using in various protocols and the usage of Enterprise Numbers
>> may (at least in theory) be different from protocol to protocol, so it
>> would be best if the respective protocol documents refer explicitly how
>> 'special' values like 0 are used. True, the convention that 0 is the
>> value reserved for IETF standards is widely used (for example to
>> identify standard notifications in SMI) but as SIP-CLF defines a
>> different DML I would suggest that adopting the convention is OK, and
>> mentioning it explicitly is best.

Bert Wijnen agreed with Dan.

Thanks,
Chris


From gsalguei@cisco.com  Mon Mar 28 10:45:37 2011
Return-Path: <gsalguei@cisco.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 7A1433A6A5E for <sip-clf@core3.amsl.com>; Mon, 28 Mar 2011 10:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.386
X-Spam-Level: 
X-Spam-Status: No, score=-10.386 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 3n1B4DSGAGH6 for <sip-clf@core3.amsl.com>; Mon, 28 Mar 2011 10:45:36 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 7CCEA3A68A9 for <sip-clf@ietf.org>; Mon, 28 Mar 2011 10:45:36 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2SHlD0h026127 for <sip-clf@ietf.org>; Mon, 28 Mar 2011 13:47:13 -0400 (EDT)
Received: from rtp-gsalguei-8719.cisco.com (rtp-gsalguei-8719.cisco.com [10.116.61.58]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p2SHlCnT027344;  Mon, 28 Mar 2011 13:47:12 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-42-904684587
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <Pine.GSO.4.63.1103261921470.11931@sjc-cde-013.cisco.com>
Date: Mon, 28 Mar 2011 13:47:11 -0400
Message-Id: <DC7B9328-74FF-4DE3-8143-B0E2E760668C@cisco.com>
References: <Pine.GSO.4.63.1103261921470.11931@sjc-cde-013.cisco.com>
To: Chris Lonvick <clonvick@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] Using the PEN
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: Mon, 28 Mar 2011 17:45:37 -0000

--Apple-Mail-42-904684587
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fantastic! Thanks Chris.

We'll proceed with my proposal and be very clear as to the treatment of =
PEN, including PEN=3D0, with respect to the logging of optional fields.

Thanks again.

--Gonzalo

On Mar 28, 2011, at 1:38 PM, Chris Lonvick wrote:

> Hi,
>=20
> I ran the question of using PEN=3D0 and PEN=3D<vendor id> past a few =
people.
>=20
> IANA did not have an opinion.
>=20
> David Harrington, the author of RFC5612 thinks that it would be good.
> http://www.rfc-editor.org/rfc/rfc5612.txt
>=20
> The best response I got was from Dan Romascanu who wrote:
>>> PENs are using in various protocols and the usage of Enterprise =
Numbers
>>> may (at least in theory) be different from protocol to protocol, so =
it
>>> would be best if the respective protocol documents refer explicitly =
how
>>> 'special' values like 0 are used. True, the convention that 0 is the
>>> value reserved for IETF standards is widely used (for example to
>>> identify standard notifications in SMI) but as SIP-CLF defines a
>>> different DML I would suggest that adopting the convention is OK, =
and
>>> mentioning it explicitly is best.
>=20
> Bert Wijnen agreed with Dan.
>=20
> Thanks,
> Chris
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


--Apple-Mail-42-904684587
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Fantastic! Thanks Chris.<div><br></div><div>We'll proceed with my =
proposal and be very clear as to the treatment of PEN, including PEN=3D0, =
with respect to the logging of optional =
fields.</div><div><br></div><div>Thanks =
again.</div><div><br></div><div>--Gonzalo</div><div><br><div><div>On Mar =
28, 2011, at 1:38 PM, Chris Lonvick wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi,<br><br>I ran the question of using PEN=3D0 and =
PEN=3D&lt;vendor id&gt; past a few people.<br><br>IANA did not have an =
opinion.<br><br>David Harrington, the author of RFC5612 thinks that it =
would be good.<br><a =
href=3D"http://www.rfc-editor.org/rfc/rfc5612.txt">http://www.rfc-editor.o=
rg/rfc/rfc5612.txt</a><br><br>The best response I got was from Dan =
Romascanu who wrote:<br><blockquote type=3D"cite"><blockquote =
type=3D"cite">PENs are using in various protocols and the usage of =
Enterprise Numbers<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">may (at least in theory) be =
different from protocol to protocol, so =
it<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">would be best if the respective protocol documents refer =
explicitly how<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">'special' values like 0 are =
used. True, the convention that 0 is =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">value reserved for IETF standards is widely used (for =
example to<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">identify standard notifications =
in SMI) but as SIP-CLF defines =
a<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">different DML I would suggest that adopting the convention =
is OK, and<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">mentioning it explicitly is =
best.<br></blockquote></blockquote><br>Bert Wijnen agreed with =
Dan.<br><br>Thanks,<br>Chris<br><br>______________________________________=
_________<br>sip-clf mailing =
list<br>sip-clf@ietf.org<br>https://www.ietf.org/mailman/listinfo/sip-clf<=
br></div></blockquote></div><br></div></body></html>=

--Apple-Mail-42-904684587--
