>The Abstract should say something like: > >The purpose of the INFO request for the Session Initiation Protocol >(SIP), as described by RFC 2976, is to provide mid-session SIP User >Agent (UA)-to-SIP UA application data transport. In the >years since the introduction of the INFO request, experience with the >use of the INFO request indicates a number of problems.
Experience has also shown the opposite. And, one reason why the problems have occured is because it has not been possible to standardize the usage. >This document explains why there are INFO-based, proprietary protocols in the wild; And there we would describe the issues which have been raised with the alternative solutions. >the flaws of using INFO; and explains why it is not possible to create a >framework to rescue INFO for general purpose use. And, why is it not possible? >The INFO method was created as a general transport mechanism in SIP. >As SIP has evolved since then, new mechanisms for different usages >were created. As these mechanisms are now available, this document >formally deprecates the use of INFO for new usages beyond >the existing standardized ones (i.e., ISUP and QSIG tunnelling). I disagree to that. We are still discussing the advantages/disadvantages/issues with INFO vs other mechanisms. Regards, Christer _______________________________________________ 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
