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

Pete Resnick <presnick@qti.qualcomm.com> Thu, 07 June 2018 23:13 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 0D126130FF1; Thu, 7 Jun 2018 16:13:24 -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 yh2D0ayNps7o; Thu, 7 Jun 2018 16:13:22 -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 EDE2E130FEE; Thu, 7 Jun 2018 16:13:21 -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=1528413202; x=1559949202; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=hj26yZObw6tftXEcm37JAg/vbLzXs7VX8MLDozfFT9I=; b=hdfgpQ0syioE5TC8PCl+oezw0A+4gESwO527ShufjQ983YrG9YqXx1qQ FLwb4mgNPGwTPUTt+Geb5oPEVOPdXOCc+0nfdoRvgD7m7yeWIS4A6ItOm Rk2ePdtme2FxEtLIeTw1DEJAkWx1oSqToUcX6TyLPznluGvzwSMfOGb/B o=;
X-IronPort-AV: E=Sophos;i="5.49,488,1520924400"; d="scan'208";a="4385449"
Received: from unknown (HELO ironmsg01-sd.qualcomm.com) ([10.53.140.141]) by alexa-out-sd-02.qualcomm.com with ESMTP; 07 Jun 2018 16:13:21 -0700
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg01-sd.qualcomm.com with ESMTP/TLS/AES256-SHA; 07 Jun 2018 16:13:21 -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; Thu, 7 Jun 2018 16:13:20 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
CC: Eliot Lear <lear@cisco.com>, The IESG <iesg@ietf.org>, draft-ietf-mtgvenue-iaoc-venue-selection-process@ietf.org, mtgvenue-chairs@ietf.org, mtgvenue@ietf.org
Date: Thu, 07 Jun 2018 18:13:18 -0500
X-Mailer: MailMate (1.11.2r5479)
Message-ID: <124F6140-7221-4F7B-95A2-0BE4769A7CD4@qti.qualcomm.com>
In-Reply-To: <1528370002.2501048.1399609512.7F7FE872@webmail.messagingengine.com>
References: <152836618219.30809.3360596354604167556.idtracker@ietfa.amsl.com> <b6ec727a-2958-c59b-5d28-e99b06c20a6a@cisco.com> <1528370002.2501048.1399609512.7F7FE872@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/8fIhtWcedwM5xTIqgdYbML4jFfg>
Subject: Re: [Mtgvenue] Alexey Melnikov'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 23:13:24 -0000

Alexey,

Are you thinking of the top of section 3 saying something like, "This 
section contains the criteria for IETF meetings based on the objectives 
described in section 2."? I think that's easy enough to do, and 
perfectly reasonable.

pr

On 7 Jun 2018, at 6:13, Alexey Melnikov wrote:

> Hi Eliot,
>
> On Thu, Jun 7, 2018, at 11:56 AM, Eliot Lear wrote:
>> It's informative. 
>
> Can you maybe say so more clearly in the document?
>
>> While there's no explicit linkage, the intent was
>> indeed to link the requirements in Section 3 to Section 2, but to 
>> some
>> pragmatic extent.
>>
>> Eliot
>>
>> On 07.06.18 06:09, Alexey Melnikov wrote:
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>> Thank you for this document.
>>>
>>> I am wondering what is the relationship between the section "2.1.  
>>> Core Values"
>>> and Section 3? I don't think all of core values are expressed as 
>>> requirements.
>>> Is section 2 (and 2.1) Informative?
>>>
>>>
>>>
>>
>>
>> Email had 1 attachment:
>> + signature.asc
>>   1k (application/pgp-signature)