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
rfc4761

Total number of IPR disclosures found: 4.

Date ID Statement
2014-02-11 2318 Juniper's Statement of IPR related to RFC 4761
2009-02-10 1091 Juniper's Statement of IPR related to RFC 4761
2005-05-11 769 Tellabs Statement about IPR claimed in draft-ietf-l2vpn-vpls-ldp-06 and draft-ietf-l2vpn-vpls-bgp-05
2005-05-11 749 Tellabs Statement about IPR Claimed in draft-ietf-l2vpn-vpls-ldp-06 and draft-ietf-l2vpn-vpls-bgp-05

Total number of documents searched: 2.

Date ID Statement
Results for RFC 4761 ("Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling")
2009-02-10 1091 Juniper's Statement of IPR related to RFC 4761
2014-02-11 2318 Juniper's Statement of IPR related to RFC 4761
Results for draft-ietf-l2vpn-vpls-bgp ("Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling"), which was became rfc draft-ietf-l2vpn-vpls-bgp ("Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling")
2005-05-11 749 Tellabs Statement about IPR Claimed in draft-ietf-l2vpn-vpls-ldp-06 and draft-ietf-l2vpn-vpls-bgp-05
2005-05-11 769 Tellabs Statement about IPR claimed in draft-ietf-l2vpn-vpls-ldp-06 and draft-ietf-l2vpn-vpls-bgp-05

Back