Re: NomCom eligibility & IETF 107

S Moonesamy <sm+ietf@elandsys.com> Sat, 14 March 2020 04:11 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 BB7073A0C9D for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 21:11:53 -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 1dtyLl4KJUcM for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 21:11:49 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A57EB3A0C9C for <ietf@ietf.org>; Fri, 13 Mar 2020 21:11:48 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.59.242]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 02E4BVGa026396 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Mar 2020 21:11:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1584159104; x=1584245504; i=@elandsys.com; bh=yyTjgp5BKU3UVDDsJdATKch2RiW+73b+0AAaS56oZfI=; h=Date:To:From:Subject:In-Reply-To:References; b=h2vI0B8BRuAwxH0H/+3kXxKIaIw6hcp0pzDXsuBzLmjlAFri6g20EC/MiW0obJt2x sv8zKKvIR+sWcaExOLdMr7RzEALsO5YfyRr2PWz3fByYX3zhqT+k3Q4nc7aFU7Tam2 TxCQqZ41Ev6mR0m1CxIc1LplcdlxiAFMB0J14eX0=
Message-Id: <6.2.5.6.2.20200313205456.0c881dc0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 13 Mar 2020 21:05:34 -0700
To: "Livingood, Jason" <Jason_Livingood@comcast.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: NomCom eligibility & IETF 107
In-Reply-To: <CALaySJ+r2OrFVbZj=3fTRUapkDkxap2T-p+QzNfaqK4N0c+haQ@mail.g mail.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <20200313162255.GB8656@faui48f.informatik.uni-erlangen.de> <20200313204317.GR21734@vurt.meerval.net> <CAA=duU0jN0y12_HpzzK73BRD+x19ZQn74V=ju2_wwS-RUL_9Yw@mail.gmail.com> <CALaySJ+r2OrFVbZj=3fTRUapkDkxap2T-p+QzNfaqK4N0c+haQ@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/Sz6BfoMXMwrMynxLiHPA4aQq0xw>
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: Sat, 14 Mar 2020 04:11:54 -0000

Hi Jason,
At 04:54 PM 13-03-2020, Barry Leiba wrote:
>Just a reminder: for the purpose of THIS discussion, we just need to 
>figure out what to do for THIS NomCom selection, which will happen 
>before IETF 108.  Of course, that NomCom might have to sort out how 
>to do its work completely remotely, but that's its job, not ours.

Will there be an open IETF LLC position?

Regards,
S. Moonesamy