Browse Prior Art Database

Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words (RFC8174)

IP.com Disclosure Number: IPCOM000250035D
Original Publication Date: 2017-May-01
Included in the Prior Art Database: 2017-May-20
Document File: 8 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Leiba: AUTHOR

Abstract

RFC 2119 specifies common key words, such as "MUST", "SHOULD", and "MAY", that may be used in protocol specifications. It says that the key words "are often capitalized," which has caused confusion about how to interpret non-capitalized words such as "must" and "should".

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 45% of the total text.

Internet Engineering Task Force (IETF)                          B. Leiba Request for Comments: 8174                           Huawei Technologies BCP: 14                                                         May 2017 Updates: 2119 Category: Best Current Practice ISSN: 2070-1721

        Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words

Abstract

   RFC 2119 specifies common key words that may be used in protocol    specifications.  This document aims to reduce the ambiguity by    clarifying that only UPPERCASE usage of the key words have the    defined special meanings.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8174.

Leiba                     Best Current Practice                 [Page 1]
 RFC 8174                 RFC 2119 Clarification                 May 2017

 Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  Clarifying Capitalization of Key Words  . . . . . . . . . . .   3    3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4    4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4    5.  Normative References  . . . . . . . . . . . . . . . . . . . .   4    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   RFC 2119 specifies common key words, such as "MUST", "SHOULD", and    "MAY", that may be used in protocol specifications.  It says that the    key words "are often capitalized," which has caused confusion about   ...