Re: Call for Comment: RFC Format Drafts
Phillip Hallam-Baker <phill@hallambaker.com> Fri, 12 February 2016 01:02 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 B6A371B3D61; Thu, 11 Feb 2016 17:02:41 -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 5AJQASqy4Tbb; Thu, 11 Feb 2016 17:02:40 -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 EF3091B3D60; Thu, 11 Feb 2016 17:02:39 -0800 (PST)
Received: by mail-lf0-x22e.google.com with SMTP id j78so42743235lfb.1; Thu, 11 Feb 2016 17:02:39 -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=/TxC1CoYfhMUcFndIhqtE6YuScVDGtumbZ7r0PTJB2A=; b=jJzQF11t3GvIkWItFEHPIhBVkPkyIMODqvs9z1LzDH5uaxM0Z+ua24HlnsS7ddOSJb hCrcppmE+d0QI21kGPrPf3TGdO6U37Xi3QGtg+6nciCEKZTb1OQDmt7k1kHwZrSiuuFp 39F0ubxfK8wk9ef1Xr0E0dd0zQT/IXm70vCL02ua8Zj8sY7zU+QSwCdjwpklqKSsaOmt RFpiI5oCeMQs1IIpTG5tLL5IobOrr8cSfor7ZYRYCAwXnvIk0wH8h34WmB9V6BUgF1tQ Yz+SJ8sWQkteRwgB6m5OzowNzsyo7i6Jqru3elgFl5tDm9aI9Ee5tiYTzVF8IFMavDNf fjgw==
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=/TxC1CoYfhMUcFndIhqtE6YuScVDGtumbZ7r0PTJB2A=; b=bQ/rXO43joFas0J4RfeXhlOTpOKCQ4KBLdA2wBp0L9KzhcC1kNoVXUnRL9EU9dIUev hTuiUev9acGUaQ5wJHKADWa68/2e/PnFPVhtqSynaDnGhX6Z0ePrUrILtrS4Iu6DLDlo S4v/Opjr5Ubp07nDaa+w6L0brSOPEWR8O7nIysUboHBDnh4UMJcKxgyGatiRbn5jXVeQ GiXSMUaJ3JPXChIugfV356vF5Hx+Tpi140et8c7GYIlXrB3lUXx0szCmaIv2LKXwGBP9 vWs8LLjG9aY32sWpGo7kYBpOUmDWQVyUk/G3ltb4s6Di4JJAC1/YX3GBTItNWU6kw/Kz 1/bA==
X-Gm-Message-State: AG10YORP1ANLbbVw18dGkY0pnYZJNT4GR8vfVYwxc5thiCEqDdrVkr27Suex5/7R7cvdNiR2pMNE/6hK3sWDog==
MIME-Version: 1.0
X-Received: by 10.25.90.3 with SMTP id o3mr6551528lfb.166.1455238958191; Thu, 11 Feb 2016 17:02:38 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.49.80 with HTTP; Thu, 11 Feb 2016 17:02:38 -0800 (PST)
In-Reply-To: <20160211173901.28789.59265.idtracker@ietfa.amsl.com>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com>
Date: Thu, 11 Feb 2016 20:02:38 -0500
X-Google-Sender-Auth: WRliqegCQXS_DezAStNp57voc8U
Message-ID: <CAMm+LwhfCUpVS-BrG=eV6-o6jmqTb_TLuV-ZPWZbOpiUR_56Mw@mail.gmail.com>
Subject: Re: Call for Comment: RFC Format Drafts
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: IETF Discussion Mailing List <ietf@ietf.org>, IAB IAB <iab@iab.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/tqfcx-bJCGvBt17Rh-yMIEcjY14>
Cc: 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 01:02:41 -0000
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. >
- Re: Call for Comment: RFC Format Drafts Phillip Hallam-Baker
- Re: Call for Comment: RFC Format Drafts Heather Flanagan (RFC Series Editor)
- Re: Call for Comment: RFC Format Drafts Phillip Hallam-Baker
- Re: [IAB] Call for Comment: RFC Format Drafts Joe Hildebrand (jhildebr)
- Re: Call for Comment: RFC Format Drafts Julian Reschke
- Re: Call for Comment: RFC Format Drafts Julian Reschke