[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -Incoming issues in need of resolution



Harald
----- Original Message ----- From: "Harald Tveit Alvestrand" <harald at alvestrand.no>
To: "Simon Josefsson" <simon at josefsson.org>
Cc: <ipr-wg at ietf.org>
Sent: Wednesday, October 03, 2007 6:54 AM
Subject: Re: -Incoming issues in need of resolution





--On 3. oktober 2007 12:36 +0200 Simon Josefsson <simon at josefsson.org> wrote:

Harald Alvestrand <harald at alvestrand.no> writes:

1) Insert a "read-only" license into -incoming, granting essentially the
same rights as is granted to any other reader, but linking them to the
submission agreement rather than to an IETF Trust grant decision:

That seems to be an OK approach. I support that it should be very clear for IETF contributors that they

Or those people they represent...

retain the copyright of their
submission.

There is another PROBLEM with the current submission model. That is that if someone writing is a sponsored writer, they MUST also list the Legal Counsel's CONTACT INFO for the SPONSOR so that any and all relying parties are informed of who they must contact ass part of their formal diligence. Otherwise, the IETF's Procexss is not USER FRIENDLY.


The idea is that ANYONE relying on these IP's should be able to get a handle on what the Sponsor's Lawyers are doing in relation to the IP...

This is also especially important to put in place when there is no TAKEDOWN Process or Policy for the IETF.

Todd Glassey

 To make that as clear as possible, making that explicit in
-incoming seems like a good idea.

Although the devil is iFrom ipr-wg-bounces at ietf.org Wed Oct 03 10:33:10 2007
Return-path: <ipr-wg-bounces at ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Id5Gx-0005OG-3U; Wed, 03 Oct 2007 10:32:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Id5Gu-0005LG-Ho
	for ipr-wg at ietf.org; Wed, 03 Oct 2007 10:32:20 -0400
Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Id5Gk-0007Av-CZ
	for ipr-wg at ietf.org; Wed, 03 Oct 2007 10:32:16 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=FJOdQ2ZLsR0A+h/Xe6iQgQ2YiRWw9/gAEaWSIqZPLpjeuYVkpYJ/UuOmQvQbhiiZ;
	h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [24.23.176.93] (helo=tsg1)
	by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1Id5GO-0000av-J7; Wed, 03 Oct 2007 10:31:48 -0400
Message-ID: <001c01c805ca$2b46c4d0$6401a8c0 at tsg1>
From: "TS Glassey" <tglassey at earthlink.net>
To: "Harald Tveit Alvestrand" <harald at alvestrand.no>,
	"Simon Josefsson" <simon at josefsson.org>
References: <47033B10.1020105 at alvestrand.no><87ve9olc2q.fsf at mocca.josefsson.org>
	<114865D5833638F3F5797A3F at [10.10.2.86]>
Date: Wed, 3 Oct 2007 07:31:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79be91c31438706bbc0b7bd89df5ba4bbc350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipr-wg at ietf.org
Subject: Re: -Incoming issues in need of resolution
X-BeenThere: ipr-wg at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>,
	<mailto:ipr-wg-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg at ietf.org>
List-Help: <mailto:ipr-wg-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>,
	<mailto:ipr-wg-request at ietf.org?subject=subscribe>
Errors-To: ipr-wg-bounces at ietf.org

Harald
----- Original Message ----- From: "Harald Tveit Alvestrand" <harald at alvestrand.no>
To: "Simon Josefsson" <simon at josefsson.org>
Cc: <ipr-wg at ietf.org>
Sent: Wednesday, October 03, 2007 6:54 AM
Subject: Re: -Incoming issues in need of resolution





--On 3. oktober 2007 12:36 +0200 Simon Josefsson <simon at josefsson.org> wrote:

Harald Alvestrand <harald at alvestrand.no> writes:

1) Insert a "read-only" license into -incoming, granting essentially the
same rights as is granted to any other reader, but linking them to the
submission agreement rather than to an IETF Trust grant decision:

That seems to be an OK approach. I support that it should be very clear for IETF contributors that they

Or those people they represent...

retain the copyright of their
submission.

There is another PROBLEM with the current submission model. That is that if someone writing is a sponsored writer, they MUST also list the Legal Counsel's CONTACT INFO for the SPONSOR so that any and all relying parties are informed of who they must contact ass part of their formal diligence. Otherwise, the IETF's Procexss is not USER FRIENDLY.


The idea is that ANYONE relying on these IP's should be able to get a handle on what the Sponsor's Lawyers are doing in relation to the IP...

This is also especially important to put in place when there is no TAKEDOWN Process or Policy for the IETF.

Todd Glassey

 To make that as clear as possible, making that explicit in
-incoming seems like a good idea.

Although the devil is in the details, specifically:


5.10. Contributors retention of rights
.br
Notwithstanding any terms in this document to the contrary, in addition
to any rights under copyright retained by Contributor and in addition to
any rights generally granted by the TETF trust, Contributor retains, and
grants to each Co-Contributor to an RFC in which such Contributor's
Contribution, or a derivative work thereof may appear, the right:

Ouch! This goes way beyond "author retains their rights", it grants co-authors some rights to other co-authors' contributions.

More importantly, the text does not explain that authors retains the
copyright in their contribution.  That is the most important thing to
describe in -incoming.

Just before anyone else goes off on this tangent: This is presently stated in -incoming, section 3.1 of the -01 version. This paragraph (note the section number) comes in *addition* to that, granting the parties submitting material some special right to what is produced (the RFC) based on their material.


The rights granted in this proposed text are, BTW, identical to those that the IETF grants to all readers in -outgoing; the difference is that since these form part of the rules under which the submitters licensed their contribution, it would be impossible to restrict those rights at a later stage. Not that I think there's any chance of such a restriction being imposed.

                 Harald



_______________________________________________
Ipr-wg mailing list
Ipr-wg at ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg


_______________________________________________
Ipr-wg mailing list
Ipr-wg at ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg