Re: [sip-ops] [dispatch] SIP-CLF: Results on ASCII vs. binary representation

["Vijay K. Gurbani" <[e-mail]>]

Hadriel Kaplan wrote:
> Depends on how you plan to disambiguate legal characters in the
> fields from the field separators.  In binary the length field removes
> the need for disambiguation, or a CRLF itself does it (depending on
> the format).  In ascii, if you have to escape characters, then that
> escaping and de-escaping could be a big hit.

Right; this is a nagging problem at the back of my head ever
since Dale pointed it out.  The least impacting way to deal
with this, I believe, will be not to save display-name type
of constructs but only addr-spec for URIs.  The generic-param
construct is another potential problem.  Spaces in it need
to be escaped or generic-param could be simply unallowed.  I
don't know what the right answer should be right now.

> But anyway, I think the real question that needs to be answered
> *first* is "what is the purpose of the CLF?"  What is it going to
> help admins do?  Is it for troubleshooting, or for registration audit
> logging, or for IDS systems, etc?

 From the list above, at least for troubleshooting, logging, and
IDS systems.  What I do not envision CLF being used for is
debugging (distinct from troubleshooting) and CDR.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/