RFC Editor Services RFI
Ray Pelletier <rpelletier@isoc.org> Sat, 24 January 2009 03:00 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 120033A6A71; Fri, 23 Jan 2009 19:00:42 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CA603A6A71 for <ietf@core3.amsl.com>; Fri, 23 Jan 2009 19:00:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.385
X-Spam-Level:
X-Spam-Status: No, score=-103.385 tagged_above=-999 required=5 tests=[AWL=0.214, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8TJican+1VAS for <ietf@core3.amsl.com>; Fri, 23 Jan 2009 19:00:39 -0800 (PST)
Received: from smtp207.iad.emailsrvr.com (smtp207.iad.emailsrvr.com [207.97.245.207]) by core3.amsl.com (Postfix) with ESMTP id A24363A69F3 for <ietf@ietf.org>; Fri, 23 Jan 2009 19:00:39 -0800 (PST)
Received: from relay10.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay10.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id 98AE71EA5B4 for <ietf@ietf.org>; Fri, 23 Jan 2009 22:00:22 -0500 (EST)
Received: by relay10.relay.iad.mlsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 7F3E91E5D9D for <ietf@ietf.org>; Fri, 23 Jan 2009 22:00:22 -0500 (EST)
Message-Id: <D57C642C-ECFF-491D-800E-D1534D0FF735@isoc.org>
From: Ray Pelletier <rpelletier@isoc.org>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: RFC Editor Services RFI
Date: Fri, 23 Jan 2009 22:00:22 -0500
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
In 2009 the IETF Administrative Oversight Committee (IAOC) plans to issue a Request for Proposal (RFP) for the performance of the RFC Editor functions beginning in 2010. The incumbent has advised that they do not intend to respond to the RFP. The purpose of the RFI is to identify potential contractors to provide the RFC Editor services and to obtain feedback from contractors and the broader Internet community on the implementation of the new RFC services model. The RFC Editor provides editing, publishing and archiving services for the RFC series on behalf of the IETF and the broader Internet community. The Internet Architecture Board (IAB) has described the RFC Editor services, which includes four functions. Following this structure could result in four vendors providing services that are currently provided by one vendor, or fewer than four vendors depending on input received from the RFI as to how the functions might be combined for the efficient delivery of professional, quality services. The overall RFC Editor function is described in RFC 4844 and the model for the RFC Editor structure is described in the IAB model at: http://tools.ietf.org/html/draft-iab-rfc-editor-04 . The model is intended to increase flexibility and operational support options, provide for the orderly succession of the RFC Editor, and ensure the continuity of the RFC series, while maintaining RFC quality, maintaining timely processing, ensuring document accessibility, reducing costs, and increasing cost transparency. The four RFC Editor functions in brief: 1. The RFC Series Editor (RSE) is responsible for overseeing the consistency and quality of the RFC Series; 2. The Independent Submissions Editor (ISE) is responsible for managing the independent submissions stream to the RFC series; 3. The RFC Production Center is responsible for the editing of documents consistent with the RFC Style Manual; and 4. The RFC Publisher is responsible for publishing and maintaining an archive of the RFC Series and its associated Errata. The RFI can be found at: http://iaoc.ietf.org/rfpsrfis.html Responses are due no later than 6 March 2009. See RFI for details. Questions about this RFI can be addressed to: rfc-editor-rfi2009@isoc.org All questions and answers will be posted on the website at http://iaoc.ietf.org/rfpsrfis.html . All information submitted in response to this announcement is voluntary and may be used in the development of the RFP(s). Ray Pelletier IETF Administrative Director _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- RFC Editor Services RFI Ray Pelletier