One document matched: draft-saintandre-xmpp-tls-00.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<?rfc compact="yes"?>
<?rfc iprnotified="no" ?>
<?rfc sortrefs="yes"?>
<?rfc strict="yes"?>
<?rfc symrefs="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>

<rfc category="info" docName="draft-saintandre-xmpp-tls-00" ipr="trust200902">

  <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

  <front>
    <title abbrev="XMPP TLS">Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)</title>
    <author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <street>1899 Wynkoop Street, Suite 600</street>
          <city>Denver</city>
          <region>CO</region>
          <code>80202</code>
          <country>USA</country>
        </postal>
        <phone>+1-303-308-3282</phone>
        <email>psaintan@cisco.com</email>
      </address>
    </author>
    <date day="9" month="September" year="2013"/>
    <abstract>
      <t>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.</t>
    </abstract>
  </front>

  <middle>

    <section title="Introduction" anchor='intro'>
      <t>The Extensible Messaging and Presence Protocol (XMPP) <xref target='RFC6120'/> (along with its precursor, the so-called "Jabber protocol") has used Transport Layer Security (TLS) <xref target='RFC5246'/> (along with its precursor, Secure Sockets Layer or SSL) since 1999.  Both <xref target='RFC6120'/> and its predecessor <xref target='RFC3920'/> provided recommendations regarding the use of TLS in XMPP.  Given the evolving threat model on the Internet today (see, for example, <xref target='I-D.trammell-perpass-ppa'/>), it is necessary to provide stronger recommendations (see also <xref target='I-D.sheffer-tls-bcp'/>).  This document updates <xref target='RFC6120'/>.</t>
    </section>

    <section title="Terminology" anchor="terms">
      <t>Various security-related terms are to be understood in the sense defined in <xref target="RFC4949"/>.</t>
      <t>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 <xref target='RFC2119'/>.</t>
    </section>

    <section title="Discussion Venue" anchor="discuss">
      <t>The discussion venue for this document is the mailing list of the XMPP Working Group, for which archives and subscription information can be found at <eref target='https://www.ietf.org/mailman/listinfo/xmpp'/>.</t>
    </section>

    <section title="Recommendations" anchor="rec">

      <section title="Protocol Versions" anchor="rec-versions">
        <t>XMPP implementations MUST NOT negotiate SSL version 2 <xref target='RFC6176'/>.</t>
        <t>XMPP implementations MUST NOT negotiate SSL version 3.</t>
        <t>XMPP implementations MUST support, and prefer to negotiate, TLS version 1.2 <xref target='RFC5246'/>.</t>
        <t>XMPP implementations MAY negotiate TLS version 1.1 <xref target='RFC4346'/>.</t>
        <t>XMPP implementations MAY negotiate TLS version 1.0 <xref target='RFC2246'/>.</t>
      </section>

      <section title="Ciphersuites" anchor="rec-cipher">
        <t>XMPP implementations MUST NOT negotiate RC4 ciphersuites <xref target='I-D.popov-tls-prohibiting-rc4'/>.</t>
        <t>XMPP implementations MUST NOT negotiate ciphersuites that use so-called "export-level" encryption (including 40-bit and 56-bit algorithms).</t>
        <t>XMPP implementations MUST NOT negotiate ciphersuites that use less than 128-bit algorithms.</t>
        <t>XMPP implementations SHOULD prefer ciphersuites that use 256-bit algorithms or higher.</t>
        <t>XMPP implementations MUST support, and SHOULD prefer to negotiate, ciphersuites that offer perfect forward secrecy, such as those in the "EDH", "DHE", and "ECDH" families.</t>
      </section>

    </section>

    <section title="Open Issues" anchor="open">
      <t>This document has the following open issues:</t>
      <t>
        <list style='symbols'>
          <t>Add information about the rationale for each recommendation, perhaps in an appendix.</t>
          <t>Recommend a specific ciphersuite or a small number of ciphersuites?</t>
          <t>Provide recommendations regarding key lengths?</t>
          <t>Discuss TLS compression vs. application-layer compression?</t>
        </list>
      </t>
    </section>

    <section title="IANA Considerations" anchor="iana">
      <t>This document requests no actions of the IANA.</t>
    </section>

    <section title="Security Considerations" anchor="security">
      <t>This entire document discusses security.</t>
    </section>

  </middle>

  <back>

    <references title="Normative References">

<reference anchor="RFC2119">
<front>
<title abbrev='RFC Key Words'>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='Scott Bradner'>
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass.  Ave.</street>
<street>Cambridge</street>
<street>MA 02138</street></postal>
<phone>- +1 617 495 3864</phone>
<email>sob@harvard.edu</email></address></author>
<date month='March' year='1997' />
<area>General</area>
<keyword>keyword</keyword>
<abstract>
<t>
   In many standards track documents several words are used to signify
   the requirements in the specification.  These words are often
   capitalized.  This document defines these words as they should be
   interpreted in IETF documents.  Authors who follow these guidelines
   should incorporate this phrase near the beginning of their document:

<list>
<t>
      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
      "OPTIONAL" in this document are to be interpreted as described in
      RFC 2119.
</t></list></t>
<t>
   Note that the force of these words is modified by the requirement
   level of the document in which they are used.
</t></abstract></front>
<seriesInfo name='BCP' value='14' />
<seriesInfo name='RFC' value='2119' />
<format type='TXT' octets='4723' target='ftp://ftp.isi.edu/in-notes/rfc2119.txt' />
<format type='HTML' octets='14486' target='http://xml.resource.org/public/rfc/html/rfc2119.html' />
<format type='XML' octets='5661' target='http://xml.resource.org/public/rfc/xml/rfc2119.xml' />
</reference>

<reference anchor='RFC4949'>
<front>
<title>Internet Security Glossary, Version 2</title>
<author initials='R.' surname='Shirey' fullname='R. Shirey'>
<organization /></author>
<date year='2007' month='August' />
<abstract>
<t>This Glossary provides definitions, abbreviations, and explanations of terminology for information system security.  The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026).  The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed.  This memo provides information for the Internet community.</t></abstract></front>
<seriesInfo name='RFC' value='4949' />
<format type='TXT' octets='867626' target='http://www.rfc-editor.org/rfc/rfc4949.txt' />
</reference>

<reference anchor='RFC5246'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.2</title>
<author initials='T.' surname='Dierks' fullname='T. Dierks'>
<organization /></author>
<author initials='E.' surname='Rescorla' fullname='E. Rescorla'>
<organization /></author>
<date year='2008' month='August' />
<abstract>
<t>This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol.  The TLS protocol provides communications security over the Internet.  The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='5246' />
<format type='TXT' octets='222395' target='http://www.rfc-editor.org/rfc/rfc5246.txt' />
</reference>

<reference anchor='RFC6120'>
<front>
<title>Extensible Messaging and Presence Protocol (XMPP): Core</title>
<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'>
<organization /></author>
<date year='2011' month='March' />
<abstract>
<t>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities.  This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions.  This document obsoletes RFC 3920. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='6120' />
<format type='TXT' octets='451942' target='http://www.rfc-editor.org/rfc/rfc6120.txt' />
</reference>

<reference anchor='RFC6176'>
<front>
<title>Prohibiting Secure Sockets Layer (SSL) Version 2.0</title>
<author initials='S.' surname='Turner' fullname='S. Turner'>
<organization /></author>
<author initials='T.' surname='Polk' fullname='T. Polk'>
<organization /></author>
<date year='2011' month='March' />
<abstract>
<t>This document requires that when Transport Layer Security (TLS) clients and servers establish connections, they never negotiate the use of Secure Sockets Layer (SSL) version 2.0.  This document updates the backward compatibility sections found in the Transport Layer Security (TLS). [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='6176' />
<format type='TXT' octets='7642' target='http://www.rfc-editor.org/rfc/rfc6176.txt' />
</reference>

    </references>

    <references title="Informative References">

<reference anchor='I-D.popov-tls-prohibiting-rc4'>
<front>
<title>Prohibiting RC4 Cipher Suites</title>
<author initials='A' surname='Popov' fullname='Andrey Popov'>
    <organization />
</author>
<date month='August' day='21' year='2013' />
<abstract><t>This document requires that Transport Layer Security (TLS) clients and servers never negotiate the use of RC4 cipher suites when they establish connections.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-popov-tls-prohibiting-rc4-00' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-popov-tls-prohibiting-rc4-00.txt' />
</reference>

<reference anchor='I-D.sheffer-tls-bcp'>
<front>
<title>Recommendations for Secure Use of TLS and DTLS</title>
<author initials='Y' surname='Sheffer' fullname='Yaron Sheffer'>
    <organization />
</author>
<date month='September' day='9' year='2013' />
<abstract><t>Over the last few years there have been several serious attacks on TLS, including attacks on its most commonly used ciphers and modes of operation.  This document offers recommendations on securely using the TLS and DTLS protocols, given existing standards and implementations.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-sheffer-tls-bcp-00' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-sheffer-tls-bcp-00.txt' />
</reference>

<reference anchor='I-D.trammell-perpass-ppa'>
<front>
<title>The Perfect Passive Adversary: A Threat Model for the Evaluation of Protocols under Pervasive Surveillance</title>
<author initials='B' surname='Trammell' fullname='Brian Trammell'>
    <organization />
</author>
<date month='September' day='4' year='2013' />
<abstract><t>This document elaborates a threat model for the Perfect Passive Adversary (PPA): an adversary with an interest in eavesdropping that can passively observe network traffic at every layer at every point in the network between the endpoints.  It is intended to demonstrate to protocol designers and implementors the observability and inferability of information and metainformation transported over their respective protocols, to assist in the evaluation of the performance of these protocols and the effectiveness of their protection mechanisms under pervasive passive surveillance.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-trammell-perpass-ppa-00' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-trammell-perpass-ppa-00.txt' />
</reference>

<reference anchor='RFC2246'>
<front>
<title>The TLS Protocol Version 1.0</title>
<author initials='T.' surname='Dierks' fullname='Tim Dierks'>
<organization>Certicom</organization>
<address>
<email>tdierks@certicom.com</email></address></author>
<author initials='C.' surname='Allen' fullname='Christopher Allen'>
<organization>Certicom</organization>
<address>
<email>callen@certicom.com</email></address></author>
<date year='1999' month='January' />
<abstract>
<t>This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.</t></abstract></front>
<seriesInfo name='RFC' value='2246' />
<format type='TXT' octets='170401' target='http://www.rfc-editor.org/rfc/rfc2246.txt' />
</reference>

<reference anchor='RFC3920'>
<front>
<title abbrev='XMPP Core'>Extensible Messaging and Presence Protocol (XMPP): Core</title>
<author initials='P.' surname='Saint-Andre' fullname='Peter Saint-Andre' role='editor'>
<organization>Jabber Software Foundation</organization>
<address>
<email>stpeter@jabber.org</email></address></author>
<date year='2004' month='October' />
<area>Applications</area>
<workgroup>XMPP Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>XMPP</keyword>
<keyword>Extensible Messaging and Presence Protocol</keyword>
<keyword>Jabber</keyword>
<keyword>IM</keyword>
<keyword>Instant Messaging</keyword>
<keyword>Presence</keyword>
<keyword>XML</keyword>
<keyword>Extensible Markup Language</keyword>
<abstract>
<t>This memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints.  While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779.</t></abstract></front>
<seriesInfo name='RFC' value='3920' />
<format type='TXT' octets='194313' target='http://www.rfc-editor.org/rfc/rfc3920.txt' />
<format type='HTML' octets='281359' target='http://xml.resource.org/public/rfc/html/rfc3920.html' />
<format type='XML' octets='234610' target='http://xml.resource.org/public/rfc/xml/rfc3920.xml' />
</reference>

<reference anchor='RFC4346'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.1</title>
<author initials='T.' surname='Dierks' fullname='T. Dierks'>
<organization /></author>
<author initials='E.' surname='Rescorla' fullname='E. Rescorla'>
<organization /></author>
<date year='2006' month='April' />
<abstract>
<t>This document specifies Version 1.1 of the Transport Layer Security (TLS) protocol.  The TLS protocol provides communications security over the Internet.  The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='4346' />
<format type='TXT' octets='187041' target='http://www.rfc-editor.org/rfc/rfc4346.txt' />
</reference>

    </references>
  </back>

</rfc>