Re: [IAB] Call for Comment: RFC Format Drafts

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Fri, 12 February 2016 17:06 UTC

Return-Path: <jhildebr@cisco.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 DAC7A1A7014; Fri, 12 Feb 2016 09:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 1iH-0RM5cCTj; Fri, 12 Feb 2016 09:06:43 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACC961A7005; Fri, 12 Feb 2016 09:06:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5958; q=dns/txt; s=iport; t=1455296802; x=1456506402; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=C4PaG5ubk5/Gr8L1v2oyumdAWj/PcNnjpYwvVx9Pg8U=; b=YHGiANtEgSQKJ8a4/TA1JagKLb+RMP9rV+Pt8xDUQMFn+84hDWSsNFKv rdm57nfdOhDD6fEqhxgaDsQskqygNpkrj+v9UalyBeJcaqjgYrIE94+vx kKCsNbw84UKjZLrR940woJ5vfl7h4X2PMjyXQS+NmDSPXXrsEX6+5VoV1 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D2AQB7EL5W/51dJa1eFoMkUm0GiFWxM?= =?us-ascii?q?gENgWchhWwCHIEdOBQBAQEBAQEBgQqEQgEBAgIdBhFFEAIBCBgCAiYCAgIwFAE?= =?us-ascii?q?QAgQBDQWIGg6yZY52AQEBAQEBAQEBAQEBAQEBAQEBAQEBFXuFFoFsgkqEAS+DA?= =?us-ascii?q?iuBDwWWdwGFT4JshRkIgVZKg3mIVY49AR4BAUKCARqBSWoBhy18AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,436,1449532800"; d="scan'208";a="76428308"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Feb 2016 17:06:41 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u1CH6fX3011842 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 12 Feb 2016 17:06:41 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 12 Feb 2016 11:06:40 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1104.009; Fri, 12 Feb 2016 11:06:40 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Subject: Re: [IAB] Call for Comment: RFC Format Drafts
Thread-Topic: [IAB] Call for Comment: RFC Format Drafts
Thread-Index: AQHRZPMjxQWou8dj+EGF2EUiGcJ9wZ8n/NAAgAD6QQCAAAbtgP//ltGA
Date: Fri, 12 Feb 2016 17:06:40 +0000
Message-ID: <E4803A36-D659-4B89-901B-076A91365151@cisco.com>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com> <CAMm+LwhfCUpVS-BrG=eV6-o6jmqTb_TLuV-ZPWZbOpiUR_56Mw@mail.gmail.com> <56BE011C.2000905@rfc-editor.org> <CAMm+LwjkwF5mpW35qxonFDnLgzESbi6DNG7BRDzN8Ff2_9jO-Q@mail.gmail.com>
In-Reply-To: <CAMm+LwjkwF5mpW35qxonFDnLgzESbi6DNG7BRDzN8Ff2_9jO-Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.160109
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.203.20]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FAE89FD0EC3A5F4B9F10FFFAD3E87BD7@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/cw0qj2BteYzzurg2Md_SykUrW_o>
Cc: 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 17:06:45 -0000

Please let me know if you find any issues in the prototype, in addition to issues you find in the specs.  Also, since the prototype is using... "esoteric" tooling, anyone who is interested in how it works should contact me directly with questions.

-- 
Joe Hildebrand






On 2/12/16, 9:23 AM, "IAB on behalf of Phillip Hallam-Baker" <iab-bounces@iab.org on behalf of phill@hallambaker.com> wrote:

>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-----
>