Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev

S Moonesamy <sm+ietf@elandsys.com> Sun, 28 April 2019 08:34 UTC

Return-Path: <sm@elandsys.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 5CC091201AB for <eligibility-discuss@ietfa.amsl.com>; Sun, 28 Apr 2019 01:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1] 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=opendkim.org header.b=oi/IwWnf; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=TO8UW8hX
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 cufCylZu1-Td for <eligibility-discuss@ietfa.amsl.com>; Sun, 28 Apr 2019 01:34:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 592A31201AA for <eligibility-discuss@ietf.org>; Sun, 28 Apr 2019 01:34:11 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.55.122]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x3S8Xpvu007100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 28 Apr 2019 01:34:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1556440446; x=1556526846; bh=SdojHr8WlRoHcWfOxxulQiIMGu1BpFuNI2xpAnplXcw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oi/IwWnfJcavOC6IoXXGozMzHYHpmqQ/0wJorhl/25KPFanDmKlkL4cjOVJex7S1+ rEtXKtHx+aY6SUwp6yXzj/YWmckhDd+pKuNvfRCrOZgJV4GFTwpR01LuE/isuhJq2G k0PPtM4Cbo0GqU4RRba9r2PaX4y4sAffTLgvYeNQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1556440446; x=1556526846; i=@elandsys.com; bh=SdojHr8WlRoHcWfOxxulQiIMGu1BpFuNI2xpAnplXcw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TO8UW8hXgH6+tY4iaFjMEpgn+Fj7Q93CmlorN1R3sk0Vu7K+wlLGXh5ey1pwuo73+ ikE4upUgHJT6pBYwn0Aos/rfZwU1y3ClIYVyMoHe47ooh/E6wWsPSi3sVhoRscsXVt FLFwEYLGl6f0hpu6jasFoBULxiLr7ZouYrNxv8gA=
Message-Id: <6.2.5.6.2.20190428003615.0b9aebd8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 28 Apr 2019 01:27:31 -0700
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: eligibility-discuss@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, John C Klensin <john-ietf@jck.com>
In-Reply-To: <20190427221856.sxr46qr7j5niwrk4@mx4.yitter.info>
References: <20190424201939.GM3137@localhost> <6.2.5.6.2.20190424134823.0c9faf68@elandnews.com> <20190424211123.GO3137@localhost> <6.2.5.6.2.20190424144539.0cabcde0@elandnews.com> <20190424234334.GQ3137@localhost> <11F97591808485C30AD98A22@PSB> <20190426150436.v4svwa67xja6267r@mx4.yitter.info> <0a1e01d4fc6c$10b93df0$322bb9d0$@olddog.co.uk> <20190427155921.i32pftxdbkvv7ist@isoc.org> <6.2.5.6.2.20190427094440.12099d10@elandnews.com> <20190427221856.sxr46qr7j5niwrk4@mx4.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/cWJYWW-j7he_iyNxaFmysWr4NFM>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
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: Sun, 28 Apr 2019 08:34:24 -0000

Hi Andrew,
At 03:18 PM 27-04-2019, Andrew Sullivan wrote:
>That does not clarify the issue of "participation" at all.  We can't
>have it be a criterion of eligibility if it does not have a
>well-defined public meaning.

There was a paper about "In-Person and Remote Participation Review at 
IETF: Collaborating Without Borders" [1].  The paper mentioned that 
"the remote participant was able to participate and interact by voice 
and text".

There was a presentation [2] by the IETF Security Area Directors in 
which the following is mentioned: "IETF-wide meetings are held three 
times a year, participation can be in person or remotely".  There is 
also an IETF Chair report [3] in which remote participation is 
mentioned.  According to the IETF Chair, "We're getting good 
participation from our remote folks".

> > Please see draft-sullivan-mtgvenue-decisions-00 as it discusses about
> > different types of attendees.
>
>I don't see how that is relevant.

The current discussion is about the criterion of eligibility.  Please 
see below.

>Actually, there are 10 randomly-chosen people from a pool of people
>who have been qualified from a well-defined meaning of having
>participated in the processes of the organization.  Whether that

There is "having participated" what you wrote.  However, the 
definition used in RFC 7437 is about 
attendance.  draft-sullivan-mtgvenue-decisions-00 discusses that in 
Section 3.2.

Regards,
S. Moonesamy

1. https://arxiv.org/abs/1805.09140
2. 
https://www.itu.int/en/ITU-T/Workshops-and-Seminars/ict-sec-chaldc/Documents/Presentations/S6P2%20Kathleen%20Moriarty.pdf
3. 
https://datatracker.ietf.org/meeting/103/materials/minutes-103-ietf-201811071730-00