[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC3161(TSP): doubts about tcp protocol




At 9:48 AM -0700 4/15/03, todd glassey wrote:
So Richard - what are you going to do when you get sued for building a
product that has NO possible use but to violate filed and reliable
Intellectual Property Rights - This is not just my claim - the original RFC
now has a section that talks to its issues with commercially supplied
patents regarding receipt generation and the use of time data therein. Only
it doesn't bother to include the XML ones or those filed and granted since
the Haber ones it does reference became moot.

This is the real issue with RFC3161 and its becoming a standard. It
essentially creates the first COMMERCIAL standard inside the IETF  since
there can be no use model that is not in violation of any number of patents.
It also will IMHO constrain PKIX for what it is  - an old boys club
masquerading as a standards group.

I see the ascension of 3161 as one of the saddest things that can happen
since it will permanently impugn PKIX and in fact may be the key item
necessary to force the deconstruction of the IETF as we know it today.

Todd Glassey

While it is thoughtful of Todd to express his opinion about the possible intellectual property issues that may be associated with the TSP RFC, it is also worth noting that:


- the RFC makes note of possible IP problems in a fashion consistent with IETF guidelines

- Todd himself is a patent holder in this area, and thus not exaclty an unbiased party

- When Entrust was sued by another patent holder in the area of time stamping, 4 claims of the patent holder were struck down by the court, who found for the defendant (Entrust)

Thus it is far from clear that, as Todd claims, any use of TSP will violate existing patents.

Steve