Dave -- very useful -- thanks!! > -----Original Message----- > From: Dave CROCKER [mailto:dhc2@xxxxxxxxxxxx] > Sent: Friday, December 19, 2008 3:56 PM > To: IETF Discussion > Cc: Contreras, Jorge > Subject: History of RFC copyright text > > > > Bob Braden wrote: > >> Indeed -- I don't see a copyright notice in RFC 1065. > This may be a > >> useful approach for old RFCs that lack a copyright notice. > Does anyone > >> know when the ISOC copyright notice was first applied to RFCs? > > > > Probably some time after 1989, when the ISOC took over > funding of the > > RFC Editor. I don't recall exactly, but it should not be > hard to find out. > > > This is probably worth summarizing, so I just did a scan of > the RFC archive: > > > > > 1) There is no copyright text in RFCs until: > > > > Network Working Group > M. Gahrns > > Request for Comments: 2221 > Microsoft > > Category: Standards Track > October 1997 > > > > > > IMAP4 Login Referrals > ... > > Copyright Notice > > > > Copyright (C) The Internet Society (1997). All Rights Reserved. > ... > > 10. Full Copyright Statement > > > > > > Copyright (C) The Internet Society (1997). All Rights Reserved. > > > > This document and translations of it may be copied and > furnished to > > others, and derivative works that comment on or > otherwise explain it > > or assist in its implmentation may be prepared, copied, published > > andand distributed, in whole or in part, without > restriction of any > > kind, provided that the above copyright notice and this > paragraph are > > included on all such copies and derivative works. However, this > > document itself may not be modified in any way, such as > by removing > > the copyright notice or references to the Internet > Society or other > > Internet organizations, except as needed for the purpose of > > developing Internet standards in which case the procedures for > > copyrights defined in the Internet Standards process must be > > followed, or as required to translate it into languages > other than > > English. > > > > The limited permissions granted above are perpetual and > will not be > > revoked by the Internet Society or its successors or assigns. > > > > This document and the information contained herein is > provided on an > > "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET > ENGINEERING > > TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, > INCLUDING > > BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION > > HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF > > MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." > > > > > > 2) In my view, the next change was the critical one, because > it altered the > ownership model, with authors being declared as having > ownership rights (where > my non-lawyers eyes read the earlier one as declaring ISOC as > owning the rights, > modulo the ones authors can't give away): > > > > Network Working Group > J. Cuellar > > Request for Comments: 3693 > Siemens AG > > Category: Informational > J. Morris > > Center for Democracy > & Technology > > > D. Mulligan > > Samuelson Law, Technology & Public > Policy Clinic > > > J. Peterson > > > NeuStar > > > J. Polk > > > Cisco > > > February 2004 > > > > > > Geopriv Requirements > ... > > > > Copyright Notice > > > > Copyright (C) The Internet Society (2004). All Rights Reserved. > ... > > 13. Full Copyright Statement > > > > > > Copyright (C) The Internet Society (2004). This > document is subject > > to the rights, licenses and restrictions contained in BCP 78 and > > except as set forth therein, the authors retain all their rights. > > > > This document and the information contained herein are > provided on an > > "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE > > REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET > SOCIETY AND THE > > INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, > EXPRESS OR > > IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT > THE USE OF > > THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR > ANY IMPLIED > > WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A > PARTICULAR PURPOSE. > > > > Intellectual Property > > > > The IETF takes no position regarding the validity or scope of any > > Intellectual Property Rights or other rights that might > be claimed > > to pertain to the implementation or use of the technology > > described in this document or the extent to which any license > > under such rights might or might not be available; nor does it > > represent that it has made any independent effort to identify any > > such rights. Information on the procedures with respect to > > rights in RFC documents can be found in BCP 78 and BCP 79. > > > > Copies of IPR disclosures made to the IETF Secretariat and any > > assurances of licenses to be made available, or the result of an > > attempt made to obtain a general license or permission > for the use > > of such proprietary rights by implementers or users of this > > specification can be obtained from the IETF on-line IPR > repository > > at http://www.ietf.org/ipr. > > > > The IETF invites any interested party to bring to its attention > > any copyrights, patents or patent applications, or other > > proprietary rights that may cover technology that may be required > > to implement this standard. Please address the > information to the > > IETF at ietf-ipr@xxxxxxxxx > > > > > > > 3) The next revision to this came with: > > > > Network Working Group > M. Munakata > > Request for Comments: 4715 > S. Schubert > > Category: Informational > T. Ohba > > > NTT > > > November 2006 > > > > > > > > The Integrated Services Digital Network (ISDN) > > > > > > Subaddress Encoding Type for tel URI > > > > > > Status of This Memo > > > > This memo provides information for the Internet > community. It does > > not specify an Internet standard of any kind. > Distribution of this > > memo is unlimited. > > > > Copyright Notice > > > > Copyright (C) The IETF Trust (2006). > ... > > Full Copyright Statement > > > > Copyright (C) The IETF Trust (2006). > > > > This document is subject to the rights, licenses and restrictions > > contained in BCP 78, and except as set forth therein, the authors > > retain all their rights. > > > > This document and the information contained herein are > provided on an > > "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION > HE/SHE REPRESENTS > > OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE > IETF TRUST, > > AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, > > EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY > WARRANTY THAT > > THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY > RIGHTS OR ANY > > IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR > > PURPOSE. > > -- > > Dave Crocker > Brandenburg InternetWorking > bbiw.net > _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf