Re: WG Review: Stay Home Meet Only Online (shmoo)

S Moonesamy <sm+ietf@elandsys.com> Fri, 10 July 2020 17:57 UTC

Return-Path: <sm@elandsys.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 3379C3A07E0; Fri, 10 Jul 2020 10:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 yXEa0qthb_df; Fri, 10 Jul 2020 10:57:54 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 45DE13A07D6; Fri, 10 Jul 2020 10:57:43 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.28.158]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 06AHvOFN026477 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Jul 2020 10:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1594403858; x=1594490258; i=@elandsys.com; bh=6giSwO+CDNC8uDxcsIXhvTzJ0r1pfG+fgBJ3+jIDejg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rqszCFi7IiqiM6papaJDkS+/zs1c0MmQ1GTxC9xbzkB7cgV78OI8jqsIhO5MRRBcw YmsP7kogaLST+EWLcEGAU0KewJI5oqIj8VNftSUSaJQm2ebw9bz8yJE1TqT8BVGSDt os237NWEIuRN1aqT/wplrq9obQ2kHEDH3fTPGUCk=
Message-Id: <6.2.5.6.2.20200710102806.0b084a90@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 10 Jul 2020 10:56:50 -0700
To: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: WG Review: Stay Home Meet Only Online (shmoo)
Cc: Alissa Cooper <alissa@cooperw.in>, IESG <iesg@ietf.org>
In-Reply-To: <CALaySJJbNHu=ktzeUX+k5Rj2bt2UQkx262mvD7wHLzEVXw3VxQ@mail.g mail.com>
References: <159318840162.4951.12569119165623562334@ietfa.amsl.com> <6.2.5.6.2.20200627023025.0b145350@elandnews.com> <5C58F041-9991-49DA-98B6-6700499DFBC9@cooperw.in> <6.2.5.6.2.20200709132444.098ec410@elandnews.com> <CALaySJJbNHu=ktzeUX+k5Rj2bt2UQkx262mvD7wHLzEVXw3VxQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FB3ET-wAQ18NFme1sgoWRm_Skpo>
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, 10 Jul 2020 17:57:58 -0000

Hi Barry,
At 06:14 AM 10-07-2020, Barry Leiba wrote:
>That wording was to be clear that 1-1-1-* is what the IETF community
>wants to happen, but to allow IASA flexibility in implementing it,
>given the realities of meeting venue selection and scheduling.  We did
>not want someone to get the mistaken idea that if we were unable to
>secure, say, an Asian venue in one particular year, the policy was
>being violated, while making it clear that IASA needs to do its
>collective best to maintain the long-term balance as set out in
>Section 2.

The policy is currently not working.  It would be reasonable, in my 
opinion, for me to go and argue with the IETF Administration LLC 
about that as I am aware that there is a pandemic.

>Indeed, and that absolutely needs to be dealt with.  In fact, I,
>personally, think it's one of the most important things we, as an
>organization, have to deal with, and I hope we can move forward *now*
>with what's been discussed on the eligibility list.  Maybe
>draft-carpenter-eligibility-expand is the right start for that, but we
>MUST correct the situation wherein some of our active, valuable
>participants do not have the same status simply because they don't
>come to in-person meetings.
>
>That said, I'm OK with separating that task from the tasks defined for SHMOO.

I just saw the message at 
https://mailarchive.ietf.org/arch/msg/ietf-announce/O9r8TOGOY5KMawJMFw9e6YdXqdM/ 
I raised an issue about the milestones with the IESG.  That is a 
requirement, as specified in Section 2.2 of RFC 2418.  In my opinion, 
the action taken by the Internet Engineering Steering Group (IESG) is 
not compliant with RFC 2418 (BCP 25).  It is very unfortunate that 
the action was taken while the proposed charter was being discussed.

I don't think that it is appropriate for me to impose my views on you 
or any other IESG member.  if the IESG, as a whole, is not persuaded 
by what I wrote previously, I doubt that there anything except for an 
appeal could change that.  May I ask for 48 hours to take a decision 
about that?

Regards,
S. Moonesamy