quire or Proxy-Require headers. Extensions using the INFO message may need the use of these mechanisms. However, the use of Require and Proxy-Require should be avoided, if possible, in order to improve interoperability between SIP entities. 5. Security Considerations If the contents of the message body are private then end-to-end encryption of the message body can be used to prevent unauthorized access to the content. There are no other security issues specific to the INFO method. The security requirements specified in the SIP specification apply to the INFO method. Donovan Standards Track [Page 7] RFC 2976 SIP INFO Method October 2000 6. References [1] Handley, M., Schulzrinne, H., Schooler, E. and J. Rosenberg, "SIP: Session Initiation Protocol", RFC 2543, March 1999. 7. Acknowledgements The author would like to thank Matthew Cannon for his contributions to this document. In addition, the author would like to thank the members of the MMUSIC and SIP working groups, especially Jonathan Rosenberg, for comments and suggestions on how to improve the document. 8. Author's Address Steve Donovan dynamicsoft 5100 Tennyson Parkway, Suite 200 Plano, Texas 75024 E-mail: sdonovan@dynamicsoft.com Donovan Standards Track [Page 8] RFC 2976 SIP INFO Method October 2000 9. Full Copyright Statement Copyright © The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in