Instant Messaging and Presence Purpose for the Call-Info Header in the Session Initiation Protocol (SIP)
draft-saintandre-impp-call-info-00

Abstract

This document defines and registers a value of "impp" ("instant messaging and presence protocol") for the "purpose" header field parameter of the Call-Info header field in the Session Initiation Protocol (SIP).

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on September 11, 2013.

Copyright Notice

Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Definition
• 2. Security Considerations
• 3. IANA Considerations
• 4. References
• 4.1. Normative References
• 4.2. Informative References
• Appendix A. Acknowledgements
• Author's Address

1. Definition

Developers of real-time communication endpoints that implement both the Session Initiation Protocol (SIP) [RFC3261] and the Extensible Messaging and Presence Protocol (XMPP) [RFC6120] sometimes wish to communicate the endpoint's SIP address over XMPP and communicate the endpoint's XMPP address over SIP. The former feature is enabled by an XMPP extension protocol called Reachability Addresses [XEP-0152]. As to the latter feature, discussion in the SIP community led to the conclusion of using the Call-Info header [RFC3261], with a predefined value of "impp" ("instant messaging and presence protocol") for the "purpose" header. Therefore this document defines and registers the "impp" value for the "purpose" parameter.

(Although the primary use case for the "impp" purpose is dual-stack SIP/XMPP endpoints [I-D.ivov-xmpp-cusax], a Uniform Resource Identifier (URI) [RFC3986] for instant messaging and presence protocols other than XMPP could be included in the Call-Info header.)

2. Security Considerations

Advertising an endpoint's XMPP address over SIP could inform malicious entities about an alternative attack vector.

3. IANA Considerations

The IANA is requested to add a new predefined value "impp" for the "purpose" header field parameter of the Call-Info header field, by adding this RFC as a reference to the line for the header field "Call-Info" and parameter name "purpose":

  Header Field: Call-Info
  Parameter Name: purpose
  Predefined Values: yes
  Reference: [RFC3261][RFC5367][RFC XXXX]
        

4. References

4.1. Normative References

4.2. Informative References

Appendix A. Acknowledgements

Thanks to Keith Drage, Saul Ibarra, Emil Ivov, Cullen Jennings, Olle Johanssen, Paul Kyzivat, Gonzalo Salgueiro, Dean Willis, and Dale Worley for their input.

Author's Address