draft-ietf-ipr-template-08.txt   draft-ietf-ipr-template-09.txt 
IPR WG IPR WG
Internet-Draft V. See (editor) Internet-Draft V. See (editor)
Document: draft-ietf-ipr-template-08.txt Microsoft Document: draft-ietf-ipr-template-09.txt Microsoft
Expires: August 13, 2004 February 2004 Expires: October 28, 2004 April 2004
A Template for IETF Patent Disclosures and Licensing Declarations A Template for IETF Patent Disclosures and Licensing Declarations
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
skipping to change at page 1, line 27 skipping to change at page 1, line 29
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 2, 2004
Copyright Notice
Copyright (C) The Internet Society 2004. All Rights Reserved.
Abstract Abstract
This document describes a proposal for one form of a template for This document describes a proposal for one form of a template for
IETF patent disclosures and licensing declarations. The optional use IETF patent disclosures and licensing declarations. The optional use
of this template is meant to simplify the process of such disclosures of this template is meant to simplify the process of such disclosures
and licensing declarations and to assist disclosers in providing the and licensing declarations and to assist disclosers in providing the
necessary information to meet the obligations documented in RFC XXXX. necessary information to meet the obligations documented in RFC 3668.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. The Patent Disclosure and Licensing Declaration Template.......2 2. The Patent Disclosure and Licensing Declaration Template.......2
3. Commentary on Terms Used in the Template.......................5 3. Commentary on Terms Used in the Template.......................6
Security Considerations...........................................7 Security Considerations...........................................7
Normative References..............................................7 Normative References..............................................7
Acknowledgments...................................................7 Acknowledgments...................................................8
Authors' Addresses................................................8 Authors' Addresses................................................8
Intellectual Property Statement...................................8 Intellectual Property Statement...................................8
Full Copyright statement..........................................9 Disclaimer of Validity............................................9
Copyright Statement...............................................9
1. Introduction 1. Introduction
RFC XXXX [i] documents the current IETF policies and obligations with RFC 3668 [i] documents the current IETF policies and obligations with
respect to disclosure of patents and patent applications. It also respect to disclosure of patents and patent applications. It also
documents the information requested in licensing declarations for documents the information requested in licensing declarations for
IETF specifications. In the interest of making these patent IETF specifications. In the interest of making these patent
disclosure and licensing declaration processes simpler, this document disclosure and licensing declaration processes simpler, this document
proposes a patent disclosure and licensing declaration template that proposes a patent disclosure and licensing declaration template that
may be optionally used as one method for IETF participants and patent may be optionally used as one method for IETF participants and patent
holders to comply with patent disclosure requirements and licensing holders to comply with patent disclosure requirements and licensing
declaration provisions under RFC XXXX. This proposal also may be declaration provisions under RFC 3668. This proposal also may be
optionally used as a model by the IETF Secretariat for Web-based optionally used as a model by the IETF Secretariat for Web-based
disclosure and licensing declaration tools; however, the intent of disclosure and licensing declaration tools; however, the intent of
this document is informational and is not meant to suggest that this this document is informational and is not meant to suggest that this
is the only method that could be used by IETF participants for is the only method that could be used by IETF participants for
disclosure of patents or for licensing declarations. For the latest disclosure of patents or for licensing declarations. For the latest
information on how to submit a patent disclosure or licensing information on how to submit a patent disclosure or licensing
declaration, please see http://www.ietf.org/ipr-instructions. declaration, please see http://www.ietf.org/ipr-instructions.
2. The Patent Disclosure and Licensing Declaration Template 2. The Patent Disclosure and Licensing Declaration Template
skipping to change at page 4, line 6 skipping to change at page 4, line 6
IV. IETF Document or Contribution to Which Patent Disclosure Relates IV. IETF Document or Contribution to Which Patent Disclosure Relates
Title: Title:
RFC Number or I-D Tag: RFC Number or I-D Tag:
Other Designations: Other Designations:
V. Disclosure of Patent Information (i.e., patents or patent V. Disclosure of Patent Information (i.e., patents or patent
applications required to be disclosed by Section 6 of RFC XXXX) applications required to be disclosed by Section 6 of RFC 3668)
A. For granted patents or published pending patent applications, A. For granted patents or published pending patent applications,
please provide the following information: please provide the following information:
Patent, Serial, Publication, Registration, or Application/File Patent, Serial, Publication, Registration, or Application/File
number(s): number(s):
Date(s) granted or applied for (YYYY-MM-DD): Date(s) granted or applied for (YYYY-MM-DD):
Country(ies): Country(ies):
skipping to change at page 7, line 42 skipping to change at page 7, line 45
There are security considerations when adopting any particular There are security considerations when adopting any particular
technology, regardless of whether patent or patent application technology, regardless of whether patent or patent application
disclosures or licensing declarations are implicated by such disclosures or licensing declarations are implicated by such
technology. A working group should take those security considerations technology. A working group should take those security considerations
into account as one part of evaluating the technology, but there are into account as one part of evaluating the technology, but there are
no security considerations per se with these IETF processes. no security considerations per se with these IETF processes.
Normative References Normative References
i Bradner, S., "Intellectual Property Rights in IETF Technology," i Bradner, S., "Intellectual Property Rights in IETF Technology,"
RFC XXXX, <month> 2003. RFC 3668, February 2004.
Acknowledgments Acknowledgments
The authors acknowledge the thoughtful contributions of Harald The authors acknowledge the thoughtful contributions of Harald
Alvestrand and Scott Bradner to this document. Alvestrand and Scott Bradner to this document.
Authors' Addresses Authors' Addresses
Valerie See Valerie See
Microsoft Corporation Microsoft Corporation
skipping to change at page 8, line 40 skipping to change at page 8, line 45
Email: alo@juniper.net Email: alo@juniper.net
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in IETF Documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementers or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. 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 The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr.org.
Full Copyright statement
Copyright (C) The Internet Society (2003). Except as set forth Disclaimer of Validity
below, authors retain all their rights.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 rights
in submissions 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 Copyright Statement
revoked by the Internet Society or its successors or assigns.
THIS DOCUMENT AND THE INFORMATION CONTAINED HEREIN IS PROVIDED ON AN Copyright (C) The Internet Society (2004). This document is subject
"AS IS" BASIS AND THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS to the rights, licenses and restrictions contained in BCP 78, and
(IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK except as set forth therein, the authors retain all their rights.
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.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/