Avoid passive voice in message requirements

[mnot@…]

=> Parameter names MUST NOT be repeated.

The document should not phrase normative requirements in the passive voice. Instead, the document should make clear which protocol partipants are bound by each requirement. For example, this requirement probably should read "servers MUST NOT generate Content-Disposition header field values with multiple instances of the same parameter name."

Suggested:

Senders MUST NOT generate C-D header field values with multiple instances of the same parameter name.

... and look for similar constructs throughout the draft.

[julian.reschke@…]

see [1073]