Re: [Sipping] Alternate CLF syntax proposal

I might not understand everything that is possible with pcap but it  
seems to me that the problem with PCAP is that it generally saves the  
whole SIP message if you want to get all the headers - Say for example  
an operator wants to log who sent INVITES to what what numbers and  
when the correlated BYE happened so  that they can debug stuff later.  
But they do not want to capture the IP addresses of the UAs because if  
they save them then they have to respond to court orders to provide  
the logs with IP in them which is just a huge pain for with the  
operator and does not provide any revenue. The other issue is that  
logging the complete messages is often just too much data.

I like the proposal - mostly I just want something that works in high  
performance systems.

Cullen in my individual contributor role.

On Mar 29, 2009, at 1:35 PM, Jiri Kuthan wrote:

> Theo Zourzouvillys wrote:
>> On Thu, Mar 26, 2009 at 4:36 PM, Jason Fischl  
>> <jason.fischl@gmail.com> wrote:
>>> I quite like this scheme. It is very simple to generate and parse  
>>> and will
>>> be blazingly fast. It would also be very simple to create a  
>>> utility to
>>> generate "human-readable" versions from it which would address that
>>> particular concern.
>> I also really like Adam's binary proposal
>
> Why aren't we happy then just with PCAP -- that's a de-facto standard.
>
> -jiri
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP