Re: [Mtgvenue] [admin-discuss] Consultation on IETF Meeting venue assessment

Eliot Lear <lear@cisco.com> Thu, 04 February 2021 08:18 UTC

Return-Path: <lear@cisco.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA37C3A0B59; Thu, 4 Feb 2021 00:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 pQmGg9wWpLSu; Thu, 4 Feb 2021 00:18:23 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4DE03A0B5B; Thu, 4 Feb 2021 00:18:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16670; q=dns/txt; s=iport; t=1612426703; x=1613636303; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=96LI5wAfxEdNmwb0Kon5PD2D2YjXUKFkTXvpGUgWtpo=; b=ahPX+1TGZvI4axmCCAuXI2FI4h8NrqXHjn3cpwTW8BK4lNWD2CLIORhv CR93XVlKP1cr4uP4K0MmcWkHgorAad+bnJeDxxTyMehFcE9B17vCG0n3d RBMOObE9xdkpy+8dILEG6Zcn9T0vWvG8vMtVWQBNB8DI9b/7Ldfrah9hH 4=;
X-Files: signature.asc : 488
X-IPAS-Result: A0ABAgBirBtglxbLJq1iHAEBAQEBAQcBARIBAQQEAQGCD4EjgX5WAScSMYRAiQSIUgODF4RXgi+KCYY1gWgEBwEBAQoDAQEYAQoMBAEBhEoCgX0mOBMCAwEBAQMCAwEBAQEFAQEBAgEGBBQBAQEBAQEBAYYJByYNhXMBAQEDAQEBIUsLBQsLGCcDAgIhBh8RBhMUgxIBglUDDiAPsCZ2gTKBO4McGGqCUA2CFhCBOIFThSmGQ0GCAIERJxyCKC4+ghtCAQECF4EIFl6CYzSCLASBVQEPgV0eIAEUDDALC14IGDsMkQeCRIlJgXCJCZBrW4MEgymBOoRThwGGI4UoAx+DLoEziROFQI9rljqJIoMBjkoqYoNyAgQGBQIWgW0hgVkzGggbFTsqAYI+CTUSGQ2JNoR3DgmIYoVEAkADMAIFMAIGAQkBAQMJiVCCRQEB
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,400,1602547200"; d="asc'?scan'208,217";a="33204370"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Feb 2021 08:18:18 +0000
Received: from [10.61.237.35] ([10.61.237.35]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 1148IHWS020467 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 4 Feb 2021 08:18:18 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <0AB6B02A-B917-4C8B-867E-F20DEF2FED2C@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9B1DCB0D-5E83-491C-A44C-750D637FD2CD"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Thu, 04 Feb 2021 09:18:16 +0100
In-Reply-To: <7A39E361-6EED-4157-82BB-B56E7921FECB@ietf.org>
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, mtgvenue@ietf.org, admin-discuss@ietf.org
To: Jay Daley <jay@ietf.org>
References: <CAB75xn4N3zrfiHAdh_djQxui2-U5CutcN2sLzBE6DiWTm33QYQ@mail.gmail.com> <7A39E361-6EED-4157-82BB-B56E7921FECB@ietf.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.237.35, [10.61.237.35]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/UelhpAYv_yfTJWnICNE63dEGGrE>
Subject: Re: [Mtgvenue] [admin-discuss] Consultation on IETF Meeting venue assessment
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2021 08:18:26 -0000

To add, one of the requirements is wheelchair accessibility.  Now… perhaps this is a given, these days, and so it’s not worth mentioning, but I did note its absence.  Personally I wouldn’t complain if you applied a more general ADA-like requirement, but that isn’t what the doc says, for reasons quite honestly I don’t remember.

Also, on human rights, there was a strong consensus at the time to not choose venues based on such a matter.

This is captured in the following non-objective:

   Politics:
      Endorsing or condemning particular countries, political paradigms,
      laws, regulations, or policies.


Our requirements are stated in terms of safety and/or security of the attendees, the likelihood of the ability of people to get to and from the venue, and the ability of attendees to have unimpeded Internet access. This may seem like a subtle difference, but the language of our requirements excludes HR so that it is clear we are not making a political statement by including or excluding a venue.  To do otherwise has implications for how the IETF is perceived, which itself might limit support for, and participation in, our community in ways we would wish it hadn’t.

Eliot


> On 4 Feb 2021, at 07:55, Jay Daley <jay@ietf.org> wrote:
> 
> Thank you Dhruv, I understand the error now. I will log this as an issue and amend the assessment form.
> 
> Jay
> 
> --
> Jay Daley
> IETF Executive Director
> 
> 
>> On 4/02/2021, at 6:36 PM, Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>> 
>> 
>> Hi Jay,
>> 
>> I agree with Stephen/Eliot. IMHO the "Internet Access" in RFC 8718 is not fully aligned with the "Internet Freedom Score" at freedomhouse.org <http://freedomhouse.org/>. For one, RFC 8718 focuses on filtering on means of communication whereas freedomhouse seems to focus on content filtering.
>> 
>> Looking at the map link - https://freedomhouse.org/explore-the-map?type=fotn&year=2019 <https://freedomhouse.org/explore-the-map?type=fotn&year=2019>, we don't have any country but Japan that meets the criteria in Asia. So, no Bangkok, Singapore, or Seoul! And not sure how the city/venue exception may override the mandatory criteria! Maybe that can be clarified. We should look for sources that focus more on the means of Internet Access more closely aligned to RFC 8718? In the absence of which, perhaps this should be a subjective judgment call.
>> 
>> Thanks!
>> Dhruv
>> 
>> On Thu, Feb 4, 2021 at 4:32 AM Jay Daley <jay@ietf.org <mailto:jay@ietf.org>> wrote:
>> Hi Eliot
>> 
>>> On 3/02/2021, at 9:47 AM, Eliot Lear <lear=40cisco.com@dmarc.ietf.org <mailto:lear=40cisco.com@dmarc.ietf.org>> wrote:
>>> 
>>> Signed PGP part
>>> Hi Jay,
>>> 
>>> I am uncomfortable with what I am reading.  The criteria you have listed don’t seem to me to be well correlated to RFC 8718.
>> 
>> Each of the criteria is taken directly from RFC 8718, though with simplified language, and is marked as to whether that is a mandatory or important criteria in RFC 8718.  If the language simplification is a problem then please let me know.
>> 
>>>  Is it your intent to update 8718?
>> 
>> No.  The intent is that RFC 8718 contains such requirements as that for "Internet Access", which we need to turn into an objective, fair and repeatable assessment process.  This is attempting to do that.  If you think we have misinterpreted the criteria then please let me know.
>> 
>>>  The goal is to have a successful meeting.  We have done so at two venues that your assessment criteria would reject, and conceivably do so in India and Mexico, which your criteria would also reject.
>> 
>> In order to address any issue here I need detail - can you please specify why you think India and Mexico would be rejected using this assessment and how that indicates failings in the assessment?
>> 
>> cheers
>> Jay
>> 
>>> 
>>> Eliot
>>> 
>>> 
>> 
>> --
>> Jay Daley
>> IETF Executive Director
>> jay@ietf.org <mailto:jay@ietf.org>
>> 
>> 
>> 
>> 
>> --
>> admin-discuss mailing list
>> admin-discuss@ietf.org <mailto:admin-discuss@ietf.org>
>> https://www.ietf.org/mailman/listinfo/admin-discuss <https://www.ietf.org/mailman/listinfo/admin-discuss>
>> --
>> admin-discuss mailing list
>> admin-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/admin-discuss