> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Dean Willis
>
> The problem that I'm trying to solve is making the task space
> manageable.
> The first thing is to distribute the chair load.

Obviously splitting/spawning WG's will do that, but I thought there was an AD 
resource contention issue - if we had more WG meeting slots then neither of our 
AD's could be in some meeting or other.  Is that not one of the issues?  It was 
the response I got when I and others suggested SIP Security topics 
(Identity/Privacy/SIPS/Certs/etc.) should be split into a separate WG a while 
back.

There was also some concern over not having any more RAI time slots anyway, but 
I think that's a red herring and overlapping some RAI WG meeting times is 
reasonable for certain topics.


> I think developing a SIP extension should be a Big Thing. If it's
> important enough to develop a SIP extension for, it is probably
> important enough to charter a working group to develop that extension.
> It's a Really Bad Idea to have a standing working group that sits
> around and develops SIP extensions. All that gets us is a whole lot of
> extensions. It doesn't get us any closer to a draft standard.

I agree with you in principle, but I doubt it's possible in practice.  There's 
some fine line there, because if you don't address an issue/need multiple 
people have, then they just go solve it in a proprietary fashion independently 
and interop still sucks.  One problem is we don't have a single cohesive 
"group" view and use of SIP, so we're left with the shotgun extensions 
approach, seeing which ones will stick.  I can't recall another successful 
protocol this complicated that didn't have one or two dominant vendors, which 
is a huge disadvantage in some ways.  It's both a blessing and a curse.

-hadriel


_______________________________________________
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

Reply via email to