Call for comments: Proposals for exploratory IETF meetings

IETF Chair <chair@ietf.org> Sat, 29 August 2020 01:53 UTC

Return-Path: <chair@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB063A0F0D for <ietf-announce@ietfa.amsl.com>; Fri, 28 Aug 2020 18:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 5u-pGVK8CfLz for <ietf-announce@ietfa.amsl.com>; Fri, 28 Aug 2020 18:53:57 -0700 (PDT)
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id E2D813A0F0E for <ietf-announce@ietf.org>; Fri, 28 Aug 2020 18:53:56 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Reply-To: ietf <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Call for comments: Proposals for exploratory IETF meetings
Message-Id: <5B273CCD-8B98-4CC1-9597-5C3CAC331D01@ietf.org>
Date: Fri, 28 Aug 2020 21:53:37 -0400
To: IETF-Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5ey0izDuwbDC38YKU6xePjGOtIk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Aug 2020 01:53:58 -0000

RFC 8719 states that IETF meetings should rotate between North America, Europe, and Asia, according to the “1-1-1-*” policy. The “*” denotes an exploratory meeting outside of these three regions. The RFC also states that:

"Someone who is interested in pursuing an exploratory venue proposes it on the IETF discussion list or on a future discussion list expressly set up and announced for this purpose. The community gets to comment on the venue and offer their opinions. If the IETF chair determines that there is community consensus to pursue the venue further, the venue will be put up for discussion on the venue-selection mailing list <https://www.ietf.org/mailman/listinfo/venue-selection>.”

There have recently been proposals [1][2] from members of the community to consider three exploratory venues:

Australia
New Zealand
Egypt

To establish whether there is community consensus to pursue any of these venues further, I am opening a call for comments on these venues. Please send your comments about whether the IETF should consider these venues for exploratory meetings to ietf@ietf.org no later than September 18, 2020. Those who wish to send private feedback can address their comments to chair@ietf.org instead. Comments that have already been sent to the list since the first proposal was made on August 24 do not need to be repeated and will be factored into the determination of consensus.

Note that this is merely the first step in a long process of meeting venue selection for an exploratory meeting, should consensus emerge. IETF meeting venues are typically booked up to four years in advance, and therefore the opportunity to schedule an exploratory meeting even if there is consensus to do so may not occur until several years from now. RFC 8718 has more details.

Thanks,
Alissa Cooper
IETF Chair

[1] https://mailarchive.ietf.org/arch/msg/ietf/4khe-SkMn7yq673h-VmYDYkr2KQ/
[2] https://mailarchive.ietf.org/arch/msg/ietf/EUiU1rZNUYCVgcPPBNUVItfN8Dk/