"professional" in an IETF context

Keith Moore <moore@network-heretics.com> Sun, 31 October 2021 17:45 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3CA3A1037 for <ietf@ietfa.amsl.com>; Sun, 31 Oct 2021 10:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 HLz7bhA29OF7 for <ietf@ietfa.amsl.com>; Sun, 31 Oct 2021 10:45:36 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 769FB3A1038 for <ietf@ietf.org>; Sun, 31 Oct 2021 10:45:35 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id EBF0C32008C0 for <ietf@ietf.org>; Sun, 31 Oct 2021 13:45:34 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 31 Oct 2021 13:45:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=od0yv4Qm+dbc2q1w9GfUjoBXggWy60MYKYU2YW6NH VI=; b=ABpkrqLcY3cVFJ4nkkSqvt8kKBymhc4W6/uRDgpgo+KPpPg3cuUgddZWV Vt4Li3TFFg5PazqMkI4/eXRQFY7AJbTYP/qDvCjxSj2JhWSlo4z1xG5rNw6Cq8ea Zu907Z++Ns9MfEdwEzNbwcTmSkPS+GwztTxB+Cn1NyvGw6IaahNlvjJi/eV21A6t 76vT0EgFeKgkbrbapRrTCkkHbfZs1cGQ031a+dXeKWc8WoLh4mjQLnNAjfASnKkD rUllXDaUKAwqNsNMscM/4LD7Dcb3i7aqGKyvov4Lh0ktL/b6AnkxkJMw81k2ik7s d4mgpgIXdHP6+XCEAln8gyOT4Sfkw==
X-ME-Sender: <xms:PdZ-Yf7tWkb12UfYLxetV0mx0soglAdJ3dndzUiMM8Q3Is3Uw0_QJQ> <xme:PdZ-YU6lp5gIuTyc8jr_AFvhItS5k5pkcoFCWR6cDr8rUoZYoUUYAHQYTNRSRo-RW HJtx9KhelG1Gw>
X-ME-Received: <xmr:PdZ-YWfOLZ2B0Bv9cqjT0ejnjQrOtYb-4CWVfKuaBzt0cCk4B6x5z5YItxBUndbaN1_h-Oziq2fqUT-_LKQsn-AeCLnKnvWYsRG-DYS_OlsRMLJP9r8wzw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvdehtddguddtudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedthe efgfefgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifoh hrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:PdZ-YQLYyPFSeCJ4ikr5oCRmZmKA2zoWiE2XIElZ7vWfVhcdjCFS8w> <xmx:PdZ-YTKJsX7Y_BNTM3QtgtLJykZNcCOXVAIX92WoQb11Z2owKL0KDQ> <xmx:PdZ-YZzy2MlY8qpLkwt8-kdZQi96yvgr9CK-0bOKDK78NXcqNBmwaQ> <xmx:PtZ-YYXajz9McSY-T1KbONP9Gg5a775wwNR0vW4LYG6Wag78BQDTxw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ietf@ietf.org>; Sun, 31 Oct 2021 13:45:31 -0400 (EDT)
Subject: "professional" in an IETF context
To: ietf@ietf.org
References: <8F4B97EA-665F-4A59-B99D-791B4AB9F2F7@yahoo.co.uk> <746C1453-FFB0-46E5-ABF2-8630DC23B959@network-heretics.com> <c3e9fe1b-8e48-a364-9e25-4084dac70889@meetinghouse.net>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <3a6bf8ad-5492-0942-a451-6317e8a93705@network-heretics.com>
Date: Sun, 31 Oct 2021 13:45:23 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <c3e9fe1b-8e48-a364-9e25-4084dac70889@meetinghouse.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JwqwDgzSs7NV8zGvDwQPavw1mqE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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 Oct 2021 17:45:41 -0000

On 10/31/21 11:18 AM, Miles Fidelman wrote:

>
> I've always interpreted that as denoting actually being knowledgeable 
> about that which you speak, exercising a measure of judgement & 
> restraint, and adhering to a code of professional ethics & decorum.
>
> It's what we expect of our doctors, lawyers, and... ENGINEERS.  It is 
> an ENGINEERING Task Force, after all.  And I would hope that most of 
> us here are actually engineers, with some reasonable level of 
> engineering knowledge, experience, and professionalism. 

Lately I've been asking myself how I would define "professional" in an 
IETF context.  What I've come up with so far is (no particular order):

1. Be competent and well-prepared.
2. Let people with appointed roles do their jobs.  It's okay to publicly 
and respectfully object when you believe they've not done their jobs 
properly, and there are various remedies like appeals that can also be 
used.   But it's not ok to try to prevent them from doing their jobs.
3. Follow the Guidelines For Conduct.
4. Treat fellow participants as equals in technical discussions (while 
respecting any appointed roles they have in IETF), regardless of their 
day jobs (or lack thereof) or who they work for.
5. Whatever you’re working on, try to help build consensus or craft or 
find a compromise that can attract broad support.  Again you’re free to 
withhold support or to point out problems with a proposal, you’re free 
to offer alternative proposals, and/or to appeal formal decisions, but 
not to obstruct discussion. State/log your objections and move on (But 
you should have a reasonable expectation that such objections will not 
be forgotten and be reviewed again at last call time).

As for ethics, I'm reminded that when I earned an engineering degree I 
was encouraged to take a solemn oath to always act with regard for 
public safety.   In the Internet context I might argue that there's a 
duty to act with regard for the security and privacy needs of the public.

Keith