Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice

Ted Lemon <mellon@fugue.com> Fri, 20 April 2018 15:12 UTC

Return-Path: <mellon@fugue.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 9C72712D7F9 for <ietf@ietfa.amsl.com>; Fri, 20 Apr 2018 08:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Y7sTzww-wEQk for <ietf@ietfa.amsl.com>; Fri, 20 Apr 2018 08:12:03 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (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 9F4BE12D7EF for <ietf@ietf.org>; Fri, 20 Apr 2018 08:12:03 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id z23-v6so10019837qti.5 for <ietf@ietf.org>; Fri, 20 Apr 2018 08:12:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XYQLLQDThJ+0k/1utKrID8X+H6MV/6BDHsfSjexC7TI=; b=v66fzzn3pdjcngPPE7hIElC/txMUJhr7EENyL/HubrlMg6vED5msjMHZzRC7mhMFGB CGW0WmwJacoyFRvVxnOmczESibExACOfvFBRoZJnJ5IyjHQAZskXrxLpDzmoXT+y+S11 yR0zVoSbBsd1iiPSu/BPw2DcgFkr5VxCRHrrHcOKP+41Vk0NKVcMMMnfdNSNDCRT4W8O WzAk6dijTTcxsMREQlr9bf5rqx9xQIbboB3InPmwlg3hl+NKG2TZalrOOx26qtZHERwP oy/SyasXvwxup9FiUjmWBBi2caJ/TZ19cDu+k1GsqKc4rja6mo9axyN1jzdugs2dQCSl xLAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XYQLLQDThJ+0k/1utKrID8X+H6MV/6BDHsfSjexC7TI=; b=E+czloAVegCKYTlZxCtwVv6q40zhuf5YV5SDhSsJLgHWAcaYu6KWCvp7Dy2zwI8iWP OnRp8cQqdZpok5u/gaNfhxRORg4M6BfEdLKUFkwi7H3k0yYsjRGofW+57z8p3aAFrbbm nOXJ3AGwUnh/UQDf/wbFAaOraQiBSLC9+TGLXpiKT3RBAvpH3gcu2Hs6RC96Z/FgI+No Mro9B9F6lM/WUPVShEeAajdVvJ9Yn+MxUKd6mpkc1AcufmH+Jmv+MTBxZcYjoeJGwYme XKrYaYLuCKzKQbJwMs0k8HdLB8r1hZJ12+IuKKLDjX+sUAS7RYrizqRTKyUPdGzPOeqR nfpg==
X-Gm-Message-State: ALQs6tDQBFs0/pvkUUXvGZHi7hAqLq4igkFGlJldGFqKboQpUmY+nNh7 WrDqTpzOdYG4PaR95w4eHEbaCg==
X-Google-Smtp-Source: AIpwx48UwIhoKX369UjL05Ub1cEFlfvc4NXhqx6fHUzmv79jiSN4RJDl7HnxidlEPKVRpwZVW5u1pw==
X-Received: by 2002:aed:2306:: with SMTP id h6-v6mr11859714qtc.287.1524237122709; Fri, 20 Apr 2018 08:12:02 -0700 (PDT)
Received: from cavall.lan (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id e13-v6sm5518349qte.40.2018.04.20.08.12.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 08:12:02 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <834A3E40-1985-44F0-8BA3-D61CE3F94686@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6F77D2CD-6D55-453C-B37F-5E8C615483CF"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice
Date: Fri, 20 Apr 2018 11:12:00 -0400
In-Reply-To: <CABcZeBPGyykdDLYHViaBQA4b+icJruOsJm9HwW6ppXEco7nS5A@mail.gmail.com>
Cc: Richard Barnes <rlb@ipv.sx>, mtgvenue@ietf.org, IETF discussion list <ietf@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
To: Eric Rescorla <ekr@rtfm.com>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <20180419013457.fq4ruqj7p4lfwxb4@mx4.yitter.info> <CABcZeBPXUqe6ixF+Yx7P6E3Jt3fGjAMUrP368DTedGq-O-T61Q@mail.gmail.com> <CAL02cgSrdhEtPUQMU80zhr6Xg2KyP=Fi-t7a0De6hkO3_3cDZg@mail.gmail.com> <47589225-F8D9-4773-A2D3-8CD253DF8849@fugue.com> <CABcZeBPGyykdDLYHViaBQA4b+icJruOsJm9HwW6ppXEco7nS5A@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KCPtiSWHPsvn28_HzYS_M4tr7z8>
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, 20 Apr 2018 15:12:06 -0000

On Apr 20, 2018, at 11:06 AM, Eric Rescorla <ekr@rtfm.com> wrote:
> Thanks for making this point. I totally agree that where we have the meetings influences participation.
> This is why I explicitly mentioned Yokohama. Even when we meet in Asia (which is presumably the
> most favorable environment for Asian participation) we still generally get below 1/3 Asian attendance,
> and if we also meet other places, the overall numbers are going to be lower.

Yes, it would be interesting to see if there is a similar visa barrier for entry into Japan that is producing this effect, or if it's simply that potential asian attendees' employers do not see sending people to IETF as being as good a cost/benefit tradeoff as U.S. employers.   But I suspect that if this is the case, the Asian employers are on the leading edge of the trend.   It will be interesting to see what the numbers look like for Bangkok—I think this is a relatively easy travel destination from China at least.

> I don't think that's the argument I'm offering. I personally wasn't much of a fan of Hawaii either, for many of the reasons you offer (though I note that they don't seem to be in the selection document!). I'm just saying that "continent" isn't a very good proxy for travel cost.


That's good to hear.   I suspect from a pure cost-of-air-travel perspective Hawaii is not a bad deal, but the hoops I had to jump through to get the travel paid for were ... unusual.   And it felt like the venue staff saw us as a problem to be managed rather than as customers to take care of.