> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean > Willis > Sent: Friday, November 21, 2008 3:45 PM > > On Nov 21, 2008, at 1:57 PM, DRAGE, Keith (Keith) wrote: > > > Well you seem to be arguing for the need for an option tag in a > > Require > > header field rather than in a Supported header field. These are a > > barrier to interoperability and therefore need to be very carefully > > considered. > > An option tag, once defined, can be used in Require, Supported (in all > requests, probe with an OPTIONS), and in RFC 3840/3841 caller > preferences/callee capabilities selective routing.
I wonder sometimes if we didn't screw up making any registered option tag automatically usable in both Supported and Require. Developers or product managers seem to not understand that putting something in Require means the call attempt will fail sometimes, and that users and operators are really really unhappy if call attempts fail. 100rel, for example, is sometimes put in Require with dire unintended consequences. -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
