CoreStreet, Ltd. Statement about IPR claimed in IETF's draft Simple Certificate Validation Protocol - draft-ietf-pkix-scvp-18 (
The text of the original IPR disclosure is available in the disclosure history.
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.
IPR Disclosure ID #563, "CoreStreet, Ltd.'s statement about IPR claimed in draft-ietf-pkix-scvp-18"
I. Patent Holder/Applicant ("Patent Holder")
- Holder legal name
- CoreStreet , Ltd.
II. Patent Holder's Contact for License Application
- Holder contact name
- David Engberg
- Holder contact email
- Holder contact info
Chief Technology Officer
III. IETF Document or Other Contribution to Which this IPR Disclosure Relates
draft-ietf-pkix-scvp ("Server-Based Certificate Validation Protocol (SCVP)")
IV. Disclosure of Patent Information i.e., patents or patent applications required to be disclosed by 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)
U.S. Patent No. 5,717,758: Witness-Based Certificate Revocation System;
U.S. Patent No. 5,717,757: Certificate Issue Lists; and
U.S. Patent No. 5,666,416: Certificate Revocation System (collectively, the "Patents").
B. Does this disclosure relate to an unpublished pending patent application?:
- Has patent pending
V. 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):
- See Text Below for Licensing Declaration
- Licensing information, comments, notes, or URL for further information
If the SCVP draft (ietf-pkix-scvp-18) is adopted as a standard by the IETF,
and any claim in any of the Patents is necessary for implementing such
standard, CoreStreet will negotiate royalty-bearing licenses of the Patents
on reasonable and nondiscriminatory terms and conditions for at least any
part or function of a product or service that is technically necessary for
compliance with such standard, including a royalty-bearing license for any
claim(s) of the Patents that would otherwise be infringed by an SCVP server
to determine certificate revocation for Delegated Path Validation (DPV),
provided that the royalty-bearing license is restricted to such use. In
addition, CoreStreet will grant a royalty-free license for any claim(s) of
the Patents that would otherwise be infringed by any product that implements
an SCVP client, provided that the royalty-free license is restricted to such
use. CoreStreet's obligation to grant any such license(s) is conditioned
upon the prospective licensee paying reasonable royalties for the
royalty-bearing license(s) and, in any case, granting a reciprocal license
to CoreStreet (and its successors) of its applicable patent rights. Except
as provided above, CoreStreet reserves its rights in its intellectual
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.
VI. Contact Information of Submitter of this Form
- Submitter name
- Submitter email
VII. Other Notes
- Additional notes
This letter describes CoreStreet's position with respect to the current IETF
IPR Policy, and provides a disclosure concerning CoreStreet patents that
relate to the subject matter of the current SCVP draft
disclosure supersedes the prior CoreStreet disclosure dated March 23, 2005.
CoreStreet understands the IPR Policy to require disclosures of intellectual
property rights that are necessarily infringed by implementation of a
standard with respect to which a person is contributing; in our case, the
SCVP. CoreStreet believes an implementation of the SCVP standard (as
currently drafted) need not necessarily infringe our patents and, for this
and other reasons, believes no disclosure of our patents has been or is
Only those sections of the relevant entry form where the submitter provided information are displayed.