Re: Update on feedback on US-based meetings, and IETF 102

Vinayak Hegde <vinayakh@gmail.com> Fri, 14 April 2017 09:06 UTC

Return-Path: <vinayakh@gmail.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 61A5F126B6E; Fri, 14 Apr 2017 02:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=gmail.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 QVQ5UkVmF-NL; Fri, 14 Apr 2017 02:06:41 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 AA8931201F8; Fri, 14 Apr 2017 02:06:41 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id p68so64949785qke.1; Fri, 14 Apr 2017 02:06:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=316zf3Ma9DNlsGA740pZl5rsIFuOYE/b0gG+4n4g6cY=; b=SpnDhQ6Z84ZVdqCTXrhPSqhjoRCJ1ue7wn3Q2SYomaQ3Hx2HF+OKzXRR3A2VThvPbO RavBVwVoWauljdWCkgBQl68UD2Ci6mpqiEZR14K4b7Bt3yrylsI1AL5h10wbHXVisk1F ohU/0EZKVdcqLFyPTQZ2tGdQKGq/LsQiHrzn6tCo9drhKsteDL8xzWPge8vIWzFj0L8l lRAX50sDcpGuyE/Fgs43KexNu9GNpEVjIm9YGEcmn/ZOXy7+iLObvk9WX5VDQZL+Cfnu RUajzt71aCDmSId4yZVOpY2wGEYeQgITaazeAS4Td35X3rUCxWmhxvVIEtngap8sqkDd GZEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=316zf3Ma9DNlsGA740pZl5rsIFuOYE/b0gG+4n4g6cY=; b=fEtdL2/Db7xtPZ6T2UAPnGAuDUMUnixeqp8JyYuPp661GtAJ5IqzaTKZpMSopJ8vda PgNPtiHqHXpXWPREW+nDqq2oxVkPzGmbZXexBtnLsaQVrVzy34WVz00zGiT3v3N2FvQq dJA27TWgGDuNZqOkKjU6DkO/bUMXTpvv+vrDAHG/5WuwxWl7DY1lgSeF8xXtOVwN9jGw PiGy4EXaPORX2KsT1DLXYLDgxenH+2uepoiB/xism8bz6m6cc0fr3lQ0a3X67HcCSbq/ ccfVAX6kAu+Hi26A6eWAdPbloPb/bumu2C87hQKgnKvF1r7LjrLMV+LTlzWXgIt1qT4u 9c0A==
X-Gm-Message-State: AN3rC/5W165tq8lLgmnVBjnTi+B51m1ViJ6/7qDgjdENoC7dLxbTWtwG xO0PSZYA+/YqxSzn6LESHf3EfdtPYxoD
X-Received: by 10.55.99.69 with SMTP id x66mr5928586qkb.129.1492160800721; Fri, 14 Apr 2017 02:06:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.34.104 with HTTP; Fri, 14 Apr 2017 02:06:40 -0700 (PDT)
In-Reply-To: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com>
From: Vinayak Hegde <vinayakh@gmail.com>
Date: Fri, 14 Apr 2017 14:36:40 +0530
Message-ID: <CAKe6YvN08wvC9N_GQQc2nNYa61EcqKmtZ=ajQUnfBUJvtEC6pw@mail.gmail.com>
Subject: Re: Update on feedback on US-based meetings, and IETF 102
To: IETF Discussion Mailing List <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DPW_IdeSiWL4iM-oFZWXzd3YAd8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 14 Apr 2017 09:06:43 -0000

On Thu, Apr 13, 2017 at 5:09 AM, IAOC Chair <iaoc-chair@ietf.org> wrote:
> On March 31, 2017, we put out a request for input on experiences with travel to the recent IETF meeting in the US, and solicited information pertinent to plans to attend IETF meetings within or outside the US in the coming years.  We have had over 350 responses to the questionnaire, and we appreciate each and every one of them!   We did not gather the data in such a way for it to reflect a representative sample of the IETF community, or of potential meeting attendees. But we did gain insights from those who responded that we did not have before.

Can the data be put out in an anonymized fashion without revealing PII
(such as name or email) ? The data has been interpreted for the
community but it might be useful for the community to look at the data
gathered as well. It might help change opinions or people on the fence
or people to rethink their positions.

> Over 40% of the respondents said they had attended 20 or more IETF meetings, and over 50% of them said they were authors of active working group documents.  Slightly more than 40% stated US residency, and just less than 60% said they were not US-resident.

Since the US-meeting disproportionately affects those traveling to the
US, I think that might be an axis against which data needs to be
interpreted. The burden on many US citizens would be (possibly) extra
travel in case the meeting is not located nearby (such as in Canada or
Mexico).

Also many nationalities might not need to apply for US visa or face
lesser stringent barriers to entry. So knowing the country of
citizenship might be useful in the data.

> The general comments on meeting in the US played along the same lines as has been shared on the IETF discussion list:  people are variously for moving all meetings out of the US, or adamantly against, or somewhere in between, each position supported by good reasons.

Again might be useful to see the data.

> The IAOC is continuing to gather data on travel to the US, concerns about traveling outside of it, and what alternatives are possible for IETF 102.  Our focus is currently on whether holding IETF 102 in San Francisco is the best option to meet the needs of IETF work, recognizing that we cannot predict the future.  While it may take several weeks to allow for review and negotiation of any alternatives (if applicable), we are moving as quickly as possible because we realize that people will need time to plan their travel.

Is there a rough timeline for this ?

-- Vinayak