Re: LLC Board Meeting Details - 14 May 2020

Alissa Cooper <alissa@cooperw.in> Fri, 08 May 2020 16:19 UTC

Return-Path: <alissa@cooperw.in>
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 4F3D83A0C4A for <ietf@ietfa.amsl.com>; Fri, 8 May 2020 09:19:19 -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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=cooperw.in header.b=C02NBp4s; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=oCj2xRjK
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 J2JCTiMsGN2O for <ietf@ietfa.amsl.com>; Fri, 8 May 2020 09:19:17 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFF313A0C49 for <ietf@ietf.org>; Fri, 8 May 2020 09:19:16 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2AB875C01F3; Fri, 8 May 2020 12:19:16 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 08 May 2020 12:19:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=U CW5y/fOoGa4XkFBkn2B8QCzDhwzicnhRE8EaAN0wYM=; b=C02NBp4sRg/r9xjlX WJ9HOx9vGnX+pBRvOCIdd6wbWFN9m2sR2a/jcb4z0gaZL08vniHA9uVOXMqCQD/I jywXYoFc9uXTKts6qSP7B65H56zAo7pJZJrG7/w5sjG2q6x2GBIlkUiUBxZSUKW0 HAk+WdSCTIau70rL9WES6Q5F5cEysee8PYG52Oaf3pDQCz2M6T1HqRITO9aR4+sw x7fxafpuadOSZ7RE0qO0fJs+uD89v6F2Qir3Mj3nmea3J2cEdlR9V6idZ123TowC 29OaJclFAaIRiRZ3RQVLmq0Jv/GOHjCLrvNk6XwJUeS7GZ0wzck6/p2SaTPnDHEn KSZCg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=fm2; bh=UCW5y/fOoGa4XkFBkn2B8QCzDhwzicnhRE8EaAN0w YM=; b=oCj2xRjKgbLTBaz696TqRGt68hLe2QPzQyOefBx33C1s6P6au7XVMi1Mk s9CapxifdR2uncaoNSZnkdMnyv01BqOVpnelD14a6Lf4AtpM503tnmJDX6lgb9DT vVI3L4DyP4IOcG8x8Rf9/Pf/mrH98QTAIs0i1APXThtnuf1kjKRXkQKd1SOWReBa WYptsvNCyUCJrK4GcTWZlxX/wWklbQmWvJsnXNDEcBnl8tHnFz6UPKr8p519xYNa 9peSSxsTpZ1iRtkEz1CZz7xHCCp5Jid88VQwTiyb1sTlb+bATFQbpafRLiz5OQIs afVk+S7Osej8TLCmKpA3JQeQGRUcw==
X-ME-Sender: <xms:g4a1XrNXMmkbPUeVI4qhevX2RVnuabkIPxDnhwZR8NRY0SCwgOfZyg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrkeefgdeffecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuggftrfgrth htvghrnhepkeeitedvtdefveehgeetvdeljefhtdeijedvleeujeelvddvteegveevgfej veeinecuffhomhgrihhnpehivghtfhdrohhrghdpghhoohhglhgvrdgtohhmpdifvggsvg igrdgtohhmnecukfhppedujeefrdefkedruddujedrkeegnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrd hinh
X-ME-Proxy: <xmx:g4a1XsgWZahWwJhQDQRxOOAtIy-qP_mS91tEhqpcRg5CvCQ9Fontxw> <xmx:g4a1XnD45eVImGcQoPrTEyUEBofWGoA-C35ydC9XSH3nS9NYm_p1_w> <xmx:g4a1XoVSwklcx2BP7KLiKp6dwzRLofnis0SQivBrf-pm-9Hf2VqeHA> <xmx:hIa1Xn5Dkd788DXKHh9tmunvtMOGmkrbzNo5ArouH93aM5mGZBPkhw>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.84]) by mail.messagingengine.com (Postfix) with ESMTPA id 9F0C130661E6; Fri, 8 May 2020 12:19:15 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
Subject: Re: LLC Board Meeting Details - 14 May 2020
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <fc27f4e6-c71a-a266-f501-96a0ed637367@gmail.com>
Date: Fri, 08 May 2020 12:19:15 -0400
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D35A1DD-72E2-4E09-8A81-32770D357D29@cooperw.in>
References: <158889282783.23704.1421198034874120499@ietfa.amsl.com> <fc27f4e6-c71a-a266-f501-96a0ed637367@gmail.com>
To: Fernando Frediani <fhfrediani@gmail.com>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PTA6QiX2i-fGI1UmG1DmvL-rPb4>
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 16:19:19 -0000

Hi Fernando,

> On May 8, 2020, at 11:21 AM, Fernando Frediani <fhfrediani@gmail.com> wrote:
> 
> I guess the Board/LLC either missed all the discussion about trying to use tools and SaaS that have IPv6 support (which is not the case of WebEx) or they have followed it and decided not to respond to it with their view at all.

I didn’t miss it. I read the emails. The discussion seemed inconclusive and opinions were quite varied. 

I think (just my opinion) if the community is unhappy with the tools the IETF is using and providing to get its work done, what would be useful is an RFC that spells out the guidelines the community wants the LLC to follow when choosing tools to provide. That way we can feel confident that we’re following community consensus and we can be consistent in applying the same guidelines with each choice.

Best,
Alissa

> 
> A pity in my view this pragmatic way of doing things and not willing to compromise on such small things in order to give the example.
> I am convinced that replacing the tool used for these meetings for another one that supports IPv6 is not a big deal and will not compromise the results and the efficiency that Board can keep conducting its business.
> 
> Fernando
> 
> On 07/05/2020 20:07, IETF Administration LLC Board of Directors Chair wrote:
>> IETF LLC Board of Directors meetings are conducted via web/teleconference. Members of the community are welcome to attend certain portions of these meetings as observers. Regular meetings are divided into four sections:
>> 
>> 1. Open (to Observers)
>> 2. Board + Support Staff Only
>> 3. Board + Executive Director Only
>> 4. Executive Session (Board-Only)
>> 
>> The next meeting will be held on Thursday, 14 May 2020 at 12:00 PT (19:00 UTC). WebEx and Dial-in information is at the bottom of this message and also at <https://www.ietf.org/about/groups/llc-board/meeting-info/>.
>> 
>> The agenda for the meeting can be found at <https://www.ietf.org/about/groups/llc-board/minutes/2020/>.
>> 
>> A calendar of upcoming public meetings can be downloaded or subscribed to at:
>> https://calendar.google.com/calendar/ical/ietf.org_vmffrv4hq14aqpedenuv5v42hs%40group.calendar.google.com/public/basic.ics
>> 
>> 
>> -------------------------------------------------------
>> JOIN WEBEX MEETING
>> https://ietf.webex.com/ietf/j.php?MTID=mbb9c7dbde03b4be9f055368b0bc9d117
>> Meeting number (access code):  640 897 669
>> 
>> 
>> JOIN BY PHONE
>> 1-650-479-3208 Call-in toll number (US/Canada)
>> Access code:  640 897 669
>> 
>> 
>> 
>> IMPORTANT NOTICE: This WebEx service includes a feature that allows
>> audio and any documents and other materials exchanged or viewed during
>> the session to be recorded. By joining this session, you automatically
>> consent to such recordings. If you do not consent to the recording,
>> discuss your concerns with the meeting host prior to the start of the
>> recording or do not join the session. Please note that any such
>> recordings may be subject to discovery in the event of litigation.
>> 
>