Re: [Gen-art] Genart last call review of draft-ietf-mtgvenue-iaoc-venue-selection-process-11

Dan Romascanu <dromasca@gmail.com> Mon, 29 January 2018 18:26 UTC

Return-Path: <dromasca@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8BB12D871; Mon, 29 Jan 2018 10:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, SPF_PASS=-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 PxSxjacfgn1M; Mon, 29 Jan 2018 10:26:35 -0800 (PST)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 C9E5F1243F6; Mon, 29 Jan 2018 10:26:34 -0800 (PST)
Received: by mail-qk0-x22c.google.com with SMTP id d21so6777460qkj.3; Mon, 29 Jan 2018 10:26:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7InrcyyUtsrkjnFrzaVmJdAVDQwp/6hWnfIlGjXMLZ8=; b=tM5XhQVFferBwaAQOCLnsWwH2xAhXp68AZoQBN2PF2q8srQCBKIPQps+ivNC9pQDiw jkpqmtGUg2Lj+CyTSBGParR/Ij2OgKD+1Bhalp4fZqv6SD3/XQXa+znMj2VGT/Y21qNw AHJ+AEMj91LYOEgal6cbsbK1k6lFjWhltLVtJiNHYv4sIsfmqW2a0Uy9+GwA19Iyec/J 9sgtAH0BrfYki6zIyyh/Laza1xY/CFzUSHj60PSCOHEhKmEffHhfaGh40R3rPaZbUMPP fKLyjCSVZez32jEQBUYiMLd6t3uXNrkhiRgvNYlmO0SbqEGWd7fvv3dpFcEnVBO2kuE0 A/qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7InrcyyUtsrkjnFrzaVmJdAVDQwp/6hWnfIlGjXMLZ8=; b=jFtUiJXp9BItLgoatY1aMTol/AGQ6tFpYaACmJiNx5+5YImnd79CtEMc1YyF/x2r9o L6HwFjfO9oz+eJ06Lq0kZs99rz0+XLx3CwVCo9twlHY8niVZGfMCawMW8jsrTscCEOfY eJE0W3hCpjooZPPsVov2MOxcoAS9VXxdhJTWKQ86+YcaF01IudvoL7li6gDniHLNQTya 1oGckzNStawE/V6ypcoUboyeUr/V26nrWa26ht9OgcJ4ENPSdoX0qE0hBc+FzwkUM0Sw SaCEemvdONlGwdyircu13BH9snA2Ie33ixL4nNEfmNgPAhRubBPkGBo1Szzfh98PnNnb A6Cg==
X-Gm-Message-State: AKwxytdTbCNFTdak4jNc51kaJAohIhY24vDOathudv8NF6yyLfP09qCj eJrGGuPPSQRehgjw3++2Fj8du0g7PJy9agONt9yFMw==
X-Google-Smtp-Source: AH8x226g81p0JVxxzsN/Ck2kz0i/bMJZXocLdNWPt0fb3t19+yMvEA/UpHc6PRlysIVPHQ40PCgBMqWblb9nnNjZHFY=
X-Received: by 10.55.73.1 with SMTP id w1mr38309854qka.215.1517250393887; Mon, 29 Jan 2018 10:26:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.23.147 with HTTP; Mon, 29 Jan 2018 10:26:32 -0800 (PST)
In-Reply-To: <EA611862-03E6-4E6E-8221-20EC57E47D98@qti.qualcomm.com>
References: <151681599994.22697.16969006332176223005@ietfa.amsl.com> <EA611862-03E6-4E6E-8221-20EC57E47D98@qti.qualcomm.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Mon, 29 Jan 2018 20:26:32 +0200
Message-ID: <CAFgnS4XdTO80y24M5g9eeFpxWnQv4_bX9HYvevO8ZNmOETcYbQ@mail.gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: gen-art <gen-art@ietf.org>, mtgvenue@ietf.org, ietf <ietf@ietf.org>, draft-ietf-mtgvenue-iaoc-venue-selection-process.all@ietf.org
Content-Type: multipart/alternative; boundary="001a114a6de8c357e10563ee6211"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/EUMwqcOctsf2RATp7Rw88C7lcUw>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-mtgvenue-iaoc-venue-selection-process-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2018 18:26:37 -0000

Hi Pete,

Thanks for your answers and for addressing my concerns.

Here are a few answers to your returned questions:



On Mon, Jan 29, 2018 at 8:12 PM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:

>
>
> - 'where the IETF guest room
>> allocations are negotiated' - do we mean to say 'where IETF guest room
>> rates
>> are applied'?
>>
>
> It's not just the rates, but also the number of rooms reserved. This seems
> just editorial to me, though probably worth addressing. I'm glad to have
> you or Eliot suggest text to clarify.
>

what about 'where a substantial number of rooms are allocated for the IETF
meeting participants at negotiated rates'?


>
> 5. Section 3.2.1:
>>
>> 'Travel to the Venue is acceptable based on cost, time, and burden for
>> participants traveling from multiple regions.'
>>
>> I am not sure what 'burden' means. I suggest drop 'burden' and just leave
>> 'cost
>> and time'.
>>
>
> "Cost" is often thought of as monetary cost. "Burden" is saying that if
> the travel requires that you row your own canoe 100km over to the island,
> or if getting a visa requires that you submit yourself at the embassy for
> exploratory surgery, that should probably disqualify a venue. ;-) Either
> way, it is left to the judgment of IASA to make sure that the burden is
> reasonable. Unless I hear others, I suggest we leave this one alone.
>

I am still unsure about the vagueness of 'burden'. Based on your
explanation, it may be appropriate to change: s/cost, time and burden/cost,
time and formalities/?


>
>
> 11. I am not sure that it is clear what is meant by 'travel risks' in 5.2
>> and
>> 5.4. In any case, wherever we are talking about sharing with the community
>> information about 'travel risks' we need also to mention if there are any
>> exceptions from the Important Criteria detailed in Section 3.2
>>
>
> I always read "travel risks" as identical with the "economic, health, and
> safety risks" mentioned in 3.2.1. Do you think we should change the text?
>

let us just say  "economic, health, and safety risks"  than.

Regards,

Dan