IETF Logo Mail Archive

Re: [rfc-i] New blog post on RFC v3 XML Issues

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 29 December 2020 17:35 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD51A3A00C9; Tue, 29 Dec 2020 09:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.628
X-Spam-Level:
X-Spam-Status: No, score=-1.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_BLOCKED=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 FEFr1Y9sJPKF; Tue, 29 Dec 2020 09:35:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 200A03A005D; Tue, 29 Dec 2020 09:35:56 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0E7FBF406DA; Tue, 29 Dec 2020 09:35:27 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 5E92AF406DA for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 09:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jc8OCv_3uPnj for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 09:35:22 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) by rfc-editor.org (Postfix) with ESMTPS id 9124BF406D1 for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 09:35:22 -0800 (PST)
Received: from [10.10.10.227] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 0BTHWd76084406 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 10:32:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.10.10.227]
From: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: rfc-interest@rfc-editor.org
Date: Tue, 29 Dec 2020 09:35:48 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <F3146E45-F5E6-46B6-8C71-BDFB69FE4C39@vpnc.org>
In-Reply-To: <5ae2e371-3b8f-6235-0303-b8f79e3c539e@gmx.de>
References: <7AAF25E8-F82A-46BA-BFDC-327DF38A0E46@ietf.org> <5ae2e371-3b8f-6235-0303-b8f79e3c539e@gmx.de>
MIME-Version: 1.0
Subject: Re: [rfc-i] New blog post on RFC v3 XML Issues
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 29 Dec 2020, at 7:06, Julian Reschke wrote:

> Am 04.11.2020 um 22:50 schrieb Jay Daley:
>> The Temporary RFC Series Project Manager (John Levine) produced a 
>> document on the RFC v3 XML Issues which I’ve put up as a blog post
>>
>> 	https://www.ietf.org/blog/rfc-v3-xml-issues/
>>
>> Jay
>> ...
>
> For the sake of accuracy... The blog says:
>
> "The author of RFC 7991 and I are slowly updating 7991bis to document
> the actual vocabulary that xml2rfc accepts and that RFCs use."
>
> The author of RFC 7991 is Paul Hoffman, and he did not participate 
> since
> autumn 2019.

Julian is completely correct here.

> I myself (author auf RFC 7749, not 7991) did participate for a few
> months this year, but I have been mostly inactive since early summer 
> as
> I didn't get the impression that we were actually getting where I 
> think
> we should be going.

And probably here.

> (In the meantime the last draft dated March has expired)

And here.

--Paul Hoffman
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email