Re: IESG Statement on surprised authors

Eliot Lear <lear@cisco.com> Sun, 31 May 2015 08:48 UTC

Return-Path: <lear@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 2838C1B2CC6 for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 01:48:28 -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 m46eCq5YeeY2 for <ietf@ietfa.amsl.com>; Sun, 31 May 2015 01:48:26 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 608091B2CC3 for <ietf@ietf.org>; Sun, 31 May 2015 01:48:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1764; q=dns/txt; s=iport; t=1433062106; x=1434271706; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=m4F4pspR+mbic67of1AvHZQCiTElkM/MlchXLsqOia8=; b=CU4byMN3w+aFFWWwc6poZjkB1B8sch+uhUIhX/pUIWyElz6y0ujeUT+W sfrwAGwCBYFAgabz45vdNCJfMNvuSqjchkRr6sbyGhMIiAjzz6GX7EvWe In5GnOXL9+HwlUzGFj59+n5APzTNoNTWp76dCyDpbIssGoUcfMjsU48nT w=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CtAwApympV/xbLJq1cDoQ0gx67HwmHUQKBYxQBAQEBAQEBgQqEIwEBBCNVARALGAkWCwICCQMCAQIBRQYNAQUCAQGIKbFZoy0BAQEBAQEBAQEBAQEBAQEBAQEBGYtDhQYHgmiBRQEElRyBQ4c9h3iPOiNhgllAPDGCRwEBAQ
X-IronPort-AV: E=Sophos;i="5.13,525,1427760000"; d="asc'?scan'208";a="500095038"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 31 May 2015 08:48:24 +0000
Received: from [10.61.71.33] (ams3-vpn-dhcp1825.cisco.com [10.61.71.33]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t4V8mOPq021095; Sun, 31 May 2015 08:48:24 GMT
Message-ID: <556ACAD7.9080506@cisco.com>
Date: Sun, 31 May 2015 10:48:23 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: David Farmer <farmer@umn.edu>
Subject: Re: IESG Statement on surprised authors
References: <20150529205551.22495.73800.idtracker@ietfa.amsl.com> <2F99A0C05DFEE698A643FC97@JcK-HP8200.jck.com> <938E070C-A69A-4D37-9B33-3CB07E09595C@piuha.net> <5568F568.9060407@bogus.com> <5568FE28.1090600@gmail.com> <55695D53.3000004@cisco.com> <E3C9C304-EFA2-4C47-AC57-354BEDDC1984@umn.edu>
In-Reply-To: <E3C9C304-EFA2-4C47-AC57-354BEDDC1984@umn.edu>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="jGHKrv2jLg4Sno4i9gf6tugdXchsTjC2i"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NzhvXWf4DpKnkXaK3EBdoEQOo-0>
Cc: John C Klensin <john-ietf@jck.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 08:48:28 -0000

There's a basic principle at stake: don't lie and don't mislead, either
directly, indirectly, or through omission.  We make an exception for
April 1 RFCs, which may do all three.

Eliot

On 5/30/15 5:14 PM, David Farmer wrote:
>> On May 30, 2015, at 01:48, Eliot Lear <lear@cisco.com> wrote:
>>
>> I like this draft, but I suggest that it apply to ALL RFCs (not just the
>> IETF stream).
>>
>> Eliot
>>
> Sorry but I disagree. Not ALL RFCs, to exemplify why, I think the use of a humorous nom de plume or a sarcastic acknowledgement would be perfectly legitimate for RFCs published on a particular day in the spring.
>
> Authorship, contribution, and acknowledgement are serious and important issues, but that is no reason to completely abandon or exclude humor and sarcasm in appropriate doses.
>