Re: [whatwg/fetch] Update Fetch to support Token Binding. (#325)

vanupam commented on this pull request.



> +          <span title=concept-request-current-url>current url</span>.
+
+          <p class="note no-backref">A user agent negotiates the use of Token Binding with a server
+          when it sets up a TLS connection to that server, creating a
+          <span title=concept-token-binding-id>Token Binding Id</span> at the end
+          of the negotiation. The <span title=concept-token-binding-id>Token Binding Id</span>
+          is saved and can then simply be looked up whenever needed.
+          If the user agent is unable to negotiate Token Binding with a server, it will not create
+          a <span title=concept-token-binding-id>Token Binding Id</span>.
+          If the <span title=concept-token-binding-id>Token Binding Id</span> for a server is
+          deleted by a user agent (e.g., as a result of some user action), the user agent will
+          need to re-establish a TLS connection to negotiate Token Binding and create a new
+          <span title=concept-token-binding-id>Token Binding Id</span>.
+
+          <li><p>If <var>providedTokenBindingId</var> is not null, then add a
+            <code title="">provided_token_binding</code> to <var>tokenBindingMessage</var>.

providedTokenBindingId is used to generate a provided_token_binding per the TOKBIND-PROTOCOL spec.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/325