Re: [Mtgvenue] document status, the role of the iaoc, and enforceability

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 27 January 2017 19:07 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 C0FBF1296F6 for <mtgvenue@ietfa.amsl.com>; Fri, 27 Jan 2017 11:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] 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 K55-mQtprU4X for <mtgvenue@ietfa.amsl.com>; Fri, 27 Jan 2017 11:07:19 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::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 51AC91296F2 for <mtgvenue@ietf.org>; Fri, 27 Jan 2017 11:07:19 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id e4so74929768pfg.1 for <mtgvenue@ietf.org>; Fri, 27 Jan 2017 11:07:19 -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=aI4XtiLFuu/JEXRZNy9SQwSp96XCMUyyZ5CizZnY+5A=; b=QwNnwc1/ulgRSzgJPAlQVDWK3IwIFbvsgc6qyrGNPMnoozPmWl1ucD3aCM4luTqU+l ghgfYYQF0c4q0k0zE7mPkFHiiUoSZqODyPie4tsHhUz4YtHK+Zd+5275wgqTcaIbvamX xokuFx7YBxs4XFZ85X9jckdfSQN5UEolqrjDsSr7a3RUvR5ZB5ScfbNstWELIZwKFQHI WwdVpxsDFCNql++RiYtfhZ1FPhWATV9BfgkW5bjPNxiLg9ypTTqk4TarQy3ZJXUk6sFz k5vFGeRZqOLm4F685LML4qLRVkz8pNlXQsVrIEay3yy5Qmvp/BNFudeGNlMr2ON4JSts BoKw==
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=aI4XtiLFuu/JEXRZNy9SQwSp96XCMUyyZ5CizZnY+5A=; b=TnfprCNPQTrC8SJa7Sbceba6k/KMBosKkx3B5joucRHiPy2+WdLWt+gVBCBwoRc7RN bo7aMSEYCNA0Iux1GNic5tdKHtV76IqhDDPQIDTP2zwoeR8UZGlv/C0LmblPalQWAmPy nq7Hh9/Eek6flzIFPuGp6G1W1TTKyTBrU4tmztwDtLzCPkC5mg4EP7MloEoNdo0G4uTx o7cTgc/egXb/Q5fEhQJRMcvegoGr/wjqTQwgm78rnzYjPcWMGb/cUopQXmJH0ek6H8xI IuRZv6CH6cK2IUrbGF9gssRNDc1qy//dtfEBbmKbcwFdfDUsZB69rEClF1krt8NIMRHB RLgw==
X-Gm-Message-State: AIkVDXLR1v7jcOyY3T7vnNLcVELUNHw5SIFwiQWzaUNYXahzWThsqHloBy6c2nq9zcCRhw==
X-Received: by 10.84.138.165 with SMTP id 34mr14615815plp.37.1485544038682; Fri, 27 Jan 2017 11:07:18 -0800 (PST)
Received: from [192.168.178.21] ([118.149.105.221]) by smtp.gmail.com with ESMTPSA id r16sm13162633pfg.76.2017.01.27.11.07.16 for <mtgvenue@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Jan 2017 11:07:17 -0800 (PST)
To: mtgvenue@ietf.org
References: <d064ed7c-abf6-68e6-584d-03d5354ee09f@nomountain.net> <1827bf44-e4d9-f436-e9d1-19da74029bfb@cisco.com> <a10c850a-9a95-fb77-5d99-931a08c38a32@dcrocker.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <26a07748-4cfc-ba42-e3e8-d08b153ce10d@gmail.com>
Date: Sat, 28 Jan 2017 08:07:27 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <a10c850a-9a95-fb77-5d99-931a08c38a32@dcrocker.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/IjRpn-xpYUrn6SG4LvsfLwjf70Y>
Subject: Re: [Mtgvenue] document status, the role of the iaoc, and enforceability
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: Fri, 27 Jan 2017 19:07:21 -0000

On 28/01/2017 04:23, Dave Crocker wrote:
> Thanks for pursuing this.
> 
> 
> On 1/27/2017 3:55 AM, Eliot Lear wrote:
>> At the end of 1.2, after the definition of terms:
>>
>> "While this document uses these terms and these meanings, it remains the
>> responsibility of the IAOC to apply their best judgment.  In particular,
>> this document is not to be used as a means to appeal the IAOC's
>> decisions.
> 
> Since this document is to be the normative basis for operation of the 
> selection process, how can it /not/ be relevant to an appeal process?
> 
> That said, if the intent is to say that there is no appeal process, we 
> probably should say that directly.

We can't. https://tools.ietf.org/html/rfc4071#section-3.5 defines
the appeal process and we certainly should not override that here.
Wouldn't it be better to say

"While this document uses these terms and these meanings, it remains the
responsibility of the IAOC to apply their best judgment.  Any appeals
remain subject to the provisions of [RFC4071]."

   Brian


> 
> If the intent is to constrain what types of meetings-related decisions 
> can be appealed, we should probably say that.
> 
> For example, in terms of pragmatic, once a contract is signed, an 
> 'appeal' would probably be counter-productive.  By contrast, appealing 
> the assessment of a possible venue, after the early community query, 
> would at least be possible.  (I'm trying to cite possibilities here. I'm 
> not sure what specifics you have in mind.)
> 
> 
>  > Individuals who disagree with IAOC decisions are invited to
>> participate in the NOMCOM process and to raise concerns with both the
>> IAB and the IESG in order that the matter may be addressed during member
>> selection."
> 
> Small editorial tweak:
> 
>     Individuals who disagree with IAOC decisions are invited to raise 
> their concerns by providing input to the various IAOC member selection 
> processes by the NOMCOM, IAB and IESG, as appropriate.
> 
> 
> 
> d/
>