Re: [tlp-interest] [Trustees] Question
Marshall Eubanks <tme@americafree.tv> Mon, 07 June 2010 17:44 UTC
Return-Path: <tme@americafree.tv>
X-Original-To: tlp-interest@core3.amsl.com
Delivered-To: tlp-interest@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 48AFD3A683F; Mon, 7 Jun 2010 10:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.749
X-Spam-Level:
X-Spam-Status: No, score=-99.749 tagged_above=-999 required=5 tests=[AWL=-1.550,
BAYES_50=0.001, J_CHICKENPOX_23=0.6, J_CHICKENPOX_34=0.6, J_CHICKENPOX_51=0.6,
USER_IN_WHITELIST=-100]
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 TuxLt-CJ57Vr;
Mon, 7 Jun 2010 10:44:49 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by
core3.amsl.com (Postfix) with ESMTP id D27B628CCA6;
Mon, 7 Jun 2010 10:07:09 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by
mail.americafree.tv (Postfix) with ESMTP id 868B5771C7D6;
Mon, 7 Jun 2010 13:07:10 -0400 (EDT)
Message-Id: <DCE6BC79-1690-4F74-B8DF-88E3E29A49EC@americafree.tv>
From: Marshall Eubanks <tme@americafree.tv>
To: RFC Editor <rfc-editor@rfc-editor.org>
In-Reply-To: <20100607021317.GA18253@rfc-editor.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 7 Jun 2010 13:07:10 -0400
References: <AANLkTik2Rvwnm4Wr1c9nLSPN1yBNdC6YQaFi1cInmwQ2@mail.gmail.com>
<20100607021317.GA18253@rfc-editor.org>
X-Mailer: Apple Mail (2.936)
Cc: trustees@ietf.org, victor nunes <victor.rebli@gmail.com>,
tlp-interest@ietf.org
Subject: Re: [tlp-interest] [Trustees] Question
X-BeenThere: tlp-interest@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of proposed revisions to the Trust Legal Provisions
<tlp-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>,
<mailto:tlp-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tlp-interest>
List-Post: <mailto:tlp-interest@ietf.org>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>,
<mailto:tlp-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 17:44:50 -0000
Dear Victor; On Jun 6, 2010, at 10:13 PM, RFC Editor wrote: > Hi Victor, > > We are forwarding your question to the tlp-interest@ietf.org mail > list, as requested at http://trustee.ietf.org/license-info/ (and CCing > the IETF Trust). We believe the Trust will be able to provide you > with guidance on this issue. > > Thank you. > > RFC Editor > > > On Sat, Jun 05, 2010 at 10:18:13PM -0300, victor nunes wrote: >> Hello, I write to express my sincere frustration about the material >> that >> provides the IETF regarding the possibility of copies of the RFC. I >> would >> like a definitive answer. I would recommend reading the relevant FAQ http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf and the Trust Legal Provisions (TLP) itself http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf as well as RFC 5377 / 5378 if these seem inadequate. >> >> What is the permission that allows the IETF to copy and distribute >> the RFC >> in part or in full? Note : I am not a lawyer and this is not legal advice, nor does it supersede or override anything in the TLP or RFC 5377 / 5378 ! Long standing IETF policy is encapsulated in the Note Well; any input is an "IETF Contribution," which requires giving some rights over to the IETF Trust (or, previously, to other organizations which have now conveyed their rights to the Trust). From the Note Well : Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Through the Note Well and the document submission process, the IETF Trust thus gains certain rights in IETF documents, and rights in older documents subject to older Note Wells have been transferred to it. While it may not be clear exactly what rights the Trust holds in any given older document, I have been informed by our Counsel that the Trust has the right to license RFCs for IETF use (as the rights to do this were demanded by 5378 and its predecessors). From the TLP : "License For Use Within the IETF Standards Process. The IETF Trust hereby grants to each participant in the IETF Standards Process, to the greatest extent that it is permitted to do so, a non-exclusive, royalty-free, worldwide right and license under all copyrights and rights of authors granted to the IETF Trust: i. to copy, publish, display and distribute IETF Contributions and IETF Documents, in whole or in part, as part of the IETF Standards Process, and ii. to translate IETF Contributions and IETF Documents, in whole or part, into languages other than English as part of the IETF Standards Process, and ..." What the policy of the IETF does not generally do is allow you to make derivative works outside of the IETF process. (In other words, you can put RFC XYZ or I-D ABC on your web site if you want, but you cannot make changes without either going to the Trust or going through the process.) This policy substantially predates both the Trust and RFCs 5377 / 5378. The other RFC streams use an even less restrictive license policy, and so you can copy alternate stream documents as well. See the TLP for more details. >> >> Hundreds of books that are explaining about the TCP / IP >> architecture and >> its various protocols outlined by the RFCs, IETF need to ask >> permission? If they simply copy the RFCs, they need not in my opinion and generally do not as a matter of fact. >> >> I could copy all RFCs to my computer? Sure. >> >> Anyway, that's it, I would greatly appreciate an answer. Hope this helps. The license situation may be unclear for some early documents, although it is reasonable to assume that there is the right to make copies. If you have concerns about specific documents please let us know. Regards Marshall >> >> Thanks, Victor >> -- >> ?Encarada do ponto de vista da juventude, a vida parece um futuro >> indefinidamente longo, ao passo que, na velhice, ela parece um >> passado >> deveras curto. Assim, a vida no seu in?cio se apresenta do mesmo modo >> que as coisas quando as olhamos atrav?s de um bin?culo usado ao >> contr?rio; >> mas, ao >> seu final, ela se parece com as coisas tal qual s?o vistas quando o >> bin?culo >> ? usado de modo normal. Um homem precisa ter envelhecido e vivido >> bastante para perceber como a vida ? curta?. >> >> (Poema de Arthur Schopenhauer) > _______________________________________________ > Trustees mailing list > Trustees@ietf.org > https://www.ietf.org/mailman/listinfo/trustees >
- Re: [tlp-interest] Question RFC Editor
- Re: [tlp-interest] [Trustees] Question Marshall Eubanks