Re: actions related to improving IETF meeting selections
Ted Lemon <mellon@fugue.com> Sun, 12 June 2016 18:07 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 960C812D0F9 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 11:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 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_LOW=-0.7, SPF_PASS=-0.001] 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 pVYFiiXDZdmS for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 11:07:02 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::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 9582F12B056 for <ietf@ietf.org>; Sun, 12 Jun 2016 11:07:01 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id f6so51626921lfg.0 for <ietf@ietf.org>; Sun, 12 Jun 2016 11:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=apwmzNqQR4gQSrCPbUw09/QFu2gQIL1Lx3gN3Ltv3k4=; b=p+Q+HcgeTDw7hSZ6gRRTsSulLAr4TDMdGpcZZS6xFv7JfxqG0IxlMr/+m/cM/0cZsi NtpjSfM81SKNhiVOwbH6GggDNUhbaEk5Kyq2GyS4m/KzqqPGmI8dns3EJOSpB+jUEacC +5qli2gmiobdgATsdIh3KCWFxx7wYPjlraB17krcgVRDSEUyyjmjpB3D+C0A/RRN+1Xs bdnrdB74xeoj6OmiLW4CKRAop+OEASTLa9t6mhaN6ORISaCUehx6Pz+gEK/mm9PAX1nZ ufrCy/Q8V/PxBw+TDs4QRaGyhkc52bLXdpW+fzfhvTg8PjGuNx5v3jsj18gkLOep1xf0 AB1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=apwmzNqQR4gQSrCPbUw09/QFu2gQIL1Lx3gN3Ltv3k4=; b=YJRR2+rjV20ZW2jXT58+wdqGeH0dcXhNzrABfFvecigOvY03ksJOi4rnBZiUienUOz 1UBKYUhIOqTs3shKT9tei2JcT+X29jYOSR0nwod7/JrZzgtpFbl7iL5samMOzZnMQ1yb 2GKDWAmTkkpy7s61P/e09nhYOZuRjegziI4LoHHrOx4TQPrY+bAzB0g4LAn0RC3Lzlhk x9gh8P+0YGT3BF+T+hh3lgAwecXAgJokRpwf6puzoyrsxpFVZN0euW6rsPDCPPsfPoju fqLEsFeJKZYabFgNVY990oDui1mzq25xFWyxgz6XUDFKOQ0aCCM0ruwgmfUs7Lqpek2p BCDQ==
X-Gm-Message-State: ALyK8tK5UdDNhwWFcK6HC1HKuD4WQcaEpXzj5LE/uXyHLJBUCfvGqQVX/KUWhsZy21NR16Z6BZPiI+1MMsXzzA==
X-Received: by 10.25.149.146 with SMTP id x140mr2398000lfd.131.1465754819515; Sun, 12 Jun 2016 11:06:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Sun, 12 Jun 2016 11:06:19 -0700 (PDT)
In-Reply-To: <557685565.1303569.1465745474144.JavaMail.yahoo@mail.yahoo.com>
References: <0DAA04D6-03FE-444D-ABF9-4A1CF2F7DFC9@ietf.org> <5D36713D8A4E7348A7E10DF7437A4B927CA81040@NKGEML515-MBX.china.huawei.com> <557685565.1303569.1465745474144.JavaMail.yahoo@mail.yahoo.com>
From: Ted Lemon <mellon@fugue.com>
Date: Sun, 12 Jun 2016 14:06:19 -0400
Message-ID: <CAPt1N1nqg9nbkgUGq2GSe7_Pu36aFx8WvX6KopZ0N9Ot9n-ceQ@mail.gmail.com>
Subject: Re: actions related to improving IETF meeting selections
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Content-Type: multipart/alternative; boundary="001a11402040585cef053518a3a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nDK1qXSGuP8hfY2xwafKL135NlQ>
Cc: "recentattendees@ietf.org" <recentattendees@ietf.org>, "chair@ietf.org" <chair@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 12 Jun 2016 18:07:04 -0000
This is a great idea, but would require a lot of regular IETFers to sign on and get support for going to those meetings. On Sun, Jun 12, 2016 at 11:31 AM, <nalini.elkins@insidethestack.com> wrote: > >Thanks so much for your efforts on both Singapore meeting and improving > future IETF meeting selections. You have done an excellent work on > respecting various opinions and making a >necessary compromise. > > +1 > > > > >Regarding to diversity among future IETF meeting selections, there are > actually multiple meanings of diversity. But in my opinion, the most > important task for IETF organizer should be to >get and keep high quality > and consistent contributors. Arising the awareness of IETF in wider areas, > attracting more diversity people (particularly, if these people would not > join the follow->up IETF meetings) are much less important than the > convenience for our majority consistent participants. Therefore, the most > important diversity should be geography diversity among the >current > majority consistent participants. Consequently, I strongly support 1+1+1 > policy. One potential option is that we may have a set of side/secondary > IETF meetings apart from the >three main IETF meetings per years. They > could be hold out of main areas to serve the other diversity purposes. > > Sheng, I find the idea of "secondary or side" meetings very intriguing. > I think this may be a path for regions who do not have a large set of > participants (yet). I would like to see this idea elaborated upon. What > are your thoughts? > > Nalini > > > >-----Original Message----- > >From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of IETF Chair > >Sent: Wednesday, June 08, 2016 9:58 PM > >To: IETF Announcement List > >Cc: recentattendees@ietf.org; ietf@ietf.org Discussion > >Subject: actions related to improving IETF meeting selections > > > > > > >The discussion about the Singapore meeting has been difficult for us. The > IETF > >needs a meeting that we are generally happy with. Various past mistakes > and > >new learnings aside, we are now in a situation where no decision in this > space > >will be perfect. We knew that no matter what choice is made, there will be > >groups of people who feel they are unfairly impacted. > > > >But perhaps the most important things are that, long-term, the community > >gets to carefully weigh what they expect from meeting locations, that we > all > >learn from more about the various challenges discussed, we are an open > >organisation for everybody including minorities, and that we improve our > >processes going forward. It is also crucial that the IETF remains an > >organisation that can do its technical work, and be open to all of our > global > >participants in a fair manner. And obviously be capable of arranging our > >operations in the real world, in areas that our participants come from. > > > >What follows is what we are proposing as additional onward work to address > >the issues highlighted in this discussion: > > > >o The IAOC as well as members of the community have asked me to > >charter a working group to continue the discussion of the detailed meeting > >criteria document (draft-baker-mtgvenue-iaoc-venue-selection-process). All > >criteria are on the table for discussion. The working group proposal is > being > >reviewed by the IESG, and will be out for community review shortly. A WG > >meeting in Berlin is planned. > > > >o Develop a BCP that defines the community-backed, official policy for > the > >overall strategy of geographic meeting distribution (our current strategy > is > >referred to as 1-1-1*). An initial draft for this is in the works. > > > >o Arrange a special session in Berlin to discuss the role of human > rights, > >visas, and other aspects of international meeting arrangements. We have > >begun to work to find outside experts in this space who can join a > >conversation. (If you have suggestions, let us know.) > > > >o Continue the new practice of informing the community of potential > >future meeting destinations, and collecting “crowd-sourced” input on their > >suitability. > > > >o Commit to a proper, informed process to identify issues that any > >subgroup (including but not only the LGBTQ community) has with our site > >selections. > > > >o Commit to returning to the 1-1-1* meeting model — or what the > >eventual BCP policy is -- for Asia for the remainder of the decade. For > the last > >decade, we’ve only met there 4 times. > > > >o Commit to holding all other currently planned meetings as they are, and > >focusing on making the most appropriate decisions about future meetings, > as > >informed by community input. > > > >o While we do not believe that we should respond to the current > >discussions merely with a suggestion of conducting our meeting virtually, > it is > >a clear direction that IETF and other organisations will be using more > virtual > >collaboration tools in the future. The IESG has discussed taking initial > steps > >with regards to bigger virtual meetings. Experiences from this could drive > >further efforts. > > > >Jari Arkko, IETF Chair > > >
- actions related to improving IETF meeting selecti… IETF Chair
- RE: actions related to improving IETF meeting sel… Sheng Jiang
- Re: actions related to improving IETF meeting sel… nalini.elkins
- Re: actions related to improving IETF meeting sel… Ted Lemon
- Re: actions related to improving IETF meeting sel… Melinda Shore
- Re: actions related to improving IETF meeting sel… Ted Lemon
- Re: actions related to improving IETF meeting sel… nalini.elkins
- RE: actions related to improving IETF meeting sel… Sheng Jiang
- Re: actions related to improving IETF meeting sel… Melinda Shore
- RE: actions related to improving IETF meeting sel… Sheng Jiang