Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Additional language for conformance statement #1

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Additional language for conformance statement #1

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9a71fa2
Additional language for conformance statement
stephenrwalli Apr 6, 2016
5fd926c
Update README.md
stephenrwalli Apr 7, 2016
e741433
Removed conditionally compliant for now.
stephenrwalli Apr 7, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,8 @@ Table of Contents

In the specifications in the above table of contents, the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119) (Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997).

An implementation is not compliant if it fails to satisfy one or more of the MUST or REQUIRED level requirements for the protocols it implements. An implementation that satisfies all the MUST or REQUIRED level and all the SHOULD level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the MUST level requirements but not all the SHOULD level requirements for its protocols is said to be "conditionally compliant."
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“satisfies all the MUST or REQUIRED level” → “satisfies all the MUST and REQUIRED level”?


# Use Cases

To provide context for users the following section gives example use cases for each part of the spec.
Expand Down