idnits 2.17.1 draft-saintandre-impp-call-info-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 10, 2013) is 4065 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) == Missing Reference: 'RFC5367' is mentioned on line 95, but not defined == Missing Reference: 'RFC XXXX' is mentioned on line 95, but not defined == Outdated reference: A later version (-09) exists of draft-ivov-xmpp-cusax-03 Summary: 1 error (**), 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: Standards Track March 10, 2013 5 Expires: September 11, 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-00 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 September 11, 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. Definition . . . . . . . . . . . . . . . . . . . . . . . . . 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. Definition 63 Developers of real-time communication endpoints that implement both 64 the Session Initiation Protocol (SIP) [RFC3261] and the Extensible 65 Messaging and Presence Protocol (XMPP) [RFC6120] sometimes wish to 66 communicate the endpoint's SIP address over XMPP and communicate the 67 endpoint's XMPP address over SIP. The former feature is enabled by 68 an XMPP extension protocol called Reachability Addresses [XEP-0152]. 69 As to the latter feature, discussion in the SIP community led to the 70 conclusion of using the Call-Info header [RFC3261], with a predefined 71 value of "impp" ("instant messaging and presence protocol") for the 72 "purpose" header. Therefore this document defines and registers the 73 "impp" value for the "purpose" parameter. 75 (Although the primary use case for the "impp" purpose is dual-stack 76 SIP/XMPP endpoints [I-D.ivov-xmpp-cusax], a Uniform Resource 77 Identifier (URI) [RFC3986] for instant messaging and presence 78 protocols other than XMPP could be included in the Call-Info header.) 80 2. Security Considerations 82 Advertising an endpoint's XMPP address over SIP could inform 83 malicious entities about an alternative attack vector. 85 3. IANA Considerations 87 The IANA is requested to add a new predefined value "impp" for the 88 "purpose" header field parameter of the Call-Info header field, by 89 adding this RFC as a reference to the line for the header field 90 "Call-Info" and parameter name "purpose": 92 Header Field: Call-Info 93 Parameter Name: purpose 94 Predefined Values: yes 95 Reference: [RFC3261][RFC5367][RFC XXXX] 97 4. References 99 4.1. Normative References 101 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 102 A., Peterson, J., Sparks, R., Handley, M., and E. 103 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 104 June 2002. 106 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 107 Resource Identifier (URI): Generic Syntax", STD 66, RFC 108 3986, January 2005. 110 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 111 Protocol (XMPP): Core", RFC 6120, March 2011. 113 4.2. Informative References 115 [I-D.ivov-xmpp-cusax] 116 Ivov, E., Marocco, E., and P. Saint-Andre, "Combined Use 117 of the Session Initiation Protocol (SIP) and the 118 Extensible Messaging and Presence Protocol (CUSAX)", 119 draft-ivov-xmpp-cusax-03 (work in progress), February 120 2013. 122 [XEP-0152] 123 Saint-Andre, P. and J. Hildebrand, "Reachability 124 Addresses", XSF XEP 0152, February 2013. 126 Appendix A. Acknowledgements 128 Thanks to Keith Drage, Saul Ibarra, Emil Ivov, Cullen Jennings, Olle 129 Johanssen, Paul Kyzivat, Gonzalo Salgueiro, Dean Willis, and Dale 130 Worley for their input. 132 Author's Address 134 Peter Saint-Andre 135 Cisco Systems, Inc. 136 1899 Wynkoop Street, Suite 600 137 Denver, CO 80202 138 USA 140 Phone: +1-303-308-3282 141 Email: psaintan@cisco.com