IETF Logo Mail Archive

Re: Terminology discussion threads

"Carlos M. Martinez" <carlosm3011@gmail.com> Mon, 17 August 2020 20:55 UTC

Return-Path: <carlosm3011@gmail.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 2CA693A124D for <ietf@ietfa.amsl.com>; Mon, 17 Aug 2020 13:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level:
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 t3opjXZ_5epI for <ietf@ietfa.amsl.com>; Mon, 17 Aug 2020 13:55:36 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA91A3A1227 for <ietf@ietf.org>; Mon, 17 Aug 2020 13:55:35 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id 2so16273983qkf.10 for <ietf@ietf.org>; Mon, 17 Aug 2020 13:55:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=hfxgAIfp2+lMpxbNuNgqfcmctEmJboiDk9P+0/gxTYs=; b=NYgkBMRPfhaTl3vxM1swJSrr1+BbliOjqRr41MojArg0bhg71SjfYEy9bNx0uSz2DT khQussyUNSkoQemdw6yqZ67LVqKlARcXA4oULGF97nr1kq51oZ6TQO/th/AbEOkQ6BZX y9MVfZjlqRtdy8yg+NpAaMt88MWMKqsd0I7kPmX+pfCgPz49IByIsuprkJHryHbPtC+3 4gO9kW5NSCEN6Viuz9mrH0AvkInYwc5A0j6QC+TqmGmJjXOKYymW21f76SBr0t7w7fsW dozxCHwYRG8rzqH/rXDWkTE/Lw+MNHQOfepOPdM32aho+veFciko0Jxesb+dtvvfQ6aw u2QQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=hfxgAIfp2+lMpxbNuNgqfcmctEmJboiDk9P+0/gxTYs=; b=b1CvLNqdvLIZg34A3naYsBHG3t6e70XhIUc0QW1aCpIpbONG42eu3CkaLZBrmG9Fg8 09fG7A6zlrEk+F1CTNJJh6vzhQnQ4bGhdF2q6wC98ConXl1xA5tJz4gAJMy8wdj4e1t0 PhFulI1cK/VBsWjnxHQyftq5npD+ToWker/i9wARAbefaYfQSDEPxl/ArRBo90TpwbzQ SXbeMgJF9+SEuZUrt+LoAZC8dGPrsIhvx7e79SCoHjdRcdWTm1EkvCwtiurPUvndMzSb ypNOPogQo5U5FqOr4yfVm72oTSoR9DJOa2wFNUWrHvhFDCRBczfOUC5chAs66vUDumzD 55nw==
X-Gm-Message-State: AOAM5313r0Oc0laCGdjCeUlt4iEihO/JCwomv7nVHJpsTd9hsoAzXWeI zHtVZRnnrxaAl68fvgDESAo=
X-Google-Smtp-Source: ABdhPJylS68lv5Rt/EQJsW768KKCXzjC/G11ajgkelbu68E630zeFMyjMgZk0fET1UmTzd3WEMrROQ==
X-Received: by 2002:a37:a0f:: with SMTP id 15mr14474126qkk.410.1597697734620; Mon, 17 Aug 2020 13:55:34 -0700 (PDT)
Received: from [192.168.89.245] ([2800:a4:2889:7200:496c:d025:6a7c:ec29]) by smtp.gmail.com with ESMTPSA id w1sm18747684qkj.90.2020.08.17.13.55.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Aug 2020 13:55:34 -0700 (PDT)
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: tom petch <daedulus@btconnect.com>
Cc: ietf <ietf@ietf.org>
Subject: Re: Terminology discussion threads
Date: Mon, 17 Aug 2020 17:55:28 -0300
X-Mailer: MailMate (1.13.1r5703)
Message-ID: <D5FDC7E0-5E50-42FB-86F0-5D9600ECA02D@gmail.com>
In-Reply-To: <5F37EE15.4000700@btconnect.com>
References: <6AA0BCBB-D95B-4036-B94D-5E79E7B94D75@ietf.org> <F15E387D-9FDC-4A76-8002-78B85F6D16BE@nohats.ca> <CABcZeBNitWbdPO4Y2WfCzjy10Z+s27px6cGT1uRHmtGHa5iX+Q@mail.gmail.com> <ed227fd5-3277-d7a9-f93d-b259944009d6@huitema.net> <20200814174247.GH92412@kduck.mit.edu> <5F37EE15.4000700@btconnect.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XKAefRiHSnLyo0L7HJeRk-BWF7A>
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: Mon, 17 Aug 2020 20:55:43 -0000

Hi,

I was trying hard not to say anything more on the topic, but this 
comment by Tom strongly resonated with me, so here it goes:

On 15 Aug 2020, at 11:15, tom petch wrote:

> Wow, want to start a firestorm, well that is how you do it.  The IETF 
> often describes itself as organised bottom up and the IESG is not what 
> I would call the bottom.

Indeed. What followed the initial IESG announcement was to be expected. 
Anyone who’s ever been remotely connected with the IETF could have 
predicted what happened after the original email.

>
> I speculate that something happened in the IESG to trigger this but 
> have no idea what that would be but that statement, to me, was always 
> going to trigger aggressive responses but why the statement was worded 
> as it is I cannot tell but it may be something for the IESG to reflect 
> on.

I would very much like to know what triggered the IESG’s announcement 
and the details of the process that produced it. Was there any external 
pressure? What was the IESG trying to accomplish ?

/Carlos

v2.23.0 | Report a Bug | By Email