[rfc-i] draft-iab-rfc-use-of-pdf-01, "C.3 PDF Generation Libraries"

rse at rfc-editor.org (Heather Flanagan (RFC Series Editor)) Sun, 13 March 2016 10:09 UTC

From: rse at rfc-editor.org (Heather Flanagan (RFC Series Editor))
Date: Sun, 13 Mar 2016 10:09:32 +0000
Subject: [rfc-i] draft-iab-rfc-use-of-pdf-01, "C.3 PDF Generation Libraries"
In-Reply-To: <729D7972-9E38-4E0D-AA78-99ABE1C7B3D0@att.com>
References: <56D6CCFB.2060909@gmx.de> <D7BE5B7F-7DE3-4330-B268-65321D453897@att.com> <56E0581B.4090007@gmx.de> <ABFCD303-0392-4AB9-9768-151BEACADBCC@cisco.com> <56E10CB7.5070601@gmx.de> <729D7972-9E38-4E0D-AA78-99ABE1C7B3D0@att.com>
Message-ID: <56E53C5C.30308@rfc-editor.org>

On 3/10/16 7:28 PM, HANSEN, TONY L wrote:
> When the plan was to keep these I-Ds as living I-Ds and not publishing them as RFCs, having this section made perfect sense. Perhaps that makes less sense now.
> 
> A related question that came up between Larry and I is whether there should be a Tooling Requirements section in section 3?
> 
> Alternative, it might be that there should be a section in one of the core documents that talks about tooling.
> 
> The comments on this appendix really revolve on how those requirements could be met, but (unless I've forgotten a place) I'm not sure that they've been stated somewhere.
> 
> I see these primary tooling requirements:
> 
>     1) RFC Production Center generation of finalized XML files and subsequent officially-blessed formatted files.
>     2) Internet Draft generation through the web site, which currently uses command line tools on linux.
>     3) Command line tools available on linux, windows and mac to generate at least internet-drafts.
>     4) A GUI version available on linux, windows and mac to generate at least internet-drafts.
> 


Good requirements, but I don't think they belong in the drafts.

-Heather