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

Submitted: February 18, 2009

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.

Updated by

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

'I'. Patent Holder/Applicant ("Patent Holder")

Holder legal name
VeriSign

'II'. Patent Holder's Contact for License Application

Holder contact name
David M'Raihi
Holder contact email
dmraihi@verisign.com
Holder contact info

Principal
685 E. Middlefield Road
T: 650 426 3832

'III'. Contact Information for the IETF Participant Whose Personal Belief Triggered this Disclosure

Name
David M'Raihi
Email
dmraihi@verisign.com
Other info

Principal
685 E. Middlefield Road
T: 650 426 3832

'IV'. IETF Document or Other Contribution to Which this IPR Disclosure Relates

Internet-Draft
draft-ietf-keyprov-pskc ("Portable Symmetric Key Container (PSKC)")
Revisions: 01
Sections: 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
Internet-Draft
draft-ietf-keyprov-dskpp ("Dynamic Symmetric Key Provisioning Protocol (DSKPP)")
Revisions: 07
Internet-Draft
draft-mraihi-totp-timebased ("TOTP: Time-Based One-Time Password Algorithm")
Revisions: 01
Internet-Draft
draft-mraihi-mutual-oath-hotp-variants ("OCRA: OATH Challenge-Response Algorithm")
Revisions: 08
Sections: since HOTP is used as a building block for the different OCRA varia
RFC
RFC4226 ("HOTP: An HMAC-Based One-Time Password Algorithm")
Sections: most technical sections but mainly section 5 and part of section 7 where the algorithm and validation are extensively described

'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: see table
Country: see table

Notes: None

B. Does this disclosure relate to an unpublished pending patent application?:

Has patent pending
Yes

'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):

Licensing
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."

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

Submitter name
David M'Raihi
Submitter email
dmraihi@verisign.com

'VIII'. Other Notes

Additional notes

None

Only those sections of the relevant entry form where the submitter provided information are displayed.