----- Original Message ----- From: <[EMAIL PROTECTED]> > > Hi Jung, > You are right about that. INFO should be treated just > like BYE since its a mid-dialog request. Hence it will not > be forked. > > RFC 2976 which you are referring to has been obsoleted > by draft-ietf-sip-info-method-05.txt where this is clearly > specified.
An RFC can only be obsoleted by a new RFC. The draft mentioned is the draft that was published as RFC 2976. There has not been any updates to INFO. <snip> > 4. Guidelines for extensions making use of INFO > : > : > - There is potential that INFO messages could be forked by a SIP > Proxy Server. The implications of this forking of the information > in the INFO message need to be taken into account. > > As far as I know, INFO message should be treated like BYE message. > And the RFC 2976 also says that "The signaling path for the INFO method is > the signaling path established as a result of the call setup". > The INFO message for an existing dialog, like a BYE message, would contain Route headers and a Request-URI equal to the remote target (i.e. the Contact from the request/response that established the dialog) which would prevent a proxy from forking it. _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
