Re: Call for Comment: RFC Format Drafts

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 12 February 2016 16:23 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A15401A6F32; Fri, 12 Feb 2016 08:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 rFAHQGiQjp4c; Fri, 12 Feb 2016 08:23:12 -0800 (PST)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BDA91A6F1F; Fri, 12 Feb 2016 08:23:09 -0800 (PST)
Received: by mail-lf0-x22e.google.com with SMTP id 78so54792103lfy.3; Fri, 12 Feb 2016 08:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=BFlhFYhyTcq3hcTcjyo8NSY2iBDDqBJgTncbBpttYs8=; b=sp9/LdKeElEabhyXMLZCiN8fwgoap+7MOujpYX5gDER1g7qjDZZtqB8xpM8zqxFNNM Da5Dfp8Th1PaNoeMJ7iBvScx9ZpS9a8E6Vt9x6gu/WM3nXeOUVhtOyHEsZbaF6MeMA27 Nr8ABqhwGyIhc2zznXP5Opp82vDQzpB2JNi6aDPL5dpQRGby7v3mZiRvnj1Jn3R4zwpE dk4wKd5A0BUNWYBVrDyaEsNLEWva7/LgwCNgi6+MBoQ1NnXbb8A3atfEj0SiVElIkw6k klH4pqX2wbm345hkUZnEv02w1u/fJqY23Zf0+kJTsbwKLXxDXt0pAGsAYRjv5hM2HRxy zy8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BFlhFYhyTcq3hcTcjyo8NSY2iBDDqBJgTncbBpttYs8=; b=Vfu07TF/5g9suabYqjEadIDlxNNNEasnkGdhEO9cu5z3wwUlrHmDyIt5BVTWcS1W+3 Qy+bzNy34sy91GO3ZSO1a7a5i3rk287RhxLwo93fIFOqGg9ZFD9lEE6QEE8DF3DKrozH I8l7vmuCh3IrNsqfkV6q8AmO83S2Cds9fA05AFj48rpeyJpuf+gCoMJ3UtBrW/F/9X7V rSzjGDamp00aWtR0Ba9wbSFXWmQ3YiWSKE9SbZwYqOETqOeNuumPNeYRaMIxAYMcAbgo RKHi5ZoBSo7DHWkx4zTBdl5CXnQ1rGNfA5N43FBKqLwXp5GoClxWlhoYaKErQbpU22/k GikA==
X-Gm-Message-State: AG10YOTl0eJn966WmyFX4QQRaVb/hvYegd8L+VM0JL6tqs0BLhV2nGNf+4CFRtg3AcWiblLYuIz3zalmzgT/Wg==
MIME-Version: 1.0
X-Received: by 10.25.205.7 with SMTP id d7mr1041089lfg.70.1455294187624; Fri, 12 Feb 2016 08:23:07 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.49.80 with HTTP; Fri, 12 Feb 2016 08:23:07 -0800 (PST)
In-Reply-To: <56BE011C.2000905@rfc-editor.org>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com> <CAMm+LwhfCUpVS-BrG=eV6-o6jmqTb_TLuV-ZPWZbOpiUR_56Mw@mail.gmail.com> <56BE011C.2000905@rfc-editor.org>
Date: Fri, 12 Feb 2016 11:23:07 -0500
X-Google-Sender-Auth: DHVVCct1OGxNfVCD5Dalv9xX_qc
Message-ID: <CAMm+LwjkwF5mpW35qxonFDnLgzESbi6DNG7BRDzN8Ff2_9jO-Q@mail.gmail.com>
Subject: Re: Call for Comment: RFC Format Drafts
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/e0YLMBrBqxWgsW0OLUY8h0G7JJw>
Cc: IAB IAB <iab@iab.org>, IETF Discussion Mailing List <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 16:23:13 -0000

Thanks,

I'll try to get round to updating my tools to support the new formats then.

On Fri, Feb 12, 2016 at 10:58 AM, Heather Flanagan (RFC Series Editor)
<rse@rfc-editor.org> wrote:
> -----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-----