BCP 9, RFC 5657 on Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard

rfc-editor@rfc-editor.org Thu, 01 October 2009 00:18 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 438B63A6864 for <ietf-announce@core3.amsl.com>; Wed, 30 Sep 2009 17:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.912
X-Spam-Level:
X-Spam-Status: No, score=-16.912 tagged_above=-999 required=5 tests=[AWL=0.687, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id id0JdyQHORH4 for <ietf-announce@core3.amsl.com>; Wed, 30 Sep 2009 17:18:19 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 6E6873A6837 for <ietf-announce@ietf.org>; Wed, 30 Sep 2009 17:18:19 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 206EE3331AD; Wed, 30 Sep 2009 17:18:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 9, RFC 5657 on Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard
From: rfc-editor@rfc-editor.org
Message-Id: <20091001001846.206EE3331AD@bosco.isi.edu>
Date: Wed, 30 Sep 2009 17:18:46 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 01 Oct 2009 00:18:20 -0000

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

        BCP 9        
        RFC 5657

        Title:      Guidance on Interoperation and Implementation 
                    Reports for Advancement to Draft Standard 
        Author:     L. Dusseault, R. Sparks
        Status:     Best Current Practice
        Date:       September 2009
        Mailbox:    lisa.dusseault@gmail.com, 
                    RjS@nostrum.com
        Pages:      12
        Characters: 29327
        Updates:    RFC2026
        See Also:   BCP0009

        I-D Tag:    draft-dusseault-impl-reports-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5657.txt

Advancing a protocol to Draft Standard requires documentation of the
interoperation and implementation of the protocol.  Historic reports
have varied widely in form and level of content and there is little
guidance available to new report preparers.  This document updates
the existing processes and provides more detail on what is
appropriate in an interoperability and implementation report.  
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.


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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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
USC/Information Sciences Institute