XEP-0218: Bootstrapping Implementation of Encrypted Sessions

This document provides guidelines to client and library developers for bootstrapping implementation of the encrypted sessions technology.

WARNING: Consideration of this document has been Deferred by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended.

Document Information

Series: XEP
Number: 0218
Publisher: XMPP Standards Foundation
Status: Deferred
Type: Informational
Version: 0.1
Last Updated: 2007-05-30
Approving Body: XMPP Council
Dependencies: XMPP Core, XEP-0116, XEP-0155, XEP-0200, XEP-0201
Supersedes: None
Superseded By: None
Short Name: N/A
Wiki Page: <http://wiki.jabber.org/index.php/Bootstrapping Implementation of Encrypted Sessions (XEP-0218)>

Author Information

Legal Notices

Discussion Venue

The preferred venue for discussion of this document is the Standards discussion list: <http://mail.jabber.org/mailman/listinfo/standards>.

Errata may be sent to <editor@xmpp.org>.

Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

Conformance Terms

The following keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".

Table of Contents

1. Introduction

The XMPP Standards Foundation (XSF) [1] has defined a technology for end-to-end encryption of XMPP communications, called "Encrypted Sessions" (ESessions). This document describes ways for client and library developers to approach the task of implementing ESessions.

In essence, implementation of ESessions proceeds in two directions:

1. From the client/interface level down.
2. From the library/API level up.

If client developers implement the "frontend" specifications, they should be able to integrate the "backend" code developed by library developers, enabling the two sets of developers to "meet in the middle" and offer complete implementations.

2. Approach

When working from the client/interface level down to the library/API level, it makes sense to implement the relevant specifications in the following order:

1. Best Practices for Message Threads [2]

   This document describes what a "stanza session" is, i.e., it is defined by the life of a message thread. Clients that implement this specification are well on their way to implementing encrypted sessions, since it is necessary to have a clear session "object" in a client before implementing an encrypted version of such a session.

2. Stanza Session Negotiation [3]

   Because this document describes how to negotiate a stanza session, it is a building block for developing how to negotiate an encrypted stanza session.

3. Stanza Encryption [4]

   By hardcoding the initial parameters during an early phase of development, implementors can use this specification as a starting point for testing of encrypted sessions. A later phase would address rekeying (Section 9) and negotiation of the initial parameters (see below).

4. Simplified Encrypted Session Negotiation [5]

   This specification (to be published concurrently) defines a simple subset of the process for negotiating the initial parameters used in an encrypted session.

5. Encrypted Session Negotiation [6]

   This specification defines the "heavy lifting" involved in going from a cleartext state to an encrypted state, i.e., it specifies how to the initial parameters for an encrypted session.

6. Cryptographic Design of Encrypted Sessions [7]

   Strictly speaking, a developer does not implement this specification, since it describes the theory behind the process of upgrading from cleartext to encryption that is defined in XEP-0116. However it is useful background knowledge for developers who implement XEP-0116.

Naturally, when developing from the library/API level up to the client/interface level, the order should be (roughly) reversed.

3. Optional Add-Ons

Once a library or client has implemented the specifications listed above, it may choose to implement the following additional specifications, which supplemented the core encrypted sessions specifications.

1. Public Key Publishing [8]

   This specification defines a precondition for implementation of the specifications that follow.

2. Offline Encrypted Sessions [9]

   We should be able to encrypt so-called "offline messages" (see Best Practices for Handling Offline Messages [10]) using the same basic principles used to encrypted messages sent while online.

3. Message Archiving [11]

   This specification enables secure archiving of the messages sent and received in an encrypted session.

4. Security Considerations

Incomplete implementations of the Encrypted Sessions technology will not have the same security properties as complete implementations.

5. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [12].

6. XMPP Registrar Considerations

This document requires no interaction with the XMPP Registrar [13].

Notes

Revision History

END