<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ralston-mimi-protocol" target="https://datatracker.ietf.org/doc/html/draft-ralston-mimi-protocol-01">
   <front>
      <title>More Instant Messaging Interoperability (MIMI) using HTTPS and MLS</title>
      <author initials="T." surname="Ralston" fullname="Travis Ralston">
         <organization>The Matrix.org Foundation C.I.C.</organization>
      </author>
      <author initials="K." surname="Kohbrok" fullname="Konrad Kohbrok">
         <organization>Phoenix R&amp;D</organization>
      </author>
      <author initials="R." surname="Robert" fullname="Raphael Robert">
         <organization>Phoenix R&amp;D</organization>
      </author>
      <author initials="M." surname="Hodgson" fullname="Matthew Hodgson">
         <organization>The Matrix.org Foundation C.I.C.</organization>
      </author>
      <date month="November" day="6" year="2023" />
      <abstract>
	 <t>   This document specifies the More Instant Messaging Interoperability
   (MIMI) protocol, which allows users of different messaging providers
   to share membership in rooms and send messages to one-another.

   More specifically, the MIMI protocol defines message formats and
   conventions that allows the servers of different providers to
   interoperate, leaving the provider-internal client-server
   communication up to the provider.

   To ensure that communications between users are confidential and
   authentic, the MIMI protocol relies on MLS ([RFC9420], through the
   MIMI DS protocol [I-D.robert-mimi-delivery-service]) to protect
   messages end-to-end.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ralston-mimi-protocol-01" />
   
</reference>
