IETF Logo Mail Archive

Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)

Nico Williams <nico@cryptonector.com> Thu, 11 July 2019 17:18 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 9FD8112030D for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 10:18:52 -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 oTt6vPfL5Uad for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 10:18:51 -0700 (PDT)
Received: from cheetah.birch.relay.mailchannels.net (cheetah.birch.relay.mailchannels.net [23.83.209.34]) (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 E95B41200D8 for <ietf@ietf.org>; Thu, 11 Jul 2019 10:18:50 -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 D30A56A2A1D; Thu, 11 Jul 2019 17:18:49 +0000 (UTC)
Received: from pdx1-sub0-mail-a25.g.dreamhost.com (100-96-38-48.trex.outbound.svc.cluster.local [100.96.38.48]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 54BD06A2EF2; Thu, 11 Jul 2019 17:18:49 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a25.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); Thu, 11 Jul 2019 17:18:49 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Exultant-Wiry: 4a96cdef766f7419_1562865529690_2279940484
X-MC-Loop-Signature: 1562865529690:2229722254
X-MC-Ingress-Time: 1562865529689
Received: from pdx1-sub0-mail-a25.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a25.g.dreamhost.com (Postfix) with ESMTP id 873027F614; Thu, 11 Jul 2019 10:18:48 -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=NfLLGNygbO7UNn EyHSAuada45LA=; b=vcu9+9Z6OOPjP4DLAIHkYKaQGzDNH1cWqkUNg11IvtuG0u 20Z2o8QJ7fQaAzfaIFL/1fmHDApPo9aJlAWzcvmFLqIQyLe9RFXZWWkHop/6Ms5A mR84gcE9o1fOAwsClO6aoLnD0X9sQyY8OO8SRd/yq4alei3s6kq8xXNPGQrBI=
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-a25.g.dreamhost.com (Postfix) with ESMTPSA id 4977A7F615; Thu, 11 Jul 2019 10:18:46 -0700 (PDT)
Date: Thu, 11 Jul 2019 12:18:44 -0500
X-DH-BACKEND: pdx1-sub0-mail-a25
From: Nico Williams <nico@cryptonector.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Ted Lemon <mellon@fugue.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
Message-ID: <20190711171843.GM3215@localhost>
References: <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <20190710045202.GA3215@localhost> <20190710064451.GB3215@localhost> <06EF2608-038E-400F-86BA-34F57630B53F@fugue.com> <CAMm+LwjFgSK7DSaN2CpLxmL=PO22s2qjBvBHC48jH9UnFy8=wg@mail.gmail.com> <4d10d37c-f6cc-f818-6ecd-244f54e6512f@gmx.de> <0477F142-49A3-4BB4-A763-0BC90A3BF3C7@fugue.com> <34FAABF1-68CC-4433-B39D-6DA261ECFE66@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <34FAABF1-68CC-4433-B39D-6DA261ECFE66@tzi.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrgeekgdduudefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucfkphepvdegrddvkedruddtkedrudekfeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhenucevlhhushhtvghrufhiiigvpedt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RRgSOIGyRsuDzSDPWA79EfRMK34>
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: Thu, 11 Jul 2019 17:18:54 -0000

On Thu, Jul 11, 2019 at 05:27:07PM +0200, Carsten Bormann wrote:
> I think, more generally, there should be some support for the -latest
> convention (e.g., in idnits, or in xml2rfc that is currently spewing a
> warning).  I think it is a good thing to have an explicit action for
> actually spending a number.  (But the number of times I got that
> specific number wrong, only to be reminded by idnits, is amazing.)

-next would be nice -- all we need is a bibxml reference for -current
and then the renderer can lookup what the previous -XY was and just + 1.

v2.23.0 | Report a Bug | By Email