[sip-clf] Vendor-specific fields in sipclf

Hadriel Kaplan <HKaplan@acmepacket.com> Sun, 14 November 2010 19:50 UTC

Return-Path: <HKaplan@acmepacket.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 C89393A6B75 for <sip-clf@core3.amsl.com>; Sun, 14 Nov 2010 11:50:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599]
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 65ASfnndGYKy for <sip-clf@core3.amsl.com>; Sun, 14 Nov 2010 11:50:31 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id F1E723A6AB7 for <sip-clf@ietf.org>; Sun, 14 Nov 2010 11:50:30 -0800 (PST)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 14 Nov 2010 14:51:09 -0500
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Sun, 14 Nov 2010 14:51:09 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Date: Sun, 14 Nov 2010 14:50:36 -0500
Thread-Topic: Vendor-specific fields in sipclf
Thread-Index: AcuENUgUyVkIh5OPSz+EfVc/jagf8A==
Message-ID: <20D456F6-C106-49BF-8095-B49E41889BB9@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sip-clf] Vendor-specific fields in sipclf
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Nov 2010 19:50:31 -0000

I think people will want vendor-specific fields in sipclf.

Currently the indexed-ascii draft doesn't define how this would work, afaict.  It defines a syntax for optional fields which are well-known/pre-defined, using a hex number for the tag name.

Regardless of whether it's a hex or integer representation, the number isn't scoped to any namespace.  That means if we define tag names 01-03 today, and a vendor uses 04 for their own, we'll collide with it if we later define one for 04.

One obvious way to handle this is to put an enterprise number before the tag name to scope it.  So an Asterix sipclf could be:
<mandatory fields> 2="Alice" 22736.1="foo" 22736.2="bar"

-hadriel