![]() InĬertain circumstances, unfortunately, conflicting needs require a specification to violate the In general, specifications interact with and rely on a wide variety of other specifications. "discouraged", "can", "cannot", "could", "could not", "might", and "might not" can be used instead. Īll of the above is applicable to both this standard and any document that uses this standard.ĭocuments using this standard are encouraged to limit themselves to "must", "must not", "should",Īnd "may", and to use these in their lowercase form as that is generally considered to be moreįor non-normative content "strongly encouraged", "strongly discouraged", "encouraged", ![]() To preserve long-standing practice in many non-IETF-published pre-RFC 8174 documents. This is a willful violation of RFC 8174, motivated by legibility and a desire These keywords have equivalent meaning when written in lowercase and cannot appear in "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", ConformanceĪll assertions, diagrams, examples, and notes are non-normative, as are all sections explicitly Order to help the editors ensure that any future breaking changes to the Infra Standard areĬorrectly reflected by any such dependencies. Specification authors are also encouraged to add their specification to the list of dependent specifications in Additionally, cross-referencing terminology To make use of the Infra Standard in a document titled X, use X depends on the Infra Standard. Help write clear and readable algorithmic prose by clarifying otherwise ambiguous concepts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |