Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107

Ted Lemon <mellon@fugue.com> Tue, 31 March 2020 17:25 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527873A2546 for <eligibility-discuss@ietfa.amsl.com>; Tue, 31 Mar 2020 10:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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=fugue-com.20150623.gappssmtp.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 iypXk6_mzyHt for <eligibility-discuss@ietfa.amsl.com>; Tue, 31 Mar 2020 10:25:05 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 D9BE23A2548 for <eligibility-discuss@ietf.org>; Tue, 31 Mar 2020 10:25:04 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id c145so23850130qke.12 for <eligibility-discuss@ietf.org>; Tue, 31 Mar 2020 10:25:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=XOUDv9JzS0f+Yli59E13tAPKjOPIKPVLEtYQSWvJiTY=; b=VwdBnypscS9BKZvHVQN7Wwf2ByjEoZ+IKvdUQ4Ftt5CnrfhzK9urHALCfiaRee5gIu sEgvsaZfktzSPi4c+8LFwQ9iURMsLwwm2DogcmFKoV17sOnV5/i/QED4FZyrfwFrMuOQ mitMh6EAxB6lOi1EMNKm7LoUuR2jybLExwBDmcQy2+lQ3PIdmgq1VC8WvwUZEMNzm7Pz A5ZPe0wLtlUH/pEsjjXgRvsBTj+WBauqf0Bd989HUWbrXIRM9ycHGh8h6BDk5f/SnAkc sBt71UYEiRmb7kT9/egYJAScaiR/bMLeWHDQC8ZDR6/TOCyiqOTOCup01qfSGpsAz61c 10HA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=XOUDv9JzS0f+Yli59E13tAPKjOPIKPVLEtYQSWvJiTY=; b=BMwnaTm11e8rZWvI6iDQI4QaJUi7bEKMlFbg32Jd0Zh5jznYxuWKaI19isTMzvuabF /N+JjRSTxkcB09LwpHPGGc+VEHwIKLA2N38pbdizjgeOYlz1BrCUduWQ4bDMxXV/VKw0 hx3o2lwxsApOHHI7gxmOoOv5JXhCleFDYVqhRF4OTL17jnt+xWBPkalXnta/JYmwR9o5 q6lhIXs2A7iqMU7a9o/P2R6j5P3katQgIZ2eRvGQUCHhw0yA6s1VCB6YIRxvaT0UTwA3 2owXBjxHDUZ+3lqrewBQ7gowsoBljFyfH9ioVBCKP4TI1c85eoMcpOwrh+z93AU+qIDC CWxQ==
X-Gm-Message-State: ANhLgQ3ijgOZDY/ppUyK8LHi5BrZKavcKf1ICGPS4g6zqW2tmgD98iXA AFC/5CGjXjwDSoOP+a++s+/2s2D5kek=
X-Google-Smtp-Source: ADFU+vsR2eoG96/MfluffUtSFNYWUG8Oo38Faj3LS0MlsCQrVCqVQhRJsLU30KdvdU8wXNFmiGnL8g==
X-Received: by 2002:a37:a2c8:: with SMTP id l191mr5475268qke.120.1585675503672; Tue, 31 Mar 2020 10:25:03 -0700 (PDT)
Received: from ?IPv6:2601:18b:300:36ee:8df6:fe32:2c03:d33e? ([2601:18b:300:36ee:8df6:fe32:2c03:d33e]) by smtp.gmail.com with ESMTPSA id h11sm13417708qtr.38.2020.03.31.10.25.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 31 Mar 2020 10:25:02 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-43179FEB-9DD6-46EF-B7B3-A9635B9E8E75"
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 31 Mar 2020 13:25:01 -0400
Message-Id: <DF014A4B-24FF-454B-939A-467164DBED48@fugue.com>
References: <CAJc3aaNhe5pwvNrfJ26UKpKB2NDVScSNvuWyfP5Cg7vkM__tMg@mail.gmail.com>
Cc: Loa Andersson <loa@pi.nu>, Michael Richardson <mcr+ietf@sandelman.ca>, eligibility-discuss@ietf.org
In-Reply-To: <CAJc3aaNhe5pwvNrfJ26UKpKB2NDVScSNvuWyfP5Cg7vkM__tMg@mail.gmail.com>
To: Victor Kuarsingh <victor@jvknet.com>
X-Mailer: iPhone Mail (17F38)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/JN8b6mdedi_pD_TL_b6Lx1WTX6k>
Subject: Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 17:25:10 -0000

I don’t see how this helps with inclusion. We simply have no way to account for IETF 107 attendance. There’s no magical rule we can come up with that accomplishes that. 

We could have a double rule: if you attended 3 of IETFs 103-107, treating remote as in-person for 107, or you attend 3 of IETFs 102-107, then you are qualified. 

This errs on the side of inclusivity, but doesn’t follow the rules. 

> On Mar 31, 2020, at 12:35, Victor Kuarsingh <victor@jvknet.com> wrote:
> 
> 
> Loa,
> 
> 
> 
>> On Tue, Mar 31, 2020 at 12:25 PM Loa Andersson <loa@pi.nu> wrote:
>> Ted, et.al.,
>> 
>> 
>> 
>> On 01/04/2020 00:16, Ted Lemon wrote:
>> > On Mar 31, 2020, at 12:01 PM, Victor Kuarsingh <victor@jvknet.com 
>> > <mailto:victor@jvknet.com>> wrote:
>> >> - (1) We keep 3 out of 5 for IETF103 - 107 and just ignore 107 which 
>> >> means you really needed 3 out of 4?
>> >>
>> >> - (2) We keep 3 out of 5 for IETF103 - 107 and assume everyone got 107
>> >>
>> >> - (3) We keep 3 out of the 5 IETF103 - 107 and fine a way to assess 
>> >> "attendance" for 107?
>> > 
>> > Another alternative which is what I thought I’d heard proposed a while 
>> > back was to simply not count IETF 107, so we’d do IETF 102-106, not 103-107.
>> 
>> Yes that has been proposed and is the only workable proposal I've seen.
>> 
>> We need to seat the NomCom fairly soon, so lets do 3 out of 5, for 102
>> to 106.
> 
> Sorry to drag this out, but in this proposal, someone may not have attended IETF 102 in person, gone to 2 of the next 4 IETFs and planned on attending IETF 107 and would therefore be excluded.
> 
> If we made it 2 or 4 and ignored IETF 107, there it would be been in line with any attendance plans and decisions one would have made.  It does lower the bar (2 of 4 vs 3 of 5), but does not raise it or change the rules.  We would fault on the side of inclusion vs. exclusion in this case. 
> 
> This would also us to seat the Nomcom quickly since the only adjustment is we ignore IETF107.   
> 
> I fear that including IETF meetings into the equation retroactively can lead to challenge (as noted). 
> 
> regards,
> 
> Victor K
>  
>> 
>> Once we have the NomCom seated, we have one year to do real work, if we
>> have continued problems with further cancelled meetings.
>> 
>> /Loa
>> 
>> > 
>> > 
>> 
>> -- 
>> 
>> 
>> Loa Andersson                        email: loa@pi.nu
>> Senior MPLS Expert
>> Bronze Dragon Consulting             phone: +46 739 81 21 64