Add files via upload

Author: kmonsen

spec.bs

@@ -274,19 +274,20 @@ The <dfn>session credential</dfn> is a [=struct=] with the following
   1. Let |header name| be "<code>Sec-Session-Challenge</code>".
   1. Let |challenge list| be the result of executing <a>get a structured
     field value</a> given |header name| and "list" from |response|’s
-    [=response/header list=]. <a>parsing structured fields</a>
+    [=response/header list=].
   1. [=list/For each=] |challenge entry| of |challenge list|:
     1. Parse |challenge entry| according to <a>parsing structured fields</a>.
     1. If the type of |challenge entry| is not string [=iteration/continue=].
     1. Let |challenge| be the parsed item.
     1. Let |session id| be null.
-    1. If params["id"] exists and is a string, Set |session id| to params["id"]
+    1. If params["id"] exists and is a string, Set |session id| to params["id"].
     1. If [=response/status=] is 401, resend this request as is with updated
-      |challenge| in [=DBSC proof=]
+      |challenge| in [=DBSC proof=].
     1. Otherwise:
-      1. If |session id| is null, [=iteration/continue=]
+      1. If |session id| is null, [=iteration/continue=].
       1. Identify session as described in [=identify a session=] given
         |response| and |session id| and store as |session object|.
+      1. If |session object| is null, [=iteration/continue=].
       1. Store |challenge| in |session object| to be used next time a
         [=DBSC proof=] is to be sent from this [=device bound session=].
 </div>
@@ -306,17 +307,25 @@ parsing the registration structured header defined in
     field value</a> given |header name| and "list" from |response|’s
     [=response/header list=].
   1. [=list/For each=] |registration entry|, |params| → |registration list|:
-    1. Parse |registration entry| as an innner list. Let |algorithm list| be a
-      list of tokens from the inner list where only algorithms supported on this
-      client should be added. If this list is empty return failure.
-    1. If |params|["path"] exists and is a string let |path| be |params|["path"]
-    1. Otherwise return failure.
-    1. Let |challenge| be null and Let |authorization| be null.
-    1. If |params|["challenge"] exists and is a string Set |challenge| to
-      |params|["challenge"].
+    1. Parse |registration entry| according to <a>parsing structured fields</a>.
+    1. If |registration entry| is not an <a>sf-inner-list</a>,
+      [=iteration/continue=].
+    1. Let |algorithm list| be an empty [=list=].
+    1. [=list/For each=] |algorithm| → |registration entry|
+      1. If |algorithm| is not a <a>sf-token</a>, [=iteration/continue=].
+      1. If |algorithm| represents a crypto algorithm supported in
+        [:Sec-Session-Registration:], and is supported on this client, add
+        |algorithm| to |algorithm list|
+    1. If |algorithm list| is empty, [=iteration/continue=].
+    1. If |params|["path"] does not exist, or is not of type <a>sf-string</a>,
+      [=iteration/continue=].
+    1. Let |path| be |params|["path"].
+    1. Let |challenge| be null, and Let |authorization| be null.
+    1. If |params|["challenge"] exists and is of type <a>sf-string</a>
+      Set |challenge| to |params|["challenge"].
     1. If |params|["authorization"] exists and is a string Set |authorization|
       to |params|["authorization"].
-    1. Call [[#algo-session-request]] with |registration list|, |path|,
+    1. Call [[#algo-session-request]] with |algorithm list|, |path|,
       |challenge| and |authorization| parameters.
 </div>
 
@@ -343,12 +352,13 @@ MUST be a <a>sf-token</a> representing a supported algorithm (ES256, RS256).
 Only these two values are currently supported.
 
 The following parameters are defined:
+- A parameter whose key is "path", and whose value is a String (Section 3.3.3 of
+  [[RFC8941]]), conveying the path to the registration endpoint. This may be
+  relative to the current [=url=], or a full [=url=]. Entries without this
+  parameter will be ignored in [=algo-create-session=].
 - A parameter whose key is "challenge", and whose value is a String (Section 
   3.3.3 of [[RFC8941]]), conveying the challenge to be used in the session
   registration.
-- A parameter whose key is "path", and whose value is a String (Section 3.3.3 of
-  [[RFC8941]]), conveying the path to the registration endpoint. This may be
-  relative to the current [=url=], or a full [=url=].
 - A parameter whose key is "authorization", and whose value is a String (Section
   3.3.3 of [[RFC8941]]), this parameter will be copied into the registration
   JWT.