Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)
RFC 7590
| Document | Type |
RFC - Proposed Standard
(June 2015; No errata)
Updates RFC 6120
Was draft-ietf-uta-xmpp (uta WG)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-saintandre-xmpp-tls | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Leif Johansson | ||
| Shepherd write-up | Show (last changed 2015-03-11) | ||
| IESG | IESG state | RFC 7590 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Stephen Farrell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) P. Saint-Andre
Request for Comments: 7590 &yet
Updates: 6120 T. Alkemade
Category: Standards Track June 2015
ISSN: 2070-1721
Use of Transport Layer Security (TLS) in the
Extensible Messaging and Presence Protocol (XMPP)
Abstract
This document provides recommendations for the use of Transport Layer
Security (TLS) in the Extensible Messaging and Presence Protocol
(XMPP). This document updates RFC 6120.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7590.
Copyright Notice
Copyright (c) 2015 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.
Saint-Andre & Alkemade Standards Track [Page 1]
RFC 7590 XMPP TLS June 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Recommendations . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Support for TLS . . . . . . . . . . . . . . . . . . . . . 3
3.2. Compression . . . . . . . . . . . . . . . . . . . . . . . 3
3.3. Session Resumption . . . . . . . . . . . . . . . . . . . 3
3.4. Authenticated Connections . . . . . . . . . . . . . . . . 4
3.5. Server Name Indication . . . . . . . . . . . . . . . . . 5
3.6. Human Factors . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Implementation Notes . . . . . . . . . . . . . . . . 9
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
The Extensible Messaging and Presence Protocol (XMPP) [RFC6120]
(along with its precursor, the so-called "Jabber protocol") has used
Transport Layer Security (TLS) [RFC5246] (along with its precursor,
Secure Sockets Layer or SSL) since 1999. Both [RFC6120] and its
predecessor [RFC3920] provided recommendations regarding the use of
TLS in XMPP. In order to address the evolving threat model on the
Internet today, this document provides stronger recommendations.
In particular, this document updates [RFC6120] by specifying that
XMPP implementations and deployments MUST follow the best current
practices documented in the "Recommendations for Secure Use of TLS
and DTLS" [RFC7525]. This includes stronger recommendations
regarding SSL/TLS protocol versions, fallback to lower versions,
TLS-layer compression, TLS session resumption, cipher suites, public
key lengths, forward secrecy, and other aspects of using TLS with
XMPP.
2. Terminology
Various security-related terms are to be understood in the sense
defined in [RFC4949].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
Saint-Andre & Alkemade Standards Track [Page 2]
RFC 7590 XMPP TLS June 2015
3. Recommendations
The best current practices documented in the "Recommendations for
Secure Use of TLS and DTLS" [RFC7525] are included here by reference.
Instead of repeating those recommendations here, this document mostly
provides supplementary information regarding secure implementation
Show full document text