IPR Search

Document search

Draft name

RFC number

Words in document title:

Working group:

IPR search

Name of patent owner/applicant:

Words in IPR disclosure title:

Text in patent information:

This search string must contain at least three characters, including at least one digit, and include punctuation marks. For best results, please enter the entire string, or as much of it as possible.

The material posted as IPR disclosures should be viewed as originating from the source of that information, and any issue or question related to the material should be directed to the source rather than the IETF. There is no implied endorsement or agreement by the IETF, the IESG or any other IETF entities with any of the material.

Back

Document IPR search results for draft-ietf-httpbis-encryption-encoding

Total number of IPR disclosures found: 1.

Date	ID	Statement
2016-03-21	2777	Glassey?McNeil's Statement about IPR related to draft-ietf-httpbis-encryption-encoding, draft-ietf-pkix-x509-ipaddr-as-extn, and draft-mm-wg-effect-encrypt-01

Total number of documents searched: 4.

Date	ID	Statement
Results for draft-thomson-http-encryption ("Encrypted Content-Encoding for HTTP"):
		No IPR disclosures have been submitted directly on draft-thomson-http-encryption, but there are disclosures on related documents, listed on this page.
Results for draft-nottingham-http-encryption-encoding ("Encrypted Content-Encoding for HTTP"), that was replaced by draft-thomson-http-encryption ("Encrypted Content-Encoding for HTTP"):
		No IPR disclosures have been submitted directly on draft-nottingham-http-encryption-encoding, but there are disclosures on related documents, listed on this page.
Results for draft-ietf-httpbis-encryption-encoding ("Encrypted Content-Encoding for HTTP"):
2016-03-21	2777	Glassey?McNeil's Statement about IPR related to draft-ietf-httpbis-encryption-encoding, draft-ietf-pkix-x509-ipaddr-as-extn, and draft-mm-wg-effect-encrypt-01
Results for RFC8188 ("Encrypted Content-Encoding for HTTP"):
		No IPR disclosures have been submitted directly on RFC 8188, but there are disclosures on related documents, listed on this page.

Back to IPR disclosure page