[Mtgvenue] Cite IASA not IAOC (issue 20)

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 14 May 2017 20:48 UTC

Return-Path: <brian.e.carpenter@gmail.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 04D46129B19 for <mtgvenue@ietfa.amsl.com>; Sun, 14 May 2017 13:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 WnbV7qsQVuh7 for <mtgvenue@ietfa.amsl.com>; Sun, 14 May 2017 13:48:56 -0700 (PDT)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (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 AFE4D129488 for <mtgvenue@ietf.org>; Sun, 14 May 2017 13:44:32 -0700 (PDT)
Received: by mail-pg0-x234.google.com with SMTP id u187so50527231pgb.0 for <mtgvenue@ietf.org>; Sun, 14 May 2017 13:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=Z3J+DC7pFfEZN13zs7PjYWHJRHg/868MXGrQc8JFWP0=; b=itCpXasfVdYjdYNq7KZl3J29MSQwJCkxNC5MgPf+xQSwasrkT+1qVQHIPnluYSwmAB xF4GL+xyK15/tSieeq2hohMwEFKCkjxzqZQzQGZ5E7293Kig76UHrLq2xsouYaeKXQSJ usSQpGbXMTUn0O2xs8Y1oLjE2R2f/iC9jncDu8X1WP5m32o2bgqzFSTnP3I5zA8xr6Qs LAi5giuRAp5r1nnttkbG+pjSkUn6TpUdWLaVQKHh6f2AxLYocqW9GPrjqjOz3u/QLmCJ Xxh7S0oZmS8gTgDKM8knapdLh4znNvL2NyBiSTg07169mAmux0O1x0UEuyO1WM0mX142 otKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=Z3J+DC7pFfEZN13zs7PjYWHJRHg/868MXGrQc8JFWP0=; b=GM9lZ3X/f6CUHg+O8+R/mH+D0tQH6QMxeLRcL6Xd755Nq9EbUda4oTM4Qy48Gapi1m hbfKXWWHHX2vwCiYqEHA64ODP49FB4RmCkZIXltrq/gcT+g4lNgPXnbY1Ty8SOJ0KhUU bu84LnOC3I8S3NHtkohC0dbCDTHcpIwl+yi+LdnMqEWpICtc5vT38zP/+GHNlb6PjGko jErf1NURnttXfaVZ9LvvqQo9SEbBw/lWrg0Trxxf61uijKhLlkgsyMGx82f7XeyWaYS8 6bfhPqpbamb0ThM7tqg0eoqqv7jb4pGwDiykSmbh0Ck7TBhXwMTjCF02FvyDutU9wFcV 1pgw==
X-Gm-Message-State: AODbwcAgqijhjlBhXedU82pBUBNrlAoQxZ5NGzGc06qld4lICovYWRBJ SP85n1AS8SDtPCCV
X-Received: by 10.99.96.70 with SMTP id u67mr2841314pgb.101.1494794672117; Sun, 14 May 2017 13:44:32 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.117.182]) by smtp.gmail.com with ESMTPSA id h28sm12633112pfd.55.2017.05.14.13.44.30 for <mtgvenue@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 14 May 2017 13:44:31 -0700 (PDT)
To: mtgvenue@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9d927288-b029-5d0f-3649-19f3209559b6@gmail.com>
Date: Mon, 15 May 2017 08:44:29 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/PYmO95AReestqYX3Aic31ZLcqfg>
Subject: [Mtgvenue] Cite IASA not IAOC (issue 20)
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, 14 May 2017 20:48:58 -0000

Hi,

draft-ietf-mtgvenue-iaoc-venue-selection-process-07 is looking much
closer to done. However, it opens thus:

   The IAOC has responsibility for arranging IETF plenary meeting venue
   selection and operation.

That statement directly contradicts BCP 101 (RFC 4071), which says

   The IAOC's role is to provide appropriate direction to the IAD, to
   review the IAD's regular reports, and to oversee IASA functions to
   ensure that the administrative needs of the IETF community are being
   properly met.  The IAOC's mission is not to be engaged in the day-
   to-day administrative work of the IASA, but rather to provide
   appropriate direction, oversight, and approval.

Discussion of that definition belongs in the IASA 2.0 debate, not here.
But it makes it plain that the venue selection draft should provide
guidance to IASA as a whole, not to the IAOC. So it should start thus:

   The IASA has responsibility for arranging IETF plenary meeting venue
   selection and operation.

Most of the document will be fine with s/IAOC/IASA/, except for the
URLs. There are some places where minor rephrasing is needed
(see ** below for an initial set of changes).

It's out of scope for this WG to comment on IASA internal organization
and the fact that the IAOC may be deviating from its mandate by performing
executive functions rather than oversight functions. I suggest not debating
that here.

Regards
   Brian Carpenter

**

1.  Introduction
...
OLD
   It remains the responsibility of the IAOC to apply their best
   judgment.  The IAOC accepts input and feedback both during the
   consultation process and later (for instance when there are changes
   in the situation at a chosen location).  Any appeals remain subject
   to the provisions of BCP101 [RFC4071].  As always, the community is
   encouraged to provide direct feedback to the NOMCOM, IESG, and IAB
   regarding the discharge of the IAOC's performance.
NEW
   It remains the responsibility of the IASA to apply its best
   judgment.  The IASA accepts input and feedback both during the
   consultation process and later (for instance when there are changes
   in the situation at a chosen location).  Since the IASA is overseen
   by the IAOC, any appeals remain subject
   to the provisions of BCP101 [RFC4071].  As always, the community is
   encouraged to provide direct feedback to the NOMCOM, IESG, and IAB
   regarding the discharge of the IAOC's performance.

4.2.  IESG and IETF Chair
...
NO CHANGE:
   The IETF Chair, among other things, relays
   these IESG-determined policies to the IAOC.  The IETF Chair is also a
   member of the IAOC.

4.4.  IETF Administrative Oversight Committee

OLD
   The IETF Administrative Oversight Committee (IAOC) has the
   responsibility to oversee and select IETF meeting venues.  It
   instructs the IAD to work with the Internet Society to write the
   relevant contracts.  It approves the IETF meetings calendar.  In
   cooperation with the IAD, the IAOC takes necessary actions to ensure
   that it is aware of participant concerns about particular venues as
   early in the process as is feasible.

NEW
   The IETF Administrative Oversight Committee (IAOC) has the
   responsibility to oversee and approve the selection of IETF meeting venues.  It
   instructs the IAD to work with the Internet Society to write the
   relevant contracts.  It approves the IETF meetings calendar.  In
   cooperation with the IAD, the IAOC takes necessary actions to ensure
   that IASA is aware of participant concerns about particular venues as
   early in the process as is feasible.


4.5.  IETF Administrative Support Activity

OLD
   The IETF Administrative Support Activity (IASA) supports the meeting
   selection process.  This includes identifying, qualifying and
   reporting on potential meeting sites, as well as supporting meeting
   Venue contract negotiation.  The IETF Secretariat is part of the IASA
   under the management of the IAD.  The IAD takes appropriate actions
   to solicit community input regarding both retrospective and
   prospective feedback from participants.

NEW
   The IETF Administrative Support Activity (IASA) performs the meeting
   selection process under the oversight of the IAOC.  This includes identifying, qualifying and
   reporting on potential meeting sites, as well as supporting meeting
   Venue contract negotiation.  The IETF Secretariat is part of the IASA
   under the management of the IAD.  The IAD takes appropriate actions
   to solicit community input regarding both retrospective and
   prospective feedback from participants.

OLD
4.7.  IAOC Meeting Committee
...
   Membership in the Meetings Committee is at the discretion of the
   IAOC; it includes an IAOC appointed chair, the IETF Administrative
   Director (IAD), IAOC members, representatives from the Secretariat,
   and interested members of the community.

NEW
4.7.  IASA Meetings Committee
...
   Membership in the Meetings Committee is approved by the
   IAOC; it includes an IAOC approved chair, the IETF Administrative
   Director (IAD), IAOC members, representatives from the Secretariat,
   and interested members of the community.