> -----Original Message----- > From: Dean Willis [mailto:[EMAIL PROTECTED] > Sent: Monday, December 01, 2008 7:42 PM > > > By detecting the legacy code using a Require option-tag, and failing the > call. > Seriously. > For a very reasonable definition of backward-compatible, that's a > backward-compatible mechanism -- it behaves predictably in the presence > of broken old crap. We can't fix the broken old crap. All we can do is > detect its presence, and work within its limitations if required.
I am considering contacting the authorities to come find you. Because you have either gone insane, or your email client has been hijacked. :) Seriously - you expect us to put in a Require header option-tag when multi-part mime is used, so it can fail against every SIP device that is deployed on the planet?? At that point, I suggest you just change the SIP version number to a new value instead. -hadriel _______________________________________________ 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
