> -----Original Message----- > From: sipping-bounces@xxxxxxxx [mailto:sipping-bounces@xxxxxxxx] On Behalf > Of Vijay K. Gurbani > Sent: Thursday, February 05, 2009 5:56 PM > > > > Then what is its purpose? > > It's purpose is much the same as the Apache CLF format: it is > not used as much to debug as it is used for trend analysis and > anomaly detection. I really like the idea of having a common log file format for third party tools to rely on, but even if it's just for trend analysis and anomaly detection you'd need a much larger list of fields if this is for anything but registrations. For example you'd need fields for localhost, p-asserted-id/preferred-id, local-reject-reason, diversion/hist-info, and probably some others I'm forgetting. And that really gets to the problem with these things - everyone wants something more/different. For example someone would probably want to see the Via/Record-Route list too. And that's not even covering the SDP side. Do you think the particular set you defined is necessary and sufficient? Or is this extensible somehow? -hadriel _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
