diff --git a/xep-0281.xml b/xep-0281.xml
index 10bbf15c..fa871496 100644
--- a/xep-0281.xml
+++ b/xep-0281.xml
@@ -9,10 +9,10 @@
 <xep>
 <header>
   <title>DMUC1: Distributed Multi-User Chat</title>
-  <abstract>This document defines methods for distributing Multi-User Chat (MUC) rooms across multiple chat services.</abstract>
+  <abstract>This document defines methods for distributing Multi-User Chat (MUC) rooms across multiple chat services. Note: This document has been retracted by the author in favor of XEP-0289.</abstract>
   &LEGALNOTICE;
   <number>0281</number>
-  <status>Deferred</status>
+  <status>Retracted</status>
   <type>Standards Track</type>
   <sig>Standards</sig>
   <dependencies>
@@ -51,7 +51,7 @@
 
 <section1 topic='Introduction' anchor='intro'>
 
-  <p class='box'><em>This document is one of several proposals for distributing XMPP chat rooms across multiple chat services. It is expected that the various approaches will be refined and harmonized before a final protocol is developed.</em></p>
+  <p class='box'><em>Note: This document has been retracted by the author in favor of &xep0289;.</em></p>
 
   <section2 topic='Motivation' anchor='motivation'>
     <p>&xep0045; defines a full-featured technology for multi-user text conferencing in XMPP. By design, <cite>XEP-0045</cite> assumes that a conference room is hosted at a single service, which can be accessed from any point on the network. However, this assumption introduces a single point of failure for the conference room, since if occupants at a using domain lose connectivity to the hosting domain then they also lose connectivity to the room. In some deployment scenarios (and even on the open Internet) this behavior is suboptimal. Therefore, this document attempts to define a technology for distributing MUC rooms across multiple services.</p>