Re: [Mtgvenue] Adam Roach's Yes on draft-ietf-mtgvenue-iaoc-venue-selection-process-15: (with COMMENT)

Pete Resnick <presnick@qti.qualcomm.com> Wed, 06 June 2018 21:11 UTC

Return-Path: <presnick@qti.qualcomm.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 B3E85130DD6; Wed, 6 Jun 2018 14:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 5X8OudqKx78P; Wed, 6 Jun 2018 14:11:07 -0700 (PDT)
Received: from alexa-out-sd-02.qualcomm.com (alexa-out-sd-02.qualcomm.com [199.106.114.39]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66149130DCF; Wed, 6 Jun 2018 14:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1528319467; x=1559855467; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=lj3ZKDxQLw1IW8sEtqbuspJcWUu6EVhDcnofOx4Zkw4=; b=g6a+jOmAVKJ+PjZBFVHbDXxq05GL4LMwx1+nDwKzuFh2akVhJ767Q4Rj 1HEOTvI8ggeTgro/wT9zhOC8LWGoIyoD6ipBegN+KOlpFVFRcP2AR9JTM rC1XCnokXNLi12ulOzD17GB0+eAvMuwviN/fUjnVmdfhUEW+G3u3O3jG6 0=;
X-IronPort-AV: E=Sophos;i="5.49,484,1520924400"; d="scan'208";a="4304128"
Received: from unknown (HELO ironmsg04-sd.qualcomm.com) ([10.53.140.144]) by alexa-out-sd-02.qualcomm.com with ESMTP; 06 Jun 2018 14:10:55 -0700
X-IronPort-AV: E=McAfee;i="5900,7806,8916"; a="103452223"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg04-sd.qualcomm.com with ESMTP/TLS/AES256-SHA; 06 Jun 2018 14:10:55 -0700
Received: from [10.38.247.241] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 6 Jun 2018 14:10:54 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Adam Roach <adam@nostrum.com>
CC: The IESG <iesg@ietf.org>, <draft-ietf-mtgvenue-iaoc-venue-selection-process@ietf.org>, <mtgvenue-chairs@ietf.org>, <mtgvenue@ietf.org>
Date: Wed, 6 Jun 2018 16:10:52 -0500
X-Mailer: MailMate (1.11.2r5479)
Message-ID: <A171F67E-AD3A-44DA-A332-518C3C4A64D6@qti.qualcomm.com>
In-Reply-To: <152825797165.19338.15869458527257723424.idtracker@ietfa.amsl.com>
References: <152825797165.19338.15869458527257723424.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/9NLouJAaEgsWQ9mcMzLKSIR4DNQ>
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 21:11:11 -0000

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.