[rfc-i] Request for Proposal: RFC Format Tools
IETF Administrative Director <iad@ietf.org> Wed, 21 September 2016 15:01 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id E270312B405
for <ietfarch-rfc-interest-archive@ietfa.amsl.com>;
Wed, 21 Sep 2016 08:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.917
X-Spam-Level:
X-Spam-Status: No, score=-4.917 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001,
RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001,
SPF_PASS=-0.001] 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 YBhnT5UpIIP1
for <ietfarch-rfc-interest-archive@ietfa.amsl.com>;
Wed, 21 Sep 2016 08:00:59 -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 9DB9C12B402
for <rfc-interest-archive-eekabaiReiB1@ietf.org>;
Wed, 21 Sep 2016 08:00:59 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1])
by rfc-editor.org (Postfix) with ESMTP id 594D6B82345;
Wed, 21 Sep 2016 08:00:59 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1])
by rfc-editor.org (Postfix) with ESMTP id 9E70AB81B29
for <rfc-interest@rfc-editor.org>; Tue, 20 Sep 2016 13:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1])
by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id CVAw-tuG5R9n for <rfc-interest@rfc-editor.org>;
Tue, 20 Sep 2016 13:12:02 -0700 (PDT)
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
by rfc-editor.org (Postfix) with ESMTPS id 1BF95B81B27
for <rfc-interest@rfc-editor.org>; Tue, 20 Sep 2016 13:12:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
by ietfa.amsl.com (Postfix) with ESMTP id 006FA12B7ED;
Tue, 20 Sep 2016 13:12:02 -0700 (PDT)
MIME-Version: 1.0
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147440232196.27640.2505672750774808591.idtracker@ietfa.amsl.com>
Date: Tue, 20 Sep 2016 13:12:01 -0700
X-Mailman-Approved-At: Wed, 21 Sep 2016 08:00:58 -0700
Subject: [rfc-i] Request for Proposal: RFC Format Tools
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.15
Reply-To: tmc@ietf-bids.org
List-Id: "A list for discussion of the RFC series and RFC Editor functions."
<rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>,
<mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>,
<mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>
The IETF Administrative Oversight Committee (IAOC), on behalf of the RFC Editor, announces this Request for Proposals for the development of a suite of tools to implement changes to the RFC format. Bidders may submit a proposal to develop the entire suite of tools or any number of the tools. The successful bidder(s) will enter into a contract with the Internet Society. The RFC Editor plans to produce a canonical RFC document in XML using the xm2rfc v3 grammar, and to publish the RFC in several Publication Formats as defined in RFC 6949. This new process requires new and updated tooling, including a revised idnits, a Publication Formatter, diff checkers, XML and SVG validators, and a text to XML generator. More specifically: 1. idnits The idnits program inspects Internet-Draft documents for a variety of conditions that should be adjusted to bring the document into line with policies from the IETF, the IETF Trust, and the RFC Editor. 2. Publication Formatter This project will result in one or more applications to produce the Text, HTML, and PDF publication formats from an xml2rfc v3 source document. It will also produce a mechanism to create an xml2rfc v3 document from an xml2rfc v2 document, and a mechanism to conditioning an xml2rfc v3 document entry into the RFC archives. 3. RFClint For a given input document, the application will help authors and the RFC Editor: • Identify and optionally remove duplicate words • Identify and optionally correct misspelled words • Verify that imbedded XML stanzas are well formed • Verify that imbedded ABNF is complete and well formed 4. svgcheck The upcoming RFC format will allow line drawings in RFCs using a specialized profile of the SVG (Scalable Vector Graphics) language. The RFC Editor requires a tool to verify that submitted SVG is valid and conforms to specific profile. 5. Text Submission This project will create an application to convert an Internet-Draft formatted text file to an xml2rfc v3 document. 6. XML Diff This project will create an application that operates on two xml2rfc v3 source documents, producing a visual presentation of the meaningful differences in the source. The RFP can be found at: <https://iaoc.ietf.org/rfps.html>. Proposals must be received via email at tmc@ietf-bids.org no later than October 17, 2016. All questions, inquiries must be submitted by September 28, 2016. Responses to questions and inquiries shall be posted online at: <https://iaoc.ietf.org/rfps.html> by October 3rd. The point of contact regarding this RFP is the IETF Administrative Director, Ray Pelletier, iad@ietf.org. Ray Pelletier IAD _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Fwd: [IAB] Request for Proposal: RFC Form… Heather Flanagan (RFC Series Editor)
- [rfc-i] Request for Proposal: RFC Format Tools IETF Administrative Director