Re: [Mtgvenue] Where we are, post #2

Dave Crocker <dhc@dcrocker.net> Mon, 30 January 2017 23:54 UTC

Return-Path: <dhc@dcrocker.net>
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 E9AE61296CF for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 15:54:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 rtNc_lh8D26a for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 15:54:53 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1F001296D0 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 15:54:53 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v0UNuRx4017536 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Jan 2017 15:56:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1485820588; bh=ReJPicBeZK228HfxT+XRitMXq3dT7+GWlWZxLa9FFPs=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=nBAfR8y1yjBvZbnVptBzh9rkzX5GKdgPpB7vxP/z72Y7ev50w30RrQPJ9s2sS85nl ja4q3p1H4eqmarPOZUhTibnD0JyGO1wDs5yz190weFldM4bAdJ1Pc/U5EyS6CZJheB XbOeF43yO4HZjjKBxevQTGjlLjL7SivHwaiJlp4o=
To: Ted Lemon <mellon@fugue.com>
References: <056312a7-741c-77af-8759-657aedb24f43@nomountain.net> <8e501210-5db5-c8db-5aa0-0f58a0a90d59@gmail.com> <a0ebba80-e028-9b5a-e531-384b0706049f@dcrocker.net> <0E900203-6558-4E8C-A166-9B1E5B36E2AE@fugue.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <62c08304-c97a-c84e-3e00-2f68f4d45a59@dcrocker.net>
Date: Mon, 30 Jan 2017 15:54:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <0E900203-6558-4E8C-A166-9B1E5B36E2AE@fugue.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/e-2aFBrI-uToCjpyn6w03u0-LGo>
Cc: mtgvenue@ietf.org
Subject: Re: [Mtgvenue] Where we are, post #2
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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 23:54:55 -0000

On 1/30/2017 3:40 PM, Ted Lemon wrote:
> The only problem with this text is that "a range" isn't defined, and
> would not be sufficient to clue in a clueless IAOC.   It will do fine if
> the IAOC _isn't_ clueless.   I don't know if we can do much better than
> this in a document of this sort, but I hope no-one imagines that this
> text guarantees a successful outcome.


In terms of IAOC decision-making, it's difficult to imagine that the 
added words -- or rather, the words being proposed to drop -- would give 
meaningful, additional guidance.  So I think the concern you raise is 
present with either form of the entry.  (Not that you implied otherwise; 
I'm just trying to be thorough...)

It's also difficult to imagine that any finite amount of additional 
language would provide meaningful detail that would be sufficiently 
complete to be useful, or that we could develop it in finite time.

So, yeah, no guarantees.  But the utility of the entry is that it 
targets a basic issue and makes dealing with it a requirement.  Where 
the only 'detail' is mandates is that the combination of nearby grocery 
and onsite service handle a wide range of dietary needs.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net