Re: Diagnostic idea

>> Nevertheless, I think that troubleshooting has been
>> historically of rather
>> marginal interest here, so I'm not sure if there is really an action to 
>> be
>> made.
>
> I think dealing with the operational aspects of SIP networks, especially 
> with troubleshooting them, is a topic whose time has come.  There are at 
> least 3 recent drafts introducing mechanisms to aid in troubleshooting 
> SIP.  Personally I think it's one of the next hurdles in growing SIP's 
> adoption.
>
> From a DISPATCH draft-routing-to-WG perspective, one could argue we 
> actually need a SipOps WG.

Hadriel,

I really agree with this. I'm assuming that "operational aspects of SIP 
networks" is

(1) big enough, and

(2) obvious enough

to justify requesting a traditional BOF (not sliding through DISPATCH). So, 
a couple of questions:

(1) is that OK, based on the current view of DISPATCH? or should we be 
requesting DISPATCH time in Stockholm? and

(2) do we have enough people with enough clue to propose a SIPOps BOF?

Thanks,

Spencer 


_______________________________________________
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