[NNTP] Additions to LIST commands

[Julien ÉLIE]

Hi Antti-Juhani,

> And in any case, I'm a bit wary about adding unimplemented features in
> standards, even though a Proposed Standard is allowed them.

But then, I still do not understand how I can write an extension for
LIST REMOVALS.

RFC 3977 mentions:

   An extension is a package of associated facilities, often but not
   always including one or more new commands.  Each extension MUST
   define at least one new capability label (this will often, but need
   not, be the name of one of these new commands).  While any additional
   capability information can normally be specified using arguments to
   that label, an extension MAY define more than one capability label.
   However, this SHOULD be limited to exceptional circumstances.

The capability label is LIST.  It already exists!


Is is true that LIST HEADERS is normally added by HDR, and LIST OVERVIEW.FMT
by OVER.
What for a new LIST variant only, without any other base command?


Should we write an erratum for RFC 3977 so as to permit extensions
without new capability labels?  Or am I missing something?

-- 
Julien ÉLIE

« The hardest thing is to go to sleep at night, when there are
  so many urgent things needing to be done.  A huge gap
  exists between what we know is possible with today's machines
  and what we have so far been able to finish. »  (Donald Knuth)