Re: IESG Statement on surprised authors

Ted Lemon <Ted.Lemon@nominum.com> Sun, 31 May 2015 22:11 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F27281B2DD5 for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 15:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HxCJ485LLNmV for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 15:11:14 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBD8D1B2DD3 for <ietf@ietf.org>; Sun, 31 May 2015 15:11:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id BCB8CDA0077; Sun, 31 May 2015 22:11:13 +0000 (UTC)
Received: from [10.0.20.121] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sun, 31 May 2015 15:11:12 -0700
References: <20150531170415.24384.qmail@ary.lan>
MIME-Version: 1.0 (1.0)
In-Reply-To: <20150531170415.24384.qmail@ary.lan>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DE499F8C-89DC-493A-BDBA-8E46C606FE81@nominum.com>
X-Mailer: iPad Mail (12F69)
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: IESG Statement on surprised authors
Date: Sun, 31 May 2015 18:11:12 -0400
To: John Levine <johnl@taugh.com>
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6suUw1ZXp3ILtce9N8uHnQoqMNE>
Cc: "<kreeger@cisco.com>" <kreeger@cisco.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Sun, 31 May 2015 22:11:15 -0000

On May 31, 2015, at 1:04 PM, John Levine <johnl@taugh.com> wrote:
> We do automatically notify authors when new drafts are posted, which
> should usually alert surprised authors to the problem.

At this point the damage is already done: the surprised author now has to publicly accuse the other author(s) of surprising them, which is really burdensome and which said surprise author kit find completely unpalatable for any number of reasons. This is not a solution.