Re: Consensus(2)? IPR rights and all that
Looks good to me Brian Harald Tveit Alvestrand wrote: After a brief trip to the lawyer, and considering current discussion... a new suggestion: Replace principle 6 with the following: 6. The IETF, through the IASA, shall have a perpetual right to use, display, distribute, reproduce, modify and create derivatives of all data created in support of IETF activities. (Jorge liked perpetual better than irrevocable permanent - the stuff after to is a well known legal incantation). And in section 3.1 IAD Responsibilities, add after paragraph 4 (The IAD negotiates service contracts): The IAD is responsible for ensuring that all contracts give the IASA and the IETF the rights in data that is needed to satisfy the principle of data access. This is needed to make sure the IETF has access to the data it needs at all times, and that the IASA can change contractors when needed without disrupting IETF work. Whenever reasonable, if software is developed under an IASA contract it should should remain usable by the IETF beyond the terms of the contract. Some ways of achieving this are by IASA ownership or an open source license; an open source license is preferrable. The IAD will decide how the interest of the IETF is best served when making such contracts. (This is giving the IAD a little more room to maneuver, while still stating a clear preference.) Works? Harald ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
Re: Consensus(2)? IPR rights and all that
Harald == Harald Tveit Alvestrand [EMAIL PROTECTED] writes: Harald6. The IETF, through the IASA, shall have a perpetual Harald right to use, display, distribute, reproduce, modify and Harald create derivatives of all data created in support of IETF Harald activities. Harald (Jorge liked perpetual better than irrevocable Harald permanent - the stuff after to is a well known legal Harald incantation). This works for me provided that the legalese gives us the right to sublicense these rights to others. --Sam ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
Re: Consensus(2)? IPR rights and all that
--On tirsdag, desember 07, 2004 04:49:36 -0500 Sam Hartman [EMAIL PROTECTED] wrote: Harald == Harald Tveit Alvestrand [EMAIL PROTECTED] writes: Harald6. The IETF, through the IASA, shall have a perpetual Harald right to use, display, distribute, reproduce, modify and Harald create derivatives of all data created in support of IETF Harald activities. Harald (Jorge liked perpetual better than irrevocable Harald permanent - the stuff after to is a well known legal Harald incantation). This works for me provided that the legalese gives us the right to sublicense these rights to others. That's more than we currently ask people to assign to the IETF when making submissions to the IETF (RFC 3667) - there, we ask only for permission to use it within the IETF process (which may mean some sublicensing, and may not). Not sure what we should write here - I wouldn't want to write something here that would require reopening RFC 3667 for consistency. Harald ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
Re: Consensus(2)? IPR rights and all that
Harald == Harald Tveit Alvestrand [EMAIL PROTECTED] writes: Harald --On tirsdag, desember 07, 2004 04:49:36 -0500 Sam Hartman Harald [EMAIL PROTECTED] wrote: Harald == Harald Tveit Alvestrand [EMAIL PROTECTED] writes: Harald 6. The IETF, through the IASA, shall have a perpetual Harald right to use, display, distribute, reproduce, modify and Harald create derivatives of all data created in support of IETF Harald activities. Harald (Jorge liked perpetual better than irrevocable Harald permanent - the stuff after to is a well known legal Harald incantation). This works for me provided that the legalese gives us the right to sublicense these rights to others. Harald That's more than we currently ask people to assign to the Harald IETF when making submissions to the IETF (RFC 3667) - Harald there, we ask only for permission to use it within the Harald IETF process (which may mean some sublicensing, and may Harald not). Not sure what we should write here - I wouldn't want Harald to write something here that would require reopening RFC Harald 3667 for consistency. well, I do happen to think 3667 is broken, but agree with you that we do not want to open that can of worms at this time. However if we change contractors, we need to have the necessary rights to give the new contractor the rights to use our data. I believe that is an absolute requirement. --Sam ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
Re: Consensus(2)? IPR rights and all that
on 2004-12-06 10:36 pm Harald Tveit Alvestrand said the following: After a brief trip to the lawyer, and considering current discussion... a new suggestion: Replace principle 6 with the following: 6. The IETF, through the IASA, shall have a perpetual right to use, display, distribute, reproduce, modify and create derivatives of all data created in support of IETF activities. (Jorge liked perpetual better than irrevocable permanent - the stuff after to is a well known legal incantation). And in section 3.1 IAD Responsibilities, add after paragraph 4 (The IAD negotiates service contracts): The IAD is responsible for ensuring that all contracts give the IASA and the IETF the rights in data that is needed to satisfy the principle of data access. This is needed to make sure the IETF has access to the data it needs at all times, and that the IASA can change contractors when needed without disrupting IETF work. Whenever reasonable, if software is developed under an IASA contract it should should remain usable by the IETF beyond the terms of the contract. Some ways of achieving this are by IASA ownership or an open source license; an open source license is preferrable. The IAD will decide how the interest of the IETF is best served when making such contracts. (This is giving the IAD a little more room to maneuver, while still stating a clear preference.) Works? Works for me. Henrik ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
RE: Consensus(2)? IPR rights and all that
In line -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Harald Tveit Alvestrand Sent: Monday, December 06, 2004 16:36 To: [EMAIL PROTECTED] Subject: Consensus(2)? IPR rights and all that After a brief trip to the lawyer, and considering current discussion... a new suggestion: Replace principle 6 with the following: 6. The IETF, through the IASA, shall have a perpetual right to use, display, distribute, reproduce, modify and create derivatives of all data created in support of IETF activities. So does the above include the copy-right on RFCs? Or is it covered elsewhere? Anyway, I have put above text in my working copy of the doc. (Jorge liked perpetual better than irrevocable permanent - the stuff after to is a well known legal incantation). And in section 3.1 IAD Responsibilities, add after paragraph 4 (The IAD negotiates service contracts): The IAD is responsible for ensuring that all contracts give the IASA and the IETF the rights in data that is needed to satisfy the principle of data access. This is needed to make sure the IETF has access to the data it needs at all times, and that the IASA can change contractors when needed without disrupting IETF work. Whenever reasonable, if software is developed under an IASA contract it should should remain usable by the IETF beyond the terms of the contract. Some ways of achieving this are by IASA ownership or an open source license; an open source license is preferrable. The IAD will decide how the interest of the IETF is best served when making such contracts. Done (This is giving the IAD a little more room to maneuver, while still stating a clear preference.) Works? Works for me Bert Harald ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
RE: Consensus(2)? IPR rights and all that
--On tirsdag, desember 07, 2004 02:20:38 +0100 Wijnen, Bert (Bert) [EMAIL PROTECTED] wrote: After a brief trip to the lawyer, and considering current discussion... a new suggestion: Replace principle 6 with the following: 6. The IETF, through the IASA, shall have a perpetual right to use, display, distribute, reproduce, modify and create derivatives of all data created in support of IETF activities. So does the above include the copy-right on RFCs? Or is it covered elsewhere? This is actually very similar to the rights that RFC 3667 states is given to the IETF on usage of IETF contributions. In that particular case, copyright is used as the mechanism to make sure we (the IETF) have those rights - so you could see RFC 3667 as an application of the principle. Harald ___ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
