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

vanupam commented on this pull request.



> +<a for=/>Token Binding</a> sense) tells the user agent to disclose the
+<a for=/>token binding ID</a> used by the user agent for that <a for=request>origin</a>
+to the target <a for=request>origin</a>. The user agent does this while processing the
+<code>Include-Referred-Token-Binding-ID</code> header in the redirect <a for=/>response</a>
+by adding a <a for=/>referred token binding ID</a> in the <a for=/>Token Binding Message</a>
+used when the <a for=/>request</a> is sent to the target server.
+
+<h4 id=getting-token-binding-key>Getting a Token Binding Key</h4>
+
+<p>Get the <a for=/>token binding key</a> for an <a for=/>origin</a> <var>tokenBindingOrigin</var>
+and <a for=/>token binding key parameters</a> <var>tokenBindingKeyParameters</var>,
+using the user agent's <a for=/>token binding key</a> store, by running these substeps:
+
+<ol>
+ <li><p>Let <var>publicNameSuffix</var> be the public name suffix - the Effective Top-Level
+ Domain + 1 name (eTLD + 1) of <var>tokenBindingOrigin</var>'s host.

Updated.

Please let me know if I should add more detail.

-- 
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#discussion_r107315674