IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Wed, 10 July 2019 16:57 UTC

Return-Path: <nico@cryptonector.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 6FBAA120155 for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 09:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 iraVuymkqkgH for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 09:57:50 -0700 (PDT)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D93851202C3 for <ietf@ietf.org>; Wed, 10 Jul 2019 09:57:28 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id CBCB42C07F8; Wed, 10 Jul 2019 16:57:27 +0000 (UTC)
Received: from pdx1-sub0-mail-a78.g.dreamhost.com (100-96-1-113.trex.outbound.svc.cluster.local [100.96.1.113]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 4FF872C021D; Wed, 10 Jul 2019 16:57:27 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a78.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.3); Wed, 10 Jul 2019 16:57:27 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Wiry-Harbor: 5fd8aa75678e78ba_1562777847615_118864351
X-MC-Loop-Signature: 1562777847615:3391056104
X-MC-Ingress-Time: 1562777847614
Received: from pdx1-sub0-mail-a78.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a78.g.dreamhost.com (Postfix) with ESMTP id F0DBC7F63A; Wed, 10 Jul 2019 09:57:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=McJUI8MvjCbDjG 6rYjhAJCU9LSs=; b=eHoBcWp5I9qXSSvj2OseV+gLN4J0/rsxgB0WudA+YZdqeh VfJq1PUIleYfwi7AZIkvToVDK0/XOgAQiydg7t9VffreL7H8B88ofk9+kZHFYzlG tviiZE0nCr7fk0c0mx/N0Bw5zATwT1Brpo0T+WPS4pPlYqTpF3xBLIT+vS5tE=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a78.g.dreamhost.com (Postfix) with ESMTPSA id A36C47F638; Wed, 10 Jul 2019 09:57:17 -0700 (PDT)
Date: Wed, 10 Jul 2019 11:57:15 -0500
X-DH-BACKEND: pdx1-sub0-mail-a78
From: Nico Williams <nico@cryptonector.com>
To: Randy Bush <randy@psg.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
Message-ID: <20190710165715.GE3215@localhost>
References: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <m2pnmingsi.wl-randy@psg.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrgeeigddutdelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucfkphepvdegrddvkedruddtkedrudekfeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhenucevlhhushhtvghrufhiiigvpedt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fylduUH__wJqmrtNVYiB1whBYsQ>
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 16:57:52 -0000

On Wed, Jul 10, 2019 at 06:46:37AM -0700, Randy Bush 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!

I want to echo this.

Even I don't need a GUI editor for this.  I strongly prefer TUIs in
general.  But I'm fond of LyX, and since others have wanted a GUI...
thus lyx2rfc.

Nico
--

v2.23.0 | Report a Bug | By Email