Skip to main content

IPR Search

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
draft-eastlake-rfc6931bis-xmlsec-uris

Total number of IPR disclosures found: 0.

Total number of documents searched: 6.

Date ID Statement
Results for draft-eastlake-rfc6931bis-xmlsec-uris ("Additional XML Security Uniform Resource Identifiers (URIs)")
No IPR disclosures have been submitted directly on draft-eastlake-rfc6931bis-xmlsec-uris.
Results for draft-eastlake-additional-xmlsec-uris ("Additional XML Security Uniform Resource Identifiers (URIs)"), which was obsoleted by draft-eastlake-rfc6931bis-xmlsec-uris ("Additional XML Security Uniform Resource Identifiers (URIs)")
No IPR disclosures have been submitted directly on draft-eastlake-additional-xmlsec-uris.
Results for RFC 6931 ("Additional XML Security Uniform Resource Identifiers (URIs)"), which was obsoleted by draft-eastlake-rfc6931bis-xmlsec-uris ("Additional XML Security Uniform Resource Identifiers (URIs)")
No IPR disclosures have been submitted directly on RFC 6931.
Results for draft-eastlake-xmldsig-uri ("Additional XML Security Uniform Resource Identifiers (URIs)"), which was obsoleted by draft-eastlake-additional-xmlsec-uris ("Additional XML Security Uniform Resource Identifiers (URIs)")
No IPR disclosures have been submitted directly on draft-eastlake-xmldsig-uri.
Results for RFC 4051 ("Additional XML Security Uniform Resource Identifiers (URIs)"), which was obsoleted by draft-eastlake-additional-xmlsec-uris ("Additional XML Security Uniform Resource Identifiers (URIs)")
No IPR disclosures have been submitted directly on RFC 4051.
Results for RFC 9231 ("Additional XML Security Uniform Resource Identifiers (URIs)")
No IPR disclosures have been submitted directly on RFC 9231.

Back