Re: IESG Statement on surprised authors

"John Levine" <johnl@taugh.com> Sun, 31 May 2015 17:04 UTC

Return-Path: <johnl@taugh.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 66DDE1A70E1 for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 10:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 9g-4C575v6Zv for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 10:04:39 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 443AA1A7034 for <ietf@ietf.org>; Sun, 31 May 2015 10:04:39 -0700 (PDT)
Received: (qmail 35573 invoked from network); 31 May 2015 17:04:45 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 31 May 2015 17:04:45 -0000
Date: Sun, 31 May 2015 17:04:15 -0000
Message-ID: <20150531170415.24384.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IESG Statement on surprised authors
In-Reply-To: <D18E2F33.14965E%kreeger@cisco.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qD0UYo0KBh-klfbz6STEPvh9Dyg>
Cc: kreeger@cisco.com
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 17:04:40 -0000

>Isn't one way to deal with this to build additional mechanisms into the
>draft submittal confirmation procedure?

When I suggested this a couple of weeks ago, people pointed out that
there are too many ways that the obvious approach, require all new
draft authors to approve posting, has its problems.  It can interfere
with legitimate drafts (on meeting cutoff day one author stays at the
office to finish the draft, the others take off for the weekend) and
it's trivial to circumvent (use plausible fake webmail addresses.)

We do automatically notify authors when new drafts are posted, which
should usually alert surprised authors to the problem.

R's,
John