[Mtgvenue] Emergency cancellation [was: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04]

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 30 January 2017 22:10 UTC

Return-Path: <brian.e.carpenter@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 E323F129BDD for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 14:10:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, 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 OQBWdfXd4a7W for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 14:10:41 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 7E330129645 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 14:10:41 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id y143so94057531pfb.0 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 14:10:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=CevGcpvCZyhB1KBBa9YhWl75PCzKXbVxFwnxtBjVjFE=; b=OXlE9+b18gnR/l4kXW2KZ5KZ9m3NI4XrBdhIDRPGkeCJIUTyrSMmcvFFlAVo0/jQn5 wicYOvolTXsV/GQFqgtjUdJkyPp89MGLCnb2CdX/XDrQtJYM0xyX8D4MQdaddK1rlvh1 gVvGrMXRyRK9gcHu3XkP8+b+gDb63xJEllxxyF4cCPurDAu4eI7B3BLPvu2s9DSzRqep hJUghnFU5cTUCfO/8ypmTNC9Ej7stt8eaDplbpivMcTGkadJgxRAar4dMQnVxArmNz7z VwNvsZWgSxdwWqj/rjE+SC4ATy3jnypACBMQh0d/eqHD/d7uBO/epb8Q/1c174sKEawB n6sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=CevGcpvCZyhB1KBBa9YhWl75PCzKXbVxFwnxtBjVjFE=; b=jztN7/N/VpeJt/FnWBaJwpon/xJdWkFVMiM3m5HXdGXAV/tNyftShj7uK2Wz88Od0L WN7TdzfAsuqGJFi/KOQkCJJTYw49qrLfkNSTRT+OA07NpdMWvJ9C6Xdof+SAxKWVMhum AoCa2ZBari37Erbj7mf213VxC8Vcmzx4TjaArlTcKnsTBjvoHHKttwLgWU8sxujz/sPs mtShaZ4KzVFK9FBvVG09+CWLIvLgHqq2mF95fcrpyIeBszf6z4wwUqd9aDjdfaszZ/sh SXC25R+cYsKByO9GyxUlKoBTSrGCfSoLCdLfsHt1MQzC2EG7/EaWJJBvO/LDe/RJOFDA BIhw==
X-Gm-Message-State: AIkVDXKenCOr7nREYgvBvLvv3jg3doCSrMCSlxyyjVOQkxDaybEwnAfoqxzOV6GS08kFJA==
X-Received: by 10.98.163.216 with SMTP id q85mr25252628pfl.123.1485814240922; Mon, 30 Jan 2017 14:10:40 -0800 (PST)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id z77sm35058391pfk.47.2017.01.30.14.10.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jan 2017 14:10:40 -0800 (PST)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Eliot Lear <lear@cisco.com>, mtgvenue@ietf.org
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <2dcdf5d1-4e93-7476-79ba-0369e41af1c0@cisco.com> <43126aa9-5bc1-fae5-ff76-3ad288e37340@cs.tcd.ie> <24c2e78e-97ab-9642-f067-1da4fc82d9b6@cisco.com> <092a25ac-ed8f-98a3-a421-6bc6af9d90a2@cs.tcd.ie>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d9e488ac-7602-3810-d0ea-6ad1321b0d38@gmail.com>
Date: Tue, 31 Jan 2017 11:10:37 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <092a25ac-ed8f-98a3-a421-6bc6af9d90a2@cs.tcd.ie>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/YteZV89C8P3_W65SyH40kBp9dEE>
Subject: [Mtgvenue] Emergency cancellation [was: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04]
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 30 Jan 2017 22:10:43 -0000

On 31/01/2017 04:07, Stephen Farrell wrote:
> 
> Hiya,,
> 
> On 30/01/17 14:14, Eliot Lear wrote:
>>

...
>> Just a question: if a meeting were to be canceled today, say due to a
>> natural catastrophe, who would make that call?
> 
> My guess is a combination of IESG/IAOC with help from
> folks involved in meeting arrangements (hosts, locals,
> ams, NOC).

It would surely depend on the urgency. If a major earthquake
hit the venue on the previous Friday, I would expect the IAD
(with the Secretariat) to take a decision within a few hours,
after a best effort to consult the IETF Chair and the local
hosts. If there was a week to go, a round of consultation
with the IAOC and the IESG would be possible.

> Ultimately, I'd say it'd be the IESG's responsibility

I don't think that's clear. BCP101 gives authority over business
decisions to IASA, which is led by the IAD, overseen by the
IAOC. Emergency cancellation of a meeting seems like a business
decision to me. But obviously, if time permits, consensus between
the IAD, the Secretariat, the IAOC and the IESG would be very
highly desirable.

In any case this seems out of scope for the present document.

    Brian

> but
> that any sane IESG would want the IAOC to agree with them
> or to have asked that the IESG make the call. Equally
> though if a sane IAOC came to the IESG and said "we really
> need to cancel" I can't see it'd be likely an IESG would
> disagree, though there'd be a fairly interesting Q&A I'm
> sure.
> 
> All that said, I've not gone looking anywhere to check
> so the above could be wrong. Maybe the contingency plan
> behind those URLs has answers?
> 
>>
>>
>>>
>>>>> - 3.1, host/sponsors: I don't think this ought be mandatory
>>>>> as we may move from a sposor-related-to-venue model to some
>>>>> other ways in which sponsors help out.  It might be better
>>>>> to cast this as a negative, i.e. to say that it is
>>>>> mandatory to ensure that a venue is not sponsor-unfriendly
>>>>> to a significant degree and I'd also s/mandatory/important/
>>>>>
>>>>> - 3.2, "within the norms of business travel": I don't like
>>>>> that characterisation - IETF participation might in future
>>>>> not live up to that budget. Ought we say "acceptable to IETF
>>>>> participants in general" maybe.
>>>> Didn't we just get away from having to evaluate what that means?
>>> Not sure what you mean. My point is that for some IETF
>>> participants (some of the time;-) "business travel" means the
>>> front of the plane and no problems with expensive hotels.
>>> Others are more constrained. I'd prefer we ground the acceptable
>>> costs on the "average" meeting-attending IETFers ability to pay.
>>
>> I get it.  Just want to avoid consensus calls on what people think is
>> reasonable.  Maybe spelling out what is meant by "norms of business
>> travel" is best...
> 
> I'd avoid the phrase "business travel" entirely. While IETF
> travel is business for almost all of us, that phrase has
> connotations of more comfort than some of us can afford, at
> least for me when I play the poor-mouth:-)
> 
> Cheers,
> S.
> 
>>
>> Eliot
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mtgvenue mailing list
>> Mtgvenue@ietf.org
>> https://www.ietf.org/mailman/listinfo/mtgvenue
>>
> 
> 
> 
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue
>