Re: [Mtgvenue] [HT-rt] HR-RT Review of draft-ietf-mtgvenue-iaoc-venue-selection-process

Randy Bush <randy@psg.com> Sun, 22 April 2018 23:44 UTC

Return-Path: <randy@psg.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 9D0A412426E; Sun, 22 Apr 2018 16:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 AWGgEVN24gQg; Sun, 22 Apr 2018 16:44:29 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 C48111200FC; Sun, 22 Apr 2018 16:44:29 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1fAOeh-0006Y3-R6; Sun, 22 Apr 2018 23:44:27 +0000
Date: Sun, 22 Apr 2018 16:44:27 -0700
Message-ID: <m2y3he957o.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Rinse Repeat <ietf@ietf.org>, mtgvenue@ietf.org
In-Reply-To: <20180422220513.32x4zfe4gt2hg4cv@mx4.yitter.info>
References: <d0739bb2-626e-8aa3-f22f-d51b07dfdacf@digitaldissidents.org> <21952.1524157167@obiwan.sandelman.ca> <7B17FF2E-4393-4644-998B-16462F71A00F@qti.qualcomm.com> <7f7fced1-489b-94a8-170b-0038e330484f@digitaldissidents.org> <CA+0Hr7viF48qJt4YcWNpBU5qHkpWVFKUwYPaKdgrWWXtVH2fPw@mail.gmail.com> <20180422220513.32x4zfe4gt2hg4cv@mx4.yitter.info>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/RGxG0bkxgTVl8-8DClexLj7CM_w>
Subject: Re: [Mtgvenue] [HT-rt] HR-RT Review of draft-ietf-mtgvenue-iaoc-venue-selection-process
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 22 Apr 2018 23:44:32 -0000

given the long thread and having a bit of free time, i decided to read
through this document.  from the discussion, i was expecting a horrible
nit-picking, micro-management, exercise in ocd, and promised myself to
just hit delete and play my one get-out-of-snark card of the week.

to my shock and pleasure, the document is mostly simple and sensible.
section 3, meeting criteria, seems to have tried to be somewhat minimal;
but once you enter that rathole it becomes a twisty maze; as can be seen
in this thread.

i would just shove this out the door and get back to seeing how complex,
unimplementable, and unusable we can make the internet protocols.

randy