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

> +              Token Binding Id.
> +            <li><p>If <var>referredTokenBindingId</var> is different from
> +              <var>providedTokenBindingId</var>, then add <var>referredTokenBindingId</var> as a
> +              <code title="">referred_token_binding</code> to <var>tokenBindingMessage</var>.
> +          </ol>
> +
> +          <li><p>If <var>tokenBindingMessage</var> is not <var>null</var>, append a
> +            <code title="">Sec-Token-Binding</code> header to <var>httpRequest</var>'s
> +            <span title=concept-request-header-list>header list</span>.
> +            <p>The value of the <code title="">Sec-Token-Binding</code> header is a
> +            <var>Token Binding Message</var> as specified in
> +            <a href="https://tools.ietf.org/id/draft-ietf-tokbind-https-03.xml#rfc.section.3">section 2</a>
> +            of the Token Binding over HTTP spec.
> +            The value of a Token Binding Message is specified in
> +            <a href="https://tools.ietf.org/id/draft-ietf-tokbind-protocol-06.xml#rfc.section.3">section 3</a>
> +            of the Token Binding Protocol spec.

This uses various different ways to refer to "token binding message". Are they all supposed to be the same variable?

---
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/files/3c6e385c02263aa186eef6eb4243f51ea5c706cc#r68724399