Internet DRAFT - draft-josefsson-ipr-notices
draft-josefsson-ipr-notices
Network Working Group S. Josefsson
Internet-Draft SJD
Updates: 3978 (if approved) May 18, 2006
Expires: November 19, 2006
RFC 3978 Update Regarding Additional Copyright Notices
draft-josefsson-ipr-notices-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 19, 2006.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
RFC 3978 disallow additional copyright notices in IETF Documents, but
the running code within the IETF appear to be to ignore that rule and
publish documents with additional copyright notices. There are
arguments for permitting additional copyright notices in IETF
documents, and some are given in this document. This document update
the paragraph in RFC 3978 that discusses additional copyrights, to
relax the requirement.
Josefsson Expires November 19, 2006 [Page 1]
Internet-Draft Addition Copyright Notices May 2006
Table of Contents
1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Revised Section 5.4 of RFC 3978 . . . . . . . . . . . . . . . . 3
3. Process Consideration . . . . . . . . . . . . . . . . . . . . . 4
4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Normative References . . . . . . . . . . . . . . . . . . . 4
5.2. Informative References . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
Intellectual Property and Copyright Statements . . . . . . . . . . 6
Josefsson Expires November 19, 2006 [Page 2]
Internet-Draft Addition Copyright Notices May 2006
1. Background
RFC 3978 [1] contains the following in section 5.4:
Additional copyright notices are not permitted in IETF
Documents except in the case where such document is the
product of a joint development effort between the IETF
and another standards development organization or the
document is a republication of the work of another
standards organization. Such exceptions must be
approved on an individual basis by the IAB.
Several RFCs have recently been published with additional copyright
notices in them, beginning with RFC 4000 and forwards, the documenst
are RFC 4122 [2], RFC 4226 [3], RFC 4287 [4], and RFC 4501 [5].
RFC 4122 contains source code with three copyright notices and
related copying conditions. RFC 4226 contains source code with one
copyright notice and related copying conditions. In RFC 4287, the
copyright notice is inside an example for the XML data format
specified, and supposedly only cover that particular example. RFC
4501 contains a copyright notice and copying conditions on the text
in the document.
We believe the examples given here break the rule for good reasons,
and that the rule be changed in light of the "running code" practice
and our argumentation.
A general reason why permitting additional copyright notices is that
it enables IETF Documents to include source code that are licensed
under various free licenses that typically require the copyright
notice to be preserved. If the copyright notice is removed, the
license is violated, and the source code cannot be included in an
IETF Document.
Thus, we argue that the rule should be changed to permit additional
copyright notices.
2. Revised Section 5.4 of RFC 3978
Replace the last paragraph in section 5.4 (reproduced in the previous
section) with the following:
Additional copyright notices are permitted in IETF
Documents, to denote the owner of copyrighted material
Josefsson Expires November 19, 2006 [Page 3]
Internet-Draft Addition Copyright Notices May 2006
within the document.
3. Process Consideration
This document intentionally do not use nor update the text for
section 5.4 in [6], to permit this document to move forward without
waiting for [6].
4. Acknowledgments
TBA
5. References
5.1. Normative References
[1] Bradner, S., "IETF Rights in Contributions", BCP 78, RFC 3978,
March 2005.
5.2. Informative References
[2] Leach, P., Mealling, M., and R. Salz, "A Universally Unique
IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
[3] M'Raihi, D., Bellare, M., Hoornaert, F., Naccache, D., and O.
Ranen, "HOTP: An HMAC-Based One-Time Password Algorithm",
RFC 4226, December 2005.
[4] Nottingham, M. and R. Sayre, "The Atom Syndication Format",
RFC 4287, December 2005.
[5] Josefsson, S., "Domain Name System Uniform Resource
Identifiers", RFC 4501, May 2006.
[6] Bradner, S., "RFC 3978 Update", draft-ietf-ipr-rules-update-01
(work in progress), October 2005.
Josefsson Expires November 19, 2006 [Page 4]
Internet-Draft Addition Copyright Notices May 2006
Author's Address
Simon Josefsson
SJD
Email: simon@josefsson.org
Josefsson Expires November 19, 2006 [Page 5]
Internet-Draft Addition Copyright Notices May 2006
Intellectual Property Statement
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@ietf.org.
Disclaimer of Validity
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.
Copyright Statement
Copyright (C) The Internet Society (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.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Josefsson Expires November 19, 2006 [Page 6]
