IETF Logo Mail Archive

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

Richard Barnes <rlb@ipv.sx> Wed, 10 July 2019 13:57 UTC

Return-Path: <rlb@ipv.sx>
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 C64AF1200FE for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 06:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.601
X-Spam-Level:
X-Spam-Status: No, score=-0.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 bIuGiVLQAHXo for <ietf@ietfa.amsl.com>; Wed, 10 Jul 2019 06:57:10 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 8543A1200A1 for <ietf@ietf.org>; Wed, 10 Jul 2019 06:57:10 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id e8so2200184otl.7 for <ietf@ietf.org>; Wed, 10 Jul 2019 06:57:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=x0fxRI51eyEs2axhQyE50T6z/olKY7FyFF8v0Snc9Kw=; b=Jiv6yPSf7naLvcY5w2b1fU1PKOwC+vLlrT4azH0SJIjYwyMWL1Zf3+2WEZPeLrqWaC o3gVrFTCa9Ompt9jXhjvn5CQzeLbEEwbHBuEivrJMZOzKOsrvUboEeCPOtL2R51qILhL aWMx1I65iCfefeHSuXRn+2nAwEPfgNpGC/mQtLfRsEMkDq/dDjGLMwTB5w6Ufj6NT+Hv AYu4nOidNvbzTJsWutk1Q97TR9SUrDcvczSD1Qfdw0M0EdvQRahlEj+yf3DrBwdEPoOO UmUIWuK11f6bgwQJNCz/MwCKaIxtkZQwhs0YNKdysnSm1yUdOuCGBrnFnUWS/QumeTG3 1Ktw==
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=x0fxRI51eyEs2axhQyE50T6z/olKY7FyFF8v0Snc9Kw=; b=CHnRaIh/+cMc6NRQ1Zkt5kromD+dE3sctfkYK+q5lGs97FvIBE1kZwUxROeQVvm8Sf aKKy0G8q0gCoM0iGEd5cpxNJDAS8jSXtaxME6QaQ7VuhPH54peqHzLPCSe6O6u5ptpS7 ar5oAFJJ1FbY5BJtKvvBdayazH9ryp/SrIhCs9maWrf3rnDNgiIhJzOlPy5teOcdd8wj RccXLx0IlJirXEUNZ0DVUQJyHV5mWwees2i62+FiJNt99cTL5bUyUrrKaX3s9fNB8Ug9 QMhpdedGSZt2FMd0k5EuCYJzLDtJxNCsMXp+SlLEYiXcXlzX4rojGsV4ZTCtQ4gerOXQ THzg==
X-Gm-Message-State: APjAAAW5eHIVR+xlwGuhwrRqXjmDte0vUTUaClWJGmEgAUdiR0r7FQrD Jgxi4T5XCPYQt7AZR7GbeBiQvtcmLJMYHUit3f2aJdBJN/w=
X-Google-Smtp-Source: APXvYqynrT1KxyciepKEhS8zPdD7mVy/dXWrI7lGMBO694V0nGfLmIrgaD2WnuTFFkvWXig6tGPCgx6et3hPVsUDv2o=
X-Received: by 2002:a05:6830:1542:: with SMTP id l2mr24826291otp.241.1562767029446; Wed, 10 Jul 2019 06:57:09 -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>
In-Reply-To: <m2pnmingsi.wl-randy@psg.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 10 Jul 2019 09:56:56 -0400
Message-ID: <CAL02cgTBL7w02sWx4kaqGLQe8bGm4jRMyMY9v7yJw57_Sp=PgA@mail.gmail.com>
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
To: Randy Bush <randy@psg.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a83ec1058d540d3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CQX73op2cub0bQmpDpY-Z2reD2U>
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 13:57:12 -0000

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.

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