Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)
draft-ietf-uta-xmpp-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07

Network Working Group                                     P. Saint-Andre
Internet-Draft                                                      &yet
Updates: 6120 (if approved)                                  T. Alkemade
Intended status: Standards Track
Expires: July 27, 2015                                  January 23, 2015

 Use of Transport Layer Security (TLS) in the Extensible Messaging and
                        Presence Protocol (XMPP)
                         draft-ietf-uta-xmpp-05

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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 27, 2015.

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    Expires July 27, 2015                 [Page 1]
Internet-Draft                  XMPP TLS                    January 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 . . . . . . . . . . . . . . . .   3
     3.5.  Unauthenticated Connections . . . . . . . . . . . . . . .   4
     3.6.  Server Name Indication  . . . . . . . . . . . . . . . . .   4
     3.7.  Human Factors . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Implementation Notes . . . . . . . . . . . . . . . .   7
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

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.

      NOTE: Unless explicitly noted otherwise, all of the
      recommendations specified in [I-D.ietf-uta-tls-bcp] apply to XMPP.
      In the main, this document merely provides supplementary
      information; those who implement and deploy XMPP technologies are
      expected to follow the recommendations of [I-D.ietf-uta-tls-bcp].

   This document updates [RFC6120].

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    Expires July 27, 2015                 [Page 2]
Internet-Draft                  XMPP TLS                    January 2015

3.  Recommendations

3.1.  Support for TLS