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

tom petch <daedulus@btconnect.com> Mon, 02 November 2020 10:12 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 5E4573A0D8C; Mon, 2 Nov 2020 02:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.696
X-Spam-Level:
X-Spam-Status: No, score=-2.696 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, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=btconnect.onmicrosoft.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 9xPevl-cbgOT; Mon, 2 Nov 2020 02:12:38 -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 BF65A3A0D84; Mon, 2 Nov 2020 02:12:38 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B6CC7F406F5; Mon, 2 Nov 2020 02:12:20 -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 C678BF406F5 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 02:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 UXshq87TKmNQ for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 02:12:14 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30113.outbound.protection.outlook.com [40.107.3.113]) by rfc-editor.org (Postfix) with ESMTPS id B7767F406D8 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 02:12:13 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oeWfGxi/Cy3DmetGqKc8WyTgYUC4A1YqJh/kRS3dpm1IJuR+IS2+1yRdTnZel18VBno/2zhn2q0dYnhh/sW2xFbAQMTnTVSPxru4CKYCoYhs5P+gITL1jN7oFBO441Zva+qo9NEGwM2TNqmpShYRfKvfudoqehBQtV+gn8jMO7ug4QEZYNo5/sv5Tb89kiSaQuROuFSkaTO/HVo4pCFX3o+ge2rQFFF0tiBVqnTfH0KIJNryOU5Kjkvmj+ZNrrkKbiOtRaUCpA4Vodpf8PCaPxFQRh+ZgboiwlvnWTeCA7JTyaPqDAZ8q3RH5S1Zfys+0zF/a9xEMgwvS2ffYqu9Jg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jbBfiSTvyEE0k4hRP62LcsS37Vz+2v24CuPtDo1DMDY=; b=UJE8RJ3JtS9kV321eRQw28LQpLzsg5YdGpMk3eUZI6D3Auc1N9jwKeMrlXzDqjGOaRw2o3+tdQ7cYAUiCIIpmldx5emRKimwMtzs82QRqPvKdeGSh+yNqZvtQC5cNZNRBZyvFZi81C50k+RaVlZ7CL4XVlXGMlCUNyeHmN+N7sDQQNN5EoX9cq3LI9IqGgI0jOsSYGG+viCjRFvDFmAxq8+0CjhrRXPC8ECLbbzyUGuFHBr1+BN+rvPVGx9bNgBR0Mb1n7fCDrK4smpdfScmvskus3fOvLh9eDpFmnnttDA6KL6GddsnHCiAHNwSw+GW9p8zspFlt/LvGP41EOkZzA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jbBfiSTvyEE0k4hRP62LcsS37Vz+2v24CuPtDo1DMDY=; b=TBQNfgN1O68M5PI5gLQR7MO8sZUG/PbI4MjsyEhWw4y6oTC3PO+ouzTOEnF9tWpSlLtc8I7k+7y9R9HPs8FyoGAP5fDV191bq9zEKVNKeA4j3GI5S7Yx98DscGXBWmu0dQobHiLasScluNkX56PTp71uy58Db0/g3rzPvyHJDr8=
Authentication-Results: rfc-editor.org; dkim=none (message not signed) header.d=none;rfc-editor.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB3085.eurprd07.prod.outlook.com (2603:10a6:802:21::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.10; Mon, 2 Nov 2020 10:12:24 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6407:6ea2:f517:eeae]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6407:6ea2:f517:eeae%7]) with mapi id 15.20.3541.010; Mon, 2 Nov 2020 10:12:24 +0000
To: "John R. Levine" <johnl@iecc.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, rfc-interest@rfc-editor.org
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> <26d1ff54-777f-884b-e35-d91e9fe59662@iecc.com> <00a1fc15-7559-96c6-7cd7-3ae5afd62237@gmail.com> <a34f219b-7c76-4b48-4844-5af3cd4f344@iecc.com> <be8dce95-2b4c-52c8-7eda-8a9b127a6dd4@gmail.com> <cdc14c1-54c9-5273-584c-ddb656912952@iecc.com>
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F9FDB7E.1080805@btconnect.com>
Date: Mon, 02 Nov 2020 10:12:14 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <cdc14c1-54c9-5273-584c-ddb656912952@iecc.com>
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO2P265CA0001.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:62::13) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO2P265CA0001.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:62::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.19 via Frontend Transport; Mon, 2 Nov 2020 10:12:23 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: c765ed6e-e429-4f25-8d33-08d87f17cb0f
X-MS-TrafficTypeDiagnostic: VI1PR07MB3085:
X-Microsoft-Antispam-PRVS: <VI1PR07MB30855BF8A3AA4C59D789B14CC6100@VI1PR07MB3085.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: ZkyUt0Js0WTRRP6eQBT07Zfy2f6m0vPfFNuP99+r21cb9LYRZ0iogW+lGpOkeI05WB7PpG6eSGjSqGVmDXs+qbW/QZm7aopo+3jWfW16z+tJb1nQ2VDxb+q/VMLBpWL29ISx0nsFbDptOFOa3CpjPAvF6gbqR5sjUEYtfP6MWDM8EJm7kRwBYodD74l00eLC/NMl5hVR7GdegCliCC4VBMHAfKIMJX8uyhuaqwfQMe+NrmvagW5LQs4pIg4ATinnf6mg8Ogvyd8jmxUbBbrxiFR4DQ5717s/GoMKctyYmde2axaTjiRybf2LmFLfjrnDyO+gRGzBg0+OvQNxGB89Tro+w6ANTh1z4ecYc4iwy5ZUcljPE3LeN2Nly8xnv/QrePL8AjV6QlGRdODhJaYy9ojWrCtYmP8KRyp0i6Tl7xTdaFs4PQwoSx1ZZjUTg61RRMfhuFBld/LOAs6LZJOw8g==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(136003)(366004)(39860400002)(396003)(376002)(16576012)(956004)(26005)(16526019)(6486002)(2616005)(110136005)(186003)(316002)(66574015)(5660300002)(6666004)(478600001)(8936002)(2906002)(53546011)(83080400002)(87266011)(966005)(33656002)(36756003)(86362001)(8676002)(52116002)(66946007)(66476007)(66556008); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: 3ufPJSOT5l4+bB+O6nHIGEF4KAXVdkfuxrwT3cfuB2VrZbf3CfeS2kbF24xyaMVN44iqH4PiXSlJDU97S6YVcb8YaRI9N9EdKHAi09AuoYwIEDP4L2DutrLB2jlqrVMB/Ne57WcCtgVIHMXqYGy2PYEcFswmCM5nN3fNW/LhD36ZljFOTGF9DNKVIiWR4x3Bjq0d4iYB9sx/1coN6e0SxsweGUknfhz1XUU5J2RtTCGrK3ctOgHd+oGvD2/9qeNbVKpZd588OdBqgZFwGIkGKoFNkwywnO7ILmAv/DUzKe7dJINYXurpU0YmkBHFE4VY+TPmE2bUwiZHCm9AOQJMivykJpoThbP7ssYLCsxy7ux/0AKzAOigH1BRT/ffF+vyPhJvN3+7K24YsrH6wzQKGACSJgpk67D2ltlD6cMIskq+jOALaGs+1LQKHS9DfwL0RPiA9yHAlRQ0l+E2EAkc582UhD33TcEP9QwqwaxjD7mbj99fuOARPNvYdrNC1ERmJ139+5fwY6duxUBUdOjpvWCz/rwUuXsP3XB/gT/qsM1venuiGXpz2y7BAQ3IntzXIFKYxynwEVe96bZjPqQRcTGowVjVa7paGNtwUOb8p4+GLbRZBjFQ9oh+25xrUHrD2zc06ToA0qnr6PDoNlkgXQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c765ed6e-e429-4f25-8d33-08d87f17cb0f
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Nov 2020 10:12:24.3472 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: BEdJ33gwhiOOYzaRaWTpGtq59rS1WVWoJAKh3xLvE97HX1eUmtGmOJ8IobrG1tEeDYiqirq+7JaQ79qY3Smmaw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3085
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 01/11/2020 14:59, John R. Levine wrote:
>>> What formats do you believe don't have section numbers?  They're in all
>>> three rendered formats and in the XML as tags like "section-3.1".
>>
>> They aren't in raw XML and they aren't in kramdown, so they aren't where
>> an author needs them when processing comments on an I-D. (So, strictly,
>> that isn't an RFC format issue, but it is an issue created by our format
>> choices and it's quite an annoyance.)
>
> Sounds like yet another thing that could be improved with better
> tooling. Adding and updating comments with section numbers isn't exactly
> rocket science.

YANG modules do not have section numbers and can be 50 (five zero) pages 
long and the same identifier (e.g. 'status') can appear multiple times 
in different branches of the schema tree and the tree can be over 10 
levels deep so providing the absolute form of the identifier of the leaf 
that you are commenting on can take more than one line.  Reference by 
page number is so simple (even ADs use it:-).

Tom Petch

>
> 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
> .
>
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest