Are you suggesting that the EncapulatedContentInfo with Optional Content needs a URL/URI to the DigestedData/SignedData/MACData/... and/or possibly a URL/URI to at least one potential Verification subscriber service? Are these not problems for CMS consumers now? Or, am I missing some other point?Do you have ASN.1 code envisioned for this mechanism?
Not at the moment but I can provide some.
Does the X9.95 TimeStampToken Verification protocol for each of the TSTs not address your concerns?
No. The material needed to perform the validation must come from somewhere. That somewhere has not been defined.