MIME-Version: 1.0
References: 
 <177998398970.1375095.10612660864397706714@dt-datatracker-5b4c8598b5-4ztf9>
 <000f01dceebf$d36c5a10$7a450e30$@sahollenbeck.com>
 <27162.11117.122681.26715@fireball.acr.fi>
In-Reply-To: <27162.11117.122681.26715@fireball.acr.fi>
From: Ruth Trevor-Allen <fleeblewidget@gmail.com>
Date: Sun, 31 May 2026 09:23:18 +0100
Message-ID: 
 <CAAVKzhF0O=bcLLjycHsBGWVYWid6BKFrUn-0JJaiTZXMyCw=rA@mail.gmail.com>
To: Tero Kivinen <kivinen@iki.fi>
Content-Type: text/plain; charset="UTF-8"
Message-ID-Hash: ZXWGDXKOM7R5EWMIR3YUJWGFK4Z6YINF
CC: Scott Hollenbeck <sah@sahollenbeck.com>, secdir@ietf.org,
 draft-ietf-regext-ext-registry-epp.all@ietf.org, regext@ietf.org
Precedence: list
Subject: =?utf-8?q?=5Bregext=5D_Re=3A_draft-ietf-regext-ext-registry-epp-07_ietf_last?=
 =?utf-8?q?_call_Secdir_review?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/regext/O2J7dtzjg_ao_c9yEJ0P5qVNNxA>

On Sat, 30 May 2026 at 01:13, Tero Kivinen <kivinen@iki.fi> wrote:
>
> Scott Hollenbeck writes:
> > > In addition of those two bigger issues, there are several cases
> > > where RFC numbers are used without any useful title or text
> > > describing which document they refer to. This makes it harder for
> > > the newcomers to read IETF documents, as to be able to read a document
> > > you first need to have the mapping from 10000 RFC numbers to the
> > > titles of those RFCs. To make documents easier to read for people
> > > who are not experts in that area (i.e., who do not have the RFC
> > > number mappings memorized), add short title before referencing
> > > an RFC. The RFC number can still stay in the actual reference
> > > link.
> > >
> > > Below is the list of such cases in this document, and proposed text
> > > to correct those:
> >
> > [SAH] I'm going to defer to Med for this one, too. In my experience
> > the RFC Editor commonly accepts citations as currently found in the
> > draft.
>
> RFC Editor do accept citations in that format, but that does not mean
> it is good idea to have citations in that format. When we only had
> 1500 or so RFCs published when I started participating in the IETF, it
> was mostly manageable to learn mapping from each RFC number to the
> actual contents, especially for your own area.
>
> Now when we have 10000 of those, at least my capability is not large
> enough to be able to map them in my head, and adding few words while
> writing the document (i.e., some kind of title) makes reading the
> document much easier. The title does not have to match exactly to the
> RFC title, but it should be something that gives reader good
> understanding what that RFC is about.
>
> I do hope even this document will have more readers than writers, so
> overall time saving will be there...
> --
> kivinen@iki.fi
>

Hi both,

For what it's worth, as a comparative newcomer to the community, I
find Tero's suggested wording much easier to process - I do spend a
certain amount of time flipping about following references in order to
remind myself which number maps to which concept.

Ruth