datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

VeriSign's Statement about IPR related to RFC 4226, draft-mraihi-mutual-oath-hotp-variants-08, draft-mraihi-totp-timebased-01, draft-ietf-keyprov-dskpp-07, draft-ietf-keyprov-pskc-01, and None

Only those sections of the "Patent Disclosure and Licensing Declaration Template for Specific IPR Disclosures" where the submitter provided information are displayed.

This IPR disclosure has been updated by IPR disclosure ID #1104, "VeriSign's Statement about IPR related to RFC 4226, draft-mraihi-mutual-oath-hotp-variants-08, draft-mraihi-totp-timebased-01, draft-ietf-keyprov-dskpp-07, and draft-ietf-keyprov-pskc-02".

Update this IPR disclosure. Note: Updates to IPR disclosures must only be made by authorized representatives of the original submitters. Updates will automatically be forwarded to the current Patent Holder's Contact and to the Submitter of the original IPR disclosure.

Submitted Date: February 18, 2009

I. Patent Holder/Applicant ("Patent Holder")
Legal Name: VeriSign
II. Patent Holder's Contact for License Application
Name: David M'Raihi
Title: Principal
Department:
Address1: 685 E. Middlefield Road
Address2:
Telephone: 650 426 3832
Fax:
Email: dmraihi@verisign.com
III. Contact Information for the IETF Participant Whose Personal Belief Triggered this Disclosure:
Name: David M'Raihi
Title: Principal
Department:
Address1: 685 E. Middlefield Road
Address2:
Telephone: 650 426 3832
Fax:
Email: dmraihi@verisign.com
IV. IETF Document or Other Contribution to Which this IPR Disclosure Relates:
RFC 4226:"HOTP: An HMAC-Based One-Time Password Algorithm"
Internet-Draft:"Portable Symmetric Key Container (PSKC)"
(draft-ietf-keyprov-pskc-01)
Internet-Draft:"Dynamic Symmetric Key Provisioning Protocol (DSKPP)"
(draft-ietf-keyprov-dskpp-07)
Internet-Draft:"TOTP: Time-Based One-Time Password Algorithm"
(draft-mraihi-totp-timebased-01)
Internet-Draft:"OCRA: OATH Challenge-Response Algorithm"
(draft-mraihi-mutual-oath-hotp-variants-08)
V. Disclosure of Patent Information (i.e., patents or patent applications required to be disclosed by Section 6 of RFC 3979)
A. For granted patents or published pending patent applications, please provide the following information:
Patent, Serial, Publication, Registration, or Application/File number(s): Application number Date Applied For Country
Date(s) granted or applied for: see table
Country: see table
Additional Notes:

None

B. Does this disclosure relate to an unpublished pending patent application?: YES
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 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 sections of the Internet-Draft or RFC that are alleged to be so covered:

In RFC 4226 most technical sections but mainly section 5 and part of section 7 where the algorithm and validation are extensively described;
In draft-mraihi-mutual-oath-hotp-variants-08, since HOTP is used as a building block for the different OCRA varia

VI. Licensing Declaration
The Patent Holder states that its position with respect to licensing any patent claims contained in the patent(s) or patent application(s) disclosed above that would necessarily be infringed by implementation of the technology required by the relevant IETF specification ("Necessary Patent Claims"), for the purpose of implementing such specification, is as follows(select one licensing declaration option only):
Royalty-Free, Reasonable and Non-Discriminatory License to All Implementers.
Licensing information, comments, notes, or URL for further information:

"The license offered by VeriSign under this Patent Disclosure and Licensing Declaration includes the terms in this statement. As used in this statement, capitalized terms shall have the following meanings:

"Patent Rights" shall mean any and all patent rights arising from the
above-listed applications that are necessary to practice RFC 4226.

"Practicing Covered Technology" shall mean making, having made, using,
selling, offering for sale, importing or exporting any technology
covered by any Patent Rights.

VeriSign agrees not to assert its Patent Rights against any entity for
any past, present or future infringement of such Patent Rights, unless:

1) An entity brings suit for patent infringement for any product or
service under any patent against VeriSign, it's affiliates or successors
in interest;

or

2) An entity brings suit for patent infringement against any other
entity for Practicing Covered Technology.

VeriSign retains the right to assert its patent rights against any
entity for practicing technology that is not necessary for compliance
with RFC 4226.

Notwithstanding the foregoing, VeriSign may grant to any entity a
royalty-bearing license to some or all of the Patent Rights on
mutually-agreed upon terms."

The individual submitting this template represents and warrants that all terms and conditions that must be satisfied for implementers of any covered IETF specification to obtain a license have been disclosed in this IPR disclosure statement.

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 the Contact Information above)
Name: David M'Raihi
Title: Principal
Department:
Address1: 685 E. Middlefield Road
Address2:
Telephone: 650 426 3832
Fax:
Email: dmraihi@verisign.com
VIII. Other Notes:

None