Re: [Mtgvenue] Adam Roach's Yes on draft-ietf-mtgvenue-iaoc-venue-selection-process-15: (with COMMENT)
Adam Roach <adam@nostrum.com> Wed, 06 June 2018 22:36 UTC
Return-Path: <adam@nostrum.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 622ED130FE5; Wed, 6 Jun 2018 15:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 rownc8u-J7x9; Wed, 6 Jun 2018 15:36:21 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 36AF0130DE1; Wed, 6 Jun 2018 15:36:21 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w56MaHFk049003 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 6 Jun 2018 17:36:19 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: mtgvenue@ietf.org, draft-ietf-mtgvenue-iaoc-venue-selection-process@ietf.org, The IESG <iesg@ietf.org>, mtgvenue-chairs@ietf.org
References: <152825797165.19338.15869458527257723424.idtracker@ietfa.amsl.com> <A171F67E-AD3A-44DA-A332-518C3C4A64D6@qti.qualcomm.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <094590c2-74d0-f62c-085f-c3baa0a2e5a4@nostrum.com>
Date: Wed, 06 Jun 2018 17:36:12 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <A171F67E-AD3A-44DA-A332-518C3C4A64D6@qti.qualcomm.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/CYv9AWl9kCeSMWZvCVYLrwbtRSI>
Subject: Re: [Mtgvenue] Adam Roach's Yes 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: Wed, 06 Jun 2018 22:36:25 -0000
Pete, Eliot -- Thanks for your quick responses. Although I continue to beleive that there are cleaner ways to thread this needle, the current approach isn't actually problematic, and it sounds like it has already had significant consideration. I appreciate the time you have each taken to explain the history of this text. /a On 6/6/18 4:10 PM, Pete Resnick wrote: > Hi Adam, > > See my reply to Spencer regarding IASA 2.0 for some more details. As > Eliot said, the current edit was an attempt to take that into account, > which we worked out with our AD. Perhaps something to discuss on the > telechat. > > I'll be sure we cover the two editorial bits. Thanks for those. > > pr > > On 5 Jun 2018, at 23:06, Adam Roach wrote: > >> Adam Roach has entered the following ballot position for >> draft-ietf-mtgvenue-iaoc-venue-selection-process-15: 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-iaoc-venue-selection-process/ >> >> >> >> >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> Thanks to everyone who worked on this document. >> >> I agree with Spencer's concern that this document is tightly tied to >> the current >> IASA structure, which is under revision at the moment. I think it >> would be an >> improvement to describe, in more general terms, the entity >> responsible for >> selecting venues, with a single note early in the document that the >> entity >> currently in that role is the IASA. >> >> I also have a handful of editorial nits that the authors may wish to >> address. >> >> --------------------------------------------------------------------------- >> >> >> Please expand "IASA" in the Abstract, assuming it remains in the >> Abstract. >> >> --------------------------------------------------------------------------- >> >> >> Abstract: >> >>> It directs the IASA to make available additional process >>> documents around that describe the current meeting selection process. >> >> I'm having a really hard time parsing this sentence. It seems to make >> sense if >> you remove "around". >> >> --------------------------------------------------------------------------- >> >> >> §2.1: >> >>> criteria below, one mandatory and others important, to allow for >>> the case where local laws may require filtering in some >>> circumstances.[MeetingNet] >> >> It's not clear what "[MeetingNet]" is doing here. Perhaps some >> explanatory text >> about what the reader can expect to find at that reference would be >> useful. >> >> In any case, consider putting a space before the opening bracket. >