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

Eliot Lear <lear@cisco.com> Wed, 17 October 2018 14:36 UTC

Return-Path: <lear@cisco.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 2F01B130DDE for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 07:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 7mdbuFyspnSD for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 07:36:43 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 685EE130DDD for <mtgvenue@ietf.org>; Wed, 17 Oct 2018 07:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9782; q=dns/txt; s=iport; t=1539787002; x=1540996602; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=pma0NLYp+aZVuXDnPitImcrRaOhNvNrlRWAbzlWTbt0=; b=XpY/M/ni7rhTQfHWKEcdhSPyrB+bEIid+C01QT6tsjNZc5gBcR78MtGp JmsBlyZctksdsHQyfg2gYTkoBa4VcayF99fGWSDU+Mm+o9qU3gbvEzv/D MS8a3zwWnqCUGD/Ra/sjDx/68+RoKypoy3qW+gh4JBZjK91IbZY7GlnkN I=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BVAAABSMdb/xbLJq1iGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBZYJrbRIog3WIdo0jJZFEh0IIBRgBCoFUgi9GAoUbOBYBAwE?= =?us-ascii?q?BAgEBAm0cDIU6AQEBAwEBIUsbCxgqAgInMAYBDAYCAQGDHAGCAQ+kSoEuH4l?= =?us-ascii?q?qD4JtiHaCAIESJwyCX4MbAQGEZIJXAp4xCYQJgWuKaQYXiS6GdJY7gVohgVU?= =?us-ascii?q?zGggbFTuCbAmCHReCc4VohUA9MIwKAQE?=
X-IronPort-AV: E=Sophos;i="5.54,392,1534809600"; d="asc'?scan'208,217";a="7257517"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Oct 2018 14:36:40 +0000
Received: from [10.61.164.232] ([10.61.164.232]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id w9HEadSj018480; Wed, 17 Oct 2018 14:36:39 GMT
To: Michael Richardson <mcr+ietf@sandelman.ca>, mtgvenue@ietf.org
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> <1668199fe88.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <1ffec901-2a99-8af5-b42f-978a79b17266@cisco.com> <32703.1539783790@localhost>
From: Eliot Lear <lear@cisco.com>
Openpgp: preference=signencrypt
Autocrypt: addr=lear@cisco.com; prefer-encrypt=mutual; keydata= xsBNBFMe1UQBCADdYOS5APDpIpF2ohAxB+nxg1GpAYr8iKwGIb86Wp9NkK5+QwbW9H035clT lpVLciExtN8E3MCTPOIm7aITPlruixAVwlBY3g7U9eRppSw9O2H/7bie2GOnYxqmsw4v1yNZ 9NcMLlD8raY0UcQ5r698c8JD4xUTLqybZXaK2sPeJkxzT+IwupRSQ+vXEvFFGhERQ88zo5Ca Sa1Gw/Rv54oH0Dq2XYkO41rhxQ60BKZLZuQK1d9+1y3I+An3AJeD3AA31fJZD3H8YRKOBgqe ILPILbw1mM7gCtCjfvFCt6AFCwEsjITGx55ceoQ+t5B5XGYJEppMWsIFrwZsfbL+gP31ABEB AAHNJUVsaW90IExlYXIgPGxlYXJAb2Zjb3Vyc2VpbXJpZ2h0LmNvbT7CwJEEEwECADsCGwMC HgECF4ACGQEWIQSY0L2QRh2wkqeyYR2HtmtG2dJ6MwUCWxJwMwULCQgHAgYVCAkKCwIEFgID AQAKCRCHtmtG2dJ6MyMyCACXvtFjAYGMtOkD9MD4nI3ifFpkrj8xTMbXjrv5hdqmzRmQ0wqA 1U/OlZux+P/NaVMiZNZc8zw0nsx/INAqDOVd4/tLWF+ywTkeRFR0VnaUxLwCReZAZOaRS+md +52u/6ddoFja2RnjZ43qbbuvVUARQVIyMJz+GbR6mEZQHR0psD7dDYZDyrpivCxm8zHQwmB6 AZUlO7OJgljDvVPVDCabg/ZnJw1qS0OzSiNb0MySk1D5A7FdwDgeKxuMYUOOoVVTTMWNWcME UkRX9LxElswEt0PQWiz/j3FYXTxiFfl/1vKcHx4pM+E5C5mhTbrdFUFLJC3Y5fLID7stK/Ch aEaBzsBNBFMe1UQBCAC0WV7Ydbv95xYGPhthTdChBIpPtl7JPCV/c6/3iEmvjpfGuFNaK4Ma cj9le20EA5A1BH7PgLGoHOiPM65NysRpZ96RRVX3TNfLmhGMFr5hPOGNdq+xcGHVutmwPV9U 7bKeUNRiPFx3YdEkExddqV2E8FltT0x2FSKe2xszPPHB6gVtMckX5buI9p1K3fbVhXdvEkcY Y/jB0JEJGyhS5aEbct5cHUvDAkT81/YFK5Jfg8RRwu1q1t1YuIJSOWAZQ9J9oUsg6D9RpClU +tIFBoe3iTp1AUfJcypucGKgLYKtpu/aygcpQONHYkYW5003mPsrajFhReVF5veycMbHs4u5 ABEBAAHCwF8EGAECAAkFAlMe1UQCGwwACgkQh7ZrRtnSejOSuQgA27p2rYB7Kh20dym6V8c6 2pWpBHHTgxr/32zevxHSiXl6xvUCg5T8WUwfUk8OvgDcBErK/blDAMXQzSg3sp450JhR8RnX HXF5Zz2T04X7HnlIVJGwf2CjnwyEAJCqMzaCmI+g3Imvg/8L4nyBFvhlFHDv+kIvMiujyycj PAu7xxKplBs1/IEwmDoAMjneFmawvfeQnwdMhSKK8PjKSuzGU5uUmxj3GBfRqvTM0qpmhMPF OmDhJSmH55HLAky2MlmqJYXJPt/9EfSEhFiua1M6gLiuNEuPkp+8jcnHQqKr0IeHt8UqcwLt 2mGfIyl0FVdF9hvWPjNRzGbgqoT1Di03RQ==
Message-ID: <31b4951e-b315-b01c-6545-fb9c70259a98@cisco.com>
Date: Wed, 17 Oct 2018 16:36:39 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <32703.1539783790@localhost>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="va1swJSp7AmX048Aam8NQlCeWVhO96Ti4"
X-Outbound-SMTP-Client: 10.61.164.232, [10.61.164.232]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/vg2jARDhkCXbTUpm_zMuZKj-Wyg>
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 14:36:50 -0000

Thanks, Michael and Lou for your thoughts.  What I am thinking about is
this: what is best for the reader?  I feel pretty strongly that at the
very least, the reference to 4071 has to come out, as it describes an
inapplicable appeals process and a structure that no longer matches how
we are operating; and simply replacing that reference with BCP 101 won't
do either, because that really just refers the reader back to RFC 4071,
as a practical matter, and there's reason to believe that there will be
a replacement appeals process that is applicable here (the big secret
here is that there really wasn't much of an appeals process in this
situation re 4071, but referencing 4071 used less words).

Your suggestion below talks about a change to the introduction to
essentially redefine the IASA.  I think if we're doing that, there are
some other alternatives we should consider, like replacing the word
"IASA" with "meeting organizers".  And then we simply point to who those
are at this moment (e.g, the LLC).  I love using plain English when we can.

To Lou's point about feeling rushed, had I believed that the LLC was
going to move as fast as it did, I would have not wanted to advance this
doc, but here we are, and AUTH48 is just a state and the RFC Editor has
patience, so... let's just figure out what the right thing to do is.

Eliot

On 17.10.18 15:43, Michael Richardson wrote:
> I think that what Eliot would like to do is change "IASA" to "LLC".
>
> Lou has suggested that "IASA" is an abstraction (a layer of indirection)
> which was resolved to IAOC before, and that now resolved to "LLC".
>
> Eliot has then asked, if IASA is a superset of LLC, what is there of
> IASA which is not LLC.  If it's empty, why make it hard for the reader,
> and just dereference the pointer.
>
> I can see both points.
>
> I suggest the text of the abstract be:
>     The IETF Administrative Support Activity (IASA) (implemented by the IETF
>     LLC) is responsible for arranging the selection and operation of the IETF
>     plenary meeting venue.  ...
>
>
> Intro:
>    The IETF Administrative Support Activity (IASA) is
>    responsible for arranging the selection and operation of the IETF
>    plenary meeting venue.  Until he fall of 2018, the IASA was embodied in
>    the form of the IETF Administrative Oversight Committee (IAOC).  From
>    fall 2018 onwards, the IASA was implemented by the IETF LLC.  This
>    document uses the abstract term "IASA" to refer to both embodiments.
>
>    The purpose of this document is to guide the IASA...
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
>
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue