BCP 14, RFC 8174 on RFC 2119 Key Words: Clarifying the Use of Capitalization

rfc-editor@rfc-editor.org Fri, 19 May 2017 05:59 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA7711274D2 for <ietf-announce@ietfa.amsl.com>; Thu, 18 May 2017 22:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xajtJHA_VOQC for <ietf-announce@ietfa.amsl.com>; Thu, 18 May 2017 22:59:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AAFE129400 for <ietf-announce@ietf.org>; Thu, 18 May 2017 22:54:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 84715B80D87; Thu, 18 May 2017 22:54:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 14, RFC 8174 on RFC 2119 Key Words: Clarifying the Use of Capitalization
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170519055406.84715B80D87@rfc-editor.org>
Date: Thu, 18 May 2017 22:54:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/VHW5w0Skfpu7HquRv8k45Dpbo9M>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 May 2017 05:59:13 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 14        
        RFC 8174

        Title:      RFC 2119 Key Words: Clarifying 
                    the Use of Capitalization 
        Author:     B. Leiba
        Status:     Best Current Practice
        Stream:     IETF
        Date:       May 2017
        Mailbox:    barryleiba@computer.org
        Pages:      4
        Characters: 6071
        Updates:    RFC 2119
        See Also:   BCP 14

        I-D Tag:    draft-leiba-rfc2119-update-02.txt

        URL:        https://www.rfc-editor.org/info/rfc8174

        DOI:        10.17487/RFC8174

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


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC