Glassey's Statement about possible IPR claimed in RFC 3161
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.
I. Patent Holder/Applicant ("Patent Holder")
- Holder legal name
II. Patent Holder's Contact for License Application
- Holder contact name
- Todd Glassey
- Holder contact email
- Holder contact info
III. IETF Document or Other Contribution to Which this IPR Disclosure Relates
RFC3161 ("Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)")
IV. Disclosure of Patent Information i.e., patents or patent applications required to be disclosed by Section 6 of RFC 8179
A. For granted patents or published pending patent applications, please provide the following information:
- Patent, Serial, Publication, Registration, or Application/File number(s)
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):
- one selected]
- Licensing information, comments, notes, or URL for further information
(No information submitted)
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
Be advised that I am formally concerned that the use of the services
defined in RFC3161 may violate any number of pre-existing patents and
because of this, extra diligence is warranted. This need for extra diligence
is predicated on the myriad of pre-existing patents on digital receipts and
watermarks and/or other evidentiary controls both here in the US and elsewhere.
Because of the sheer number of different patents, including ours (McNeil's'
and mine), it is my recommendation that in all instances, RFC3161's use should
be very carefully scrutinized prior to any services being released whether
public or private.
Likewise, be advised that the public testing of RFC3161 itself may also possibly
violate claims on any number of the patents or multiple patents, and as such
prior to those services being released or made available on the web, their use
models need to be carefully checked and vetted against the IP rights of those
individual patent holders, including myself and McNeil.
Only those sections of the relevant entry form where the submitter provided information are displayed.