The biggest editorial issue with this draft is the use of language that conflates requirements of the protocol, versus requirements of the specification(s) which will define it. In reality, this document should be using language that targets the protocol requirements first at foremost, maybe with suggestions on what to include in the specification as non-normative.
Reading through current HEAD of the document, I think this has been addressed. Obviously if anything else sticks out after this point in time we should be able to addresses it as needed.
The biggest editorial issue with this draft is the use of language that conflates requirements of the protocol, versus requirements of the specification(s) which will define it. In reality, this document should be using language that targets the protocol requirements first at foremost, maybe with suggestions on what to include in the specification as non-normative.