Re: WG Review: IETF Administrative Support Activity 2 (iasa2)

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 April 2018 21:22 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A2A12DA12 for <ietf@ietfa.amsl.com>; Thu, 12 Apr 2018 14:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, URIBL_BLOCKED=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 ik5XVvdiHgYB for <ietf@ietfa.amsl.com>; Thu, 12 Apr 2018 14:22:45 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 AB2FE1270AC for <ietf@ietf.org>; Thu, 12 Apr 2018 14:22:45 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id u86so4857264pfd.2 for <ietf@ietf.org>; Thu, 12 Apr 2018 14:22:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=IiQotSe0M2rNd2C6/oiDmPDB3T+4seZ7pn0zMzpz8Q0=; b=Z552e0XrK8LRxkCImX9AozYg68tbtnmnkXgDXSmWYLyB1dUpF7RJEQJ8kg0sEcYbda k0eYyYNc23Ythq69oLpYMUkCENAaAVYyoOi2GlOsSNF57xj4ssGqMdIkIGoqxpU43Pri nLWSbLW+9QmdLoY7Rsi2JnCU8sXp+OqUEiKbVMQhJQm/IYC1zCfKv+JvS8g9CWxw6HDm 95VNkcNryUR3JD7YuH46ByuoyVMj0lueA3kZRPT+8BCAOS0ydUmQoALukGUCBZGyZRx6 OU8uo/tN62L5p1i5pi3jPV04naKzLtjRkf7XcjcRai0riTEX9VvyGUNIZ0zJGtv2bW/9 iugw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=IiQotSe0M2rNd2C6/oiDmPDB3T+4seZ7pn0zMzpz8Q0=; b=drPnsffPg75SsFGFneYuSbXwuV6LRPxn5Wn1UL2P9kYZ2nkAaA7JS7ljfHhHVcIDO+ EkT+3YDFeXPYx3wFlbN20sjifR3Bn/8CBe8+3IcmH2q6jrvkkc0RbH+ZBisyac7ic9GD zeruPxL9QaiFsmk49XP9Niov94Owfnk95tQqwuSwy78RPZ3ljEdG2Ng2iQNsNvGVR+WO ztEl85hcapgz8EApPT0vNfI0+7HcmeTDk/HR0yny20FRhh31mMMZHrYtWgbRwi/kqzZi CKdGlp4AgHcjoOGrNXC68zqJJS7mNOpStsPZftUrkBgvISgTmHkRKellFNs8hi7k02Kt QcIQ==
X-Gm-Message-State: ALQs6tDOcwyqZhI3xs/P3mLrZAbEJsjzXXxISVDePgav1VZzBZkDY3UW zW7K00wKqVyj44WT0Ppvka4c9g==
X-Google-Smtp-Source: AIpwx4+aEm3olj6EMXzzGTsnSHFwhJkoGWHpr6ieZ7E5f2CZqXVBK/ktrJwvcPgfNuUan9PMM7AaLA==
X-Received: by 10.98.9.72 with SMTP id e69mr9087074pfd.197.1523568164884; Thu, 12 Apr 2018 14:22:44 -0700 (PDT)
Received: from [192.168.178.26] ([118.148.68.60]) by smtp.gmail.com with ESMTPSA id u28sm9340742pfl.15.2018.04.12.14.22.42 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Apr 2018 14:22:43 -0700 (PDT)
Subject: Re: WG Review: IETF Administrative Support Activity 2 (iasa2)
To: ietf@ietf.org
References: <152303081671.3739.8330720014623256850.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7fb3e84d-2625-dc99-0d47-c32ee1a386ce@gmail.com>
Date: Fri, 13 Apr 2018 09:22:48 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <152303081671.3739.8330720014623256850.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2BnBc33vpP7CVvfG0brleAAsZfY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Apr 2018 21:22:49 -0000

Hi everybody,

One comment about this draft WG charter. It includes these words:

>  ...Among
> multiple legal structure options that were considered by the IETF community,
> a new limited liability corporation (LLC) that is a disregarded entity of
> ISOC (i.e., it is treated as a branch or division of ISOC for tax purposes)
> will be created to house the administration of the IETF. ISOC supports this
> plan.
>
> This working group is chartered to document the normative changes to IETF
> administrative structures and processes necessary to effectuate this change.

In other words, if the charter is approved, we will effectively have decided
on a major change to the administrative and organizational status of the IETF.
Of course, eventually there will be a formal IETF last call on RFC4071bis, but
by then things will be far advanced.

I'm not commenting here on whether this is the right or wrong decision,
since I've had ample opportunity to do so in the IASA2.0 discussion so far.
I just want to be sure that people *not* active in that discussion understand
what we are deciding to do.

Regards
   Brian Carpenter

On 07/04/2018 04:06, The IESG wrote:
> A new IETF WG has been proposed in the General Area. The IESG has not made
> any determination yet. The following draft charter was submitted, and is
> provided for informational purposes only. Please send your comments to the
> IESG mailing list (iesg@ietf.org) by 2018-04-16.
> 
> In November 2016, the IETF Chair kicked off the IASA 2.0 project [1]. 
> Throughout 2017 and 2018, community discussions occurred on the 
> iasa20@ietf.org mailing list, in two virtual workshops [2], by way of 
> individual drafts [3][4][5], and at BoF sessions at IETF 98, 99, 100, 
> and 101. In 2017 the IETF Chair convened a design team to evaluate 
> potential legal and organizational options for the IETF's administrative 
> structure. The design team examined types of organizational models and 
> made initial recommendations [6] prior to IETF 100. As a result of that 
> discussion, the design team working with the IETF Chair asked the 
> Internet Society's tax law attorneys to outline a series of specific 
> legal options [7][8][9]. These options, together with proposed elements 
> of a specific organizational structure [10] were discussed at IETF 101. 
> The design team's recommendation [11] and the rough consensus in the 
> room as confirmed on the iasa20@ietf.org list in favor of a specific 
> legal option -- a limited liability corporation that is treated as a 
> branch or division of ISOC for tax purposes -- is embedded in the 
> charter text below.
> 
> [1] https://mailarchive.ietf.org/arch/msg/ietf/IkZfIBfM5jSrMflbY9k4cOzK8Ps
> [2] https://tools.ietf.org/html/draft-hall-iasa20-workshops-report-00
> [3] https://tools.ietf.org/html/draft-daigle-iasa-retrospective-01
> [4] https://tools.ietf.org/html/draft-arkko-ietf-iasa-thoughts-00
> [5] https://tools.ietf.org/html/draft-arkko-ietf-finance-thoughts-00
> [6] https://tools.ietf.org/html/draft-haberman-iasa20dt-recs-01
> [7] https://mailarchive.ietf.org/arch/msg/iasa20/XT_3vfd3OWVFCW335mRrvWuusaI/
> [8] https://mailarchive.ietf.org/arch/msg/iasa20/cPK6ei47a-VG3vERO0JqpT144uE
> [9] https://mailarchive.ietf.org/arch/msg/iasa20/UiGdiDEXyiT1x0WM8iUkxJkq1OI
> [10] https://tools.ietf.org/html/draft-hall-iasa2-struct-01
> [11] https://tools.ietf.org/html/draft-dt-iasa20-proposal-00
> 
> IETF Administrative Support Activity 2 (iasa2)
> -----------------------------------------------------------------------
> Current status: Proposed WG
> 
> Chairs:
>   TBD
> 
> Assigned Area Director:
>   Alissa Cooper <alissa@cooperw.in>
> 
> General Area Directors:
>   Alissa Cooper <alissa@cooperw.in>
> 
> Mailing list:
>   Address: iasa20@ietf.org
>   To subscribe: https://www.ietf.org/mailman/listinfo/iasa20
>   Archive: https://mailarchive.ietf.org/arch/search/?email_list=iasa20
> 
> Group page: https://datatracker.ietf.org/group/iasa2/
> 
> Charter: https://datatracker.ietf.org/doc/charter-ietf-iasa2/
> 
> The arrangements relating to administrative support for the IETF (referred to
> as the "IETF Administrative Support Activity" (IASA) [RFC4071]) were created
> more than ten years ago, when the IETF initially took charge of its own
> administration.  The arrangements have served the IETF reasonably well, but
> there have been considerable changes in the size and scope of the IASA work,
> in the world around the IETF, and in the IETF community's own expectations
> since the creation of IASA.
> 
> As documented in [draft-haberman-iasa20dt-recs], the current
> administrative arrangements are facing a number of challenges. The range of
> IETF administrative tasks have grown considerably; the IASA organizational
> structure is not as clear, efficient, or as fully resourced as it should be;
> the division of responsibilities between the IETF and ISOC continues to
> evolve; expectations about transparency have changed; and the IETF faces
> continued challenges related to funding IETF activities against a backdrop of
> increasing costs and lack of predictability in our funding streams.
> 
> In November 2016, the IETF Chair launched a project in the community to
> re-assess the IETF's administrative arrangements. Since then, the IETF
> community has discussed the challenges we face, the properties we expect from
> future arrangements, options for the legal structure of future arrangements,
> and options for the organizational structure of future arrangements.
> 
> For legal purposes, IASA is currently organized as an activity of ISOC. Among
> multiple legal structure options that were considered by the IETF community,
> a new limited liability corporation (LLC) that is a disregarded entity of
> ISOC (i.e., it is treated as a branch or division of ISOC for tax purposes)
> will be created to house the administration of the IETF. ISOC supports this
> plan.
> 
> This working group is chartered to document the normative changes to IETF
> administrative structures and processes necessary to effectuate this change.
> The main deliverable will be a document that obsoletes RFC 4071. The working
> group will produce other supporting documents as necessary to achieve its
> charter objective. In parallel, the legal documents necessary to establish
> the LLC will be developed outside the working group with the support of legal
> counsel. These documents will not be products of the working group, but this
> working group will be the venue where these documents will be presented to
> the IETF community for review and discussion before they are finalized.
> 
> Aside from instances where they presently relate to IASA, it is outside the
> scope of this working group to consider any changes to anything related to
> the oversight or steering of the standards process as currently conducted by
> the IESG and IAB, the appeal chain, the confirming bodies for existing IETF
> and IAB appointments, the IRTF, or ISOC's memberships in other organizations.
> 
> Milestones:
> 
>   Nov 2018 - Document obsoleting RFC 4071 sent to IESG
> 
>   Nov 2018 - Document obsoleting RFC 4371 sent to IESG
> 
> 
>