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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 04 May 2020 20:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 445053A10A0; Mon, 4 May 2020 13:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iFU7n4cLBmZB; Mon, 4 May 2020 13:47:24 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 618533A104D; Mon, 4 May 2020 13:47:18 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id s20so268821plp.6; Mon, 04 May 2020 13:47:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=vGNN3bHZn3eTyDKBbkeAXpnDDA6hSpqbV3YnNQc/Kgs=; b=EC7SNhtU7SNZahjm7fCloccwrO1cGt6PMuXDjTB4KTEgHf/CX8rUAxnmS2fwse57KG YgCWieLdJGrk9/GTYF29WwDkIeWR9oSEbZiKg8OFyHV+QeZBXzN+rGVQRFSeQG497Sqd /vkJPGCznDR/cdwAtQtw00v3hRvUyQilbz6Jh4yQBEctcedSYZjR0Xb9tppv9Uy7/ptm NQC2iM2ENcE01rb4uvII2wR3xuFOTS9D0Ct3DiZs0GdY+Y4O+1mmxiC+9O7G1KLT+Xk7 Qf/clulvu/oSBEERQWoWRMngEvvbhHWkaxLrl6PgCVgjN/eYlPm1AqoQZpnrOeAn6mmm ZIgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vGNN3bHZn3eTyDKBbkeAXpnDDA6hSpqbV3YnNQc/Kgs=; b=Hgta06IHWssxVHIk1lz8JzyCyleXd1Qa8RDrfSDwllTZLNLXZMBqX3b89SMR+0ofWB 6W7Pj1i1XMcQGq/kRskgf1eb4qcVCLMdLgiaQp6u4+UxB/RFBOaABwT6nSzvcgKj+ed4 HQqr1qOM8MoAnbD5JH92wFcT11odmYyk4UnCwkpMxeRvHbn/Iad6+YVXUCXxb8geJfgl NAD4yyY52rkbwTtsVZqUPaKomuB+wkzUrBqTQsth5538yzYaElByxzpGQC9hYJTbGlSW g7/cYg/iIpzQuzlIQVsFlsgs7DcLt4YDfPG2ZiUuxZj8KNBEOKUMU4KCWS5cfEAqJRyB ICGw==
X-Gm-Message-State: AGi0PubkoME6Nnush9DzXpv9rJSM7cShZezbA/AUiJpqNDiuwAvRgWyf DiNDHPq9567eEtcUD5A3Ih3EXsW9vNQ=
X-Google-Smtp-Source: APiQypIYm29dB0dKIryjSspMlfUvacp2QIO2RUrw/a45e4WdSZ7SRQHjk9jc6t6Gf6cvD3Hm7/1TxQ==
X-Received: by 2002:a17:902:32b:: with SMTP id 40mr1015137pld.73.1588625237515; Mon, 04 May 2020 13:47:17 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.84]) by smtp.gmail.com with ESMTPSA id c4sm8354810pgg.17.2020.05.04.13.47.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 May 2020 13:47:16 -0700 (PDT)
To: Carsten Bormann <cabo@tzi.org>, John Bradley <ve7jtb@ve7jtb.com>
Cc: jose@ietf.org, Tools Team Discussion <tools-discuss@ietf.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: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2a7deac9-afaa-8a0a-face-fc889b5d62e9@gmail.com>
Date: Tue, 5 May 2020 08:47:11 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <EF1F3CC8-9D69-4892-A05B-A3E48A9EEBE7@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/KLU44uhf8m5UGEUQfOW1s2lXx90>
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 20:47:32 -0000

An even SmallerMOP is to add a disclaimer to the info block at the head of
each HTMLised RFC. Fixed it for you:
https://www.cs.auckland.ac.nz/~brian/RFC7515x.html

Regards
   Brian

On 05-May-20 02:53, 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
>