Good thing I'm not done with the update :-) On Aug 20, 2008, at 12:21 PM, Paul Kyzivat wrote:
Elwell, John wrote:1. Section 6.1 includes a question whether it is OK to prohibit Send-Info/Recv-Info in re-INVITE or UPDATE, and mentions that Adam points out 3PCC needs it. I agree with Adam. 2. There is no provision for Send-Info/Recv-Info in 200/ACK (i.e.omitting from an INVITE request, in the same way that SDP offer can be omitted). It seems to me that some of the use cases that motivate INVITEwithout SDP offer could also motivate INVITE without Send-Info/Recv-Info. For example, a 3PCC make-call might need to do this.Yep. It is usually my role to remind people that it isn't done until it works with 3PCC. But thats true regardless of who does the reminding.Thanks, Paul _______________________________________________ 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
