[rfc-i] Fwd: [IAB] Request for Proposal: RFC Format Tools
"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Wed, 21 September 2016 08:13 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 EDF2C12B0EF
for <ietfarch-rfc-interest-archive@ietfa.amsl.com>;
Wed, 21 Sep 2016 01:13:25 -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, HTML_MESSAGE=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 MOYnXc04b9mr
for <ietfarch-rfc-interest-archive@ietfa.amsl.com>;
Wed, 21 Sep 2016 01:13:22 -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 C38B512B12E
for <rfc-interest-archive-eekabaiReiB1@ietf.org>;
Wed, 21 Sep 2016 01:13:22 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1])
by rfc-editor.org (Postfix) with ESMTP id 706F9B80F35;
Wed, 21 Sep 2016 01:13:22 -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 C617FB80F34
for <rfc-interest@rfc-editor.org>; Wed, 21 Sep 2016 01:13:20 -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 O1gmyNI5_d15 for <rfc-interest@rfc-editor.org>;
Wed, 21 Sep 2016 01:13:19 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40])
by rfc-editor.org (Postfix) with ESMTPS id 75125B80F33
for <rfc-interest@rfc-editor.org>; Wed, 21 Sep 2016 01:13:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
by c8a.amsl.com (Postfix) with ESMTP id 080951E5D61
for <rfc-interest@rfc-editor.org>; Wed, 21 Sep 2016 01:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1])
by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id S-IziPvUaDu4 for <rfc-interest@rfc-editor.org>;
Wed, 21 Sep 2016 01:07:17 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (unknown [62.28.89.233])
by c8a.amsl.com (Postfix) with ESMTPSA id 161361E5D60
for <rfc-interest@rfc-editor.org>; Wed, 21 Sep 2016 01:07:16 -0700 (PDT)
References: <147440232196.27640.2505672750774808591.idtracker@ietfa.amsl.com>
To: rfc-interest@rfc-editor.org
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
X-Forwarded-Message-Id: <147440232196.27640.2505672750774808591.idtracker@ietfa.amsl.com>
Message-ID: <034f9b66-c454-825e-fee5-a3ec24b179b3@rfc-editor.org>
Date: Wed, 21 Sep 2016 09:13:16 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <147440232196.27640.2505672750774808591.idtracker@ietfa.amsl.com>
Subject: [rfc-i] Fwd: [IAB] Request for Proposal: RFC Format Tools
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.15
Precedence: list
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: multipart/mixed; boundary="===============7455421807040873844=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>
FYI -------- Forwarded Message -------- Subject: [IAB] Request for Proposal: RFC Format Tools Date: Tue, 20 Sep 2016 13:12:01 -0700 From: IETF Administrative Director <iad@ietf.org> Reply-To: tmc@ietf-bids.org To: IETF Announcement List <ietf-announce@ietf.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