Fwd: RFC 5378 and Draft Submissions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: RFC 5378 and Draft Submissions
Folks submitting Internet Drafts which incorporate material from
earlier IETF content should be aware of the below. You may also want
to take a look at http://www.ietf.org/mail-archive/web/ietf/current/msg54839.html
.
I would be interested in knowing if any rtgwg draft authors believe
they will be affected by this issue. Any discussion of this issue not
specifically related to rtgwg drafts should be taken to the main IETF
discussion list where you will find a lively discussion underway.
--John
Begin forwarded message:
From: "Eric Rescorla" <ekr at rtfm.com>
Date: January 15, 2009 12:03:42 AM GMT-05:00
To: "Working Group Chairs" <wgchairs at ietf.org>
Subject: Fwd: RFC 5378 and Draft Submissions
FYI
---------- Forwarded message ----------
From rtgwg-bounces at ietf.org Fri Jan 16 13:57:01 2009
Return-Path: <rtgwg-bounces at ietf.org>
X-Original-To: rtgwg-web-archive at optimus.ietf.org
Delivered-To: ietfarch-rtgwg-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 222063A6AFA;
Fri, 16 Jan 2009 13:57:01 -0800 (PST)
X-Original-To: rtgwg at core3.amsl.com
Delivered-To: rtgwg at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id E6C023A67DF
for <rtgwg at core3.amsl.com>; Fri, 16 Jan 2009 13:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.52
X-Spam-Level:
X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[AWL=0.079,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Uk55OjaBSRPy for <rtgwg at core3.amsl.com>;
Fri, 16 Jan 2009 13:56:59 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169])
by core3.amsl.com (Postfix) with ESMTP id 1677D3A6AF6
for <rtgwg at ietf.org>; Fri, 16 Jan 2009 13:56:59 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
exprod7ob108.postini.com ([64.18.6.12]) with SMTP
ID DSNKSXECmpKKvklySRzfyR4IkOe6LHUABGLN at postini.com;
Fri, 16 Jan 2009 13:56:44 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
Fri, 16 Jan 2009 13:54:16 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by
p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan
2009 13:54:16 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net
with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 16 Jan 2009 13:54:16 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Jan 2009 13:54:16 -0800
Received: from [172.16.13.200] ([172.16.13.200]) by magenta.juniper.net
(8.11.3/8.11.3) with ESMTP id n0GLsFM60019 for <rtgwg at ietf.org>;
Fri, 16 Jan 2009 13:54:15 -0800 (PST) (envelope-from jgs at juniper.net)
Message-ID: <C94E6447-8A5A-4D5C-A198-824F24AA5F4E at juniper.net>
From: "John G. Scudder" <jgs at juniper.net>
To: rtgwg at ietf.org
MIME-Version: 1.0 (Apple Message framework v930.3)
Subject: Fwd: RFC 5378 and Draft Submissions
Date: Fri, 16 Jan 2009 16:54:14 -0500
References: <d3aa5d00901142103k2d612508q770e37528c2169f1 at mail.gmail.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 16 Jan 2009 21:54:16.0613 (UTC)
FILETIME=[FA0DBD50:01C97824]
X-BeenThere: rtgwg at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>,
<mailto:rtgwg-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtgwg>
List-Post: <mailto:rtgwg at ietf.org>
List-Help: <mailto:rtgwg-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>,
<mailto:rtgwg-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rtgwg-bounces at ietf.org
Errors-To: rtgwg-bounces at ietf.org
Folks submitting Internet Drafts which incorporate material from
earlier IETF content should be aware of the below. You may also want
to take a look at http://www.ietf.org/mail-archive/web/ietf/current/msg54839.html
.
I would be interested in knowing if any rtgwg draft authors believe
they will be affected by this issue. Any discussion of this issue not
specifically related to rtgwg drafts should be taken to the main IETF
discussion list where you will find a lively discussion underway.
--John
Begin forwarded message:
From: "Eric Rescorla" <ekr at rtfm.com>
Date: January 15, 2009 12:03:42 AM GMT-05:00
To: "Working Group Chairs" <wgchairs at ietf.org>
Subject: Fwd: RFC 5378 and Draft Submissions
FYI
---------- Forwarded message ---- From: Eric Rescorla <ekr at rtfm.com>
Date: Wed, Jan 14, 2009 at 9:03 PM
Subject: RFC 5378 and Draft Submissions
To: tls at ietf.org
IETF Chair Russ Housley has asked WG chairs to apprise their WGs of
the following information.
If you've been following the IETF mailing list, you may be aware of
the ongoing discussion about the impact of RFC 5378 on revised draft
submissions. Briefly, RFC 5378 requires Contributors to grant a more
expansive set of rights than were granted by RFC 3978, and 4748. If
you are submitting a document which contains text contributed by
others prior to the publication of RFC 5378 you may need to obtain
additional rights from the
copyright holders of that text in order to contribute under the 5378
terms.
The IESG and the IETF Trustees are working to resolve those issues
(see
http://trustee.ietf.org/docs/Background-to-Draft-Update-to-IETF-Trust-Legal-Provisions.txt)
.
However,
at present I would advise care prior to submitting any draft
which contains material derived from an RFC, draft, or mailing
list message published prior to November 10, 2008.
Speaking personally, I have chosen not to submit new versions
of most of my drafts until matters are resolved.
Please take any general discussion of RFC 5378 to ietf at ietf.org
-Ekr
[As WG Chair]
_______________________________________________
rtgwg mailing list
rtgwg at ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg
------
From: Eric Rescorla <ekr at rtfm.com>
Date: Wed, Jan 14, 2009 at 9:03 PM
Subject: RFC 5378 and Draft Submissions
To: tls at ietf.org
IETF Chair Russ Housley has asked WG chairs to apprise their WGs of
the following information.
If you've been following the IETF mailing list, you may be aware of
the ongoing discussion about the impact of RFC 5378 on revised draft
submissions. Briefly, RFC 5378 requires Contributors to grant a more
expansive set of rights than were granted by RFC 3978, and 4748. If
you are submitting a document which contains text contributed by
others prior to the publication of RFC 5378 you may need to obtain
additional rights from the
copyright holders of that text in order to contribute under the 5378
terms.
The IESG and the IETF Trustees are working to resolve those issues
(see
http://trustee.ietf.org/docs/Background-to-Draft-Update-to-IETF-Trust-Legal-Provisions.txt)
.
However,
at present I would advise care prior to submitting any draft
which contains material derived from an RFC, draft, or mailing
list message published prior to November 10, 2008.
Speaking personally, I have chosen not to submit new versions
of most of my drafts until matters are resolved.
Please take any general discussion of RFC 5378 to ietf at ietf.org
-Ekr
[As WG Chair]
_______________________________________________
rtgwg mailing list
rtgwg at ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.
