Re: [Unbearable] WGLC 3 on core documents

[Martin Thomson <[e-mail]>]

> I was only including a list since the current structure of a
> TokenBindingMessage allows for multiple referred TBIDs. I wasn't
> trying to change how a redirect chain would work. If we change TBPROTO
> to have signature-less referred token bindings, I think the
> TokenBindingMessage would to change to one of the following:

I would have thought that you would instead make the message contents
dependent on the type.  That would be consistent with the needs of any
future addition of attestations, which have yet another format.

As I mentioned in my review, I would also prefer to see the entire
contents of the message signed.  Thus:

struct {
  TokenBindingType type;
  TokenBindingContent content<1..2^16-1>;
  opaque signature<1..2^16-1>;
} TokenBindingMessage;

The signature would cover type, the content length and the content in
an ideal situation.

And then you can define per-type content, which for a regular message
is just one TBID, or, for a referred TB, two (or many, still can't
grok the use case for that - AND or OR?).