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
rfc4842

Total number of IPR disclosures found: 3.

Date ID Statement
2005-02-25 542 Level 3 Communications, Inc.'s statement about IPR claimed in draft-ietf-pwe3-sonet-10.txt
2004-05-26 424 Lycium Networks Statement about IPR Claimed in draft-ietf-pwe3-sonet
2003-05-05 123 Vivace Networks Patent Statement Pertaining to draft-malis-sonet-ces-mpls-xx.txt and draft-ietf-pwe3-sonet-xx.txt

Total number of documents searched: 3.

Date ID Statement
Results for RFC 4842 ("Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)")
No IPR disclosures have been submitted directly on RFC 4842, but there are disclosures on related documents, listed on this page.
Results for draft-ietf-pwe3-sonet ("Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)"), which was became rfc draft-ietf-pwe3-sonet ("Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)")
2003-05-05 123 Vivace Networks Patent Statement Pertaining to draft-malis-sonet-ces-mpls-xx.txt and draft-ietf-pwe3-sonet-xx.txt
2004-05-26 424 Lycium Networks Statement about IPR Claimed in draft-ietf-pwe3-sonet
2005-02-25 542 Level 3 Communications, Inc.'s statement about IPR claimed in draft-ietf-pwe3-sonet-10.txt
Results for RFC 5143 ("Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) Encapsulation"), which was obsoleted by RFC 4842 ("Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)")
No IPR disclosures have been submitted directly on RFC 5143, but there are disclosures on related documents, listed on this page.

Back