When this occurs, a document using the Infra Standard shouldĭenote such transgressions as a willful violation, and note the reason for that 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 To make use of this standard in a document titled X, use:Īdditionally, cross-referencing all terminology is strongly encouraged to avoid ambiguity. Help write clear and readable algorithmic prose by clarifying otherwise ambiguous concepts. īe a place for concepts used by multiple standards without a good home.2.2 Compliance with other specificationsĪlign standards on conventions, terminology, and data structures.
The Infra Standard aims to define the fundamental concepts upon which standards are built.
0 kommentar(er)
