Per Carl Wallace feedback:
Suggest changing the minimum number of *-collection-entries from 2 to 1 to allow for the case where normally there are several items but it is possible only one is available.

One example is setting destination-claim to EAT nonce, I can use an EAT token from an entity that thinks it is participating in a remote attestation protocol to look like it is the top-level signer of a collection.

A dedicated claim for the "binder destination" would allow for explicit participation in the binding from the top-level signer. That claim should be multi-valued if we want to support the full potential scope that destination-claim brings.

Leaving destination-claim, potentially as optional (absence of which would imply dedicated claim defined in previous paragraph), would require some fuzzy requirement that the claim "cannot be abused". This requirement might prove very difficult to automate.

EAT Collection draft, needs to have a suitable Media Type to indicate that the associated content pertains to an EAT Collection

Per Laurence Lundblade review on RATS list: "EAT collections don’t support mixed devices. It’s hard to tell right now if this will be a problem. Most folks are oriented around CBOR tokens, but JSON is very widely used."
and a suggestion to look at the Nested Token CDDL in EAT to see if that provides the appropriate generality

Conceptual Message Wrappers allow encapsulating any RATS message into a uniform, typed item, which can be easily plugged into JSON / CBOR containers.

A Collection could be a more scalable container if it allowed CMWs as its values.

Either via the signature of the token in which it's found or, if in a UCCS, by adding it into the "projection" onto the linked token.

It's obvious, but better stating this explicitly.

AR-augmented Evidence (§3.2 of AR4SI) is a structure which aggregates and binds ‘claims’ from both the Verifier and Attester. It is therefore an excellent candidate for an EAT collection.

BUG CWT placeholder present in doc (and above placeholder comment in CDDL file).
Consider resolution to change to include