Re: LLC Board Meeting Details - 14 May 2020

Fernando Frediani <fhfrediani@gmail.com> Fri, 08 May 2020 19:38 UTC

Return-Path: <fhfrediani@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 8875B3A0E07 for <ietf@ietfa.amsl.com>; Fri, 8 May 2020 12:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=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 O7MCeV1U_Uen for <ietf@ietfa.amsl.com>; Fri, 8 May 2020 12:38:26 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 8A4CE3A0AC5 for <ietf@ietf.org>; Fri, 8 May 2020 12:38:25 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id v4so1435769qte.3 for <ietf@ietf.org>; Fri, 08 May 2020 12:38:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=aDedy76YYO3N2R1tCSDXsfrTFYJF/2UQWQ3HQ7/KD4g=; b=tGLoMfzbaFqGjhK2tIwE7e7Rsz7uZcwIsbXGwn06wp0qbNXAgBu8oiKxIc7RPSzDif tU5JMr6+/cdLPHeI5io68nnSpfksf2AFeqjCe0lwDkl/WG3+OCK+Lce3/NEs+Amr2j/N 7KuNlH5B7UJILIBtgmIVdstl5sbCzizAMYJ3iEqzfKK/4O99R1H5pbpWeReICbZKsOFe RFXmKG8eRYmwGU1kG+3Uz/Ti2uMWt6ubWHCpsG3FPmDKcripKTZLazzjEnrDKjtbsM/D tJbZZLwULMskf+IcSoTc8pKsMRN3WlZbbjqwF6wN7v1G2/IXB9lBAOKbCT4q484atK4N aOaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=aDedy76YYO3N2R1tCSDXsfrTFYJF/2UQWQ3HQ7/KD4g=; b=VDkM5YuR4ZV0vakBDnMxtEVFaX4fBiT9Zv452qmFjE/gwjSLkIJyGxxbm8AgSPYaVD Ad6/hyZwjUjrPPnBBEHQmC5y+rmKDG1MQazSAX5z9I1ih0Kc2d+sULTivFo9aVmtDGFj zdhrPeIBXOwaRkdy/kjCEKA9TrTa89gDfyc0xuNQxfIg8Ie+PCuhrqva3BNpIbGpD9ia uMJySzedKaAV4VRNYraR8JZEDp2PU7kTh8W6zXERpf52LpPWuuX3gx+R74KpddnGq2VU sEwiI/azt7fsRWJuiiKToHp3rwh3I0eff7SgABujH2N4H4E1rsFijNoLq/72fmz/KNrY dEUw==
X-Gm-Message-State: AGi0Pub+9uVpw2jHqHsv+/zKbd5tw5TsBR4p4OMR3XcCcUiM3WOp4Tj8 3hs3A5yhWu+HXPJXemkhCFCoTWkjlPk=
X-Google-Smtp-Source: APiQypKYKmzshoEx1hbS0qTtVZfKNaJk0KIZsWcpTnt4PICnI5xqpcXYW4s2px5fTG1GAMy5irIDIg==
X-Received: by 2002:ac8:31aa:: with SMTP id h39mr4741794qte.190.1588966702914; Fri, 08 May 2020 12:38:22 -0700 (PDT)
Received: from ?IPv6:2804:368:9:8000:c9be:24d2:262e:2c59? ([2804:368:9:8000:c9be:24d2:262e:2c59]) by smtp.gmail.com with ESMTPSA id a194sm1877918qkb.21.2020.05.08.12.38.20 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 08 May 2020 12:38:22 -0700 (PDT)
Subject: Re: LLC Board Meeting Details - 14 May 2020
To: IETF discussion list <ietf@ietf.org>
References: <158889282783.23704.1421198034874120499@ietfa.amsl.com> <fc27f4e6-c71a-a266-f501-96a0ed637367@gmail.com> <2D35A1DD-72E2-4E09-8A81-32770D357D29@cooperw.in> <9717fa55-af80-050b-3dd6-1bec957a31d0@gmail.com> <CABcZeBO_6vwxn3XTJfJvHGifx-boyKQ2KxVAS2-x-i5NFKpd9w@mail.gmail.com>
From: Fernando Frediani <fhfrediani@gmail.com>
Message-ID: <bfbea793-9b07-ee56-3b34-cf2054562e66@gmail.com>
Date: Fri, 08 May 2020 16:38:19 -0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBO_6vwxn3XTJfJvHGifx-boyKQ2KxVAS2-x-i5NFKpd9w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------FD802B73CB667175814AC954"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D7XtvaJyWsSDh8ziEJX5lWpae6g>
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, 08 May 2020 19:38:29 -0000

On 08/05/2020 14:51, Eric Rescorla wrote:
> <clip>
>
> I would make two points here:
>
> First, I think you are wrong on the merits. I do not believe that 
> support for IPv6 (nor DNSSEC, nor TLS 1.3) should be a primary 
> criterion for selecting tools. It may make us sad that these 
> technologies are not being adopted at a faster rate but I don't think 
> that inconveniencing ourselves in order to make a statement is the 
> right answer.
Perhaps one of the reasons they are not being sufficiently adopted 
because of the lack examples of people and organizations using them and 
the main propose is that as much as possible organizations start to do 
that in the many ways possible, and IETF is an natural one. Really do 
you see such an inconvenience on that ?
>
> Second, for the LLC board to take this kind of unilateral action on a 
> matter which does not primarily impact the efficient operation of the 
> IETF but rather is about messaging, seems like precisely the kind of 
> overreach that people were worried the LLC would engage in. That kind 
> of policy decision should come from the IETF, and as Alissa says, the 
> position you are espousing does not seem to have gathered even rough 
> consensus.
When you say "unilateral" action I see as something natural. I don't 
think the community has to tell very detailed how the Board conduct 
every step of their business, that's why I am askinf for their 
consideration for this matter. They should have a fair amount of 
freedoom to decide smaller things like this which as I said are just 
administrative decisions. If there was a guiding document telling them 
how to do on this matter specifically fine, but there isn't and that 
doesn't stop them to make some adjustments, should they have the same 
view about the example it gives to other people and organizations and 
*specially to products that get more aware they can start to be rejected 
for not having support for the current Internet Protocol*

Rich - answering your question here it is not about that their view 
matters more of less of anyone else. It's just about being practical 
that *this* type of adjustment can be taken by themselves without need 
of any document with guidelines as it was already done for the tool 
currently used. If in the future community reach consensus on how this 
should be done, not just for the Board but for other scenarios, then all 
will adjust for that.

Regards
Fernando