BCP 205, RFC 7942 on Improving Awareness of Running Code: The Implementation Status Section

rfc-editor@rfc-editor.org Mon, 11 July 2016 23:15 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 C7E9212B02A for <ietf-announce@ietfa.amsl.com>; Mon, 11 Jul 2016 16:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 0CDusWIdxOXC for <ietf-announce@ietfa.amsl.com>; Mon, 11 Jul 2016 16:15:42 -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 D368D12D5C7 for <ietf-announce@ietf.org>; Mon, 11 Jul 2016 16:15:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CE273B80B90; Mon, 11 Jul 2016 16:15:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 205, RFC 7942 on Improving Awareness of Running Code: The Implementation Status Section
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160711231539.CE273B80B90@rfc-editor.org>
Date: Mon, 11 Jul 2016 16:15:39 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mZrIr9uZ2KlT76EXZP6LnsvWAcY>
Cc: 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: Mon, 11 Jul 2016 23:15:52 -0000

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

        BCP 205        
        RFC 7942

        Title:      Improving Awareness of Running Code: 
                    The Implementation Status Section 
        Author:     Y. Sheffer, A. Farrel
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2016
        Mailbox:    yaronf.ietf@gmail.com, 
                    adrian@olddog.co.uk
        Pages:      8
        Characters: 17273
        Obsoletes:  RFC 6982
        See Also:   BCP 205

        I-D Tag:    draft-sheffer-rfc6982bis-03.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7942

This document describes a simple process that allows authors of
Internet-Drafts to record the status of known implementations by
including an Implementation Status section.  This will allow
reviewers and working groups to assign due consideration to documents
that have the benefit of running code, which may serve as evidence of
valuable experimentation and feedback that have made the implemented
protocols more mature.

This process is not mandatory.  Authors of Internet-Drafts are
encouraged to consider using the process for their documents, and
working groups are invited to think about applying the process to all
of their protocol specifications.  This document obsoletes RFC 6982,
advancing it to a Best Current Practice.


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