Token Binding
charter-ietf-tokbind-01

[Ballot comment]
I like that you're doing this, and I like short and clear charters. Thank you.

I'm looking at these two no-particular-order goals in the charter:

5. Make the Token Binding protocol useable in combination with a variety of
application protocols.
6. Allow the negotiation of the Token Binding protocol without additional
round-trips

and I'm looking at https://tools.ietf.org/html/draft-popov-token-binding-00, which uses ALPN to accomplish these goals, which seems very reasonable.

Is there a reason the charter goals are written more broadly than the starting-point draft requires?

Would mentioning ALPN in the charter explicitly be worth doing?

[Ballot comment]

Well, nearly yes:-)

I need to check one thing with W3C (one of the drafts for this wants to
modify XMLHTTPRequest).

And there will be more to be said about how this relates to OAuth but
that will be true at all future times probably, so no big deal there:-)

Mllestones in github version were:

Milestones:
- WG document for the Token Binding Protocol v1.0.
- WG document for HTTPS Token Binding.
- Token Binding Protocol v1.0 to IESG.
- HTTPS Token Binding to IESG.