Final Update - IETF Trust Consensus Call

Brian Carpenter <brc@zurich.ibm.com> Mon, 05 December 2005 12:55 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjFsF-0004No-SK; Mon, 05 Dec 2005 07:55:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjFsD-0004NX-Vt for ietf-announce@megatron.ietf.org; Mon, 05 Dec 2005 07:55:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12734 for <ietf-announce@ietf.org>; Mon, 5 Dec 2005 07:54:27 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjGDW-00081o-80 for ietf-announce@ietf.org; Mon, 05 Dec 2005 08:17:18 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1EjFsC-0000mI-VV for ietf-announce@ietf.org; Mon, 05 Dec 2005 07:55:16 -0500
Content-Type: text/plain
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: Brian Carpenter <brc@zurich.ibm.com>
Message-Id: <E1EjFsC-0000mI-VV@newodin.ietf.org>
Date: Mon, 05 Dec 2005 07:55:16 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Subject: Final Update - IETF Trust Consensus Call
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iaoc.ietf.org@newodin.ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

(posted for Lucy Lynch, IAOC Chair)

All -

The amended language for Section 9.5 (Licensing) of the IETF Trust was
posted to the IETF lists on December 1st and the IETF Trust FAQ has
been updated to reflect the new text (see below). We have also added
additional details on the handling of historical data. As we develop
procedures for the transfer of assets into the IETF Trust and an
inventory of items held by the IETF Trust we will publish them to the
IAOC web site (see: http://koi.uoregon.edu/~iaoc/)

Several people asked for additional time to review our final language,
and with that in mind, I would like to extend this Call one last
time to December 8th, 2005.

Please send comments to: ietf@ietf.org or iaoc.ietf.org

- Thanks

Lucy E. Lynch                           Academic User Services
Computing Center                        University of Oregon
llynch  @darkwing.uoregon.edu           (541) 346-1774

FAQ Updates:
-------------------------------------------------------------------------
18. How will the license provisions in Section 9.5 affect the contents
of Standards related documents like RFCs and Internet Drafts.

The IETF IPR rules in force when such documents were published still
apply and Section 9.5 has been updated to reflect community concerns
about the effect of licensing terms. The new text reads:

"9.5 Licenses.

The Trust (acting through the Trustees) shall have the right to grant
licenses for the use of the Trust Assets on such terms, subject to
Section 7.1, as the Trustees deem appropriate; provided, however, that
the Trust shall not grant any license that would be deemed a transfer
of ownership or abandonment of any Trust Assets under applicable law.
Specifically, any license granted by the Trust for the use of the
Trust Assets consisting of IPR other than rights in IETF
standards-related documents (such as RFCs, Internet Drafts and the
like) that have been acquired by the Trust through non-exclusive
licenses granted by their contributors pursuant to the IETF
community-approved procedures currently set forth in RFC 3978, and any
community-approved updates and revisions thereto, shall include
provisions stating that (a) the licensee agrees to grant and assign to
the Trust all right, title, and interest it may have or claim in any
derivative works of licensee that are based on or incorporate the IPR,
and (b) the licensee's use of the IPR and any goodwill associated
therewith shall inure to the benefit of the Trust."

19. Which of the assets listed in Schedule A will be transferred when
the IETF Trust is established? Will the Trustees publish an accounting
of these assets?

All of the Marks, Domain Names, and Current Data listed in Schedule A
will be transferred at closing. In addition, Historical Data that is
currently available from available from the servers currently operated
by or for the IETF Secretariat (i.e. data available on spinning disk)
will also be transferred at closing. The Trustees will inventory all
assets and provide a full accounting to the IETF community. Historical
data which is currently in-accessible will be subject to the
conditions outlined in sub-sections b-g. When and if additional data
becomes available, those assets will transfer to the IETF Trust and
will be added to the inventory.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce