Re: IESG Statement on surprised authors

Toerless Eckert <eckert@cisco.com> Fri, 29 May 2015 22:17 UTC

Return-Path: <eckert@cisco.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 81FC21A7022 for <ietf@ietfa.amsl.com>; Fri, 29 May 2015 15:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 w-BW91R-LfR1 for <ietf@ietfa.amsl.com>; Fri, 29 May 2015 15:16:58 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73EF91A039B for <ietf@ietf.org>; Fri, 29 May 2015 15:16:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1374; q=dns/txt; s=iport; t=1432937817; x=1434147417; h=date:from:to:subject:message-id:references:mime-version: in-reply-to; bh=5HpxJCGdwPCeXwzG6jORukPOeCiLj+tpVEfOEo7tEE0=; b=dxm6QSSed8d1g3NlxSdFLTN8MkEyqDXbqcPNTqqmWcRAAbXh3+uJ9Har 0IxpPQcAYfoDS0TZcC7E95/amNGMrLAV/tGNEtDnxot384Lwl0c4q2/yg 9mDOQmElisk/V11NYvXaN4DTz2xp/lVmMrFn9oyupPiYiARPTOTaQYq4p 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJBQBj4mhV/4QNJK1cgxBUXr4zgVqFdwKBSjoSAQEBAQEBAYEKhCMBAQQ6MR4LGAklDwVcFIgZDdUEAQEBAQEFAQEBAQEBARuLQ4UNFoMBgRYFi1Vsin6GXAGBKT6DM5IYI2GDNx4xAYJGAQEB
X-IronPort-AV: E=Sophos;i="5.13,519,1427760000"; d="scan'208";a="154595362"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-2.cisco.com with ESMTP; 29 May 2015 22:10:48 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t4TMAlTT026160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 29 May 2015 22:10:48 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t4TMAkH6025279 for <ietf@ietf.org>; Fri, 29 May 2015 15:10:46 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t4TMAjtt025278 for ietf@ietf.org; Fri, 29 May 2015 15:10:45 -0700
Date: Fri, 29 May 2015 15:10:45 -0700
From: Toerless Eckert <eckert@cisco.com>
To: ietf@ietf.org
Subject: Re: IESG Statement on surprised authors
Message-ID: <20150529221045.GA5551@cisco.com>
References: <20150529205551.22495.73800.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20150529205551.22495.73800.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yIuWxoMdRe5TpKzO9k_SU0btOhY>
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: Fri, 29 May 2015 22:17:02 -0000

This is the same problem as with domain names:

When you want to highlight through a fake list of authors on a
draft widespread support for it, its really hard to come up
with an expert sounding randomn name that has not already been
taken up by some physically existing person that also happens
to work in the IETF. So you get unintended collisions and concerns.

This problem really needs to be solved through extensions of RFC6761.

Eg: "Strong the 3rd Supporter @ example.com" or the like.
"Rocky Balboa@local.local.local", etc. pp/.

Cheers
    Toerless

[C'mon, it's friday! A joke a month keeps the anger away.]

On Fri, May 29, 2015 at 01:55:51PM -0700, IESG Secretary wrote:
> IETF community,
> 
> The IESG is planning to publish an IESG statement concerning the
> authorship of Internet drafts. This statement is only focused on the
> situation where an IETF participant feels he/she has been erroneously
> listed as an author on a draft. The statement can be seen here:
> 
> http://trac.tools.ietf.org/group/iesg/trac/wiki/SurprisedAuthors
> 
> We are seeking community feedback on this statement and welcome input
> that will help encourage proper behavior. Please provide any feedback
> by June 10, 2015 to either ietf@ietf.org or the IESG directly at
> iesg@ietf.org.
> 
> Regards,
> Brian and Benoit (on behalf of the IESG)