From 4bc357a0ad75f5282a9e43b8ffbf71f6b644784a Mon Sep 17 00:00:00 2001
From: Georg Lukas <georg@op-co.de>
Date: Tue, 15 Jan 2019 16:48:33 +0100
Subject: [PATCH] XEP-0410: advertise self-ping optimization

---
 xep-0410.xml | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/xep-0410.xml b/xep-0410.xml
index 2c875d03..b9d368bc 100644
--- a/xep-0410.xml
+++ b/xep-0410.xml
@@ -174,7 +174,19 @@
       ping request might never be responded to.</p>
     <p>Therefore, a MUC service supporting this protocol may directly respond
       to a participant's Ping request to the participant's own nickname, as
-      opposed to routing it to any of the participant's clients.</p>
+      opposed to routing it to any of the participant's clients. A service
+      implementing this behavior needs to advertise the
+      <tt>self-ping-optimization</tt> feature in the &xep0030; response on
+      the individual MUC room JIDs.</p>
+<example caption='MUC Service Advertises Self-Ping Optimization'><![CDATA[
+<iq from='darkcave@chat.shakespeare.lit'
+    type='result'>
+  <query xmlns='http://jabber.org/protocol/disco#info'>
+    <!-- ... -->
+    <feature var='http://jabber.org/protocol/muc#self-ping-optimization'/>
+  </query>
+</iq>
+]]></example>
   </section2>
 </section1>
 <section1 topic='Implementation Notes' anchor='impl'>