{ "$schema": "folio-library-entry/v1", "id": "rfc8174-uppercase-vs-lowercase-2119-key-words", "blocks": [ { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-001", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 1", "pageStart": 1, "pageEnd": 1, "target": "../sections/page-001.md", "narrative": null, "content": "RFC 8174:\nAmbiguity of Uppercase vs Lowercase in RFC 2119\nKey Words\nB. Leiba\nBEST CURRENT PRACTICE\nInternet Engineering Task Force (IETF) B. Leiba\nRequest for Comments: 8174 Huawei Technologies\nBCP: 14 May 2017\nUpdates: 2119\nCategory: Best Current Practice\nISSN: 2070-1721\n Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words\nAbstract\n RFC 2119 specifies common key words that may be used in protocol\n specifications. This document aims to reduce the ambiguity by\n clarifyin", "truncated": true, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-002", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 2", "pageStart": 2, "pageEnd": 2, "target": "../sections/page-002.md", "narrative": null, "content": "Leiba Best Current Practice [Page 1]\n9/21/26, 6:25 PM\nRFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words | RFC Editor\nhttps://www.rfc-editor.org/info/rfc8174/\n2/8", "truncated": false, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-003", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 3", "pageStart": 3, "pageEnd": 3, "target": "../sections/page-003.md", "narrative": null, "content": "RFC 8174 RFC 2119 Clarification May 2017\nCopyright Notice\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with respect\n to this document. Code Components extracted from this document must\n include Simplif", "truncated": true, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-004", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 4", "pageStart": 4, "pageEnd": 4, "target": "../sections/page-004.md", "narrative": null, "content": "Leiba Best Current Practice [Page 2]\n9/21/26, 6:25 PM\nRFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words | RFC Editor\nhttps://www.rfc-editor.org/info/rfc8174/\n4/8", "truncated": false, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-005", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 5", "pageStart": 5, "pageEnd": 5, "target": "../sections/page-005.md", "narrative": null, "content": "RFC 8174 RFC 2119 Clarification May 2017\n2. Clarifying Capitalization of Key Words\n The following change is made to [RFC2119]:\n === OLD ===\n In many standards track documents several words are used to signify\n the requirements in the specification. These words are often\n capitalized. This document defines these words as they should be\n interpreted in IETF documents. Authors who follow these guidelines\n should incorporate this phrase near the beginning of their document:\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"", "truncated": true, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-006", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 6", "pageStart": 6, "pageEnd": 6, "target": "../sections/page-006.md", "narrative": null, "content": "appear in all capitals, as shown here.\n === END ===\nLeiba Best Current Practice [Page 3]\n9/21/26, 6:25 PM\nRFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words | RFC Editor\nhttps://www.rfc-editor.org/info/rfc8174/\n6/8", "truncated": false, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-007", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 7", "pageStart": 7, "pageEnd": 7, "target": "../sections/page-007.md", "narrative": null, "content": "RFC 8174 RFC 2119 Clarification May 2017\n3. IANA Considerations\n This document does not require any IANA actions.\n4. Security Considerations\n This document is purely procedural; there are no related security\n considerations.\n5. Normative References\n [RFC2119] Bradner, S., \"Key words for use in RFCs to Indicate\n Requirement Levels\", BCP 14, RFC 2119,\n DOI 10.17487/RFC2119, March 1997,\n .\nAuthor's Address\n Barry Leiba\n Huawei Technologies\n Phone: +1 646 827 0648\n Ema", "truncated": true, "provenance": "ingested", "summary": { "status": "not-summarised" } }, { "id": "library/rfc8174-uppercase-vs-lowercase-2119-key-words/blocks/prose-page-008", "types": [ "folio-assistant-core:Prose", "doco:Section" ], "kind": "prose", "title": "Page 8", "pageStart": 8, "pageEnd": 8, "target": "../sections/page-008.md", "narrative": null, "content": "Leiba Best Current Practice [Page 4]\n9/21/26, 6:25 PM\nRFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words | RFC Editor\nhttps://www.rfc-editor.org/info/rfc8174/\n8/8", "truncated": false, "provenance": "ingested", "summary": { "status": "not-summarised" } } ] }