Re: [Tools-discuss] [jose] [Editorial Errata Reported] RFC7515 (6118)

Carsten Bormann <cabo@tzi.org> Mon, 04 May 2020 14:53 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971E03A09F1; Mon, 4 May 2020 07:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 f3zoqcLXapcD; Mon, 4 May 2020 07:53:17 -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 E138D3A098E; Mon, 4 May 2020 07:53:09 -0700 (PDT)
Received: from [172.16.42.112] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (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 49G5Sg3MqJzygP; Mon, 4 May 2020 16:53:07 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <b2cb80a5-aa20-491b-791a-1b368c54525f@ve7jtb.com>
Date: Mon, 4 May 2020 16:53:06 +0200
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Tools Team Discussion <tools-discuss@ietf.org>, jose@ietf.org
X-Mao-Original-Outgoing-Id: 610296786.810202-e013359493f4d6afcd5439acd1a21cd9
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF1F3CC8-9D69-4892-A05B-A3E48A9EEBE7@tzi.org>
References: <20200422200954.2B867F40729@rfc-editor.org> <00e601d618e3$dfd06e30$9f714a90$@augustcellars.com> <CAANoGhLDiq1jcTBQo1PDpXu-3MeD0U5Qx0sNhB2ZdmpRcW-G+g@mail.gmail.com> <FD2113D1-F25A-4D00-A8F5-18757852703A@tzi.org> <b2cb80a5-aa20-491b-791a-1b368c54525f@ve7jtb.com>
To: John Bradley <ve7jtb@ve7jtb.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/jTzZm8oifBBooLPKZ4EbX5e3DkM>
Subject: Re: [Tools-discuss] [jose] [Editorial Errata Reported] RFC7515 (6118)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 14:53:21 -0000

On 2020-05-04, at 14:31, John Bradley <ve7jtb@ve7jtb.com> wrote:
> 
> It may be possible to improve the tools, however TEXT to HTML has been a
> issue for a long time.

Yes.  And the SMOP below solves that problem nicely.

> The exesting TEXT RFC 7515 won't change.  

It doesn’t need to (as long as it is read by a human).
The issue is that the htmlizer’s heuristics only have limited AI.

> Perhaps the HTML rendering
> will imporove, but our best bet is still the impovement in the nomative
> version to be something other than TEXT.

Which is already the case with the RFCXMLv3 transition.

> In any event nothing that a eratta to RFC7515 can help with.

No, but the report is still useful as the information in it could go into the database the SMOP uses.
I just picked this specific report for responding as it is number N+1 of the same kind, where N is the number where I’m finally losing the patience needed to ignore the problem.

Grüße, Carsten

> 
> John B.
> 
> On 5/4/2020 2:00 AM, Carsten Bormann wrote:
>> [On the usual problem with htmlizing links to other RFCs:]
>> 
>> On 2020-05-04, at 02:30, John Bradley <ve7jtb@ve7jtb.com> wrote:
>>> One day this will be fixed for new RFC but not for existing ones. 
>> Why not?
>> 
>> It would be a SMOP(*) to invest the htmlizer with knowledge about misdirected links that were discovered in existing RFCs.  Each of these errata reports (and all the existing rejected ones) would inform this.
>> 
>> Grüße, Carsten
>> 
>> (*) SMOP: Small matter of programming.
>> Usually said by people who don’t want to do the work themselves.
>> 
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
> 
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose