From 1f904b69be066170883167bde5b52887d3f4ba4a Mon Sep 17 00:00:00 2001
From: Sam Whited <sam@samwhited.com>
Date: Wed, 22 Apr 2020 11:28:11 -0400
Subject: [PATCH] XEP-0389: add an IQ query for flows

---
 xep-0389.xml | 51 +++++++++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 49 insertions(+), 2 deletions(-)

diff --git a/xep-0389.xml b/xep-0389.xml
index 011c05f2..236d67a2 100644
--- a/xep-0389.xml
+++ b/xep-0389.xml
@@ -264,8 +264,55 @@
       fact by including a feature of "urn::xmpp:register:0" in response to
       &xep0030; information requests and in their &xep0115; profiles.
     </p>
-    <example caption='Disco response'><![CDATA[
-<feature var='urn:xmpp:register:0' />]]></example>
+    <example caption='Disco info response'><![CDATA[
+<query xmlns='http://jabber.org/protocol/disco#info'>
+  …
+  <feature var='urn:xmpp:register:0' />
+  …
+</query>]]></example>
+  </section2>
+  <section2 topic='Retrieving the Flows'>
+    <p>
+      To find what flows an entity provides (if any) after stream negotiation is
+      complete the requester can send an IQ of type "get" containing a
+      &lt;register&gt; or &lt;recovery&gt; element qualified by the
+      "urn:xmpp:register:0" namespace.
+    </p>
+    <p>
+      When responding to a query for registration or recovery flows the list of
+      challenges should be included just as it would be if during stream feature
+      negotiation.
+      That is, a "register" or "recovery" element containing a list of flows,
+      each with an id, containing a name and a list of challenges.
+      If an entity supports this specification but does not provide any flows
+      after stream negotiation it MUST respond with an empty list.
+    </p>
+    <example caption='Registration flows query'><![CDATA[
+<iq type='get'>
+  <register xmlns='urn:xmpp:register:0'/>
+</iq>]]></example>
+    <example caption='Registration flows results'><![CDATA[
+<iq type='result'>
+  <register xmlns='urn:xmpp:register:0'>
+    <flow id='0'>
+      <name>Verify with SMS</name>
+      <challenge type='jabber:x:data'/>
+    </flow>
+    <flow id='1'>
+      <name>Verify by Phone Call</name>
+      <challenge type='jabber:x:data'/>
+    </flow>
+    <flow id='2'>
+      <name>Verify with the web</name>
+      <challenge type='jabber:x:data'/>
+      <challenge type='jabber:x:oob'/>
+    </flow>
+  </register>
+</iq>]]></example>
+    <example caption='Empty registration flows results'><![CDATA[
+<iq type='result'>
+  <register xmlns='urn:xmpp:register:0'/>
+</iq>]]></example>
   </section2>
 </section1>
 <section1 topic='Challenges' anchor='challenge'>