[TLS] Summary of IPR discussion on draft-ietf-tls-extractor-05
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[TLS] Summary of IPR discussion on draft-ietf-tls-extractor-05
I haven't heard anyone dispute that the current statement referenced in
https://datatracker.ietf.org/ipr/1004/ pertains to the use of the draft
with ECC technology. I have heard concern that there may be IPR claims
that may not be disclosed by Certicom or another party. However, this
is always the case and no new evidence of the existence of additional
claims has been brought forth. My recommendation is to move forward
with publishing the draft on standards track. Here is a what I suggest
should go in the PROTO write-up
(1.d) Does the Document Shepherd have any specific concerns or
issues with this document that the Responsible Area Director
and/or the IESG should be aware of? For example, perhaps he
or she is uncomfortable with certain parts of the document, or
has concerns whether there really is a need for it. In any
event, if the WG has discussed those issues and has indicated
that it still wishes to advance the document, detail those
concerns here. Has an IPR disclosure related to this document
been filed? If so, please include a reference to the
disclosure and summarize the WG discussion and conclusion on
this issue.
The document shepherd has no concerns with the document. There is an
IPR disclosure that lists this document:
https://datatracker.ietf.org/ipr/1004/. There has been some discussion
of this disclosure on the TLS list. In general the disclosure only
discusses the use of the draft with ECC technology. Some members are
worried that this leaves a loop hole for later assertions to be made by
the owner of the #1004 disclosure or that another third party may try to
assert claims. No new evidence about these existence of additional
claims has been provided to the working group so the document shepherd
has decided to move forward with progressing the draft on standards
track.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.