I like the idea of being clear where SIP INFO belongs (arguably only for use with SIP-T) and then having a BCP which identifies common places where SIP INFO is being used today, and then references the preferred practice (typically not using SIP INFO) or work in progress (for example, the mediactrl work) which will result in new practices.
The problem from a manufacturer's standpoint is that customers have existing products (for example, gateways) that use SIP INFO for DTMF passage and they insist on having compatibility with these bad practices built into other products, thus perpetuating the cycle of bad practice. A BCP might at least point the preferred way out of this mess. James _______________________________________________ Sip mailing list https://www1.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
