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

Lou Berger <lberger@labn.net> Fri, 19 October 2018 17:51 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 8856A130F88 for <mtgvenue@ietfa.amsl.com>; Fri, 19 Oct 2018 10:51:39 -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 7Oj-BkW1nzAZ for <mtgvenue@ietfa.amsl.com>; Fri, 19 Oct 2018 10:51:37 -0700 (PDT)
Received: from gproxy1-pub.mail.unifiedlayer.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 6D346130DC4 for <mtgvenue@ietf.org>; Fri, 19 Oct 2018 10:51:35 -0700 (PDT)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id A200B3627ECF1 for <mtgvenue@ietf.org>; Fri, 19 Oct 2018 11:25:23 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id DYWZgEEpxE0jMDYWZgePPV; Fri, 19 Oct 2018 11:25:23 -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:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc: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=P8tsnYFuS+48a/6tPEIY9qJA7Pl0z2yap9JwCQJyzcQ=; b=TilCjWGos9OoBXU/EJYIwjcp0z zqIqDA4eRAYPgwBzEIssTg9AZa7Roe9GIm9scWcWYCJOQfYORm+oxmABGqoqIsK7k76A/CNCvPlzr eaCvJsAHFvrtHvbb0hmUl5UpD;
Received: from pool-100-15-106-211.washdc.fios.verizon.net ([100.15.106.211]:36090 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1gDYWZ-0047xL-81; Fri, 19 Oct 2018 11:25:23 -0600
To: Eliot Lear <lear@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, mtgvenue@ietf.org
Cc: Alissa Cooper <alissa@cooperw.in>
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> <e462c84b-62ba-8be9-a783-522cec948115@gmail.com> <7fa65dc0-729a-7cb7-821e-f4f0cb9cb07b@cisco.com> <f1e69b34-09cc-5c8d-cf49-8245f467a7ab@cisco.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <9f0ee951-9057-b197-f526-8254480a9e47@labn.net>
Date: Fri, 19 Oct 2018 13:25:21 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <f1e69b34-09cc-5c8d-cf49-8245f467a7ab@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
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: 1gDYWZ-0047xL-81
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-106-211.washdc.fios.verizon.net ([IPv6:::1]) [100.15.106.211]:36090
X-Source-Auth: lberger@labn.net
X-Email-Count: 5
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/2CzsKuUlvp7QtR0-sbqB6EAWSQ0>
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: Fri, 19 Oct 2018 17:51:39 -0000


On 10/19/2018 2:53 AM, Eliot Lear wrote:
>
> I have received one response to this in public, and several in 
> private, all preferring referencing of the LLC.  Last call, please.  
> Especially those who prefer retaining IASA.
>
>
> On 18.10.18 10:31, Eliot Lear wrote:
>>
>>
>>
>> On 17.10.18 21:48, Brian E Carpenter wrote:
>>> 1) The effort is called IASA 2 for a reason. IASA 1 was based on the
>>> IAD+IAOC structure. IASA 2 is based on the LLC structure. Who knows
>>> what IASA 3 will be based on? I see no problem with using IASA as
>>> the umbrella term.
>>
>> Two questions – for everyone:
>>
>>  1. Do you believe referencing the struct draft and using IASA is
>>     easier or harder for the reader?
>>
I really don't care at this point, as it's a no-op  to me -- 
particularly as the LLC will likely delegate the role/function so LLC is 
no more "transparent" than IASA, just one less step of indirection.

>>  1. Should we block on the struct draft?
>>
for what purpose -- to describe LLC selection and removal? then yes, a 
normative reference is required.

if just to point to a description of the LLC.  This is an informative 
reference that, per IETF process, can point to a draft.
>>
>>  1. Could we reference the LLC page informationally and use the LLC?
>>
If you are looking for an informative reference, the draft is a better 
reference.  If looking for a normative reference, The IETF process 
doesn't support normative references to a web site.

Lou

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