Опубликованный пакет / CLIR
ietf.bcp14
v0.1.0Key words for use in RFCs to Indicate Requirement Levels
Пломба §208
sha256:908bc6665c19d788078db551bca3439adf4dec945b14b5cd20d219602afa13e0Подключить /
law.toml[dependencies] ietf.bcp14 = "0.1.0"
Получить канонические байты
curl -O /blobs/908bc6665c19d788078db551bca3439adf4dec945b14b5cd20d219602afa13e0.lawir.json
Все адресуемые узлы пакета. Помеченные internal — не часть контракта: сослаться на них из другого пакета нельзя (§24). Свою страницу имеют только публичные символы.
symbol_decl — 44
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| AllCapitals | the key word appears in all capitals and so carries its defined meaning (RFC 8174) | ||
| Lowercase | the key word is not capitalized and so has its normal English meaning (RFC 8174) | ||
| May | MAY — the item is truly optional (RFC 2119, Section 5) | ||
| Must | MUST — an absolute requirement of the specification (RFC 2119, Section 1) | ||
| MustNot | MUST NOT — an absolute prohibition of the specification (RFC 2119, Section 2) | ||
| NotRecommended | NOT RECOMMENDED — synonym of SHOULD NOT; added to the inclusion phrase by RFC 8174 | ||
| Optional | OPTIONAL — synonym of MAY (RFC 2119, Section 5) | ||
| Recommended | RECOMMENDED — synonym of SHOULD (RFC 2119, Section 3) | ||
| Required | REQUIRED — synonym of MUST (RFC 2119, Section 1) | ||
| Shall | SHALL — synonym of MUST (RFC 2119, Section 1) | ||
| ShallNot | SHALL NOT — synonym of MUST NOT (RFC 2119, Section 2) | ||
| Should | SHOULD — valid reasons may exist to ignore the item (RFC 2119, Section 3) | ||
| ShouldNot | SHOULD NOT — valid reasons may exist when the behavior is acceptable (RFC 2119, Section 4) | ||
| absolute_prohibition | the definition is an absolute prohibition of the specification | ||
| absolute_requirement | the definition is an absolute requirement of the specification | ||
| abstains_from | the implementation abstains from the behaviour which the requirement prohibits | ||
| actually_required_for_interoperation | the requirement is actually required for interoperation | ||
| adopted_bcp14 | the document incorporates the BCP 14 phrase and so adopts these definitions | ||
| authored_by | the document is authored by the person | ||
| behaviour_conforms | the observed behaviour of the implementation conforms to the requirement | ||
| behaviour_deviates | the observed behaviour of the implementation deviates from the requirement | ||
| claims_conformance | the implementation claims conformance to the document | ||
| deviation_from_recommendation_justified | it is established that ignoring this recommended item is justified | internal | |
| discouraged_behaviour_acceptable | it is established that the discouraged behaviour is acceptable or even useful here | internal | |
| discouraged_item | the behavior is discouraged: valid reasons may exist when it is acceptable or even useful | ||
| discouragement_binding | the discouragement binds this implementation | ||
| elaborates_security_implications | the author has elaborated the security implications of not following the recommendations or requirements | internal | |
| imperative_use_admissible | it is established that the imperative was used where BCP 14 allows it | internal | |
| implications_understood_and_weighed | the full implications have been understood and carefully weighed before choosing a different course | ||
| includes_option | the implementation includes the optional item | ||
| keyword_used | the key word carries its BCP 14 meaning for this requirement | ||
| keyword_written | the key word is written next to the requirement in the given casing | ||
| limits_potentially_harmful_behavior | the requirement limits behavior which has potential for causing harm | ||
| lowercase_carries_force_by_earlier_practice | under the practice preceding RFC 8174 this lowercase occurrence was read as a key word | internal | |
| omits_option | the implementation does not include the optional item | ||
| recommendation_binding | the recommendation binds this implementation | ||
| recommended_item | the item is recommended: valid reasons may exist to ignore it | ||
| requirement_satisfied | the implementation satisfies the requirement | ||
| stated_in | the requirement is stated in the document | ||
| subject_to | the implementation is bound by the requirement | ||
| truly_optional | the item is truly optional | ||
| uses_imperative | the author has used a BCP 14 imperative for this requirement | ||
| valid_reason_for_discouraged_behaviour | there exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful | ||
| valid_reason_to_ignore | there exist valid reasons in particular circumstances to ignore this particular item |
type_decl — 6
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| Author | the author of an IETF document, who chooses which imperatives to use | ||
| Casing | whether a key word appears in all capitals or not | ||
| Document | an IETF document in which the key words may be used | ||
| Implementation | an implementation of the specification | ||
| Keyword | a BCP 14 key word | ||
| Requirement | an item, a definition or a particular behavior to which a key word is attached |
rule — 40
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| AbsoluteProhibitionBindsTheImplementation | an absolute prohibition of the specification binds every implementation which claims conformance | 1 | internal |
| AbsoluteRequirementBindsTheImplementation | an absolute requirement of the specification binds every implementation which claims conformance | 1 | internal |
| AbstentionFromDiscouragedBehaviourIsPresumed | an implementation is presumed to abstain from a discouraged behaviour until the contrary appears | 1 | internal |
| AbstentionIsPresumed | an implementation is presumed to abstain from a prohibited behaviour until the contrary appears | 1 | internal |
| AcceptableBehaviourReleasesFromTheDiscouragement | where the behaviour is acceptable or even useful the discouragement does not bind | 1 | internal |
| AuthorMustUseImperativesOnlyWhereAllowed | imperatives must be used with care and sparingly: they MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm | 1 | internal |
| CapitalisedKeywordCarriesTheDefinedMeaning | the words have the meanings specified herein only when they are in all capitals | 1 | internal |
| ConformanceClaimBindsToTheRequirementsOfTheDocument | an implementation which claims conformance to a document is bound by the requirements stated in it | 1 | internal |
| ConformingBehaviourSatisfiesTheRequirement | observed conforming behaviour satisfies the requirement | 1 | internal |
| DeviatingBehaviourFailsTheRequirement | observed deviating behaviour fails the requirement | 1 | internal |
| DeviationFromRecommendationIsJustified | ignoring a recommended item is justified when valid reasons exist and the full implications have been weighed | 1 | internal |
| DiscouragedBehaviourIsAcceptableHere | the discouraged behaviour is acceptable where valid reasons exist and the case has been carefully weighed | 1 | internal |
| DiscouragedBehaviourPerformedBreaksAbstention | performing the discouraged behaviour breaks the abstention | 1 | internal |
| DiscouragementBindsUnlessAcceptable | a discouraged behaviour is to be avoided by the implementation which claims conformance | 1 | internal |
| DiscouragementCreatesADefeasibleDutyOfAbstention | a binding discouragement creates a duty to abstain from the behaviour | 1 | internal |
| ImperativeAdmissibleForInteroperation | imperatives MUST only be used where it is actually required for interoperation | 1 | internal |
| ImperativeAdmissibleToLimitHarm | imperatives MUST only be used to limit behavior which has potential for causing harm | 1 | internal |
| ImperativeUseInadmissibleWhereNeitherGroundHolds | an imperative used neither where it is actually required for interoperation nor to limit potentially harmful behavior is used where BCP 14 does not allow it | 1 | internal |
| IncludingImplementationMustInteroperate | an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option | 1 | internal |
| JustifiedDeviationReleasesFromTheRecommendation | where the deviation is justified the recommendation does not bind | 1 | internal |
| LowercaseKeywordCarriesNoDefinedMeaning | when these words are not capitalized, they have their normal English meanings and are not affected by this document | 1 | internal |
| LowercaseKeywordUnderEarlierPracticeCarriesTheDefinedMeaning | under the earlier practice a lowercase occurrence of a key word carried its defined meaning | 1 | internal |
| MayDenotesTrueOptionality | MAY: this word means that an item is truly optional | 1 | internal |
| MustDenotesAnAbsoluteRequirement | MUST: this word means that the definition is an absolute requirement of the specification | 1 | internal |
| MustNotDenotesAnAbsoluteProhibition | MUST NOT: this phrase means that the definition is an absolute prohibition of the specification | 1 | internal |
| NotRecommendedDenotesDiscouragement | NOT RECOMMENDED: this phrase means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful | 1 | internal |
| OmittingImplementationMustInteroperate | an implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option | 1 | internal |
| OptionalDenotesTrueOptionality | OPTIONAL: this adjective means that an item is truly optional | 1 | internal |
| OptionalItemMayBeIncludedOrOmitted | MAY: one vendor may choose to include the item while another vendor may omit the same item | 1 | internal |
| PreRfc8174Practice/EarlierPracticeAppliesToEveryLowercaseKeyword | before RFC 8174 every lowercase occurrence of a key word was argued to carry its defined meaning | internal | |
| PreRfc8174SecurityDuty/AuthorShouldElaborateSecurityImplications | document authors should take the time to elaborate the security implications of not following recommendations or requirements | 1 | internal |
| ProhibitedBehaviourBreaksAbstention | performing the prohibited behaviour breaks the abstention | 1 | internal |
| RecommendationBindsUnlessJustifiedOtherwise | a recommended item binds the implementation which claims conformance | 1 | internal |
| RecommendationCreatesADefeasibleDuty | a binding recommendation creates a duty to satisfy the item | 1 | internal |
| RecommendedDenotesARecommendation | RECOMMENDED: this adjective means that there may exist valid reasons in particular circumstances to ignore a particular item | 1 | internal |
| RequiredDenotesAnAbsoluteRequirement | REQUIRED: this term means that the definition is an absolute requirement of the specification | 1 | internal |
| ShallDenotesAnAbsoluteRequirement | SHALL: this term means that the definition is an absolute requirement of the specification | 1 | internal |
| ShallNotDenotesAnAbsoluteProhibition | SHALL NOT: this phrase means that the definition is an absolute prohibition of the specification | 1 | internal |
| ShouldDenotesARecommendation | SHOULD: this word means that there may exist valid reasons in particular circumstances to ignore a particular item | 1 | internal |
| ShouldNotDenotesDiscouragement | SHOULD NOT: this phrase means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful | 1 | internal |
priority_rule — 6
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| AcceptabilityBeatsTheDiscouragement | an established acceptability prevails over the discouragement it departs from | 1 | internal |
| DeviationBeatsConformance | an absolute requirement is failed by any deviation: the counterexample prevails over conforming behaviour observed elsewhere | 1 | internal |
| EarlierPracticeBeatsTheCapitalisationRule | where the earlier practice is chosen, the lowercase occurrence binds notwithstanding the later clarification | 1 | internal |
| JustifiedDeviationBeatsTheRecommendation | a justified deviation prevails over the recommendation it departs from | 1 | internal |
| PerformanceBeatsThePresumptionOfAbstention | the observed prohibited behaviour prevails over the presumption of abstention | 1 | internal |
| PerformanceBeatsThePresumptionOfAbstentionForDiscouragedBehaviour | the observed discouraged behaviour prevails over the presumption of abstention | 1 | internal |
norm_template — 9
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| AbstainFromProhibitedBehaviour | an absolute prohibition of the specification binds every implementation which claims conformance | 1 | internal |
| AvoidDiscouragedBehaviour | a binding discouragement creates a duty to abstain from the behaviour | 1 | internal |
| FollowRecommendation | a binding recommendation creates a duty to satisfy the item | 1 | internal |
| IncludeOrOmitTheOption | MAY: one vendor may choose to include the item while another vendor may omit the same item | 1 | internal |
| InteroperateWithIncludingImplementation | an implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option | 1 | internal |
| InteroperateWithOmittingImplementation | an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option | 1 | internal |
| PreRfc8174SecurityDuty/ElaborateSecurityImplications | document authors should take the time to elaborate the security implications of not following recommendations or requirements | 1 | internal |
| SatisfyAbsoluteRequirement | an absolute requirement of the specification binds every implementation which claims conformance | 1 | internal |
| UseImperativesOnlyWhereAllowed | imperatives must be used with care and sparingly: they MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm | 1 | internal |
interpretation — 2
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| PreRfc8174Practice | pre-2017 reading: RFC 2119 said only that the key words 'are often capitalized', so lowercase occurrences were argued to carry the same force | internal | |
| PreRfc8174SecurityDuty | pre-2017 reading of section 7: the lowercase 'should' was read as the BCP 14 key word, and the author owed a duty to elaborate the security implications | internal |
external_decl — 4
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| actually_required_for_interoperation/external | the requirement is actually required for interoperation | internal | |
| limits_potentially_harmful_behavior/external | the requirement limits behavior which has potential for causing harm | internal | |
| valid_reason_for_discouraged_behaviour/external | there exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful | internal | |
| valid_reason_to_ignore/external | there exist valid reasons in particular circumstances to ignore this particular item | internal |
fragment — 15
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC2119_ABSTRACT | — | internal | |
| RFC2119_S1 | — | internal | |
| RFC2119_S2 | — | internal | |
| RFC2119_S3 | — | internal | |
| RFC2119_S4 | — | internal | |
| RFC2119_S5 | — | internal | |
| RFC2119_S6 | — | internal | |
| RFC2119_S7 | — | internal | |
| RFC2119_S8 | — | internal | |
| RFC2119_S9 | — | internal | |
| RFC8174_S1 | — | internal | |
| RFC8174_S2 | — | internal | |
| RFC8174_S3 | — | internal | |
| RFC8174_S4 | — | internal | |
| RFC8174_S5 | — | internal |
publication — 2
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC2119_EN_TEXT | — | internal | |
| RFC8174_EN_TEXT | — | internal |
reference — 1
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC8174_UPDATES_RFC2119 | Updates: 2119 (RFC 8174, May 2017) | internal |
source_edition — 2
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC2119_EN | RFC 2119 (S. Bradner) | internal | |
| RFC8174_EN | RFC 8174 (B. Leiba) | internal |
source_work — 2
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC2119 | Key words for use in RFCs to Indicate Requirement Levels | internal | |
| RFC8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words | internal |