Eric, > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Eric Burger > Sent: 01 August 2008 21:01 > To: SIP IETF > Subject: [Sip] INFO Issue: Info-Send Procedures > <snip/> > > Related to this is we currently explicitly disallow renegotiation at > re-INVITE and UPDATE time. Do we really want this restriction? OK > with me.
This would forbid B2BUAs that do third party call transfer, for example, renegotiating to take into account the capabilities of the new party. Whilst we may frown on 3rd party call transfer, the fact that REFER and Replaces are effectively "MAY" (i.e., support for the RFCs is optional), vendors are forced into continuing to support third party transfer. John _______________________________________________ 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
