Re: [Mtgvenue] Alvaro Retana's No Objection on draft-ietf-mtgvenue-iaoc-venue-selection-process-15: (with COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Thu, 07 June 2018 11:22 UTC

Return-Path: <aretana.ietf@gmail.com>
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 382671310CF; Thu, 7 Jun 2018 04:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 jIo9BIP9gWEo; Thu, 7 Jun 2018 04:22:03 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (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 63D2F1310E8; Thu, 7 Jun 2018 04:21:53 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id d19-v6so5510189oti.8; Thu, 07 Jun 2018 04:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=iq3dLVtgh1Uq/dJp6SU54Xz6RsfhgYiSsSlJiSEZWkg=; b=Som52CGpIhSeP/iVGnoOHBkSLHbg346ObH9tmRt9m9jHVnHxDy3k9V5DLdvdHTSmfs cpzQpw04CzhQ8+6JPTfkdRKqUox6K3p0gx/BDBzF/qJNcQ1/TvoYm+mUeHBLGAm8+Eud UMmGx0jZXyxST9XpvU/kr0gLaSw7Y3lk/CgeP67q+OrPCivVwlg8TsW9Qxs6Ors1qDjo ZgAVzMAX1mOqdCveFPsQZ3LCt8RMTco5izwbYlsXh0lFMC2OJJhQ/HM3ApNWdUbrEsxB wvAxduRNLG3N5bN02FEnzKTYBCibE+XlgGyKXsXWV8HzmMUPYytrGatCE7/E8ehO26gp MJfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=iq3dLVtgh1Uq/dJp6SU54Xz6RsfhgYiSsSlJiSEZWkg=; b=BzhKDMQXuIwz/Cn8bM02aP6xZF0CcKant6NM2VuUpgfg0nFjLuQ6kiwAPMC/7ixBFl NtR+OqcoptX2dzbo5uWq8TSM8Yjh2PPqWJTgjXmZ/aqtNaoIfzddyO3r/iUIcsEHqFxs QLaNYWo4MWiZmQrVwb+/YF+Pz9YqyiPfAAtUa37mVSU6B5d0YKcHfqBl72RWfrKqXkN4 09Ui1ZWxOLTViX8kB154zdjujAy5aUpVYsE64OmS2uyeS32BKKfer/9WvtjsBAj+2CHR 9GM+lNl+aSg/JFdDokPxO95aZIJOztDO1+ECO27gOooCrsNl3CVUgo1IVDjSDS2mWvVc V14Q==
X-Gm-Message-State: APt69E1y3TnFGaRPO8EemYKmau5OEOCOg89EPSFyjBVh+aahoUhe1WVz NU/f6Hj8wt8PALh4xhs+n9smzv+r/owhRPO82T8=
X-Google-Smtp-Source: ADUXVKKsUqgv9SeAQpktahPGo/hqq2fUiWhenRbU37QJFf/OrXPHCeDLiKMYIbal6UUjam/Oe3OR+Kwgd6achOw0f4A=
X-Received: by 2002:a9d:56e8:: with SMTP id b37-v6mr661086otj.175.1528370512772; Thu, 07 Jun 2018 04:21:52 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 7 Jun 2018 04:21:51 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <6D1FE14F-6BEE-46A9-A511-77B3E63DD49D@qti.qualcomm.com>
References: <152830294286.6280.13192764028667391463.idtracker@ietfa.amsl.com> <6D1FE14F-6BEE-46A9-A511-77B3E63DD49D@qti.qualcomm.com>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Thu, 7 Jun 2018 04:21:51 -0700
Message-ID: <CAMMESsypzLZGRWz1s=LsoU81uSZTDUaPgk3oarhYUtwfxK+qbQ@mail.gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: mtgvenue-chairs@ietf.org, draft-ietf-mtgvenue-iaoc-venue-selection-process@ietf.org, The IESG <iesg@ietf.org>, mtgvenue@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007fc338056e0b7d7a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/9Q8i1HzClCzOEE5fwZmtWsG8zzo>
Subject: Re: [Mtgvenue] Alvaro Retana's No Objection on draft-ietf-mtgvenue-iaoc-venue-selection-process-15: (with COMMENT)
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 07 Jun 2018 11:22:10 -0000

On June 6, 2018 at 6:27:22 PM, Pete Resnick (presnick@qti.qualcomm.com)
wrote:

Pete:

Hi!

Just insisting a little bit more on consistent terminology...

On 6 Jun 2018, at 11:35 <http://airmail.calendar/2018-06-06 11:35:00 EDT>,
Alvaro Retana wrote:

----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


(1) The term "participant" is used in several places, sometimes with
different
modifiers; for example: active, IETF and regular. Some of the phrases seem
to
want to differentiate between them, but that distinction is not clear (for
example): "in order to spread the difficulty and cost of travel among active
participants, balancing travel time and expense across the regions in which
IETF participants are based." What is the difference between active and IETF
participants?

Note that "attendee" is also used, in my interpretation, to also mean
"participant". Is that the intent, or is there a difference?

Clarifying and being consistent would help. I don't think that a terminology
section is needed -- I just want to probe whether the terms were
differentiated
on purpose, and, if so, to understand what that differentiation may be.

We'll give these a scrub to make sure they're consistent. My take is:

Your take sounds fine to me, and it is about the same as my own.  However,
the real point here is that we shouldn’t leave this up to interpretation.
While many/most people involved in the selection may interpret the text the
same way as you or me, we don’t have certainty that the interpretation
won’t change over time.


   -


   "IETF participants" is simply "participants" and, the "IETF" bit should
   simply be removed.
   -

   The "where we meet" section mentions "active" participants because we
   want meetings near people who are currently contributing participants.

You added a new modifier in the explanation: “contributing"…but that is not
what that section says anyway.  The text is: "We meet in different
locations globally, in order to spread the difficulty and cost of travel
among active participants, balancing travel time and expense across the
regions in which IETF participants are based.”  The balancing is to be done
where “IETF participants” live, not where “active participants” do (which I
interpret to be the contributing ones).


   -


   The "least astonishment" section mentions "regular" participants because
   we want people who regularly follow or contribute to work to be able to
   easily discover information.
   -

   "Attendees" are people who actually show up at a meeting. "Participants"
   are people who participate in the IETF (whether in person or
   electronically) who might want to show up at a meeting.

Thanks!

Alvaro.