Apologies for being tardy.

I reviewed the other Directorate comments and the SecADs comments. I do not really have anything of substance to add. But, I will offer my normal warning when publishing a requirements draft before you're done with the protocol - you might want to hold off on publishing this draft until the actual protocol gets done just in case you find out you can't meet you're requirements. Nothing like doing a bis to remove a requirement.

Nits:

0) s2.1.2: Contains this: "There is also the possibility of an intermediate situation ..." But, later (and earlier) I think the term “intermediate schedule” is used. Rephrasing the sentence in s2.1.2 to refer to “intermediate schedule”, I think, might help if people are searching on that term.

1) s6.2: Should "ability" be "availability" in the following: "The schedule ability could enable attackers to launch highly targeted attacks ..."