<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sullivan-mls-attachments" target="https://datatracker.ietf.org/doc/html/draft-sullivan-mls-attachments-00">
   <front>
      <title>Encrypted Attachments for MLS</title>
      <author initials="N." surname="Sullivan" fullname="Nick Sullivan">
         <organization>Cryptography Consulting LLC</organization>
      </author>
      <author initials="R." surname="Robert" fullname="Raphael Robert">
         <organization>Phoenix R&amp;D GmbH</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   This document defines random-access authenticated encryption of large
   write-once files for Messaging Layer Security (MLS) groups.  A file
   is encrypted so that a receiver can decrypt and authenticate any byte
   range without processing the whole file.  The encryption is SEAL-
   attachment, SEAL&#x27;s named write-once attachment scheme (raAE),
   parameterized by the AEAD and key derivation function of the group&#x27;s
   MLS cipher suite and keyed from the MLS exporter.  The encrypted
   bytes are carried by any means, and a recipient needs only a small
   reference (the object&#x27;s identifier and length, and an optional
   locator) to fetch, key, and verify the object.  MLS application
   messages cannot carry large files, and existing attachment encryption
   produces an opaque, immutable blob with no partial access.  This
   extension supplies the random-access layer those uses need.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sullivan-mls-attachments-00" />
   
</reference>
