[regext] Re: draft-ietf-regext-ext-registry-epp-07 ietf last call Secdir review

[Tero Kivinen <[e-mail]>]

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...
-- 
[e-mail]