From d2b32e36f323b29528eab21134607b39a205f046 Mon Sep 17 00:00:00 2001 From: Rohan Mahy Date: Sun, 22 Oct 2023 14:34:59 -0700 Subject: [PATCH] Manually creating draft-mahy-kp-context-00.xml --- versioned/draft-mahy-mls-kp-context-00.xml | 289 +++++++++++++++++++++ 1 file changed, 289 insertions(+) create mode 100644 versioned/draft-mahy-mls-kp-context-00.xml diff --git a/versioned/draft-mahy-mls-kp-context-00.xml b/versioned/draft-mahy-mls-kp-context-00.xml new file mode 100644 index 0000000..c6c5466 --- /dev/null +++ b/versioned/draft-mahy-mls-kp-context-00.xml @@ -0,0 +1,289 @@ + + + + + +]> + + + + + + KeyPackage Context Extension for Message Layer Security (MLS) + + + Wire +
+ rohan.mahy@wire.com +
+ + + sec + MLS + mls extension + keypackage context + keypackage extension + + + +This document describes a Message Layer Security (MLS) KeyPackage extension +to convey a specific context or anticipated use for the KeyPackage. It is useful +when a client provides the KeyPackage out-of-band to another client, and wants +the specific KeyPackage used only in the anticipated context, for example a +specific MLS group. + + + About This Document + + Status information for this document may be found at . + + + Discussion of this document takes place on the + MLS Working Group mailing list (), + which is archived at . + Subscribe at . + + Source for this draft and an issue tracker can be found at + . + + + + + +
+ Terminology + 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 when, and only when, they +appear in all capitals, as shown here. + + +The terms MLS client, MLS group, LeafNode, GroupContext, KeyPackage, +GroupContextExtensions Proposal, Credential, CredentialType, and +RequiredCapabilities have the same meanings as in the MLS +protocol . +
+
+ Introduction + In some use cases of MLS, a client might wish to provide a KeyPackage to +another client, but communicate that the specific KeyPackage is only to be +used in a specific context, for example to join a specific MLS group. This +document describes a KeyPackage extension that can convey that context. +
+
+ Extension Description + This document specifies a KeyPackage MLS extension kp_context +of type ContextPair. The syntax is described using +the TLS Presentation Language + Each PerDomainTrustAnchor represents a specific identity domain which is +expected and authorized to participate in the MLS group. It contains the +domain name and the specific trust anchor used to validate identities for +members in that domain. + ; +} ContextPair; + +ContextPair kp_context; +]]> +
+
+ IANA Considerations + This document proposes registration of a new MLS Extension Type. + RFC EDITOR: Please replace XXXX throughout with the RFC number assigned to this document +
+ kp_context MLS Extension Type + The kp_context MLS Extension Type is used inside KeyPackage objects. It +contains a URN Anchors object representing the trust anchors which are expected +for identity validation inside the MLS group. + +
+
+ urn:ietf:mls:kp_context:group_id URN registration + +
+
+
+ Security Considerations + The Security Considerations of MLS apply. + The use of this extension may reveal the client's intentions or wishes +in an out-of-band protocol, which may have weaker privacy protections than +MLS handshake messages. +
+ + + + Normative References + + + Key words for use in RFCs to Indicate Requirement Levels + + + + 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. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. + + + + + + + + + Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words + + + + RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. + + + + + + + + + The Messaging Layer Security (MLS) Protocol + + Cisco + + + Inria & Mozilla + + + Phoenix R&D + + + Meta Platforms + + + Google + + + University of Oxford + + + + Messaging applications are increasingly making use of end-to-end security mechanisms to ensure that messages are only accessible to the communicating endpoints, and not to any servers involved in delivering messages. Establishing keys to provide such protections is challenging for group chat settings, in which more than two clients need to agree on a key but may not be online at the same time. In this document, we specify a key establishment protocol that provides efficient asynchronous group key establishment with forward secrecy (FS) and post-compromise security (PCS) for groups in size ranging from two to thousands. + + + + + + + + The Transport Layer Security (TLS) Protocol Version 1.3 + + + + This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. + This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. + + + + + + + + + + + + + +