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

vanupam commented on this pull request.



> +A <dfn title=concept-token-binding>Token Binding</dfn> is established by the user agent generating
+a public-private key-pair for the server and proving possession of the private key on every request
+to the server, as described in
+<a href="https://tools.ietf.org/id/draft-ietf-tokbind-protocol-10.xml#rfc.section.1">section 1</a>
+of the Token Binding Protocol spec.
+A <dfn title=concept-token-binding-id>Token Binding Id</dfn> is the representation of a
+<span title=concept-token-binding>Token Binding</span>, as described in
+<a href="https://tools.ietf.org/id/draft-ietf-tokbind-protocol-10.xml#rfc.section.3.2">section 3.2</a>
+of the Token Binding Protocol spec.
+
+A <dfn title=concept-token-binding-message>Token Binding Message</dfn> is transmitted by
+a user agent to a server to prove possession of
+<span title=concept-token-binding>Token Binding</span> keys.
+The value of a <span title=concept-token-binding-message>Token Binding Message</span> is specified
+in <a href="https://tools.ietf.org/id/draft-ietf-tokbind-protocol-10.xml#rfc.section.3">section 3</a>
+of the Token Binding Protocol spec.

I added a subsection to Infrastructure, and moved it to just above the HTTP subsection (since there were no subsections before that).

Reasonable?

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