Re: [Mtgvenue] issue #3: Too many mandatory

Lou Berger <lberger@labn.net> Wed, 05 April 2017 21:43 UTC

Return-Path: <lberger@labn.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 C8EE21294BC for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 14:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 h8j0uu7PPOyT for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 14:43:34 -0700 (PDT)
Received: from outbound-ss-1812.hostmonster.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) (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 CE3FF1294B2 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 14:43:26 -0700 (PDT)
Received: from cmgw4 (cmgw5 [10.0.90.85]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id F00A9178532 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 15:27:15 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id 4lTC1v00n2SSUrH01lTFue; Wed, 05 Apr 2017 15:27:15 -0600
X-Authority-Analysis: v=2.2 cv=QdwWhoTv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=AzvcPWV-tVgA:10 a=izSsRRaaGeDCKhXD1YsA:9 a=pILNOxqGKmIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=VKnULnpjbqTOwb8O47MFcK6VD5nAThGGPZjL6Bu4Lcw=; b=HA2HGYbuz9oOr0or3BIcW2iFa7 54qOIeLtWpvRrKtvqRfc9vNVbaW/Wr+775iwFTHmv4n7sA6DXBJmGZOaWuspBlqUgemnKbLp+FIBx YfVAqMOz9BbePEg8qpk3Lm2eS;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:38260 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1cvsSO-00048y-M6; Wed, 05 Apr 2017 15:27:12 -0600
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com> <a1b4fb14-64ec-2848-91e7-faa93ba6e697@labn.net> <cfd7ace5-d834-fb41-57a4-ea11d0126f0f@cisco.com> <10ee5913-87d4-d895-e880-54471b2469a7@labn.net> <759DD927-BEC2-4989-A9F5-46B7DD090B24@qti.qualcomm.com>
Cc: Eliot Lear <lear@cisco.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
From: Lou Berger <lberger@labn.net>
Message-ID: <4fdf7dea-b565-845e-1e0e-541d88a530e1@labn.net>
Date: Wed, 05 Apr 2017 17:27:06 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <759DD927-BEC2-4989-A9F5-46B7DD090B24@qti.qualcomm.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.84.20
X-Exim-ID: 1cvsSO-00048y-M6
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:38260
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/vA_kZ7zQztCQRlX0bhtgGii9Y7k>
Subject: Re: [Mtgvenue] issue #3: Too many mandatory
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: Wed, 05 Apr 2017 21:43:36 -0000

Pete,

    Thanks for the response.


On 4/5/2017 3:31 PM, Pete Resnick wrote:
> On 5 Apr 2017, at 11:44, Lou Berger wrote:
>
>> On 4/5/2017 12:02 PM, Eliot Lear wrote:
>>> This one gets removed based on comments in the room.
>>>
>> I don't mind being in the minority / the rough, but I think it
>> reasonable for us to follow rfc2418 in this discussion.
> I would take Eliot's sentence to mean, "Based on what was said in the 
> f2f room in Chicago, this is to be removed. Speak up if you disagree." 

Well I wanted to get more info and to understand before rehashing what
was discussed.  As this wasn't minuted (but I didn't listen to the
recording) I thought asking before disagreeing made sense.  Depending on
the rationale/conclusion I may even agree.

> In particular, I would not interpret it to mean, "This is absolutely the 
> consensus of the WG, therefore it will be removed and we are done with 
> this topic."

Fair enough.  Given the brevity of the response -- This is basically how
I read it.

>  So I think we are following regular 2418 order here.

Great.  My hope  is to see (quoting here)

   Decisions reached during a face-to-face meeting about
   topics or issues which have not been discussed on the mailing list,
   or are significantly different from previously arrived mailing list
   consensus MUST be reviewed on the mailing list.


Specifically, I think it's reasonable to explain on the list  the
rational for basically saying the it's okay to plan for a meeting that
will operate at a loss discussed.

Lou

> Still looking in the Meetecho recording for the section that speaks to 
> your substantive point. (Gee, transcription service would be nice.)
>
> pr