draft-ietf-ipr-template-06.txt   draft-ietf-ipr-template-07.txt 
IPR WG IPR WG
Internet-Draft V. See (editor) Internet-Draft V. See (editor)
Document: draft-ietf-ipr-template-06.txt Microsoft Document: draft-ietf-ipr-template-07.txt Microsoft
Expires: February 11, 2004 August 2003 Expires: February 19, 2004 August 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. all provisions of Section 10 of RFC2026.
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
skipping to change at page 2, line 39 skipping to change at page 2, line 39
see http://www.ietf.org/ipr-instructions. see http://www.ietf.org/ipr-instructions.
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 a) patent information Template and is submitted to inform the IETF of a) patent information
regarding the IETF document or contribution listed in Section IV, and regarding the IETF document or contribution listed in Section IV, and
b) a Patent Holder's intention with respect to the licensing of its b) a Patent Holder's intention with respect to the licensing of its
necessary patent claims upon approval by the IESG for publication as necessary patent claims. No actual license is implied by submission
an RFC of the relevant IETF specification. No actual license is of this template. Please complete and submit a separate template for
implied by submission of this template. Please complete and submit a each IETF document or contribution to which the disclosed patent
separate template for each IETF document or contribution to which the information relates.
disclosed patent information relates.
I. Patent Holder/Applicant ("Patent Holder") I. Patent Holder/Applicant ("Patent Holder")
Legal Name: Legal Name:
II. Patent Holder's Contact for License Application II. Patent Holder's Contact for License Application
Name: Name:
Title: Title:
skipping to change at page 4, line 8 skipping to change at page 4, line 8
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 XXXX)
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: Date(s) granted or applied for (dd/mm/yy):
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. If an Internet-Draft or RFC includes multiple parts and it is not C. 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 patent information disclosed in Section alleged to be covered by the patent information disclosed in Section
V(A) or V(B), it is helpful if the discloser identifies here the V(A) or V(B), it is helpful if the discloser identifies here the
sections of the Internet-Draft or RFC that are alleged to be so sections of the Internet-Draft or RFC that are alleged to be so
covered. covered.
VI. Licensing Declaration VI. Licensing Declaration
The Patent Holder states that, upon approval by the IESG for The Patent Holder states that its position with respect to licensing
publication as an RFC of the relevant IETF specification, its any patent claims contained in the patent(s) or patent application(s)
position with respect to licensing any patent claims contained in the disclosed above that would necessarily be infringed by implementation
patent(s) or patent application(s) disclosed above that would of the technology required by the relevant IETF specification
necessarily be infringed by implementation of the technology required ("Necessary Patent Claims"), for the purpose of implementing such
by such IETF specification ("Necessary Patent Claims"), for the specification, is as follows (select one licensing declaration option
purpose of implementing the specification, is as follows (select one only):
licensing declaration option only):
a) ___ No License Required for Implementers a) ___ No License Required for Implementers
Check here if this licensing declaration is limited solely Check here if commitment to forgo a license is limited
to standards-track IETF documents ___ solely to standards-track RFCs ___
b) ___ Royalty-Free, Reasonable and Non-Discriminatory License to b) ___ Royalty-Free, Reasonable and Non-Discriminatory License to
All Implementers All Implementers
Check here if this licensing declaration is limited solely Check here if this commitment to license is limited solely
to standards-track IETF documents ___ to standards-track RFCs ___
c) ___ Reasonable and Non-Discriminatory License to All c) ___ Reasonable and Non-Discriminatory License to All
Implementers with Possible Royalty/Fee Implementers with Possible Royalty/Fee
Check here if this licensing declaration is limited solely Check here if this commitment to license is limited solely
to standards-track IETF documents ___ to standards-track RFCs ___
d) ___ Licensing Declaration to be Provided Later (implies a d) ___ Licensing Declaration to be Provided Later (implies a
willingness to commit to the provisions of a), b), or c) willingness to commit to the provisions of a), b), or c)
above to all implementers; otherwise, the next option - above; otherwise, the next option - "Unwilling to Commit to
"Unwilling to Commit to the Provisions of a), b), or c) the Provisions of a), b), or c) Above" - must be selected)
Above" - must be selected)
e) ___ Unwilling to Commit to the Provisions of a), b), or c) e) ___ Unwilling to Commit to the Provisions of a), b), or c)
Above Above
NOTE: The individual submitting this template represents and warrants NOTE: The individual submitting this template represents and warrants
that he or she is authorized by the Patent Holder to agree to the that he or she is authorized by the Patent Holder to agree to the
above-selected licensing declaration. above-selected licensing declaration.
VII. Contact Information of Submitter of this Form (if different from VII. Contact Information of Submitter of this Form (if different from
IETF Participant in Section III above) IETF Participant in Section III above)
skipping to change at page 6, line 20 skipping to change at page 6, line 20
Section VI 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 Necessary Patent Claims require parties to acquire any license to its Necessary Patent Claims
in order to make, have made, use, import, offer to sell, sell, or in order to make, have made, use, import, offer to sell, sell, or
distribute technology that implements such IETF specification. distribute technology that implements such IETF specification.
b) Royalty-Free, Reasonable and Non-Discriminatory License to All b) Royalty-Free, Reasonable and Non-Discriminatory License to All
Implementers: The Patent Holder is willing, upon request, to grant a Implementers: The Patent Holder is willing, upon request, to grant a
license to its Necessary Patent Claims to all persons on a royalty- license to its Necessary Patent Claims to all persons on a royalty-
free basis (i.e., no royalty or other fee) and under reasonable and free basis (i.e., no royalty or other fee) and under other reasonable
non-discriminatory terms, to make, have made, use, import, offer to and non-discriminatory terms and conditions, to make, have made, use,
sell, sell, and distribute technology that implements such IETF import, offer to sell, sell, and distribute technology that
specification. implements such IETF specification.
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 is willing, upon request, to Possible Royalty/Fee: The Patent Holder is willing, upon request, to
grant a license to its Necessary Patent Claims to all persons under grant a license to its Necessary Patent Claims to all persons under
reasonable and non-discriminatory terms (which may include a reasonable and non-discriminatory terms and conditions (which may
royalty/fee), to make, have made, use, import, offer to sell, sell, include a royalty/fee), to make, have made, use, import, offer to
and distribute technology that implements such IETF specification. sell, sell, and distribute technology that implements such IETF
specification.
d) Licensing Declaration to be Provided Later: The Patent Holder is d) Licensing Declaration to be Provided Later: The Patent Holder is
willing to commit to the provisions of a), b), or c) above to all willing to commit to the provisions of a), b), or c) above, but wants
implementers of the IETF specification, but wants to defer its to defer its specific selection of one of these licensing declaration
specific selection of one of these licensing declaration options options until a later point in time (or when asked for this
until a later point in time (or when asked for this information by information by the IESG). This option may not be selected if the
the IESG). This option may not be selected if the Patent Holder is Patent Holder is unwilling to commit to the provisions of a), b), or
unwilling to commit to the provisions of a), b), or c) above. In that c) above. In that case, the Patent Holder must select licensing
case, the Patent Holder must select licensing declaration option e) - declaration option e) - "Unwilling to Commit to the Provisions of a),
"Unwilling to Commit to the Provisions of a), b), or c) Above". b), or c) Above".
e) Unwilling to Commit to the Provisions of a), b), or c) Above: The e) Unwilling to Commit to the Provisions of a), b), or c) Above: The
Patent Holder indicates an unwillingness to commit to the provisions Patent Holder indicates an unwillingness to commit to the provisions
of any of options a), b), or c) described above. of any of options a), b), or c) described above.
Options a), b), and c) above also allow the Patent Holder to indicate Options a), b), and c) above also allow the Patent Holder to indicate
(with a check) whether its licensing declaration is limited solely to (with a check) whether its licensing declaration is limited solely to
standards-track documents. If left unchecked, the Patent Holder's standards-track RFCs. If left unchecked, the Patent Holder's
licensing declaration will be deemed to apply to all IETF documents, licensing declaration will be deemed to apply to any implementation
including non-standards-track documents. This standards-track of the relevant IETF specification, including non-standards-track
qualifier is not relevant to licensing declaration options d) and e), documents and Internet-Drafts. However, the Patent Holder may list
because under d) the Patent Holder has not yet indicated its specific other conditions or restrictions on its commitment to forego a
license (option a)) or on its commitment to license (options b) and
c)) in Section VIII - "Other Notes". This standards-track qualifier
is not relevant to licensing declaration options d) and e), because
under d) the Patent Holder has not yet indicated its specific
licensing intention and under e) the Patent Holder has indicated a licensing intention and under e) the Patent Holder has indicated a
general refusal to commit to the provisions of any of options a), b), general refusal to commit to the provisions of any of options a), b),
or c) above. or c) above.
Section VIII in the template, "Other Notes," may be used for any Section VIII in the template, "Other Notes," may be used for any
additional information a discloser or Patent Holder wishes to additional information a discloser or Patent Holder wishes to
provide. For example, a Patent Holder may use the "Other Notes" provide. For example, a Patent Holder may use the "Other Notes"
Section to indicate any other conditions on the licensing declaration Section to indicate any other conditions or restrictions on the
option selected in Section VI (e.g., reciprocity). licensing declaration option selected in Section VI (e.g., 1)
reciprocity, or 2) that a license will only be made available for
implementations of any RFC (standards-track or non-standards-track),
but not for implementations of Internet-Drafts or other documents).
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 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.
 End of changes. 

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