[Nsis-imp] [Fwd: [rfc-dist] BCP 9, RFC 5657 on Guidance on Interoperation and Implementation Reportsfor Advancement to Draft Standard]
Xiaoming Fu <fu@cs.uni-goettingen.de> Thu, 01 October 2009 01:44 UTC
Return-Path: <fu@cs.uni-goettingen.de>
X-Original-To: nsis-imp@core3.amsl.com
Delivered-To: nsis-imp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6C933A677D for <nsis-imp@core3.amsl.com>; Wed, 30 Sep 2009 18:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 x92ubxIzqrDF for <nsis-imp@core3.amsl.com>; Wed, 30 Sep 2009 18:44:47 -0700 (PDT)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by core3.amsl.com (Postfix) with ESMTP id AFEB63A6939 for <nsis-imp@ietf.org>; Wed, 30 Sep 2009 18:44:46 -0700 (PDT)
Received: from cs-32-97.cs.ucla.edu ([131.179.32.97]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <fu@cs.uni-goettingen.de>) id 1MtAkC-0002Ja-SA; Thu, 01 Oct 2009 03:46:09 +0200
Message-ID: <4AC409DD.3050704@cs.uni-goettingen.de>
Date: Wed, 30 Sep 2009 18:46:05 -0700
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
Organization: University of Goettingen, Germany
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: nsis-imp@ietf.org
Content-Type: multipart/mixed; boundary="------------010103070207090605050807"
X-Authenticated: Id:xfu
X-Virus-Scanned: (clean) by exiscan+sophie
Subject: [Nsis-imp] [Fwd: [rfc-dist] BCP 9, RFC 5657 on Guidance on Interoperation and Implementation Reportsfor Advancement to Draft Standard]
X-BeenThere: nsis-imp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for implementation questions for NSIS protocols <nsis-imp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nsis-imp>, <mailto:nsis-imp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsis-imp>
List-Post: <mailto:nsis-imp@ietf.org>
List-Help: <mailto:nsis-imp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsis-imp>, <mailto:nsis-imp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2009 01:44:48 -0000
FYI
--- Begin Message ---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 _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org--- End Message ---