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

Robert Sparks <rjsparks@nostrum.com> Mon, 04 May 2020 15:19 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D0E3A0A22; Mon, 4 May 2020 08:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.404
X-Spam-Level:
X-Spam-Status: No, score=-1.404 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.275, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 XV54La0-R6ot; Mon, 4 May 2020 08:19:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 F181D3A0A1B; Mon, 4 May 2020 08:19:03 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 044FJ0QF074296 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 4 May 2020 10:19:01 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1588605542; bh=tuaL+xp7X47canVBo6oNVr/smSDNC6b9IKzbBkS2g9Q=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=hVz/3gG/VyxY5iw+AngN7yipUrMXkFtIdReDws6xc8VqfXBDrBDyR3ZLmyuIOO6A/ xpaCuliY/3KAiHm08kohO6Zk7MwTt5yfu6o8q3jgMyhpN8jHsqRA8u7it45cxF2dqm wiM19Bm2Ck3cwuMIZnxp8Jaz6isYXsvIzNyBF7lU=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Carsten Bormann <cabo@tzi.org>, John Bradley <ve7jtb@ve7jtb.com>
Cc: jose@ietf.org, Tools Team Discussion <tools-discuss@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.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> <EF1F3CC8-9D69-4892-A05B-A3E48A9EEBE7@tzi.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <2638adfe-23ee-be15-d952-5a16d56243ab@nostrum.com>
Date: Mon, 4 May 2020 10:19:00 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <EF1F3CC8-9D69-4892-A05B-A3E48A9EEBE7@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/CCWcYB3kfZSPM0WOZ7iYSLfoi9U>
Subject: Re: [jose] [Tools-discuss] [Editorial Errata Reported] RFC7515 (6118)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 15:19:07 -0000

Hi Carsten -

How is the SMOP you are envisioning different from the inline-errata 
tooling?

See https://www.rfc-editor.org/rfc/inline-errata/rfc6016.html or 
https://www.rfc-editor.org/rfc/inline-errata/rfc8400.html for small 
examples.

https://www.rfc-editor.org/rfc/inline-errata/rfc3261.html#btn_1051 and 
https://www.rfc-editor.org/rfc/inline-errata/rfc3261.html#btn_1470 show 
placers where the errata could be algorithmically applied directly to 
the text.

RjS


On 5/4/20 9:53 AM, Carsten Bormann wrote:
> 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
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
>
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org