Re: SIP Tracing Facility

Eric Burger wrote:
> Wouldn't SIP-CLF be a better way to go?

Hadriel Kaplan wrote:
> Yes that's what I was thinking too - for basic connectivity check
> type things, do SIP ping/traceroute.  To troubleshoot actual proxy
> and UA behavior issues, retargeting issues, perform any type of
> root-cause, etc., you need logs and there's just no getting away from
> that.  And only the authoritative administrator of each SIP device
> can (and *should*) be able to get such info.
> 
> The real question is whether we can (or could) provide standardized
> ways of helping admin's get the info they need. And I think that is
> actually a really good topic for a BOF, or at least a discussion on
> RAI-DISPATCH.

Funny you should mention a BoF.  Eric has also suggested that we
hold a Bar BoF to discuss sipping-clf.

I am modifying sipping-clf based on Dale's extensive comments
from the last round and from other comments received.  It
will be submitted before the Monday deadline and we can think
of holding at least a Bar BoF on this.

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/
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip