Re: Call for Comment: RFC Format Drafts
"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Fri, 12 February 2016 15:58 UTC
Return-Path: <rse@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A9E1A1BFF; Fri, 12 Feb 2016 07:58:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
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 zlQVgewtDth5; Fri, 12 Feb 2016 07:58:22 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 069C81A1BFE; Fri, 12 Feb 2016 07:58:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C3DF51E5D50; Fri, 12 Feb 2016 07:58:02 -0800 (PST)
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 P2NZmE-2_lnF; Fri, 12 Feb 2016 07:58:02 -0800 (PST)
Received: from Heathers-MacBook-Pro.local (unknown [98.125.156.160]) by c8a.amsl.com (Postfix) with ESMTPSA id 7063D1E5D4F; Fri, 12 Feb 2016 07:58:02 -0800 (PST)
Subject: Re: Call for Comment: RFC Format Drafts
To: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, IAB IAB <iab@iab.org>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com> <CAMm+LwhfCUpVS-BrG=eV6-o6jmqTb_TLuV-ZPWZbOpiUR_56Mw@mail.gmail.com>
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Message-ID: <56BE011C.2000905@rfc-editor.org>
Date: Fri, 12 Feb 2016 07:58:20 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAMm+LwhfCUpVS-BrG=eV6-o6jmqTb_TLuV-ZPWZbOpiUR_56Mw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/KWcXxmpRpSC62KpqoIOOr5H0p7s>
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 15:58:24 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello Philip, In production or as a prototype? In production, no. As a prototype, yes. You can find v3 XML and associated HTML here: http://hildjj.github.io/draft-iab-html-rfc/ Is that what you're looking for? - -Heather On 2/11/16 5:02 PM, Phillip Hallam-Baker wrote: > Is there an example of the proposed format in use anywhere? > > On Thu, Feb 11, 2016 at 12:39 PM, IAB Executive Administrative > Manager <execd@iab.org> wrote: >> This is an announcement of an IETF-wide Call for Comment on the >> RFC Format Drafts. These documents are being considered for >> publication as Informational RFCs within the IAB stream. The >> suggested reading order is: >> >> 1. The big picture >> >> - - - Flanagan, H., "RFC Format Framework", >> http://datatracker.ietf.org/doc/draft-iab-rfc-framework/ >> >> 2. The underlying vocabulary >> >> - - - Hoffman, P., "The 'XML2RFC' version 3 Vocabulary", >> https://datatracker.ietf.org/doc/draft-iab-xml2rfc/ >> >> 3. The outputs >> >> - - - Hildebrand, J. and P. Hoffman, "HyperText Markup Language >> Request For Comments Format”, >> https://datatracker.ietf.org/doc/draft-iab-html-rfc/ >> >> - - - Flanagan, H., "Requirements for Plain Text RFCs", >> https://datatracker.ietf.org/doc/draft-iab-rfc-plaintext/ >> >> - - - Hansen, T., Masinter, L., and M. Hardy, "PDF for an RFC >> Series Output Document Format”, >> https://datatracker.ietf.org/doc/draft-iab-rfc-use-of-pdf/ >> >> - - - Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", >> https://datatracker.ietf.org/doc/draft-iab-svg-rfc/ >> >> 4. Generalized requirements >> >> - - - Flanagan, H., "The Use of Non-ASCII Characters in RFCs", >> https://www.ietf.org/id/draft-iab-rfc-nonascii-00.pdf >> >> - - - Flanagan, H., “CSS Requirements for RFCs”, >> https://datatracker.ietf.org/doc/draft-iab-rfc-css/ >> >> 5. Workflow and tools (note that the examples draft will not >> become an RFC, but is necessary for the project) >> >> - - - Hildebrand, J. and P. Hoffman, "RFC v3 Prep Tool >> Description", >> https://datatracker.ietf.org/doc/draft-iab-rfcv3-preptool/ >> >> - - - Hoffman, P. and T. Hansen, "Examples of the ‘XML2RFC' >> Version 2 and 3 Vocabularies”, >> http://datatracker.ietf.org/doc/draft-hoffman-rfcexamples/ >> >> 6. The Statements of Work >> >> - - - http://www.nostrum.com/~rjsparks/rfced/ >> >> The Call for Comment will last until 2016-03-10. Please send >> comments to iab@iab.org. For comments on individual drafts, >> please include the relevant document filename in the subject >> line. >> > -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWvgEcAAoJEJlIWQlAXuk2Y9MQANSsSV1SL2M85F1rnw6dafOn vzM9rs9nAz3BehX+ilDY9aGcRr1rWyZbt2jm73LmXXZAyS2amLtUEBuK/RoYDjj1 jBWrzbSVwZoxnoUwT0Q1ckYurni7jzTczwKyOFu4ymgjqfe3HZl3lkvJL3cG8y++ 6z2kcHLS27blnCmgd6UguTjad6+wK5yXqkHHy92viPSkGDz3RRWngxustvjPxlCj AHMtAY/OjWyh1ExqT4ENJIw1jc80CkwzU8LdiYX65DRBvNOTeq9M/BBvJ3R8DLdn lR/9v8w8y0+yAEglJAvyqgYKt3c49qPUdZQ2spn83QFbd1KvBPLqJGLqVJNt36RF r8BkYO/irbNVt3iNrmlGlIL86l/wtAl+jBANKD2SO1rkXZJkewk4a6dsKgxmtX0S 9abpoPeMChLqa7l6Die0Mqpid7ryvaITU4ySsJtY7KMnCsGAYRxowm87KYvvzX7l 3a51B6QaNuiPsk/AKsmRKrTb+XENC/UTxyIDgu5hK2zU0FMSx6m8odtQUAgUcqsi H1QFY1jThtQ0AmVm2AXGER142uL28XS0Mgsc4BaWPfoA7xRu+JNfgM/Qa8+UZUba SPrnTKcvNW3JTZT/jhYjLK4Vfigyr1RobLS38nM4pVv4JtTp2Vz19cVJKP4cqTHZ lZZanFqYn2nxhhFqPnQd =eB+m -----END PGP SIGNATURE-----
- Call for Comment: RFC Format Drafts IAB Executive Administrative Manager
- Re: Call for Comment: RFC Format Drafts Heather Flanagan (RFC Series Editor)