IETF Logo Mail Archive

Re: [xml2rfc] Embedded lists in V3 syntax

Carsten Bormann <cabo@tzi.org> Tue, 27 April 2021 09:58 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C933A0BB0 for <xml2rfc@ietfa.amsl.com>; Tue, 27 Apr 2021 02:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 v0KbTTMDEls9 for <xml2rfc@ietfa.amsl.com>; Tue, 27 Apr 2021 02:58:36 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DDCD3A0BAA for <xml2rfc@ietf.org>; Tue, 27 Apr 2021 02:58:36 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FTxzX1ZT2z13tf; Tue, 27 Apr 2021 11:58:31 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <d50ca4fe-0bfd-bf15-c49f-a21368819c97@gmx.de>
Date: Tue, 27 Apr 2021 11:58:28 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 641210307.955323-2d6abf7ddf121910518c3f4e93f61abf
Content-Transfer-Encoding: quoted-printable
Message-Id: <A783282F-47C3-459F-9CB3-D68F41D68E2C@tzi.org>
References: <B82E621C-0475-42BD-BFE7-C3717A2DDACC@orandom.net> <d50ca4fe-0bfd-bf15-c49f-a21368819c97@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/fmEr8DmqEXvAueDUfXd1WWY5SeE>
Subject: Re: [xml2rfc] Embedded lists in V3 syntax
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 09:58:41 -0000

On 2021-04-27, at 06:16, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> 7991

RFC 7991 is an important historic document, in particular since it marks the last time we actually finished a process leading up to a specification on the emerging RFCXMLv3.

However, it is often a misleading document when discussing what RFCXMLv3 is today.

I wish people in the know would stop referring to RFC 7991 (except in that historic role), and that the documentation that is accessible to RFC authors would deemphasize RFC 7991 in favor of documents that are closer to the reality of RFCXMLv3 [1].

Grüße, Carsten

[1]: https://xml2rfc.tools.ietf.org/xml2rfc-doc.html

v2.23.0 | Report a Bug | By Email