Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?

"John R. Levine" <johnl@iecc.com> Sun, 01 November 2020 01:38 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 A616D3A0C8A; Sat, 31 Oct 2020 18:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=iecc.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 pifoamBT1Bar; Sat, 31 Oct 2020 18:38:52 -0700 (PDT)
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 BADC63A0C88; Sat, 31 Oct 2020 18:38:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 30F32F40723; Sat, 31 Oct 2020 18:38:36 -0700 (PDT)
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 D9E25F40723 for <rfc-interest@rfc-editor.org>; Sat, 31 Oct 2020 18:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com
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 xfkPnTezKEOd for <rfc-interest@rfc-editor.org>; Sat, 31 Oct 2020 18:38:31 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) by rfc-editor.org (Postfix) with ESMTPS id 316CBF40721 for <rfc-interest@rfc-editor.org>; Sat, 31 Oct 2020 18:38:30 -0700 (PDT)
Received: (qmail 56568 invoked from network); 1 Nov 2020 01:38:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=dcf6.5f9e11a4.k2010; i=johnl-iecc.com@submit.iecc.com; bh=vXCdQkxxKq1kPtZfIte5eW5D89XvfpaHIe9umNhin2w=; b=kXpBSyWdBu27NoKX4tts6DZblovXzbwRIku7pv7IKNUOu3uQ8aAmvWFnxZQmFypQef4mibbgsr+qhzT6Fv2c8mXmfEHHz9/AIxSx0MoyLelTzqDdrLUe1iYrKCK9jSVfW+UMHGn4s3XJXGGJ5j5ftlwPVm+MS63bZLro2ieDTwBkJP8q3TYoJgeQqVcbn9iSB3nYUxfiYbruR4oa8NF7H93OXAQQ8G5sbch3Uz3Igo9KXG7u/gmdGWitmatcm2cYp6vDW6bpRQPtN11Z/P8DUhnC6ixnqOt6LNtORHabi9XzHgXQPpWo9l0qWyJ842kgu5enOErQQGZR/BWCbusFDA==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 01 Nov 2020 01:38:44 -0000
Date: Sat, 31 Oct 2020 21:38:44 -0400
Message-ID: <26d1ff54-777f-884b-e35-d91e9fe59662@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfc-interest@rfc-editor.org
In-Reply-To: <e8554ea2-1849-279f-733d-5798de8817b9@gmail.com>
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <CADaq8jdSeTDWy_0fCV25ykxKFMV1ZBtUMMNesoOuaXCzFVfpOA@mail.gmail.com> <D2D0455D-8D6C-4A19-ACAE-4DD972D83DC1@bluepopcorn.net> <20201028164053.GB12700@faui48f.informatik.uni-erlangen.de> <263C265C19B24BA97AF48934@PSB> <225062D7-C061-4543-8665-53A4F4831510@isc.org> <20201029005519.GT39170@kduck.mit.edu> <A05242FC-C38C-474F-A2AC-412329CA5C52@isc.org> <CAKq15ve-kAFZWH_f7=1XXC5PfxvO-sAzppB1fVTyqUufLftkVg@mail.gmail.com> <D2DB703DBF2A44A19B8F80DD@PSB> <CAKq15vdFVkG6_grNtqUqq-yDwj9QQcHJFZB5+RB-8fdxQXhFSw@mail.gmail.com> <fa36e919-b1a0-5b3c-9b42-54c6fdaadfb@iecc.com> <e8554ea2-1849-279f-733d-5798de8817b9@gmail.com>
MIME-Version: 1.0
Subject: Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?
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: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On Sun, 1 Nov 2020, Brian E Carpenter wrote:
>> See, for example
>>
>> https://tools.ietf.org/rfc/rfc793#section-3.1
>
> For a while now, as a reviewer I have been trying to remember to use something like this in my reviews:
>
>  Section 3.1 (Header Format):
>
>  > Note that one tick mark represents one bit position.
>
>  Please use a more accurate description than "tick mark".
>  There are no tick marks in the diagram.
>
> I know from experience as an XML author that I can find "Header Format" trivially, but finding a section number is fiddly & confusing, especially if a draft has recently been reorganised. Much the same goes for page numbers, if the author is using a different format than the reviewer, which is increasingly the case today.

I think you may be confusing fragment identifiers in URLs with textual 
comments.  My point was that if you want a mechanical reference to a 
section in an RFC, the RFCs we publish now have them.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest