Re: On diversity in the NomCom

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 16 July 2020 20:52 UTC

Return-Path: <brian.e.carpenter@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 705203A0CE0 for <ietf@ietfa.amsl.com>; Thu, 16 Jul 2020 13:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 JFPb1qQe3lvR for <ietf@ietfa.amsl.com>; Thu, 16 Jul 2020 13:52:51 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 C74553A0CDF for <ietf@ietf.org>; Thu, 16 Jul 2020 13:52:51 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id w17so4381111ply.11 for <ietf@ietf.org>; Thu, 16 Jul 2020 13:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=60zuYLbh5NDKi/jvcH64SUIDKMH1+5qfw0b/l8PcfPc=; b=LsI0tJIzcUQzK5nU+LZF3TQnSs659xzZ6BQKqfKkKs7it4eJGHrw2ctDCZCfKNpDkZ OfFhG1PBVZ/UQT2+qy+SkpMZFLjOdW++KiPtikWEtPGQ+wEW3wS5nNGJZTQmc+ss0Yx+ pCxezNtck5IVE/HRNsBUqkP6fhSAP5Yimu2bCefGB+u4glMIsRZAP8VlJOx2TgdrefhF h35qtRfq09J/BwFq5T7gFIyvAacxbNuto5aWZ17xrh1ss7QPqCAkia1l1jyuadchpTqY Un1EXJbdtYKqneQv8wnI8BbQj28ionzPsqrJ90ih5616nYf5Luq7Nd0RCtg7SzmXPSQF OqeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=60zuYLbh5NDKi/jvcH64SUIDKMH1+5qfw0b/l8PcfPc=; b=OXbucE+QIVIR3j6sb2TJOh2i5/Fny+nJFRo43vi+gfIVJ5fqTObcx0rtA62kqzPnx1 Ihy4u8futkDBBoX1r/iXc2S4DkuAMZJnRsK3M9JtN/V5ZTUOR9ZmRNjWhtVE2LVeDusw aIKAtUJljdgMQq/B7nRQ6i3peInfHlwAwCrBYy38hfZzwYsK1uBS3iBA/6sJwwDp4hps u1w/7NCo7ycfe+MxG/W5M9+MIHxbg5dgw9r1Wj5wAm+oLM9DQ2cqEvsS0V4l/OKhvVG+ 3JqcjLGorVpxEjEc4aNXhryPbZhQ6ebtWsS0XyhGj5rKppG8GWze9d0zSNlwDxepPwB2 ZhXA==
X-Gm-Message-State: AOAM530zqyQbYks7UARmVc/qnH57+vEQAhS8ckpiP299U05Omq+Es9qe bBHGEYluHvHjiabc7NY/HAm1Z93a
X-Google-Smtp-Source: ABdhPJz0PytvlEj8ecXyQ5cO4iQwwa1SAeqIhrZlbMGVoCuKeccP8QM8o6zJfCRQaLn8QaAYo0hhtg==
X-Received: by 2002:a17:90a:7c4f:: with SMTP id e15mr6223164pjl.133.1594932770903; Thu, 16 Jul 2020 13:52:50 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.13]) by smtp.gmail.com with ESMTPSA id n2sm5648809pgv.37.2020.07.16.13.52.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Jul 2020 13:52:50 -0700 (PDT)
Subject: Re: On diversity in the NomCom
To: Joel Halpern <jmh@joelhalpern.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: IETF discussion list <ietf@ietf.org>
References: <7429392e-a411-4c40-8fa9-f03de558b7ca@dogfood.fastmail.com> <d3187a20-76a8-0ef9-d32f-6b8e400a0d30@gmail.com> <ee517835-1ad4-e2c0-a33b-e194f7c37f95@gmail.com> <CAChr6SxXwKwwtXxL+9f2Zz8kufpnOLmHHkK-dY6PC+k9mNE4+w@mail.gmail.com> <16772aec-9ead-3658-16c8-dfbcdfa19edc@gmail.com> <CAChr6Sy+a=ziSH-D8Q+wQLDA6rEXg2SfiE+4V7trr2z20kQs9Q@mail.gmail.com> <2D8F8708458BF390168BD5EC@PSB> <A3B22E6E-8A16-4C1F-B3BF-30D27DCE1616@akamai.com> <2b5fc4b5-ea50-7d7f-2e8c-6a4d8126d38d@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7e77e51b-e443-829a-2d55-fddf0207e5af@gmail.com>
Date: Fri, 17 Jul 2020 08:52:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <2b5fc4b5-ea50-7d7f-2e8c-6a4d8126d38d@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aT6aDqiNls8X1vy4fRws_YbDU5k>
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: Thu, 16 Jul 2020 20:52:54 -0000

On 17-Jul-20 04:11, Joel Halpern wrote:
> If we were to do what?  Publish IETF Stream (rough consensus) 
> Informational and Experimental RFCs?  We already do that.  And have done 
> so for many years.
> 
> If you are trying to argue that we should use a different form of 
> publication, please make and justify that argument.  There is lots of 
> disinformation and misinformation out there.  (I recently observed 
> another SDO citing an expired individual draft as if it were an approved 
> RFC.)

I hope everyone realises that this conversation has been going on for
about 25 years. It actually doesn't matter, from this point of view, what
the document series is called or what the boilerplate says. It will still
be cited as "The IETF says..." sometimes.

Just look here for a recent example:
https://www.theregister.com/2020/06/08/developers_renew_push_to_get/

   Brian

> 
> Yours,
> Joel
> 
> On 7/16/2020 11:04 AM, Salz, Rich wrote:
>>> I also note that many other SDOs publish informative,
>> non-standard, documents in the form of technical reports and
>> that things we would call Experimental (or our original
>> definition of Proposed Standard) show up as things "for trial
>> use".  So, again, fwiw, we are not the only, or even the first,
>> body to conclude that formal review, consensus, and publication
>> of such documents is a practical necessity.
>>
>> If we were to do this, we need another term besides RFC.  After 20 years, everyone "knows" that RFC means an Internet standard.
>>
>> (Yes, I exaggerate about what everyone knows)
>>
> 
>