Correction: Request for Proposal: RFC Format CSS Design

IETF Administrative Director <> Fri, 22 July 2016 10:06 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 6BF3912DF36; Fri, 22 Jul 2016 03:06:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <>
To: IETF Announcement List <>
Subject: Correction: Request for Proposal: RFC Format CSS Design
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Fri, 22 Jul 2016 03:06:16 -0700
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 22 Jul 2016 10:06:16 -0000

The previous announcement contained an error in the list of 
Deliverables.  Below is the corrected list.

The IETF Administrative Oversight Committee (IAOC), on behalf of the
IETF, announces this Request for Proposals for the development of a
RFC Format CSS Design.  The successful bidder will enter into a
contract with the Internet Society.

The RFC Editor plans to produce a canonical RFC document in XML
using the xml2rfc v3 grammar, and to publish the RFC in several
Publication Formats as defined in RFC6949.  In particular, there
will be an HTML and PDF output that will support many new features
within the documents, including SVG line art.  This project will
result in a CSS file that will reflect visually pleasing,
accessible, and responsive design.


•	Provide a responsive design CSS for future RFCs following the
guidance in draft-iab-rfc-css

•	The PDF and HTML output must look as similar as possible

•	All of the HTML features  that have been called out in
draft-iab-html-rfc need to be in place in the CSS

The RFP can be found at: <>.

Proposals must be received via email at no later
than September 9, 2016.  All questions, inquiries must be submitted
by August 8, 2016.  Responses to questions and inquiries shall be
posted online at:  <> by August 15,

The point of contact regarding this RFP is the IETF Administrative
Director, Ray Pelletier,

Ray Pelletier