Right, thanks Brian.
I am surprised that this causes so much traffic, but anyway, the fault is mine
as "responsible AD" (read "irresponsible AD"?)
The bug was introduced post IETF last call, and spotted immediately. It did not
warrant a respin of the document and an RFC Editor Note was added to fix it.
Several ADs noticed during IESG evaluation and made Comments or raised
Discusses having failed to note the RFC Editor Note, but they cleaned them up
after discussion.
As Brian says, the announcement text is auto-generated. But it is editable, and
I should have edited it. I forgot / didn't notice.
As soon as the email came out I did notice (see my Twitter feed).
I raised a ticket with the Secretariat (who were shockingly having lunch at the
time) and a revised announcement was sent as soon as they were back.
If I were not the person responsible for this error I would say "Nothing to
see. Move along." But I leave you to judge.
Adrian
-----Original Message-----
From: ietf-bounces(_at_)ietf(_dot_)org
[mailto:ietf-bounces(_at_)ietf(_dot_)org] On Behalf Of Brian E
Carpenter
Sent: 06 November 2013 15:26
To: Bjoern Hoehrmann
Cc: ietf(_at_)ietf(_dot_)org
Subject: Re: Document Action: 'Terms used in Ruting for Low power And Lossy
Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
On 07/11/2013 03:34, Bjoern Hoehrmann wrote:
* Glen Zorn wrote:
You're joking, right? 14 revs, IESG review and still nobody asked what
"Ruting" was?
(The document title was changed in the latest revision, it did not
contain the word earlier. And it has been spotted in this version.)
I think this deserves a few more words of explanation (we happened to
discuss it at the RFC Editor Advisory Group meeting yesterday).
The bug was introduced in the final rev before IESG approval.
It was noticed by, among others, the Gen-ART reviewer.
The General AD even put a short-term DISCUSS on the draft until the
bug was acknowledged by the authors. Clearly, it will be fixed
during editing.
However, the text of the approval message is generated automatically
from data in the tracker, so it automatically contained the bug.
Bottom line: the system worked.
Brian
P.S. I assume that the correct title is 'Terms used in Rusting for Low Power
and
Lossy Networks'.