| Internet-Draft | MLS Implementations | September 2022 |
| Kohbrok & Kiefer | Expires 1 April 2023 | [Page] |
The MLS protocol is a large and complex security protocol. In this document, we provide guidance and recommendations for implementers of MLS regarding correctness, security, efficiency and robustness.¶
This note is to be removed before publishing as an RFC.¶
Discussion of this document takes place on the Messaging Layer Security Working Group mailing list (mls@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/mls/.¶
Source for this draft and an issue tracker can be found at https://github.com/kkohbrok/mls-implementation-considerations.¶
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 https://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 1 April 2023.¶
Copyright (c) 2022 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 (https://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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Implementing the specification of a complex security protocol in a correct and secure manner is a challenging task.¶
This document aims to provide guidance to implementers of the Messaging Layer Security (MLS) protocol specification [I-D.ietf-mls-protocol] in a variety of ways.¶
The goal of this document is also to extend the existing guidance given in the MLS architecture document [I-D.ietf-mls-architecture] on how to use MLS securely in a larger context.¶
Finally, this document is also meant to provide examples on how to fill several of the gaps that the protocol specification and architective document have left open, but that are likely going to be needed by a large number of MLS users.¶
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 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
TODO Security¶
This document has no IANA actions.¶
TODO acknowledge.¶