[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sip] INFO considered harmful



inline.

Dean Willis wrote:

Jonathan Rosenberg wrote:

Folks,

For some time, I've been complaining about the continued abuse of the INFO method for things that should be done other ways (frequently, not using sip at all). I've written up a summary of the problems and a proposed path forward. Specifically, I'd like to obsolete INFO and replace it with a spec that is approved ONLY for SIP-T.

Until the I-D appears, you can pick up a version at:

http://www.jdrosen.net/papers/draft-rosenberg-sip-info-harmful-00.txt
http://www.jdrosen.net/papers/draft-rosenberg-sip-info-harmful-00.html

Jonathan and I have had "extended discussions" on this. I'm more inclined to think that INFO needs specifications for specific usages, much as we use "events packages" for SIP Events (SUBSCRIBE, NOTIFY). In my own completely non-original way, I call these "INFO Packages".

I think that the SIP-T usage of INFO is a perfect example of an INFO package. However, I think it is NOT the only reasonable use for INFO.
Unsolicited in-dialog "stuff" is pretty darned useful. All we really need is for the usages to be differentiable, negotiable, and well-documented.
The point I was making in the draft was - why bother? INFO by itself provides nothing. If you want differentiable, negotiable and well-documented things, define them as new methods. What does INFO give you beyond that?


--
Dean
Not Speaking From The Chair.

From the stool then? ;)

-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip