IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Mon, 02 November 2020 12:37 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 37B993A0FB0; Mon, 2 Nov 2020 04:37:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level:
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, 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 (body has been altered)" header.d=gmx.net
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 pVccDaoovuhE; Mon, 2 Nov 2020 04:37:47 -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 75A2E3A0F4A; Mon, 2 Nov 2020 04:37:47 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 46920F406F5; Mon, 2 Nov 2020 04:37:29 -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 D5EFCF406F5 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 04:37:27 -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=gmx.net
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 YDuRkRSffZbs for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 04:37:24 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by rfc-editor.org (Postfix) with ESMTPS id 9455FF406D8 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 04:37:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1604320658; bh=PJEwxgcWI9LiD4H55pYMVDAhYhJl6sJYE8QI19vvpiE=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=GK/HwmmPSDYLy15ph+HcmUHPgleQ5YaZA4rFwcHZ+ota0y1B+MoBv4ZJ0wOtoVW3Q oTWtRQ08O9SijgspR9xnPjUC81BX9cQWSefrXOzGcVitLiCaBgSZEfKUNk5JkTua5w NVCd6q/Gyp1OGkxrozbZ71O1GAzWe8+pFEq3e5S4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.236] ([217.91.35.233]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MQMyf-1kmP0V2PjN-00MNB5; Mon, 02 Nov 2020 13:37:38 +0100
To: tom petch <daedulus@btconnect.com>, rfc-interest@rfc-editor.org
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <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> <5F9FDB7E.1080805@btconnect.com> <ae44e31b-964a-7901-4883-72abb0dbb8d3@gmx.de> <5F9FF8EA.9020809@btconnect.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <bfa63584-1f49-1370-65d0-a217dcc4dbc5@gmx.de>
Date: Mon, 02 Nov 2020 13:37:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <5F9FF8EA.9020809@btconnect.com>
X-Provags-ID: V03:K1:6iZT7KunHHNeuDq5rcQa7PywzG4KeLX4819wOcghKPJDOowLDLf tLM8/LJkI9/5DJzB9ysl9OTBrkPepQkH90rUDpDFTsTQaHe7c+yk+GPb8eWvHhnLySIL+JT hoBb7CgGDkGmOspqmQz7n7bSic0WkGgAdAM0+1ctsAOm3SMxi9wuBTY2Hug/SCSbskF41em yZuEG2fI7OS/oryNTH20A==
X-UI-Out-Filterresults: notjunk:1;V03:K0:SZn+P55ogOs=:xX42yvLS6+OORrxGylkxiz Jg9iJooQbyB51uvqRp4lnAdHJxehWBu7WP+ukoU/tB7R5xxk6iLDTctCRNGV6cKPCJVVDdNmP liz6aizY/Syo1XLfzDQoCM88Y+B9RqjZycxBt19/3stPqx+PcXy/SMBvWboq5M3hXILKqBnBF ekXFXeYa4UJfuNEsh1iaIqgJ5GuAvKcbek3704klGYw24xp1KwRbdl8V3kblW5WWE46yTBV/Y xmLd3x++OVWoZ7YUFIr2SFjDSnEeO3bqJPxoa0xeF13WcWd5YXTBSF0OJsPESDlXJJ+bLL+DX HqgPr7MDp8BPuQ/BVN/7KWQQD/qROP5FJQjdtBlXXY32lPmiuqs0x2o9ewBj7Pxt+1wHZm7GX CtDEAa4ArU90Bg/GTjXY9tBZyD+LIkjZ277uOpVUdb3QXr4b91MgrEhstkbllU9wLOcXbdXkP yfRVtzXStTGGltF9MUF9+2G+VL5LrtsL3wWrwQuzb3EgkER+iae1NwHk48NWnpXpK1qFpn/Pw UqqmZkIKnpE1Hn5OLutc8MX82HLzfiNibb+b18XaaaBZWmmWC/SPtDX2F7ebrDTzogC3vl7yb vYjQZpZ//cE1dCBfAx9dGlpCVuMKgrFFEX7WZN0X7aXV/syAmHyZxWDVFFnYN5IrXKgS4oyWG +XTgKoHeAUQXz4vMMiJbaD6ILbzG810jePSNiGjhAvDN22jEujZmANY3zDfCdb82ZKAUXpJDt 0rOu5V9ynEJce9ZAKtMXiEoTq7bgAMdUHVluIR2Wt2Aoki10uNYOJ3S+WpaaHlMWX2ZtZgUxK cGE3mgzaTLX+yy0Op0xEKLd5o2XXzVf4olBM07TFJuqMERdKdM2UjdjGDua36U2+Oohe9swXN HtrlgolMtR3giIanTboA==
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: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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.

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

v2.23.0 | Report a Bug | By Email