idnits 2.17.1 draft-saintandre-impp-call-info-03.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 (May 14, 2013) is 4001 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-05 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 May 14, 2013 5 Expires: November 15, 2013 7 Instant Messaging and Presence Purpose for the Call-Info Header Field in 8 the Session Initiation Protocol (SIP) 9 draft-saintandre-impp-call-info-03 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 November 15, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 54 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 55 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 4.1. Normative References . . . . . . . . . . . . . . . . . . . 4 57 4.2. Informative References . . . . . . . . . . . . . . . . . . 4 58 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 4 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 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 field [RFC3261] with a value of "impp" ("instant 74 messaging and presence protocol") for the "purpose" header field 75 parameter. An example follows. 77 Call-Info: ;purpose=impp 79 Although CUSAX endpoints constitute the primary use case for the 80 "impp" purpose, a Uniform Resource Identifier (URI) [RFC3986] for an 81 instant messaging and presence protocol other than XMPP could be 82 included in the Call-Info header field. 84 2. Security Considerations 86 Advertising an endpoint's XMPP address over SIP could inform 87 malicious entities about an alternative attack vector. Because the 88 "purpose" header field parameter could be spoofed, the receiving 89 endpoint ought to check the value against an authoritative source 90 such as a user directory. Clients can integrity protect and encrypt 91 this header field using end-to-end mechanisms such as S/MIME or hop- 92 by-hop mechanisms such as TLS. 94 3. IANA Considerations 96 This document defines and registers a new predefined value "impp" for 97 the "purpose" header field parameter of the Call-Info header field. 98 The IANA can complete this action by adding this RFC as a reference 99 to the line for the header field "Call-Info" and parameter name 100 "purpose" in the Header Field Parameters and Parameter Values section 101 of the Session Initiation Protocol (SIP) Parameters registry: 103 Header Field: Call-Info 104 Parameter Name: purpose 105 Predefined Values: Yes 106 Reference: [this document] 108 4. References 110 4.1. Normative References 112 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 113 A., Peterson, J., Sparks, R., Handley, M., and E. 114 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 115 June 2002. 117 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 118 Resource Identifier (URI): Generic Syntax", STD 66, 119 RFC 3986, January 2005. 121 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 122 Protocol (XMPP): Core", RFC 6120, March 2011. 124 4.2. Informative References 126 [I-D.ivov-xmpp-cusax] 127 Ivov, E., Saint-Andre, P., and E. Marocco, "Combined Use 128 of the Session Initiation Protocol (SIP) and the 129 Extensible Messaging and Presence Protocol (CUSAX)", 130 draft-ivov-xmpp-cusax-05 (work in progress), May 2013. 132 [XEP-0152] 133 Saint-Andre, P. and J. Hildebrand, "Reachability 134 Addresses", XSF XEP 0152, February 2013. 136 Appendix A. Acknowledgements 138 Thanks to Gonzalo Camarillo, Keith Drage, Saul Ibarra, Emil Ivov, 139 Cullen Jennings, Olle Johanssen, Paul Kyzivat, Gonzalo Salgueiro, 140 Dean Willis, and Dale Worley for their input. Elwyn Davies, 141 Salvatore Loreto, and Glen Zorn completed reviews on behalf of the 142 General Area Review Team, Applications Area Directorate, and Security 143 Directorate, respectively. Thanks to Yana Stamcheva for her helpful 144 comments and for shepherding the document. 146 Author's Address 148 Peter Saint-Andre 149 Cisco Systems, Inc. 150 1899 Wynkoop Street, Suite 600 151 Denver, CO 80202 152 USA 154 Phone: +1-303-308-3282 155 Email: psaintan@cisco.com