mirror of
https://github.com/vacp2p/rfc-index.git
synced 2026-01-09 15:48:03 -05:00
Remove MUST keywords from descriptive Payload statements
As discussed in PR #216, RFC 2119 keywords should be reserved for actual normative requirements, not descriptive statements.
This commit is contained in:
@@ -148,9 +148,9 @@ class BlendingHeader:
|
|||||||
|
|
||||||
#### Payload
|
#### Payload
|
||||||
|
|
||||||
The payload MUST be formatted according to the
|
The Payload is formatted according to the
|
||||||
[Payload Formatting Specification][payload-formatting].
|
[Payload Formatting Specification][payload-formatting].
|
||||||
The formatted payload MUST be generated as the outcome of
|
The formatted Payload is generated as the outcome of
|
||||||
the [Message Encapsulation Mechanism][message-encapsulation].
|
the [Message Encapsulation Mechanism][message-encapsulation].
|
||||||
|
|
||||||
#### Maximum Payload Length
|
#### Maximum Payload Length
|
||||||
|
|||||||
Reference in New Issue
Block a user