RFC Editor RFI
IETF Administrative Director <iad@ietf.org> Wed, 31 May 2006 20:03 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlWuC-00043m-IN; Wed, 31 May 2006 16:03:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlWtn-0003ji-7F; Wed, 31 May 2006 16:02:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlWtm-0002AN-Eu; Wed, 31 May 2006 16:02:34 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k4VK2YHp009504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 May 2006 20:02:34 GMT
Received: from mirror by ietf.org with local (Exim 4.43) id 1FlWtl-0007Sj-Ul; Wed, 31 May 2006 16:02:33 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: IETF Administrative Director <iad@ietf.org>
Message-Id: <E1FlWtl-0007Sj-Ul@ietf.org>
Date: Wed, 31 May 2006 16:02:33 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: wgchairs@ietf.org, iab@ietf.org, iesg@ietf.org
Subject: RFC Editor RFI
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: rfc-editor-rfi2006@ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
The Internet Engineering Task Force Administrative Oversight Committee plans to issue a Request for Proposal in 2006 for the performance of the RFC Editor functions. To that end the IAOC is issuing a Request for Information to identify organizations interested in pursuing contract award, as well as comments and suggestions from any party about the functions, practices and structure of the RFC Editor. The RFC Editor functions include: (1) Editorial management and publication of the "Request for Comment" (RFC) document series, which includes the permanent document repository of the IETF community; (2) Editorial management and publication of RFCs from Independent Submissions; (3) Maintenance of indices, errata and lists associated with RFCs; (4) Communication of relevant RFC and processing information online; and (5) Liaison with and training of IETF community. The RFI can be found at: www.ietf.org at the IASA link. Responses are due no later than June 21, 2006 to rfc-editor-rfi2006@ietf.org. All information submitted in response to this announcement is voluntary and may be used in the development of an RFP. Questions about this RFI can be addressed to: rfc-editor-rfi2006@ietf.org All questions and answers will be posted on the aforementioned website. Ray Pelletier IETF Administrative Director _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
- RFC Editor RFI IETF Administrative Director