I was thinking the same thing. Dealing with this in the context of
"features" that use it has some promise of at least demonstrating the
problems with existing approaches to those that matter.
Paul
Spencer Dawkins wrote:
I spoke at the mike a minute ago about having this draft done in SIP,
and then Rohan suggested that BLISS would be the right place to do the
work. I would be OK with that, too, if others see it the same way.
Dean called the question as "do something IN THIS WG", which is fair
(because that's the WG he chairs), but I would support "doing something
IN THE RIGHT WG", if the chairs and ADs think there's a better home for
the work.
Pointing to a MEDIACTRL draft is not the right thing to do, and pointing
to a long-expired draft that people may or may not have agreed with at
the time is even worse.
Spencer
I finally got to look at draft-burger-sip-info-00. I like what I see.
I did
notice some nits, and am willing to provide a more formal review, but
I support adoption of this draft as a WG deliverable, even in its
current form.
You may have noticed that the MEDIACTRL WG editors were forced to
discuss INFO in their specifications, because we currently have one
draft providing guidance on INFO that people seem to generally agree
with, but it expired years ago. I
Thanks, Eric, for taking this on.
Spencer
_______________________________________________
Sip mailing list https://www1.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
_______________________________________________
Sip mailing list https://www1.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
