Skip to content

Commit e36712b

Browse files
author
Ma Shimiao
committed
Add MUST NOT and SHALL NOT to conventions
MUST NOT and SHALL NOT means an absolute prohibition of the spec. They should be one of requirements to judge one implementation if it is compliant. Signed-off-by: Ma Shimiao <[email protected]>
1 parent e6013db commit e36712b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

spec.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
2929

3030
The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the [rationale for the C99 standard][c99-unspecified].
3131

32-
An implementation is not compliant if it fails to satisfy one or more of the MUST, REQUIRED, or SHALL requirements for the protocols it implements.
33-
An implementation is compliant if it satisfies all the MUST, REQUIRED, and SHALL requirements for the protocols it implements.
32+
An implementation is not compliant if it fails to satisfy one or more of the MUST, MUST NOT, REQUIRED, SHALL, or SHALL NOT requirements for the protocols it implements.
33+
An implementation is compliant if it satisfies all the MUST, MUST NOT, REQUIRED, SHALL, and SHALL NOT requirements for the protocols it implements.
3434

3535
## Overview
3636

0 commit comments

Comments
 (0)