draft-ietf-ipr-template-05.txt   draft-ietf-ipr-template-06.txt 
IPR WG IPR WG
Internet-Draft V. See (editor) Internet-Draft V. See (editor)
Document: draft-ietf-ipr-template-05.txt Microsoft Document: draft-ietf-ipr-template-06.txt Microsoft
Expires: December 13, 2003 June 13, 2003 Expires: February 11, 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 [i]. 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
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 36 skipping to change at page 1, line 36
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. The optional use of this template is meant to licensing declarations. The optional use of this template is meant to
simplify the process of such disclosures and licensing declarations simplify the process of such disclosures and licensing declarations
and to assist disclosers in providing the necessary information to and to assist disclosers in providing the necessary information to
meet the obligations documented in RFC XXXX [ii]. meet the obligations documented in RFC XXXX.
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...........................................7 Security Considerations...........................................7
References........................................................7 Normative References..............................................7
Acknowledgments...................................................7 Acknowledgments...................................................7
Authors' Addresses................................................7 Authors' Addresses................................................7
Intellectual Property Statement...................................8
Full Copyright statement..........................................8 Full Copyright statement..........................................8
1. Introduction 1. Introduction
RFC XXXX [ii] documents the current IETF policies and obligations RFC XXXX [i] documents the current IETF policies and obligations with
with respect to disclosure of patents and patent applications. It respect to disclosure of patents and patent applications. It also
also documents the information requested in licensing declarations documents the information requested in licensing declarations for
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. For the latest information on declaration provisions under RFC XXXX. For the latest information on
how to submit a patent disclosure or licensing declaration, please how to submit a patent disclosure or licensing declaration, please
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
skipping to change at page 2, line 44 skipping to change at page 2, line 45
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 upon approval by the IESG for publication as
an RFC of the relevant IETF specification. No actual license is an RFC of the relevant IETF specification. No actual license is
implied by submission of this template. Please complete and submit a implied by submission of this template. Please complete and submit a
separate template for each IETF document or contribution to which the separate template for each IETF document or contribution to which the
disclosed patent information relates. disclosed patent information relates.
I. Patent Holder/Organization ("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:
Department: Department:
skipping to change at page 3, line 34 skipping to change at page 3, line 34
Department: Department:
Address: Address:
Telephone: Telephone:
Fax: Fax:
Email: Email:
IV. IETF Document or Working Group Contribution to Which Patent IV. IETF Document or Contribution to Which Patent Disclosure Relates
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 XXXX)
skipping to change at page 4, line 27 skipping to change at page 4, line 27
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, upon approval by the IESG for
publication as an RFC of the relevant IETF specification, its publication as an RFC of the relevant IETF specification, its
position with respect to licensing any patent claims contained in the position with respect to licensing any patent claims contained in the
patent(s) or patent application(s) disclosed above that would be patent(s) or patent application(s) disclosed above that would
necessary to implement the technology required by such IETF necessarily be infringed by implementation of the technology required
specification ("Patent Claims"), for the purpose of implementing the 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 this licensing declaration is limited solely
to standards-track IETF documents ___ to standards-track IETF documents ___
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 licensing declaration is limited solely
to standards-track IETF documents ___ to standards-track IETF documents ___
skipping to change at page 6, line 6 skipping to change at page 6, line 6
Section III requests contact information for the Patent Holder's IETF Section III requests contact information for the Patent Holder's IETF
participant whose personal belief that necessary patent claims are participant whose personal belief that necessary patent claims are
implicated by an IETF document or contribution caused this template implicated by an IETF document or contribution caused this template
to be filed. This is an optional section. However, if Section III is to be filed. This is an optional section. However, if Section III is
not completed, then Section VII must be completed. Even if Section not completed, then Section VII must be completed. Even if Section
III is completed, Section VII must still be completed if the III is completed, Section VII must still be completed if the
submitter of this template is different from the IETF participant submitter of this template is different from the IETF participant
identified in Section III. identified in Section III.
The "Other Designations" field in Section IV may be used to identify The "Other Designations" field in Section IV may be used to identify
an IETF working group contribution (oral or written) other than an an IETF contribution (oral or written) other than an Internet-Draft
Internet-Draft or RFC to which a disclosure is related. or RFC to which a disclosure is related.
Here is an explanation of the licensing declaration options in Here is an explanation of the licensing declaration options in
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 Patent Claims in order require parties to acquire any license to its Necessary Patent Claims
to implement the IETF specification. in order to make, have made, use, import, offer to sell, sell, or
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 Patent Claims to all implementers of the IETF license to its Necessary Patent Claims to all persons on a royalty-
specification on a royalty-free basis (i.e., no royalty or other fee) free basis (i.e., no royalty or other fee) and under reasonable and
and under reasonable and non-discriminatory terms. non-discriminatory terms, to make, have made, use, import, offer to
sell, sell, and distribute technology that 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 Patent Claims to all implementers of the IETF grant a license to its Necessary Patent Claims to all persons under
specification under reasonable and non-discriminatory terms (which reasonable and non-discriminatory terms (which may include a
may include a royalty/fee). royalty/fee), to make, have made, use, import, offer to 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 to all
implementers of the IETF specification, but wants to defer its implementers of the IETF specification, but wants to defer its
specific selection of one of these licensing declaration options specific selection of one of these licensing declaration options
until a later point in time (or when asked for this information by until a later point in time (or when asked for this information by
the IESG). This option may not be selected if the Patent Holder is the IESG). This option may not be selected if the Patent Holder is
unwilling to commit to the provisions of a), b), or c) above. In that unwilling to commit to the provisions of a), b), or c) above. In that
case, the Patent Holder must select licensing declaration option e) - case, the Patent Holder must select licensing declaration option e) -
"Unwilling to Commit to the Provisions of a), b), or c) Above". "Unwilling to Commit to the Provisions of a), b), or c) Above".
skipping to change at page 7, line 21 skipping to change at page 7, line 25
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.
References Normative References
i Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
ii Bradner, S., "Intellectual Property Rights in IETF Technology", i 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 8, line 17 skipping to change at page 8, line 17
Paul Gleichauf Paul Gleichauf
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, San Jose, CA 95134 USA 170 West Tasman Drive, San Jose, CA 95134 USA
Email: phg@cisco.com Email: phg@cisco.com
Allen Lo Allen Lo
Juniper Networks Juniper Networks
1194 North Mathilda Ave., Sunnyvale, CA 94089 USA 1194 North Mathilda Ave., Sunnyvale, CA 94089 USA
Email: alo@juniper.net Email: alo@juniper.net
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property 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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright statement Full Copyright statement
Copyright (C) The Internet Society (2003). Except as set forth Copyright (C) The Internet Society (2003). Except as set forth
below, authors retain all their rights. below, authors retain all their rights.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
 End of changes. 

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