[CCG] Upcoming Changes to the IETF Trust

Russ Housley <housley@vigilsec.com> Thu, 11 October 2018 18:18 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ccg@ietfa.amsl.com
Delivered-To: ccg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4E8130EB9 for <ccg@ietfa.amsl.com>; Thu, 11 Oct 2018 11:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mw8VlRRN4S_P for <ccg@ietfa.amsl.com>; Thu, 11 Oct 2018 11:18:54 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31DFF1200D7 for <ccg@ietf.org>; Thu, 11 Oct 2018 11:18:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id E6425300AA8 for <ccg@ietf.org>; Thu, 11 Oct 2018 14:18:51 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EaG_PGtL3R0e for <ccg@ietf.org>; Thu, 11 Oct 2018 14:18:50 -0400 (EDT)
Received: from new-host-5.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id B29B8300266 for <ccg@ietf.org>; Thu, 11 Oct 2018 14:18:50 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <95B4908A-BFEB-44A5-81C4-3E39B39CFE42@vigilsec.com>
Date: Thu, 11 Oct 2018 14:18:51 -0400
To: ccg@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccg/jgglW-vUg4W_EOaDrxU3xxsIk4s>
Subject: [CCG] Upcoming Changes to the IETF Trust
X-BeenThere: ccg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IANA IPR Community Coordination Group <ccg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccg>, <mailto:ccg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccg/>
List-Post: <mailto:ccg@ietf.org>
List-Help: <mailto:ccg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccg>, <mailto:ccg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 18:18:56 -0000

Dear CCG:

The IETF is making some changes to its administrative structure.  The
biggest change is the replacement of the IAOC with an LLC.  This
indirectly has an impact on the IETF Trust.  In the past, the members
of the IAOC also served at the trustees of the IETF Trust.  Since the
IAOC is going away, the selection mechanism for the trustees is being
replaced.  Going forward:

   In this newly revised IETF Trust structure, there will be five
   Trustees.  Three shall be appointed by the IETF Nominating Committee
   (NomCom) and confirmed by the Internet Engineering Steering Group
   (IESG), one shall be appointed by the IESG, and one shall be
   appointed by the Internet Society (ISOC) Board of Trustees.  The
   appointments by the IESG and ISOC Board of Trustees do not require
   confirmation.

You can find details of the changes to the IETF Trust here:
https://datatracker.ietf.org/doc/draft-ietf-iasa2-trust-update/

You can find an informational document about the rationale here:
https://datatracker.ietf.org/doc/draft-ietf-iasa2-trust-rationale/

Finally, you can find the DRAFT changes to the Trust Agreement here:
https://github.com/bradbiddle/legal-and-finance/blob/master/IETF%20Trust%20Agreement%20REDLINE%2020-FEB-14%20v%2010-OCT-18.pdf

Since the CCG exists to provide advice to the IETF Trust regarding
the IANA-related IPR, it is appropriate to highlight the changes that
are in the works and give you an opportunity to comment on them.  These
changes will be finalized soon, so please offer any comment that you
might have by the end of next week.

Thanks,
 Russ