Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process

Lou Berger <lberger@labn.net> Wed, 17 October 2018 10:41 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 3D74812F1A2 for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 03:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 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=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0hI0ilSCiODp for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 03:41:38 -0700 (PDT)
Received: from outbound-ss-579.bluehost.com (outbound-ss-579.bluehost.com [74.220.218.175]) (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 59BCF12D7EA for <mtgvenue@ietf.org>; Wed, 17 Oct 2018 03:41:38 -0700 (PDT)
Received: from cmgw14.unifiedlayer.com (unknown [10.9.0.14]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id E04CB1E14CD for <mtgvenue@ietf.org>; Wed, 17 Oct 2018 04:37:27 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id CjChgc9QavdTuCjChgxEV0; Wed, 17 Oct 2018 04:37:27 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject: References:In-Reply-To:Message-ID:Date:CC:To:From: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=hDPro7XdvqRtWsl8LCYLjqBTyFvelr2Pw2m8DYaC4oA=; b=0jmDpUFl1VfUjRoZrr4rK2lhyK FOQEf4NEqajYhahXyHhsTRtwyvZKOFaIv2r234hTlvfaSDf06b2rhX7DvrtN3uPYtX7S5P/ky/j13 Ot1201YAdFA8gEVz2wsaVCz1O;
Received: from pool-100-15-106-211.washdc.fios.verizon.net ([100.15.106.211]:44135 helo=[11.4.0.65]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1gCjCh-001ROc-Ij; Wed, 17 Oct 2018 04:37:27 -0600
From: Lou Berger <lberger@labn.net>
To: Eliot Lear <lear@cisco.com>, <mtgvenue@ietf.org>
CC: Alissa Cooper <alissa@cooperw.in>
Date: Wed, 17 Oct 2018 06:37:25 -0400
Message-ID: <1668199fe88.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <6b18f4f3-1e5a-24ac-36e1-54c509139d25@cisco.com>
References: <328e9dfe-8e30-6388-68be-95b55af0a5b0@cisco.com> <1667ccb8a70.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <471f7ba9-0b9e-256c-513d-78559ff200a1@cisco.com> <58f9ebdd-355e-129f-a987-dab72bc5da6f@labn.net> <9472f4e7-86bc-121c-ae43-13fcdde451d4@cisco.com> <38ad1b3b-309c-4bdb-fe14-0bbd584bb808@labn.net> <adc56f21-0f57-0be0-799e-126072c62fe0@cisco.com> <1667f3a9670.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <6b18f4f3-1e5a-24ac-36e1-54c509139d25@cisco.com>
User-Agent: AquaMail/1.16.0-1193 (build: 101600006)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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.106.211
X-Source-L: No
X-Exim-ID: 1gCjCh-001ROc-Ij
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-106-211.washdc.fios.verizon.net ([11.4.0.65]) [100.15.106.211]:44135
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/v57RKdrPayPGsHjeqafbJlixrdM>
Subject: Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Oct 2018 10:41:40 -0000

Eliot


----------
On October 17, 2018 2:46:15 AM Eliot Lear <lear@cisco.com> wrote:

> Lou,
>
>
> On 17.10.18 01:33, Lou Berger wrote:
>> Eliot,
>>
>> The LLC is part of IASA.  The issue is that this change is more than a
>> simple sed.
>>
>
> I asked twice, and I've yet to get an answer as to what part of IASA
> remains that is NOT the LLC.  Can I get a straight answer to that? 

I don't think this is a fair statement.  I do accept that I have failed at 
describing the difference between iasa, something that was defined many 
years ago, and the LLC which is still nacent, to your satisfaction.  I 
suggest you look to the iasa2 wg and the many drafts being produced there 
to see if they can provide the information you are seeking.

> Otherwise, this really *is* not much more than a simple sed.  The
> fundamental: adding unnecessary levels of indirection is confusing to
> the reader.

Iasa was sufficiently clear for all the LC reviews. I therefore see this 
proposed change as a difference without distinction, but if the working 
group consensus is to make the change it will do no harm other than causing 
a delay in publication.

If this change is made, I do I think we have to get the language right and 
also agree with Bob that a normative reference to the document defining the 
LLC is needed in this document.

Lou
>
> Eliot
>
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue