Subject: RE: [Sip] SIP INFO method - Any reason it MUST BE stateless.

From: Jonathan Rosenberg <[email-masked]>
Date: Sun, 21 Oct 2001 18:42:11 -0400

> -----Original Message-----
> From: Sarvi Shanmugham [mailto:[email-masked]]
> Sent: Tuesday, October 16, 2001 2:13 AM
> To: [email-masked]
> Cc: [email-masked]
> Subject: Re: [Sip] SIP INFO method - Any reason it MUST BE stateless.
> 
> 
> Hi Eric,
>     This is not to carry signalling information. The scenario 
> that we are
> looking at is to setup a SIP session to a media server with a 
> 2-way RTP stream
> to it.
>     SIP is used for setting up this session.
>     The INFO method would be used to carry 
> commands/information/responses
> between the applications sitting at either end of the SIP session.

INFO is not meant as a universal way to carry stuff between elements. What
you are proposing, IMHO, is to use SIP as a tunneling method for MGCP or
RTSP or something similar. I see exactly zero value in doing things like
that. They are recipes for interoperability failures of astounding
proportions, and are contrary to the design guidelines we have established
for sip:

http://search.ietf.org/internet-drafts/draft-ietf-sip-guidelines-02.txt

If you are worried about transporting such large content with sip and its
responses, this should be interpreted as a clear sign that SIP is the *WRONG
THING*.

-Jonathan R.

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

_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email-masked] for questions on current sip
Use [email-masked] for new developments on the application of sip