async registration policy checking apears disallowed by 2.1.2

[robinbryce]

In 2.1.2. Signed Statement Registration

We have "The Registration Policy for the Transparency Service MUST be applied to the payload bytes, before any additional processing is performed"

This appears to rule out implementations which do async processing of registration statements.

I understood that the combined effect, and intent, of

https://www.ietf.org/archive/id/draft-ietf-scitt-architecture-06.html#name-registration 5. & 7. With the subsequent text

"A Transparency Service MUST ensure that a Signed Statement is registered before releasing its Receipt."

Was to enable the implementation to defer application of registration policies until receipt issuance.

I think, if that is consistent with the intent of the authors intent, a specific requirement along the lines of "Registration policies MUST be applied before issuing a Receipt" would be much clearer

[JAG-UK]

Does this wording actually belong in SCRAPI at all, or should it be removed because these semantics are specified in the architecture? I'm thinking delete.