draft-ietf-ipr-template-00.txt   draft-ietf-ipr-template-01.txt 
IPR WG IPR WG
Internet Draft V. See (editor) Internet Draft V. See (editor)
Document: draft-ietf-ipr-template-00.txt Microsoft Document: draft-ietf-ipr-template-01.txt Microsoft
Expires: November 1, 2003 May 1, 2003 Expires: November 22, 2003 May 22, 2003
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 This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [i]. <Editorial comment - all provisions of Section 10 of RFC2026 [i]. <Editorial comment -
insert updated boilerplate in conformance with Bradner submission- insert updated boilerplate in conformance with Bradner submission-
rights document.> rights document.>
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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.
Abstract Abstract
This document describes a template for IETF patent disclosures and This document describes a template for IETF patent disclosures and
licensing declarations. Such a template may be used to inform the licensing declarations. Such a template may be used to inform the
IETF of patent information for all IETF documents, and licensing IETF of patent information regarding all types of IETF documents, and
information regarding IETF standards-track documents. The optional licensing information regarding IETF standards-track documents. The
use of this template is meant to simplify the process of such optional use of this template is meant to simplify the process of
disclosures and to assist disclosers in providing the necessary such disclosures and licensing declarations and to assist disclosers
information to meet the obligations documented in <insert pointer to in providing the necessary information to meet the obligations
Bradner technology-rights RFC here>. documented in <insert pointer to Bradner technology-rights RFC here>.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [ii].
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.......................5
Security Considerations...........................................5 Security Considerations...........................................6
References........................................................6 References........................................................7
Acknowledgments...................................................6 Acknowledgments...................................................7
Authors' Addresses................................................6 Authors' Addresses................................................7
Full Copyright statement..........................................7 Full Copyright statement..........................................8
1. Introduction 1. Introduction
RFC XXXX [iii] <RFC Editor - please substitute Bradner technology- RFC XXXX [ii] <RFC Editor - please substitute Bradner technology-
rights RFC number here> documents the current IETF policies and rights RFC number here> documents the current IETF policies and
obligations with respect to disclosure of patents and patent obligations with respect to disclosure of patents and patent
applications containing patent claims that a patent holder believes applications. It also documents the information requested in
would be necessary to implement the technology required in an licensing declarations for IETF Proposed Standards, Draft Standards,
Internet-Draft or RFC. It also documents the information requested in and Standards. In the interest of making these patent disclosure and
licensing declarations for IETF Standards, Proposed Standards, and licensing declaration processes simpler, this document proposes a
Draft Standards. In the interest of making these disclosure processes patent disclosure and licensing declaration template that may be
simpler for patent holders, this document proposes a patent optionally used as one method for IETF participants and patent
disclosure and licensing declaration template that may be optionally holders to comply with patent disclosure requirements and licensing
used as one method for patent holders to fulfill their obligations declaration provisions under RFC XXXX. For the latest information on
under RFC XXXX. For the latest information on how to submit a patent how to submit a patent disclosure or licensing declaration, please
disclosure or licensing declaration, please see <insert URL for see <insert URL for submission information here - same as in
submission information here - same as in technology-rights (RFC technology-rights (RFC XXXX)>.
XXXX)>.
2. The Patent Disclosure and Licensing Declaration Template 2. The Patent Disclosure and Licensing Declaration Template
<START OF TEMPLATE> <START OF TEMPLATE>
This document is an IETF Patent Disclosure and Licensing Declaration This document is an IETF Patent Disclosure and Licensing Declaration
Template and is submitted to inform the IETF of patent information Template and is submitted to inform the IETF of a) patent information
for all IETF documents, and licensing information regarding IETF regarding the IETF document listed in Section IV, and b) licensing
Standards Track documents. No actual license is implied by submission information in cases where such listed document is or becomes an IETF
of this document. Please complete and submit a separate template for standards track document or where the Patent Holder elects to provide
each IETF document. this licensing information for a non-standards track document. No
actual license is implied by submission of this template. Please
complete and submit a separate template for each IETF document.
I. Patent Holder/Organization ("Patent Holder") I. Patent Holder/Organization ("Patent Holder")
Legal Name: Legal Name:
II. Patent HolderĘs Contact for License Application II. Patent Holder's Contact for License Application
Name:
Department:
Address:
Telephone:
Fax:
Email:
III. Contact Information for the IETF Participant Whose Personal
Belief Triggered the Disclosure in this Template (Optional):
Name: Name:
Department: Department:
Address: Address:
Telephone: Telephone:
Fax: Fax:
Email: Email:
III. IETF Document IV. IETF Document or Working Group Contribution to Which Patent
Disclosure Relates
Title: Title:
RFC Number or I-D Tag: RFC Number or I-D Tag:
Other Designations: Other Designations:
IV. 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 XXXX
[insert reference to Bradner's technology-rights document.] [insert reference to Bradner's technology-rights document.]
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
numbers: number(s):
Date(s) granted or applied for: Date(s) granted or applied for:
B. Does your disclosure relate to an unpublished pending patent B. Does your disclosure relate to an unpublished pending patent
application? application?
Select one: Yes ______ No ______ Select one: Yes ______ No ______
C. Please check here to acknowledge that, if requested by an IETF C. The discloser of the above patent information acknowledges that
working group or the IESG, the Patent Holder will file a new copy of the discloser will file a new copy of this template to provide an
this template to provide an update (if any) in the status of the update (if any) in the status of a disclosed patent application that
disclosed patent application or patent, such as whether the patent has been published or granted. The discloser should also withdraw its
application or patent has been published, granted, abandoned, or is disclosure of a patent application that is abandoned.______
no longer applicable to the IETF Document. ______
D. If an Internet-Draft or RFC includes multiple parts and it is not D. If an Internet-Draft or RFC includes multiple parts and it is not
reasonably apparent which part of such Internet-Draft or RFC is reasonably apparent which part of such Internet-Draft or RFC is
alleged to be covered by the information disclosed in IV(A) or IV(B), alleged to be covered by the information disclosed in IV(A) or IV(B),
the discloser should identify here the sections of the Internet-Draft the discloser should identify here the sections of the Internet-Draft
or RFC that are alleged to be so covered. or RFC that are alleged to be so covered.
V. Licensing Declaration for IETF Standards, Proposed Standards, or VI. Licensing Declaration for IETF Proposed Standards, Draft
Draft Standards: Standards, or Standards (or for non-standards-track IETF documents at
the election of the Patent Holder):
If the IETF Document referenced in III above is or becomes an IETF If the IETF Document referenced in Section IV above is or becomes an
Standards Track document, the Patent Holder states that its position IETF Standards Track document (or if the Patent Holder elects to make
with respect to licensing any patent claims contained in the a licensing declaration with respect to a non-Standards Track
patent(s) or patent application(s) disclosed above that the Patent document), the Patent Holder states that its position with respect to
Holder believes would be necessary to implement the technology licensing any patent claims contained in the patent(s) or patent
required by the IETF Standard, Proposed Standard, or Draft Standard application(s) disclosed above that would be necessary to implement
("Patent Claims") is as follows (select one option only): the technology required by the IETF Proposed Standard, Draft
Standard, or Standard (or other IETF document)("Patent Claims") is as
follows (select one option only):
___ No License Required for Implementers ___ No License Required for Implementers
___ Royalty-Free, Reasonable and Non-Discriminatory License to All ___ Royalty-Free, Reasonable and Non-Discriminatory License to All
Implementers Implementers
___ Reasonable and Non-Discriminatory License to All Implementers ___ Reasonable and Non-Discriminatory License to All Implementers
with Possible Royalty/Fee with Possible Royalty/Fee
___ Licensing Declaration to be Provided Later (implies a ___ Licensing Declaration to be Provided Later (implies a
willingness to license in some form to all implementers; willingness to license in some form to all implementers;
otherwise, "Unwilling to License to All Implementers" must be otherwise, "Unwilling to License to All Implementers" must be
selected) selected)
___ Unwilling to License to All Implementers ___ Unwilling to License to All Implementers
VI. Other Notes: NOTE: The individual submitting this template represents and warrants
that he or she is authorized by the Patent Holder to agree to the
above-selected licensing declaration.
VII. Contact Information of Submitter of this Form (if different from
IETF Participant in Section IV above)
Name:
Title:
Department:
Address:
Telephone:
Fax:
Email:
VIII. Other Notes:
<END OF TEMPLATE> <END OF TEMPLATE>
3. Commentary on Terms used in the Template 3. Commentary on Terms used in the Template
Section VI in the template, "Other Notes," may be used for any The "Other Designations" field in Section IV "IETF Document" may be
additional information a discloser wishes to provide. used to identify relevant IETF working group materials (oral or
written) other than an Internet-Draft or RFC to which a disclosure is
related.
Section III requests contact information for the Patent HolderĘs IETF
Participant whose personal belief that necessary patent claims were
implicated by an IETF document or discussion caused this template to
be filed. This is an optional section. However, if Section III is not
completed, then Section VII must be completed. Even if Section III is
completed, Section VII must still be completed if the submitter of
this template is different from the IETF participant identified in
Section III.
Section VIII in the template, "Other Notes," may be used for any
additional information a discloser or Patent Holder wishes to
provide.
Here is an explanation of the licensing declaration options in Here is an explanation of the licensing declaration options in
Section V of the template: Section VI of the template:
a) No License Required for Implementers: The Patent Holder does not a) No License Required for Implementers: The Patent Holder does not
require parties to acquire any license to its Patent Claims in order require parties to acquire any license to its Patent Claims in order
to implement the IETF Standard, Proposed Standard, or Draft Standard. to implement the IETF Proposed Standard, Draft Standard, or Standard.
b) Royalty-Free, Reasonable and Non-Discriminatory License to All b) Royalty-Free, Reasonable and Non-Discriminatory License to All
Implementers: The Patent Holder will, upon request, grant a license Implementers: The Patent Holder will, upon request, grant a license
to its Patent Claims to all implementers of the IETF Standard, to its Patent Claims to all implementers of the IETF Proposed
Proposed Standard, or Draft Standard on a royalty-free basis (i.e., Standard, Draft Standard, or Standard on a royalty-free basis (i.e.,
no royalty or other fee) and under reasonable and non-discriminatory no royalty or other fee) and under reasonable and non-discriminatory
terms. terms.
c) Reasonable and Non-Discriminatory License to All Implementers with c) Reasonable and Non-Discriminatory License to All Implementers with
Possible Royalty/Fee: The Patent Holder will, upon request, grant a Possible Royalty/Fee: The Patent Holder will, upon request, grant a
license to its Patent Claims to all implementers of the IETF license to its Patent Claims to all implementers of the IETF Proposed
Standard, Proposed Standard, or Draft Standard under reasonable and Standard, Draft Standard, or Standard under reasonable and non-
non-discriminatory terms (which may include a royalty/fee). discriminatory terms (which may include a royalty/fee).
d) Licensing Declaration to be Provided Later (implies a willingness d) Licensing Declaration to be Provided Later (implies a willingness
to license in some form to all implementers): The Patent Holder is to license in some form to all implementers): The Patent Holder is
willing to license its Patent Claims in some form to all implementers willing to license its Patent Claims in some form to all implementers
of the IETF Standard, Proposed Standard, or Draft Standard, but wants of the IETF Proposed Standard, Draft Standard, or Standard, but wants
to defer the declaration of its licensing type until a later point in to defer the declaration of its licensing type until a later point in
time (or when asked for this information by the IESG). This option time (or when asked for this information by the IESG). This option
may not be selected if the Patent Holder is unwilling to license its may not be selected if the Patent Holder is unwilling to license its
Patent Claims. Patent Claims.
e) Unwilling to License to All Implementers: The Patent Holder e) Unwilling to License to All Implementers: The Patent Holder
refuses to license its Patent Claims to all implementers of the IETF refuses to license its Patent Claims to all implementers of the IETF
Standard, Proposed Standard, or Draft Standard, except on an Proposed Standard, Draft Standard, or Standard, except on an
implementer-by-implementer basis, in its sole discretion. implementer-by-implementer basis, in its sole discretion.
Security Considerations Security Considerations
This document relates to IETF process, not any particular technology. This document relates to IETF process, not any particular technology.
There are security considerations when adopting any particular There are security considerations when adopting any particular
technology, regardless of whether patents and patent applications or technology, regardless of whether patents and patent applications or
licensing disclosures are implicated by such technology. A working licensing disclosures are implicated by such technology. A working
group should take those security considerations into account as one group should take those security considerations into account as one
part of evaluating the technology, but there are no security part of evaluating the technology, but there are no security
considerations per se with these IETF processes. considerations per se with these IETF processes.
References References
i Bradner, S., "The Internet Standards Process -- Revision 3", BCP i Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
ii Bradner, S., "Key words for use in RFCs to Indicate Requirement ii Bradner, S., "Intellectual Property Rights in IETF Technology",
Levels", BCP 14, RFC 2119, March 1997
iii Bradner, S., "Intellectual Property Rights in IETF Technology",
RFC XXXX, <month> 2003. RFC XXXX, <month> 2003.
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
skipping to change at page 7, line 27 skipping to change at page 8, line 27
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for rights developing Internet standards in which case the procedures for rights
in submissions defined in the Internet Standards process must be in submissions defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an THIS DOCUMENT AND THE INFORMATION CONTAINED HEREIN IS PROVIDED ON AN
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" BASIS AND THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
(IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. 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/