Last Call for Comments: Proposed work-around to the Pre-5378 Problem
Ed Juskevicius <edj.etc@gmail.com> Fri, 06 February 2009 05:28 UTC
Return-Path: <edj.etc@gmail.com>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0E373A6A03; Thu, 5 Feb 2009 21:28:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-5CtCD2jNYb; Thu, 5 Feb 2009 21:28:21 -0800 (PST)
Received: from mail-fx0-f20.google.com (mail-fx0-f20.google.com [209.85.220.20]) by core3.amsl.com (Postfix) with ESMTP id DEF233A6A49; Thu, 5 Feb 2009 21:28:10 -0800 (PST)
Received: by fxm13 with SMTP id 13so856074fxm.13 for <multiple recipients>; Thu, 05 Feb 2009 21:28:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=Enl4lx3RSa0Vu/VSYT6yoOzE47g493WQSIeGsZYEXlg=; b=uD5IZ4vdyPVV82YhDCdYIWqJaeeYyibmY5mE7xZIK5b6sk5Q79c9sRgebq2NrI+wd4 68uBTcYfXNUl6fmhTCguaRZeSGHToi+M+ESTK3LWHuENMV2MSoJJ1alHIXndNsDA6M53 oiYet5TtbpKu/cJDO55J6/r0cHQ4WTCYcWOdw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=lkd0sg/SrF2VehK2N4bN5vCceRbaTDfPeNKETYjwUHX244c3kzXFED9r/cKXySlPmB 9JFSw68yieglRCQksCPt765Hdi2fggu3pDCmglgGzBF29Xn+EHByvuRnPjqa6taOymAL XW9ik3WmSeB4yNbrUak8YjW9VIa5eVFKQTpPk=
MIME-Version: 1.0
Received: by 10.181.36.19 with SMTP id o19mr446530bkj.135.1233898091145; Thu, 05 Feb 2009 21:28:11 -0800 (PST)
Date: Fri, 06 Feb 2009 00:28:11 -0500
Message-ID: <9e8bc9820902052128i1fe6ba93ved493e7ac2ac5e5d@mail.gmail.com>
Subject: Last Call for Comments: Proposed work-around to the Pre-5378 Problem
From: Ed Juskevicius <edj.etc@gmail.com>
To: ietf@ietf.org, ietf-announce@ietf.org, wgchairs@ietf.org, iab@iab.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: multipart/alternative; boundary="001636c5bfb5696bbd04623949a3"
X-Mailman-Approved-At: Fri, 06 Feb 2009 10:32:51 -0800
Cc: Trustees <trustees@ietf.org>, "Contreras, Jorge" <Jorge.Contreras@wilmerhale.com>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 05:28:23 -0000
The IETF Trustees met via telechat on February 5th to decide on some proposed revisions to the "Legal Provisions Relating to IETF Documents" policy, based on comments received from the community in the last two weeks. Please recall this work is being done to provide a work-around for authors having the 'pre-5378 problem'. The telechat was productive. The Trustees reached consensus to do the following: 1) Clarify the copyright text at the beginning of the BSD license in Section 4.1 to read as follows: Copyright (c) <insert year> IETF Trust and the persons identified as its authors. All rights reserved. 2) Replace the word "and" by the word "or" in one place so that the last sentence of Section 6.c.iii becomes: Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. 3) Fix some nits with respect to the inappropriate use of square brackets '[' and ']' in two places. The IETF Trust website has been updated with a new version of the draft "Legal Provisions Relating to IETF Documents" including the changes described in this message. Please look for the documents dated 2009-02-05 at: http://trustee.ietf.org/policyandprocedures.html . If you have any final comments on this, please post them before the end of February 7th. This is the last call for comments. Regards, Ed Juskevicius, on behalf of the IETF Trustees edj.etc@gmail.com
- Last Call for Comments: Proposed work-around to t… Ed Juskevicius
- Re: Last Call for Comments: Proposed work-around … Ed Juskevicius