[storm] FW: Collecting input on future xml2rfc vocabulary

"Black, David" <david.black@emc.com> Fri, 24 January 2014 21:02 UTC

Return-Path: <david.black@emc.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D264E1A011B for <storm@ietfa.amsl.com>; Fri, 24 Jan 2014 13:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
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 NcKb7Y0zulSn for <storm@ietfa.amsl.com>; Fri, 24 Jan 2014 13:02:24 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 991A41A0099 for <storm@ietf.org>; Fri, 24 Jan 2014 13:02:24 -0800 (PST)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0OL2Hjj007645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <storm@ietf.org>; Fri, 24 Jan 2014 16:02:17 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0OL2Hjj007645
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390597337; bh=sAALNMWc6r/Rmm/sML+vpBBHxDc=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=W8x44PyV2wg2RW7oS4yrjUyJtnQXw3qerx9DVEK0mJpp5zZsAQJsEE1YguTXn29iw wU57pVAbIlTK4fsPeNJpF6+KzIZ7Oz7aoNDgd+vw8KgNUJtKtYRbh732MIPZn04UzF GZJs2uNyWdND5P3PK404iCCZApILkgatDnyuWu6s=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0OL2Hjj007645
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd56.lss.emc.com (RSA Interceptor) for <storm@ietf.org>; Fri, 24 Jan 2014 16:01:56 -0500
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0OL1uPr016497 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <storm@ietf.org>; Fri, 24 Jan 2014 16:01:56 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Fri, 24 Jan 2014 16:01:55 -0500
From: "Black, David" <david.black@emc.com>
To: "storm@ietf.org" <storm@ietf.org>
Date: Fri, 24 Jan 2014 16:01:55 -0500
Thread-Topic: Collecting input on future xml2rfc vocabulary
Thread-Index: Ac8W2W5bxZsqYl67RjSbd856ngA11QCbPNMQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F162156@MX15A.corp.emc.com>
References: <52DEBDF2.6080503@rfc-editor.org>
In-Reply-To: <52DEBDF2.6080503@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Subject: [storm] FW: Collecting input on future xml2rfc vocabulary
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm/>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 21:02:27 -0000

FYI - if you're using XML to produce Internet-Drafts, and there are things
that you wish the XML (plus XML to RFC) would do for you, the RFC Editor
and RFC Format Design Team would like to hear from you.

The IETF is planning to switch from text to XML as the reference format
for publishing RFCs

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

-----Original Message-----
From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Heather Flanagan (RFC Series Editor)
Sent: Tuesday, January 21, 2014 1:36 PM
To: 'Working Group Chairs'
Subject: Collecting input on future xml2rfc vocabulary

Hello WG Chairs,

I would like to enlist your assistance in getting the word out to active
authors about current efforts to update the xml2rfc vocabulary and DTD.
Some of the best input comes at the point when an author is trying to
create a draft and finds themselves wishing that xml2rfc had a
particular feature, or behaved in a different way.  Now is the best time
to collect that information, since the RFC Format Design Team is in the
process of recommending a variety of changes to support the new proposed
formats for RFCs.

Authors should send their suggestions to the rfc-interest@rfc-editor.org
mailing list, where they will be discussed and then captured by the
design team.  The archives of that list (available from
<http://www.rfc-editor.org/pipermail/rfc-interest/2014-January/thread.html>)
provide details on what has already been discussed.  The Design Team
wiki (read-only) has also captured some of the discussion and decisions
so far.  See:
<http://www.rfc-editor.org/rse/wiki/doku.php?id=design:xml-tags>.

Thank you for your help,
Heather Flanagan
RFC Series Editor