idnits 2.17.1 draft-saintandre-impp-call-info-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 07, 2013) is 4036 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-09) exists of draft-ivov-xmpp-cusax-04 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Saint-Andre 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track April 07, 2013 5 Expires: October 09, 2013 7 Instant Messaging and Presence Purpose for the Call-Info Header in the 8 Session Initiation Protocol (SIP) 9 draft-saintandre-impp-call-info-01 11 Abstract 13 This document defines and registers a value of "impp" ("instant 14 messaging and presence protocol") for the "purpose" header field 15 parameter of the Call-Info header field in the Session Initiation 16 Protocol (SIP). 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on October 09, 2013. 35 Copyright Notice 37 Copyright (c) 2013 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Security Considerations . . . . . . . . . . . . . . . . . . . 2 54 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 55 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4.1. Normative References . . . . . . . . . . . . . . . . . . 3 57 4.2. Informative References . . . . . . . . . . . . . . . . . 3 58 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1. Introduction 63 To improve interoperability among real-time communication endpoints 64 that support the combined use of the Session Initiation Protocol 65 (SIP) [RFC3261] and the Extensible Messaging and Presence Protocol 66 (XMPP) [RFC6120] (so-called "CUSAX" endpoints [I-D.ivov-xmpp-cusax]), 67 it can be helpful to communicate the endpoint's SIP address over XMPP 68 and the endpoint's XMPP address over SIP to provide hints about the 69 endpoints communication capabilities. The former feature is enabled 70 by an XMPP extension protocol called Reachability Addresses 71 [XEP-0152]. As to the latter feature, discussion in the SIP 72 community led to the conclusion that it would be best to use the 73 Call-Info header [RFC3261] with a value of "impp" ("instant messaging 74 and presence protocol") for the "purpose" header field parameter. 75 This document defines and registers the "impp" value. 77 (Although CUSAX endpoints constitute the primary use case for the 78 "impp" purpose, a Uniform Resource Identifier (URI) [RFC3986] for an 79 instant messaging and presence protocol other than XMPP could be 80 included in the Call-Info header.) 82 2. Security Considerations 84 Advertising an endpoint's XMPP address over SIP could inform 85 malicious entities about an alternative attack vector. Because the 86 "purpose" header field parameter could be spoofed, the receiving 87 endpoint ought to check the value against an authoritative source 88 such as a user directory. 90 3. IANA Considerations 92 The IANA is requested to add a new predefined value "impp" for the 93 "purpose" header field parameter of the Call-Info header field, by 94 adding this RFC as a reference to the line for the header field 95 "Call-Info" and parameter name "purpose": 97 Header Field: Call-Info 98 Parameter Name: purpose 99 Predefined Values: Yes 100 Reference: [this document] 102 4. References 104 4.1. Normative References 106 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 107 A., Peterson, J., Sparks, R., Handley, M., and E. 108 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 109 June 2002. 111 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 112 Resource Identifier (URI): Generic Syntax", STD 66, RFC 113 3986, January 2005. 115 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 116 Protocol (XMPP): Core", RFC 6120, March 2011. 118 4.2. Informative References 120 [I-D.ivov-xmpp-cusax] 121 Ivov, E., Saint-Andre, P., and E. Marocco, "Combined Use 122 of the Session Initiation Protocol (SIP) and the 123 Extensible Messaging and Presence Protocol (CUSAX)", 124 draft-ivov-xmpp-cusax-04 (work in progress), April 2013. 126 [XEP-0152] 127 Saint-Andre, P. and J. Hildebrand, "Reachability 128 Addresses", XSF XEP 0152, February 2013. 130 Appendix A. Acknowledgements 132 Thanks to Keith Drage, Saul Ibarra, Emil Ivov, Cullen Jennings, Olle 133 Johanssen, Paul Kyzivat, Gonzalo Salgueiro, Dean Willis, and Dale 134 Worley for their input. Thanks to Yana Stamcheva for her helpful 135 comments and for shepherding the document. 137 Author's Address 138 Peter Saint-Andre 139 Cisco Systems, Inc. 140 1899 Wynkoop Street, Suite 600 141 Denver, CO 80202 142 USA 144 Phone: +1-303-308-3282 145 Email: psaintan@cisco.com