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-hollenbeck-rfc4934bis
Total number of IPR disclosures found: 0.
Total number of documents searched: 7.
Date | ID | Statement |
---|---|---|
Results for draft-hollenbeck-epp-rfc3734bis ("Extensible Provisioning Protocol (EPP) Transport Over TCP") | ||
No IPR disclosures have been submitted directly on draft-hollenbeck-epp-rfc3734bis. | ||
Results for RFC 4934 ("Extensible Provisioning Protocol (EPP) Transport Over TCP"), which was obsoleted by draft-hollenbeck-rfc4934bis ("Extensible Provisioning Protocol (EPP) Transport over TCP") | ||
No IPR disclosures have been submitted directly on RFC 4934. | ||
Results for STD 69 ("Extensible Provisioning Protocol (EPP) Transport over TCP") | ||
No IPR disclosures have been submitted directly on STD 69. | ||
Results for draft-hollenbeck-rfc4934bis ("Extensible Provisioning Protocol (EPP) Transport over TCP") | ||
No IPR disclosures have been submitted directly on draft-hollenbeck-rfc4934bis. | ||
Results for RFC 5734 ("Extensible Provisioning Protocol (EPP) Transport over TCP") | ||
No IPR disclosures have been submitted directly on RFC 5734. | ||
Results for draft-ietf-provreg-epp-tcp ("Extensible Provisioning Protocol (EPP) Transport Over TCP"), which was obsoleted by draft-hollenbeck-epp-rfc3734bis ("Extensible Provisioning Protocol (EPP) Transport Over TCP") | ||
No IPR disclosures have been submitted directly on draft-ietf-provreg-epp-tcp. | ||
Results for RFC 3734 ("Extensible Provisioning Protocol (EPP) Transport Over TCP"), which was obsoleted by draft-hollenbeck-epp-rfc3734bis ("Extensible Provisioning Protocol (EPP) Transport Over TCP") | ||
No IPR disclosures have been submitted directly on RFC 3734. |