idnits 2.17.1 draft-saintandre-impp-call-info-04.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 30, 2013) is 3984 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC5367' is mentioned on line 111, but not defined == Missing Reference: 'RFC6910' is mentioned on line 111, but not defined == Outdated reference: A later version (-09) exists of draft-ivov-xmpp-cusax-05 Summary: 0 errors (**), 0 flaws (~~), 4 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: Informational May 30, 2013 5 Expires: December 1, 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-04 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 December 1, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 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 This specification provides a new way to correlate otherwise possibly 95 unconnected identifiers. Because such correlations can be privacy 96 sensitive, user agents ought to provide a means for users to control 97 whether or not these values are sent. 99 3. IANA Considerations 101 This document defines and registers a new predefined value "impp" for 102 the "purpose" header field parameter of the Call-Info header field. 103 The IANA can complete this action by adding this RFC as a reference 104 to the line for the header field "Call-Info" and parameter name 105 "purpose" in the Header Field Parameters and Parameter Values section 106 of the Session Initiation Protocol (SIP) Parameters registry: 108 Header Field: Call-Info 109 Parameter Name: purpose 110 Predefined Values: Yes 111 Reference: [RFC3261][RFC5367][RFC6910][this document] 113 4. References 115 4.1. Normative References 117 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 118 A., Peterson, J., Sparks, R., Handley, M., and E. 119 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 120 June 2002. 122 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 123 Resource Identifier (URI): Generic Syntax", STD 66, 124 RFC 3986, January 2005. 126 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 127 Protocol (XMPP): Core", RFC 6120, March 2011. 129 4.2. Informative References 131 [I-D.ivov-xmpp-cusax] 132 Ivov, E., Saint-Andre, P., and E. Marocco, "Combined Use 133 of the Session Initiation Protocol (SIP) and the 134 Extensible Messaging and Presence Protocol (CUSAX)", 135 draft-ivov-xmpp-cusax-05 (work in progress), May 2013. 137 [XEP-0152] 138 Saint-Andre, P. and J. Hildebrand, "Reachability 139 Addresses", XSF XEP 0152, February 2013. 141 Appendix A. Acknowledgements 143 Thanks to Gonzalo Camarillo, Keith Drage, Saul Ibarra, Emil Ivov, 144 Cullen Jennings, Olle Johanssen, Paul Kyzivat, Gonzalo Salgueiro, 145 Dean Willis, and Dale Worley for their input. Elwyn Davies, 146 Salvatore Loreto, Glen Zorn, and Mehmet Ersue completed reviews on 147 behalf of the General Area Review Team, Applications Area 148 Directorate, Security Directorate, and Operations and Management 149 Directorate, respectively. Stephen Farrell and Pete Resnick provided 150 substantive feedback during IESG review. Thanks to Yana Stamcheva 151 for her helpful comments and for shepherding the document. 153 Author's Address 155 Peter Saint-Andre 156 Cisco Systems, Inc. 157 1899 Wynkoop Street, Suite 600 158 Denver, CO 80202 159 USA 161 Phone: +1-303-308-3282 162 Email: psaintan@cisco.com