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

I'm going to respond to some of your comments in a new comment since collapsed threads are not great:

* How is an OAuth token stored by the user agent?
* If token binding is on for a connection, *every* request will include a header automatically? If so, I guess you don't need a new pool then indeed.
* Putting information on HTTP/2 coalescing in connections is fine, not sure how much detail we need.
* Instead of "eTLD" you want to use "registrable domain", just like HTML does. eTLD is obsolete terminology as far as I'm aware.

It would also help if you could select the checkbox in the sidebar that allows me to push to your branch. That way I can help clean things up.

Next steps:

1. I'd like to see another review from @mikewest. Maybe @equalsJeffH can help review too since I saw his name on the RFCs.
2. It would be good to see the tests before doing the final detailed review and cleanup. So maybe that's a good place to focus on now.

-- 
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#issuecomment-288327216