Browse Source

Publish SASL2 and IBR2 as XEP-0388 and XEP-0389

Sam Whited 2 years ago
parent
commit
1b091c3c69
3 changed files with 36 additions and 17 deletions
  1. 22
    12
      xep-0388.xml
  2. 12
    5
      xep-0389.xml
  3. 2
    0
      xep.ent

inbox/sasl2.xml → xep-0388.xml View File

@@ -9,8 +9,8 @@
9 9
   <title>Extensible SASL Profile</title>
10 10
   <abstract>This document describes a replacement for the SASL profile documented in RFC 6120 which allows for greater extensibility.</abstract>
11 11
   &LEGALNOTICE;
12
-  <number>XXXX</number>
13
-  <status>ProtoXEP</status>
12
+  <number>0388</number>
13
+  <status>Experimental</status>
14 14
   <type>Standards Track</type>
15 15
   <sig>Standards</sig>
16 16
   <dependencies>
@@ -20,6 +20,16 @@
20 20
   <supersededby/>
21 21
   <shortname>sasl2</shortname>
22 22
   &dcridland;
23
+  <revision>
24
+    <version>0.1.0</version>
25
+    <date>2017-03-16</date>
26
+    <initials>XEP Editor (ssw)</initials>
27
+    <remark>
28
+      <ul>
29
+        <li>Move to experimental.</li>
30
+      </ul>
31
+    </remark>
32
+  </revision>
23 33
   <revision>
24 34
     <version>0.0.1</version>
25 35
     <date>2017-02-07</date>
@@ -62,10 +72,10 @@
62 72
     <p>Clients, upon observing this stream feature, initiate the authentication by the use of the &lt;authenticate/> top-level element, within the same namespace. The nature of this element is to inform the server about properties of the final stream state, as well as initiate authentication itself. To achieve the latter, it has a single mandatory attribute of "mechanism", with a string value of a mechanism name offered by the Server in the stream feature, and an optional child element of &lt;initial-response/>, containing a base64-encoded SASL Initial Response.</p>
63 73
     <p>On subsequent connections, if a Client has previously cache the stream feature, the Client MAY choose to send it before seeing the stream features - sending it "pipelined" with the Stream Open tag for example.</p>
64 74
     <example caption="An authentication request"><![CDATA[
65
-    <authenticate xmlns='urn:xmpp:sasl:0' mechanism="BLURDLYBLOOP">
66
-      <initial-response>SW1wcm92ZWQgZW5jYXNwdWxhdGlvbiBvZiBvcHRpb25hbCBTQVNMLUlSIGRhdGE=</initial-response>
67
-    </authenticate>
68
-    ]]>
75
+<authenticate xmlns='urn:xmpp:sasl:0' mechanism="BLURDLYBLOOP">
76
+  <initial-response>SW1wcm92ZWQgZW5jYXNwdWxhdGlvbiBvZiBvcHRpb25hbCBTQVNMLUlSIGRhdGE=</initial-response>
77
+</authenticate>
78
+]]>
69 79
     </example>
70 80
     <p>In order to provide support for other desired stream states beyond authentication, additional child elements are used. For example, a hypothetical XEP-0198 session resumption element might be included, and/or Resource Binding requests.</p>
71 81
     <example caption="An authentication request with a (hypothetical) bind request"><![CDATA[
@@ -90,7 +100,7 @@
90 100
 <response xmlns='urn:xmpp:sasl:0'>
91 101
   QmFzZSA2NCBlbmNvZGVkIFNBU0wgcmVzcG9uc2UgZGF0YQ==
92 102
 </response>
93
-    ]]>
103
+]]>
94 104
     </example>
95 105
   </section2>
96 106
   <section2 topic="During Authentication">
@@ -108,7 +118,7 @@
108 118
   </success-data>
109 119
   <authorization-identifier>juliet@montague.example/Balcony/a987dsh9a87sdh</authorization-identifier>
110 120
 </success>
111
-      ]]></example>
121
+]]></example>
112 122
       <p>Other extension elements MAY also be contained by the &lt;success/> element.</p>
113 123
       <example caption="Successful re-authentication and resumption"><![CDATA[
114 124
 <success xmlns='urn:xmpp:sasl:0'>
@@ -118,7 +128,7 @@
118 128
   <authorization-identifier>juliet@montague.example/Balcony/a987dsh9a87sdh</authorization-identifier>
119 129
   <sm:resumed xmlns='urn:xmpp:sm:3:example' h='345' previd='124'/>
120 130
 </success>
121
-      ]]></example>
131
+]]></example>
122 132
       <p>Any security layer negotiated SHALL take effect after the ">" octet of the closing tag (ie, immediately after "&lt;/success>").</p>
123 133
     </section3>
124 134
     <section3 topic="Failure">
@@ -129,7 +139,7 @@
129 139
   <optional-application-specific xmlns='urn:something:else'/>
130 140
   <text>This is a terrible example.</text>
131 141
 </failure>
132
-    ]]></example>
142
+]]></example>
133 143
     </section3>
134 144
     <section3 topic="Continue" anchor="continue">
135 145
       <p>A &lt;continue/> element is used to indicate that while the SASL exchange was successful, it is insufficient to allow authentication at this time.</p>
@@ -147,13 +157,13 @@
147 157
   <mechanisms>
148 158
   <text>This account requires 2FA</text>
149 159
 </continue>
150
-      ]]></example>
160
+]]></example>
151 161
       <p>Clients respond with a &lt;next-authenticate/> element, which has a single mandatory attribute of "mechanism", containing the selected mechanism name, and contains an OPTIONAL base64 encoded initial response.</p>
152 162
       <example caption="Client Continues"><![CDATA[
153 163
 <next-authenticate xmlns='urn:xmpp:sasl' mechanism='TOTP-EXAMPLE'>
154 164
   MkZBIG9yIHBhc3N3b3JkIGNoYW5nZSBvciBzb21ldGhpbmc=
155 165
 </next-authenticate>
156
-      ]]></example>
166
+]]></example>
157 167
     </section3>
158 168
   </section2>
159 169
 </section1>

inbox/ibr2.xml → xep-0389.xml View File

@@ -17,8 +17,8 @@
17 17
     recovery.
18 18
   </abstract>
19 19
   &LEGALNOTICE;
20
-  <number>xxxx</number>
21
-  <status>ProtoXEP</status>
20
+  <number>0389</number>
21
+  <status>Experimental</status>
22 22
   <type>Standards Track</type>
23 23
   <sig>Standards</sig>
24 24
   <approver>Council</approver>
@@ -31,6 +31,16 @@
31 31
   <supersededby/>
32 32
   <shortname>ibr2</shortname>
33 33
   &sam;
34
+  <revision>
35
+    <version>0.1.0</version>
36
+    <date>2017-03-16</date>
37
+    <initials>XEP Editor (ssw)</initials>
38
+    <remark>
39
+      <ul>
40
+        <li>Move to experimental.</li>
41
+      </ul>
42
+    </remark>
43
+  </revision>
34 44
   <revision>
35 45
     <version>0.0.2</version>
36 46
     <date>2017-02-15</date>
@@ -370,7 +380,4 @@
370 380
     &NSVER;
371 381
   </section2>
372 382
 </section1>
373
-<section1 topic='XML Schema' anchor='schema'>
374
-  <p>TODO before advancing to Draft.</p>
375
-</section1>
376 383
 </xep>

+ 2
- 0
xep.ent View File

@@ -1443,3 +1443,5 @@ IANA Service Location Protocol, Version 2 (SLPv2) Templates</link></span> <note>
1443 1443
 <!ENTITY xep0385 "<span class='ref'><link url='https://xmpp.org/extensions/xep-0385.html'>Stateless Inline Media Sharing (XEP-0385)</link></span> <note>XEP-0385: Stateless Inline Media Sharing (SIMS) &lt;<link url='https://xmpp.org/extensions/xep-0385.html'>https://xmpp.org/extensions/xep-0385.html</link>&gt;.</note>" >
1444 1444
 <!ENTITY xep0386 "<span class='ref'><link url='https://xmpp.org/extensions/xep-0386.html'>Bind 2.0 (XEP-0386)</link></span> <note>XEP-0386: Bind 2.0 &lt;<link url='https://xmpp.org/extensions/xep-0386.html'>https://xmpp.org/extensions/xep-0386.html</link>&gt;.</note>" >
1445 1445
 <!ENTITY xep0387 "<span class='ref'><link url='https://xmpp.org/extensions/xep-0387.html'>XMPP Compliance Suites 2017 (XEP-0387)</link></span> <note>XEP-0387: XMPP Compliance Suites 2017 &lt;<link url='https://xmpp.org/extensions/xep-0387.html'>https://xmpp.org/extensions/xep-0387.html</link>&gt;.</note>" >
1446
+<!ENTITY xep0388 "<span class='ref'><link url='https://xmpp.org/extensions/xep-0388.html'>Extensible SASL Profile (XEP-0388)</link></span> <note>XEP-0388: Extensible SASL Profile &lt;<link url='https://xmpp.org/extensions/xep-0388.html'>https://xmpp.org/extensions/xep-0388.html</link>&gt;.</note>" >
1447
+<!ENTITY xep0389 "<span class='ref'><link url='https://xmpp.org/extensions/xep-0389.html'>Extensible In-Band Registration (XEP-0389)</link></span> <note>XEP-0389: Extensible In-Band Registration &lt;<link url='https://xmpp.org/extensions/xep-0389.html'>https://xmpp.org/extensions/xep-0389.html</link>&gt;.</note>" >

Loading…
Cancel
Save