Mike,
I think there are a couple of factual mistakes in here, though I don’t
think they’ll change either of our opinions about this particular
document:
On 13 Aug 2015, at 10:26, Michael StJohns wrote:
1) Unlike the publication of a new RFC and its associated dates, there
isn't any way to permanently associate the change of status date with
the RFC. At some future time (and here I'm talking 10-20 years), will
it ever be important to be able to identify when the change was made
(without having to do email archeology)?
A change in status of a Standards Track document (whether up in the
Standards Track or down to Historic) requires a “Standards Action”
notification, and that gets documented in the IESG minutes. Not an ideal
markup system (only half better than email spelunking), but the process
is there. (See 2026 6.1.3, and RFC 7100.)
Changes to Historic require the submission of an RFC to mark the
change
Not according to 2026 6.4. All it requires is a Last-Call and then the
notification procedures in 6.1.3.
2) According to RFC 2026, BCPs are documents of the IESG, not the IAB
and IESG together.
Well, they go through IESG review, but they’re documents that are
“viewed as having the technical approval of the IETF”. That said,
2026 does recognize the IAB as a potential author of a BCP:
While it is recognized that entities such as the IAB and IESG are
composed of individuals who may participate, as individuals, in the
technical work of the IETF, it is also recognized that the entities
themselves have an existence as leaders in the community. As
leaders
in the Internet technical community, these entities should have an
outlet to propose ideas to stimulate work in a particular area, to
raise the community's sensitivity to a certain issue, to make a
statement of architectural principle, or to communicate their
thoughts on other matters. The BCP subseries creates a smoothly
structured way for these management entities to insert proposals
into
the consensus-building machinery of the IETF while gauging the
community's view of that issue.
My read has always been that the IAB and/or IESG can create a document
for the purposes above, it goes through an IETF discussion/edit, and
then it can become a BCP of the IETF.
pr
--
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478