[sip-clf] optional fields in sipclf

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

From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
Date: Sun, 14 Nov 2010 14:39:47 -0500
Thread-Topic: optional fields in sipclf
Thread-Index: AcuEM7RJNpDndepsSwGi588MLdW+0w==
Message-ID: <297D265A-5CC2-4D3D-9C07-E57FDF6B0CEA@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sip-clf] optional fields in sipclf
Precedence: list

Currently the indexed-ascii format does optional fields with (in ABNF):
*(TAB tag-hex COMMA length-hex COMMA value-string)

So an example would be:
<mandatory fields>	01,07,foo.bar	02,0b,hello world

Why can't we just do:
*(SP tag-num EQUAL DQUOTE value-string DQUOTE)

so an example would be:
<mandatory fields> 1="foo.bar" 2="hello world"

That way it's easier to read, and non-existence could be 1=- and non-parse could be 1=X.

Also, the use of numbers or hex to define tags doesn't accommodate vendor-specific fields, does it?
I'll send a separate email on that.

-hadriel

[sip-clf] optional fields in sipclf Hadriel Kaplan