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

tom petch <daedulus@btconnect.com> Tue, 03 November 2020 11:36 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 CA0083A03F3; Tue, 3 Nov 2020 03:36:13 -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 SYb-Bwa0_J-O; Tue, 3 Nov 2020 03:36:12 -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 03ED63A03F1; Tue, 3 Nov 2020 03:36:11 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A1312F40714; Tue, 3 Nov 2020 03:35:52 -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 96452F40714 for <rfc-interest@rfc-editor.org>; Tue, 3 Nov 2020 03:35:51 -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 O6-HAHqCVJeP for <rfc-interest@rfc-editor.org>; Tue, 3 Nov 2020 03:35:47 -0800 (PST)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2139.outbound.protection.outlook.com [40.107.20.139]) by rfc-editor.org (Postfix) with ESMTPS id 9D014F40712 for <rfc-interest@rfc-editor.org>; Tue, 3 Nov 2020 03:35:45 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bANBZrhELigYUCxOlbvGDplt7uS3aJr6aWh915GfzjX+Jzi385Qg7NHCbRtLmG9OAblod2zB8NfGoAAx5fbZod6U5oNriilXj3B9rbMjwaLXuiyBc9Kheclls1t7rendPTYUaXYsZJoE1s70GTj6ZqDDY+rAhX5GbT6akN4kuTQOMZd0w0NVEV8fOC3826q7MsiP5bvWC5i0efg29Fx3apNj0X17yLbFGgKjd1OPMJ8cwrpCdlQtNLtT3MYgDsli4KAMrnZ1JLXdjTGqBIVBO5nUmF9LpOPPpiFMMncg/Tgj2R6THtBPfSFvP5NPGk4JZAzOR09oH/YLrjTv3s+oSQ==
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=5Vtd/QWYR9k5Mz+p+a5O/8eqZHAyFLlG0f3dT14SREk=; b=PI1Wu3otGx7eHAFWZ+pHriHOhX5qYyDDtzWqbxMG9l1jl6EKRrmaexLnRMuQPM4pORSxTTzWsDR7EfMMucZ17S11wbsEpv4JB0HHWaxpXJxfrxBAD7ZfBpWeViG0pxqDAUTenYTalVXJSv7FSGaHNw/wbcAKFiMOAYI7X9jQS+Nv4Wx9Qo5EiYplbj4I+CXltBSwG8I/31dBtewRA4FLaFMpDzbZHkyK869+VvKsoM5fQ6o7sSbWTEycdwGcBbn9gEC47wu7wHS0QQ4yJAjFVqYg4s1lbKimWohl3WqwaM7aLie8ZCmbssCBD7Ds8qV/jHMqLWAqHgTamaGpikAtMw==
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=5Vtd/QWYR9k5Mz+p+a5O/8eqZHAyFLlG0f3dT14SREk=; b=WN5FAIZI9R+iooe/DhuNVzp7GDlPqZfHocrp4fLKc8N8qmpF9NJW2AlAObJdURHtiq8yQqA+kyS8qJroy6j9Op0dnD6bHcQN91z1s5I7AAxKRX0xpKD2hbbO8Ww/e7nDJBGLvuwPVCLbR3YZnDgVaGWS/hkfDuQdGExjwFJri2U=
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 VI1PR07MB6591.eurprd07.prod.outlook.com (2603:10a6:800:188::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.10; Tue, 3 Nov 2020 11:36:02 +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.015; Tue, 3 Nov 2020 11:36:02 +0000
To: Julian Reschke <julian.reschke@gmx.de>, rfc-interest@rfc-editor.org
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <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> <5F9FDB7E.1080805@btconnect.com> <ae44e31b-964a-7901-4883-72abb0dbb8d3@gmx.de> <5F9FF8EA.9020809@btconnect.com> <bfa63584-1f49-1370-65d0-a217dcc4dbc5@gmx.de>
From: tom petch <daedulus@btconnect.com>
Message-ID: <5FA14097.1000305@btconnect.com>
Date: Tue, 03 Nov 2020 11:35:51 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <bfa63584-1f49-1370-65d0-a217dcc4dbc5@gmx.de>
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO2P265CA0096.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:8::36) 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 LO2P265CA0096.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:8::36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.18 via Frontend Transport; Tue, 3 Nov 2020 11:36:01 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 5a8eb827-2763-4917-ebcb-08d87feca443
X-MS-TrafficTypeDiagnostic: VI1PR07MB6591:
X-Microsoft-Antispam-PRVS: <VI1PR07MB659175C477DB6C13542A98D3C6110@VI1PR07MB6591.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: FWBVmuHf70yTM5RN79scjoA29+zvliSbvv7WyogNazzlxKtAfFFXLhqw0Dbzdp6x99bKNjov3ATA27U7GmbQHkLRRYnaCKih82r56gP4SkIizkPOBokWp0ZR/5G1QSh4UGnl3DFypj/7/z3/2BiJje0RhC7E6HkLvZfZjkydAhqHt7szx5QjWz7Df5RjGkLRxTNttjX3KCvsegxfPgUrKBHMvFQM00xmrbsvagty9SqB8FipQUKKyDXb8H3gthZN05T9as1MbpCMcnbFpmjvM+CyRmImeLMh+/HjNYLcMURC3Q3H4SQJGYdZNjtt+Nl/9Ryri9nEzrJ8YxE+NMj+si0MGrZpUUQAKRVvi+wFmGMc0Kaw5QL8TOcz5T3cXLk+SqHmdyvKxOismw6gjOehRg==
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)(376002)(39860400002)(396003)(366004)(136003)(16526019)(26005)(186003)(87266011)(52116002)(16576012)(53546011)(6666004)(316002)(6486002)(83380400001)(86362001)(8936002)(2906002)(2616005)(478600001)(956004)(5660300002)(36756003)(66476007)(8676002)(66946007)(33656002)(66556008); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: V708Tz+tzmymCaDh9YUOfRXYmAYtnh8PHakBFADuIRegxmTMJcGZa5PVunD6GcVtz3QNrIYc3kCipoKjxtPmwo3H5IdWjTo13BzBRPqx7Aj70Kmq40VFazHtEFb4p/qOeJf9potXJL/8/fyH6/0OGgA1RhRReAUQmtDT9CfwSvV1aGvKP7nvI65+lpxJC41rSqnjq68cMX/ReE7ohptzaerAmEEjkwH5vRLPUXnybfgqDos/zgbOXS3Zedpe7qf/NZEVGgRRukk4wfS2TlbYdJZncf5uzsUzavK99VYhra+qavZq/n5GgyddQbWch8lCY8QhdQMkkYoTWEOJvIfc4jAEokDLWEAsycOogFbri+VM+6LFqm6+dVfX90iMm00QaFcHYyfM10G1ICmCOr06fjxH/QZlgC8YPBYR3itF5wMPKgpldujP+5uewcRs2Kyee+07VYPAfL3RpN24f4GlTK+XZwMoOPdxvSDqW1C6cYT82FttG4BVSSSHjrXxctwgAieTOwalkTxTAxNYAfq5JoKgF6kDtUpFE3HpqwqPiLkczpdYQUW31GXJdhCyS7xuuXD2H9k2+vP8mDrkrysnsUe6e9RFQSbvyxRJzHQscJj16jAGBs1x2EqXVSBeArJOXm/LzL1ieWtb9roOOoJPyA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5a8eb827-2763-4917-ebcb-08d87feca443
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Nov 2020 11:36:01.9750 (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: k3Zy6g2XQZ2huvl+kxuFfOWWTD1N2tDuPkWiwKiM09FIubyPVQD3JsG7ZmzbgRB/ny4YNzAC2S+4CrsEWqu1Nw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB6591
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>

<inline a query on v3>

On 02/11/2020 12:37, Julian Reschke wrote:
> Am 02.11.2020 um 13:17 schrieb tom petch:
>> ...
>> It is like writing anything in code, modular is better than spaghetti,
>> but there is a limit to how far that can go without creating a spiders
>> web of interconnections between modules.  The i2nsf I-D I just looked at
>> is 55 pages split into three modules and I would not subdivide it any
>> further.  YANG modules must be self-contained and comprehensible,
>> independent of the RFC they come from so in a well written one, a large
>> part with be text description; and the whole idea of YANG was that it be
>> text-based, unlike the binary encoding of SNMP, so you have text
>> identifiers, type, references to RFC, IANA etc.  It all mounts up.  Five
>> pages would be very small.
>> ...
>
> I'll assume the example is
> <https://www.ietf.org/archive/id/draft-ietf-i2nsf-nsf-facing-interface-dm-10.txt>?
>
>
> What you could do now: split the module into top-level artefacts and
> place them into separate <sourcecode> elements. These can have anchors
> the split tool could generate. Thus each of the pieces would have an
> anchor you can link to.
>
> What might be desirable as xml2rfc feature: the ability to add line
> numbers to <sourcecode>.
>
> I do understand that both would interfere with extraction code that has
> been written for plain text, but that should not be needed/used anymore
> in the v3 xml world anyway.

That I do not understand.  What is different with the v3 xml world that 
the extraction code is not needed?  And is this also true for the checks 
that are performed on YANG modules that they 'compile' ok which I think 
are done automativally when a I-D with a YANG module in it is submitted 
(it is a while since I submitted an I-D with a YANG module it it)?

Tom Petch

> Best regards, Julian
> .
>
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest