[Mtgvenue] What does "mandatory mean?"

Melinda Shore <melinda.shore@nomountain.net> Tue, 31 January 2017 17:12 UTC

Return-Path: <melinda.shore@nomountain.net>
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 B6FAB129FF5 for <mtgvenue@ietfa.amsl.com>; Tue, 31 Jan 2017 09:12:20 -0800 (PST)
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, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.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 BJgG4ROhs1cy for <mtgvenue@ietfa.amsl.com>; Tue, 31 Jan 2017 09:12:19 -0800 (PST)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 B0E0E1299D5 for <mtgvenue@ietf.org>; Tue, 31 Jan 2017 09:12:19 -0800 (PST)
Received: by mail-pf0-x236.google.com with SMTP id y143so108608619pfb.0 for <mtgvenue@ietf.org>; Tue, 31 Jan 2017 09:12:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=1SWaT2/VBsoUKOmyL6ivxf8JaiXitcX5z7kval2UGzY=; b=y7gnf6fandGycsbJUHPrWvPlaELyqaiKdEMf7XMNf73q9c7pTepuxo9TlEY/SPMGKw m76SDAnH20Suj8ddvyPv3i7ji1KF0KfyuOcvfoEIXXBJ6GQCuwP/1oy/cuDZL0z5sLSg fQ6lRXtw5ojBXoTbmBSiXx9VaLB4eQTbwZ1MAu/f1Vt4wCRmpbdVH/a+uLtI6p/aBDXd b2xycRD2ZHZk4wRu3WGmJTYHUuDJRz/WGwKIZSnNWEDwN6MjZMTRUId02t100bXRpeU6 HEvcjsCiOy40HwgYa0U7gNmGawZG7MPblyFMes70w/rbIEEbu9QAIOvtC3VAutGlqSbS DYGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=1SWaT2/VBsoUKOmyL6ivxf8JaiXitcX5z7kval2UGzY=; b=pUZmH10ufIQfJ7si8VzVKUJARhm7/CK3HnPUdBvwncBxZb3QsrwxDhlXWEdnPRTvq3 0cGuohKlpZiR64cwROgMWvhCt9Ny6nwfIO41Gdb80Ghe0atdtHr7OIHb1Wxl61Q13xhg uJTj7rhf/Ns7agwEwuUwZ6FI/7GJvUTuTcw58Pmf5Twmi4xNSVswAMDOhuAHqx1VROu4 roGRs6lSZ5Zox4nqXkcS5AfpL+eayfk+x3GVSASDFtjJ0pviPVp+cCVL7zwvfMqcXohx ldduVxSmijXmjY4yQemSmkwzAWc2yHXORPHUn9O1IQzHVtb+wQLXAwZ/Rw03rwNoAQFA +L0g==
X-Gm-Message-State: AIkVDXIRLhPmoF6iTXyvESqHCSnn3GLWhFp606iTxXYPJwIddaDrgnhmqbTa82W6JMzXdQ==
X-Received: by 10.98.48.66 with SMTP id w63mr29830361pfw.179.1485882739139; Tue, 31 Jan 2017 09:12:19 -0800 (PST)
Received: from Melindas-MacBook-Pro.local (74-124-96-230-radius.dynamic.acsalaska.net. [74.124.96.230]) by smtp.gmail.com with ESMTPSA id p26sm42954324pgn.39.2017.01.31.09.12.18 for <mtgvenue@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 09:12:18 -0800 (PST)
To: mtgvenue@ietf.org
References: <20170131010548.GL47762@mx2.yitter.info> <de401360-8827-c427-19fe-ace8d2987f40@gmail.com> <20170131040757.GM47762@mx2.yitter.info> <2c957e0e-999f-f8a2-3a61-3aff3606b087@dcrocker.net> <20170131152139.GC53056@mx2.yitter.info>
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <47488b7f-29f0-f082-c3c0-8dc201c5dea7@nomountain.net>
Date: Tue, 31 Jan 2017 08:12:16 -0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <20170131152139.GC53056@mx2.yitter.info>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="tOedQ7CXBeIswPbRFWMU9gsHpxjLUWHA5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/EHVbAMMwNO95bAEutL_gSK0u2YQ>
Subject: [Mtgvenue] What does "mandatory mean?"
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 31 Jan 2017 17:12:20 -0000

It's clear that one of the problems underlying our inability
to come to agreement on some of the requirements is that
there's not agreement about what "mandatory" means in the
context of this document.  It seems that some people see
"mandatory" (and other requirements language) as applying
to the venue under consideration, and others see "mandatory"
as applying to the IAOC meeting committee's evaluation
process.  To be honest, in the current draft I read it as
applying to the venue.

I don't see any way to come to consensus on the requirements
without greater clarity about that, and it also seems clear
that the document needs to include some text stating explicitly
what entity the requirements language applies to (the venue or
the committee).  But first, we need agreement on what's
intended.

Melinda