IETF Logo Mail Archive

Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 10 July 2019 18:43 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E500312070D for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 11:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.126
X-Spam-Level:
X-Spam-Status: No, score=-0.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.247, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 agXXrDRXBNjO for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 11:43:48 -0700 (PDT)
Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (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 1BFE6120729 for <ietf@ietf.org>; Wed, 10 Jul 2019 11:43:43 -0700 (PDT)
Received: by mail-ot1-f51.google.com with SMTP id n5so3208929otk.1 for <ietf@ietf.org>; Wed, 10 Jul 2019 11:43:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fBI7ornHvqhG7ik9YEKemWUovRV10w1mQmP7AWFyxUE=; b=BW3HwyhzOdEetsnYYwjfmB4Bu7sfa/VFsNRN3dXF7bbThPdsj/q1seh5Jqkf+ze78h kAUehyLbCw4AoU/Y6EJLnHiEqWPZg31Fxy4/S7AKAv7OT/056LAsQDkV9YZ7WnrG1zmN QSURWbayh06Yx0ELp5natFJyqtlyLLyOdtO98ojcvqQ1uId+ntaoBE/WK0iKL7QGKIXZ XPZN5io2ICM9OCchFr5w42IgwP0FYOV6YY00T+/Dwi8Ael4efQH3xvwF2ma46Bopxc41 4rmBPbBmLrQX8dSw6Jhyyy9OM6fNFF0bAyOYtI/ChVbc/adRf92HTKbl3o4txmFhHqEB iKFA==
X-Gm-Message-State: APjAAAVRR1sH5GsiStF//7XKJYPNFky1mLbhRKyCxA1B/aQIomTqbn+7 Z+fLEtPzz3b71GdheGNww+rsRdzlAFUHU3AE8jrGBQ==
X-Google-Smtp-Source: APXvYqw3O1kCgnnwVOPt99qr8UeVnLXkLZNcyqetTrfQN9mefIqxnVAQPFuCkGTpRfLQT2+Tfed6fVY18KDGxEOqWqE=
X-Received: by 2002:a9d:c22:: with SMTP id 31mr6383525otr.48.1562784222177; Wed, 10 Jul 2019 11:43:42 -0700 (PDT)
MIME-Version: 1.0
References: <20190704140552.GE49950@hanna.meerval.net> <b0943792-1afc-0c94-51b7-f2d393ef39c5@network-heretics.com> <20190705205723.GI55957@shrubbery.net> <20190706185415.GB14026@mit.edu> <CABcZeBPgNr5UqQ0pLwwNu5wh0g9L9wCd6YyYKCUDO37SPru-_Q@mail.gmail.com> <20190708202612.GG60909@shrubbery.net> <9ae14ad1-f8d5-befb-64e4-fff063c88e02@network-heretics.com> <CABcZeBOH9LH8Jrz-A5eu9arqUb+bx8xs_eKWi0pyoh7a3qpOPA@mail.gmail.com> <20190708223350.GO3508@localhost> <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <944332dc-bb2a-0717-8b9f-254b036fe59f@gmx.de> <m2pnmingsi.wl-randy@psg.com> <CAL02cgTBL7w02sWx4kaqGLQe8bGm4jRMyMY9v7yJw57_Sp=PgA@mail.gmail.com> <CABcZeBMB+4xdfiqVX1o7BddPSaaszc4fx2-xgGQJAUKCPAQWew@mail.gmail.com>
In-Reply-To: <CABcZeBMB+4xdfiqVX1o7BddPSaaszc4fx2-xgGQJAUKCPAQWew@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 10 Jul 2019 14:43:30 -0400
Message-ID: <CAMm+LwhxDg_bpsLoeULD16mDAxrPyyLTD=_90BG5Yn7DH1DzNQ@mail.gmail.com>
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
To: Eric Rescorla <ekr@rtfm.com>
Cc: Richard Barnes <rlb@ipv.sx>, Julian Reschke <julian.reschke@gmx.de>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006c6da9058d580ef8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F_n8I_fZ_Gk2tDR4UfhyjbALMWs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Jul 2019 18:43:50 -0000

My tool takes in Markdown and spits out XML2RFC.

It also takes in Microsoft Word .docx format which is supported by almost
every editor as an output format.

Most of my docs are a combination of text written in Word so that the spell
and grammar checker can be used and examples that are generated in
markdown.


On Wed, Jul 10, 2019 at 10:10 AM Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Wed, Jul 10, 2019 at 6:57 AM Richard Barnes <rlb@ipv.sx> wrote:
>
>> I'm glad it works for you.  The non-IETF-habituated new authors I've
>> worked with have found it mystifying.  Including everyone from junior
>> engineers to Fellows of major engineering organizations.
>>
>
> Indeed. And even a large number of habituated authors have gravitated
> towards markdown, despite the rather klunky workflow of MD -> XML -> TXT.
>
> -Ekr
>
>
>> As Christian says, our continued attachment to bespoke tools is a barrier
>> to getting new work in the IETF, and thus detrimental to the long-term
>> health of the organization.
>>
>> --RLB
>>
>>
>> On Wed, Jul 10, 2019 at 9:47 AM Randy Bush <randy@psg.com> wrote:
>>
>>> >> Tooling is just one of the problems with XML2RFC. The real issue is
>>> >> that XML2RFC is completely specific to the IETF. This translate into
>>> >> training ...
>>> > It also has been optimized for the production of RFCs. Also note that
>>> > many changes in the v3 vocab just align the language with HTML (lists
>>> > and tables come to mind).
>>>
>>> from an xml non-lover:
>>>
>>> xml2rfc rocks!  it produces the baroqe, designed by committee, internet
>>> draft format from input which i can easily produce in my text editor.
>>>
>>> and the support, maintenance, and responsiveness of the tools team is
>>> simply stunning.
>>>
>>> [ and for the poster who wished for a gooey, there is one ]
>>>
>>> thank you!
>>>
>>> randy
>>>
>>>

v2.23.0 | Report a Bug | By Email