[Eligibility-discuss] Warren Kumari's No Objection on draft-ietf-elegy-rfc8989bis-04: (with COMMENT)

Warren Kumari via Datatracker <noreply@ietf.org> Wed, 01 February 2023 16:20 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: eligibility-discuss@ietf.org
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 923ABC1522AA; Wed, 1 Feb 2023 08:20:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-elegy-rfc8989bis@ietf.org, elegy-chairs@ietf.org, eligibility-discuss@ietf.org, barryleiba@computer.org, barryleiba@computer.org, dromasca@gmail.com, opsdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <167526845257.58861.18143942889282130562@ietfa.amsl.com>
Date: Wed, 01 Feb 2023 08:20:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/EaCy0MiEoVQTiyLn4rdALEkSxR8>
Subject: [Eligibility-discuss] Warren Kumari's No Objection on draft-ietf-elegy-rfc8989bis-04: (with COMMENT)
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF eligibility procedures <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: Wed, 01 Feb 2023 16:20:52 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-elegy-rfc8989bis-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-elegy-rfc8989bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

"The two-per-organization limit in [RFC8713] complicates such an attack.  To
circumvent it, an organization must either [...] (3) propose candidates with
false affiliations."

It's not really clear to me what a "false affiliation" actually is -- in some
other organizations, where voting is a thing, it is common for there to be lots
of one or two person consulting companies. These consultants all have different
affiliations, they just *happen* to have contracts with the same larger
organization, and also just *happen* to all vote in the same way... Would these
be false affiliations? Note that I don't really view this as major issue -- if
we end up in a scenario where people are gaming this, then we've already lost.

As a nit: 'either' is generally used with 2 options.

Thanks to Dan Romascanu for the OpsDir review.