RE: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
"Adrian Farrel" <adrian@olddog.co.uk> Wed, 06 November 2013 17:48 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A37521E808D for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 09:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBkvUQzTP1Tj for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 09:48:18 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEB321E8148 for <ietf@ietf.org>; Wed, 6 Nov 2013 09:48:16 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id rA6HmDcs008545; Wed, 6 Nov 2013 17:48:13 GMT
Received: from 950129200 (dhcp-a27f.meeting.ietf.org [31.133.162.127]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id rA6Hm7uE008448 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 6 Nov 2013 17:48:09 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'Bjoern Hoehrmann' <derhoermi@gmx.net>
References: <20131105184722.29536.20794.idtracker@ietfa.amsl.com> <527A0582.9010505@gmail.com> <aokk791t6iuaie7tn7ukgg5358hjlp3gkp@hive.bjoern.hoehrmann.de> <527A5F8E.3060703@gmail.com>
In-Reply-To: <527A5F8E.3060703@gmail.com>
Subject: RE: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
Date: Wed, 06 Nov 2013 17:48:07 -0000
Message-ID: <02eb01cedb18$5d53bcb0$17fb3610$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF5V1ZjXBBbZB2tINCtNCQ+pahSvgGLywtNAtMBHY4BuPVodpqSwhDA
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 17:48:24 -0000
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@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Brian E > Carpenter > Sent: 06 November 2013 15:26 > To: Bjoern Hoehrmann > Cc: ietf@ietf.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'.
- Re: Document Action: 'Terms used in Ruting for Lo… Glen Zorn
- Re: Document Action: 'Terms used in Ruting for Lo… Bjoern Hoehrmann
- Re: Document Action: 'Terms used in Ruting for Lo… Brian E Carpenter
- RE: Document Action: 'Terms used in Ruting for Lo… Adrian Farrel
- Re: Document Action: 'Terms used in Ruting for Lo… Spencer Dawkins at IETF