BCP 97, RFC 8067 on Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level

rfc-editor@rfc-editor.org Wed, 25 January 2017 01:16 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 3C1211295F8 for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2017 17:16:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, 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 o5R75xD9D22w for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2017 17:16:43 -0800 (PST)
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 EE53E1295F5 for <ietf-announce@ietf.org>; Tue, 24 Jan 2017 17:16:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E666CB81BEF; Tue, 24 Jan 2017 17:16:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 97, RFC 8067 on Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170125011643.E666CB81BEF@rfc-editor.org>
Date: Tue, 24 Jan 2017 17:16:43 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Gkt4LJP381H-dYD1xSsc0lzEYi8>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Wed, 25 Jan 2017 01:16:45 -0000

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

        BCP 97        
        RFC 8067

        Title:      Updating When Standards Track Documents 
                    May Refer Normatively to Documents at 
                    a Lower Level 
        Author:     B. Leiba
        Status:     Best Current Practice
        Stream:     IETF
        Date:       January 2017
        Mailbox:    barryleiba@computer.org
        Pages:      3
        Characters: 6215
        Updates:    RFC 3967
        See Also:   BCP 97

        I-D Tag:    draft-leiba-3967upd-downref-03.txt

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

        DOI:        10.17487/RFC8067

RFC 3967 specifies a process for allowing normative references to
documents at lower maturity levels ("downrefs"), which involves
calling out the downref explicitly in the Last Call notice.  That
requirement has proven to be unnecessarily strict, and this document
updates RFC 3967, allowing the IESG more flexibility in accepting
downrefs in Standards Track documents.


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