Re: Some more thoughts about language and what to do next

Eliot Lear <lear@cisco.com> Fri, 31 July 2020 16:53 UTC

Return-Path: <lear@cisco.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 353F53A0913 for <ietf@ietfa.amsl.com>; Fri, 31 Jul 2020 09:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 li8zln2zRBmZ for <ietf@ietfa.amsl.com>; Fri, 31 Jul 2020 09:52:59 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97D953A090B for <ietf@ietf.org>; Fri, 31 Jul 2020 09:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5932; q=dns/txt; s=iport; t=1596214378; x=1597423978; h=from:mime-version:subject:date:references:to:in-reply-to: message-id; bh=lo3FBSBfWERokW0lez4HnE/0l4TsMDj8kD7tSCMreIQ=; b=Pe1MGYzYNE+O+fhLMyEg/ZCXkpJPpDRTejInrz3yQ+nL/YgoiHJXoXcK RdZjT8Hp/qaq5nl57vi0k4Mmq0BS8chU35+rd03egNuLhdX7xmqUBpHjI RM2BkGC+PlW81votp1iMb/6to7g3iXRe8HNsN+yzQ8kCbZAqga9V5gKru k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DdBwApTCRf/xbLJq1gHQEBAQEJARIBBQUBggoCgSGCSgEgEiyENYkBh3Ilk3aIFwsBAQEMAQEvBAEBhEwCgjQlOQUNAgMBAQsBAQUBAQECAQYEbYVohXEBAQEDASNIEwsLGCoCAlcGExSDEoJdILBMdoEyik2BOAGNJ4IAgTgMEIIfLj6HUzOCLQS2CoJqgwqWegMekU6OKa1wg1YCBAYFAhWBayKBVzMaCBsVZQGCPj4SGQ2caD8DMDcCBgEHAQEDCZEfAQE
X-IronPort-AV: E=Sophos; i="5.75,418,1589241600"; d="scan'208,217"; a="28322620"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Jul 2020 16:52:39 +0000
Received: from [10.61.228.22] ([10.61.228.22]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 06VGqcA1031701 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 31 Jul 2020 16:52:39 GMT
From: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5F7CC499-F680-41B0-9D0F-978922B2CF6B"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Some more thoughts about language and what to do next
Date: Fri, 31 Jul 2020 18:52:38 +0200
References: <09474801-7189-4C01-8242-163454C3E936@cisco.com> <20200731140536.GQ3100@localhost> <2E217C0C-2FD9-4420-BEB7-B62ED53F0B8C@cisco.com> <20200731164323.GD42601@straasha.imrryr.org>
To: The IETF List <ietf@ietf.org>
In-Reply-To: <20200731164323.GD42601@straasha.imrryr.org>
Message-Id: <B08D4220-9460-449E-84F7-1B8B0A42F47B@cisco.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Outbound-SMTP-Client: 10.61.228.22, [10.61.228.22]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xG67VlzyxYjbIIUpmMPgkYT1qgQ>
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: Fri, 31 Jul 2020 16:53:03 -0000


> On 31 Jul 2020, at 18:43, Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
> 
> This presumes the existence of objectively qualified experts[1].  Will
> we know one when we see one?  Who decides which experts are qualified?
> I don't think ducking the responsibility to make the choices can work.
> Ultimately, the IETF community are the experts in how we use our
> terminology.


I may or may not know what an expert in this space looks like, but I can tell you what one doesn’t look like.  And so I guess I would fundamentally disagree with you that we are the experts.  However, we would be the customers of the expert advice, and we get to decide either individually or collectively to use it.

Eliot