[apps-discuss] Last Call conduct redux (Was: Last Call: <draft-ietf-appsawg-nullmx-05.txt> (A NULL MX Resource Record for Domains that Accept No Mail) to Proposed Standard)

Pete Resnick <presnick@qti.qualcomm.com> Tue, 22 July 2014 13:27 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEFC61AD6B0; Tue, 22 Jul 2014 06:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 cBxZuDR56P7C; Tue, 22 Jul 2014 06:27:46 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F2B61A0AFD; Tue, 22 Jul 2014 06:27:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1406035666; x=1437571666; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=S/+1lVtAVp/iAjyp47LAF1JCRNH8IAVzBHMxACOjtwA=; b=M1g851eLvL+HEWRDmi8UpEx3Tq1QcILEUjeY3IyBeb45RuL5dM6ktCMi iB3Dz2qlI/T3oEiIfdujyn8nUw5BvbYs3hgbJKaEnmo+9ERWkRNL0uzI0 WjfgUCNRSnTikiveux83NojKL1roERSWF7IhPSgRJaVpYjy0TtA99VcuH w=;
X-IronPort-AV: E=McAfee;i="5600,1067,7506"; a="70980609"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 22 Jul 2014 06:27:45 -0700
X-IronPort-AV: E=Sophos;i="5.01,710,1400050800"; d="scan'208";a="680301843"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Jul 2014 06:27:45 -0700
Received: from dhcp-abf0.meeting.ietf.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 22 Jul 2014 06:27:44 -0700
Message-ID: <53CE66CF.4090104@qti.qualcomm.com>
Date: Tue, 22 Jul 2014 09:27:43 -0400
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: IETF-Discussion list <ietf@ietf.org>
References: <20140703190347.24899.45193.idtracker@ietfa.amsl.com> <7140A115A74391DED82A2028@JcK-HP8200.jck.com> <53C8394A.6080508@dcrocker.net>
In-Reply-To: <53C8394A.6080508@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/AwX_szzPHHMfWnitpjEy1G5pmvM
Cc: dnsop@ietf.org, Apps Discuss <apps-discuss@ietf.org>
Subject: [apps-discuss] Last Call conduct redux (Was: Last Call: <draft-ietf-appsawg-nullmx-05.txt> (A NULL MX Resource Record for Domains that Accept No Mail) to Proposed Standard)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2014 13:27:49 -0000

This message is admittedly 4 days too late. In my opinion, we area 
directors got caught out not paying attention and did not act to address 
problematic behavior on this list in a reasonable amount of time, and 
haven't been doing so for some time. The IESG is taking this ongoing 
behavior seriously, and you'll see some discussion in the next few days 
about how we intend to address it. But this particular thread had some 
serious misbehavior, that behavior came from senior members of the 
community, and it needs to be called out in particular.[1]

Of course we need to learn to focus our review comments and discussions 
at Last Call, we need to make concrete and constructive suggestions for 
changes (preferably supplying text), and when we respond to reviews we 
should filter superfluous commentary and solicit specific 
recommendations where they were missing. But this is general advice and 
not an issue of the kind of misconduct I'm referring to. The problem in 
this thread came when, instead of constructively responding to the 
initial posting and simply filtering out non-constructive comments, the 
responses and continuing conversation served to *raise* the temperature 
instead of lowering it. Engaging in sarcasm, belittling of comments, 
baiting rhetorical questions, and aggressive (whether directly or 
passive-aggressive) commentary drives some folks away from the 
discussion (or participation in general), causes other folks to think 
that it's acceptable behavior, and causes further discussion to degrade.

Luckily this thread seems to have converged, and I think it would be 
terribly unproductive to argue about the merits and demerits of this 
particular thread on this list, but this kind of behavior needs to stop. 
That requires everyone to commit to trying harder to engage civilly, and 
to not tolerate misbehavior. That doesn't mean that you should take it 
upon yourself to police and control other people's behavior; that only 
serves to compound the problem. But if discussions are not being 
appropriately moderated, you should bring that to the attention of the 
ADs; we are committing to making sure that things improve.

pr

[1] You may react to this by saying, "There has been far worse behavior 
on this list in recent years. Why pick on this particular thread?" The 
answer is, we have to start somewhere, and it happens that several 
people, including some of the participants in this thread, made specific 
complaints about his particular case.

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478