Re: [Mtgvenue] Spencer Dawkins' Yes on draft-ietf-mtgvenue-meeting-policy-06: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 06 June 2018 10:33 UTC

Return-Path: <spencerdawkins.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 16815130F05; Wed, 6 Jun 2018 03:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 8kRkUTD4eR9X; Wed, 6 Jun 2018 03:33:05 -0700 (PDT)
Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (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 93A0A130EFF; Wed, 6 Jun 2018 03:33:05 -0700 (PDT)
Received: by mail-yb0-x235.google.com with SMTP id d123-v6so1798116ybh.9; Wed, 06 Jun 2018 03:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eVOZiQiUSIywiCCXE9R1OREYdLLVrFP0lPPXdWDLxXw=; b=dwLxQmkvHhSbDZBI+6WzoauYmLJrhYC+RkPGk4ZgnorgyijA84qmYtq5+H8swY519a K1CK8LtbbX+xCo3cOg7/HaFAgm+uW3Elxy/V4XHOfwNVAADKNg7Ac35w+b7dlQShenin BtfNuEtTUamn4VlMr7XKGow6qbbdiHo/RCyKyu+Njaj25zWGU1elkcKWnst/Kq4j5Itv P2MRUS2UZDAk3N9J0t2AaRz0ep7P+zgLRNAHBrFasIYODhwaJIgegnAlcTEdP+V3Y9F6 3pYgJcy9jCAPu67eiYaRVmEhtFuf/QPSSo8I9L/zKwH9TMMwf+Q0ookaOa6KggBa5hqB 0IjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eVOZiQiUSIywiCCXE9R1OREYdLLVrFP0lPPXdWDLxXw=; b=TR28gTQoN0MUy5vopBx4Mn/BzKHopcZnuTm0BD/NzdS8wBVBg5VE0P8U9BO5AoJhCv 61fXkocuiowY8koFjkoWYgn557j1N3nrdnm1t6p21D5Ei3mafgePKKLuxGXo+6DYI2yX EaHKSgsCrLxlrl/VZqFIJ4DCsqdGlMDwCqxMJJIl+dRE7fb6apNKs21eFtgrVRWbpQJq bJjyQxvkIRD3C2ueAK7e9WYJtlo7avKuXglslzlzCzt5+tpZWf6TfW6pSDfKOtNKc9x2 5GMvO3bqJLGmcS4/hO6CztVvOjuiZli81wE0tubZToJXrlbMu3xD7O5tE7uQcPp1nXA9 0glQ==
X-Gm-Message-State: APt69E25WtBgN692wCVbTCzFzvJfa+1pjeRu65u6T3EKGrnhziYfCNCL XOcMzgL7S/DllFrxySYLCIB8GEzRXZ0QJHKDqjo=
X-Google-Smtp-Source: ADUXVKKRihLsp9JqDdwQ2Jm1Z4XnyLA9TV3Q9DQYzsVjUP8s7HzUki4u10UjdUGYnvbd1zWEyL24n/M8h0e0xEs0E9I=
X-Received: by 2002:a25:ac9c:: with SMTP id x28-v6mr1144983ybi.44.1528281184597; Wed, 06 Jun 2018 03:33:04 -0700 (PDT)
MIME-Version: 1.0
References: <152823338873.19118.12210512458972748727.idtracker@ietfa.amsl.com> <79BD0AE0-7173-4DD5-B76C-1A56A9EDCAD9@kaloom.com>
In-Reply-To: <79BD0AE0-7173-4DD5-B76C-1A56A9EDCAD9@kaloom.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 6 Jun 2018 05:32:50 -0500
Message-ID: <CAKKJt-cZ4qZeNLjzvDaAoempFiOdR1ws7MD2CbnoxHZcCHbNow@mail.gmail.com>
To: Suresh Krishnan <Suresh@kaloom.com>
Cc: IESG <iesg@ietf.org>, draft-ietf-mtgvenue-meeting-policy@ietf.org, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, mtgvenue-chairs@ietf.org, mtgvenue@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001ffced056df6b141"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/6p4uoRQoJVTWFAIp4BL4xJfygUo>
Subject: Re: [Mtgvenue] Spencer Dawkins' Yes on draft-ietf-mtgvenue-meeting-policy-06: (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: Wed, 06 Jun 2018 10:33:19 -0000

Hi, Suresh,

Non-blocking comments, and I'm sure you'll do the right thing. Just as
input for you doing the right thing :-) ...

On Wed, Jun 6, 2018 at 12:48 AM Suresh Krishnan <Suresh@kaloom.com> wrote:

> Hi Spencer,
>   Thanks for your comments. Please find responses inline.
>
> > On Jun 5, 2018, at 5:16 PM, Spencer Dawkins <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > Spencer Dawkins has entered the following ballot position for
> > draft-ietf-mtgvenue-meeting-policy-06: Yes
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-meeting-policy/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > (Sorry, this is a resend. The only change is that I should have clicked
> on Yes,
> > instead of No Objection)
> >
> > Nice work. I know BCP process text is hard.
> >
> > I share Martin's question, at least to the point where I'm guessing what
> that
> > text means.
>
> I made a text proposal to Martin. Let me know if it works for you as well.
>

You're headed the right direction.


>
> >
> > 1-1-1-* is used in
> >
> > 1.  Introduction
> >
> >   The work of the IETF is primarily conducted on the working group
> >   mailing lists, while face-to-face WG meetings mainly provide a high
> >   bandwidth mechanism for working out unresolved issues.  The IETF
> >   currently strives to have a 1-1-1-* meeting policy [IETFMEET] where
> >   the goal is to distribute the meetings equally between North America,
> >   Europe, and Asia.
> >
> > but defined in Section 2, following. I don't know whether it would be
> better to
> > say "meeting policy" or "meeting rotation policy", but 1-1-1-* probably
> isn't
> > universally understood without scanning down to Section 2.
>
> I think actually changing this to "1-1-1" might be better. Thoughts?
>

My point was that 1-1-1-* has been kind of a term of art, for people
talking about where we meet. The same is true of "1-1-1".

If someone hasn't been following those conversations, I'm not sure how
clear "1-1-1-*" is without the definition in Section 2. Even a forward
pointer would be an improvement.


> >
> > Are you just going to remove the prefix "BACKGROUND NOTE:"? This could
> be in
> > its own section, I guess, maybe in an appendix?
>
> I think removing it makes sense.
>
> >
> > In
> >
> >  While this meeting rotation caters to the current set of IETF
> >   participants, we need to recognize that due to the dynamic and
> >   evolving nature of participation, there may be significant changes to
> >   the regions that provide a major share of participants in the future.
> >
> > perhaps we should say "we recognize"? I'm hoping we've already done that
> :-)
>
> Sounds good.
>
> >
> > Is
> >
> >  NOTE: There have not been a large number of such exploratory meetings
> >   under the current 1-1-1-* policy (with IETF95 in Buenos Aires and
> >   IETF47 in Adelaide being the exceptional instances).
> >
> > saying
> >
> >  NOTE: There have not been a large number of meetings that would qualify
> >   as exploratory meetings
> >   under the current 1-1-1-* policy (with IETF95 in Buenos Aires and
> >   IETF47 in Adelaide being the exceptional instances).
> >
> > ? They weren't actually held under 1-1-1-*, which postdates IETF 27 and
> IETF 54
> > considerably …
>
> I think the word “such” is ambiguous in this context. I think your wording
> works well. I will make this change.
>
> >
> > Might
> >
> >  o  There were some logistical issues (venue availability, cost etc.).
> >
> > be clearer as
> >  o  There were some logistical issues (venue availability on previously
> >  committed dates, cost etc.).
>
> I think the dates is kind of understood. I don’t mind either way. Let me
> know if you feel strongly about this.
>

Not strongly, but my understanding was that the IAOC really did try harder
to find Asian venues than the results would lead you to think, and the
problem was that they found some venues that might have worked on other
dates, but we'd announced our committed dates like 2-3 years previously,
and didn't want to change them.

Spencer


> Thanks
> Suresh
>
>