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

Draft search results

Total number of IPR disclosures found: 5.

Date	ID	Statement
2009-05-07	1145	Juniper's Statement of IPR related to RFC 4875
2009-03-09	1110	Redback Networks, Inc.'s Statement about IPR related to RFC 4875
2009-02-09	1077	Juniper's Statement of IPR related to RFC 4875
2008-11-11	1016	Fujitsu Limited's Statement about IPR related to RFC 4875
2008-11-10	1011	Fujitsu Limited's Statement about IPR related to RFC 4875

Total number of documents searched: 2.

Date	ID	Statement
Results for draft-ietf-mpls-rsvp-te-p2mp ("Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)"):
		No IPR disclosures have been submitted directly on draft-ietf-mpls-rsvp-te-p2mp, but there are disclosures on a related document, listed on this page.
Results for RFC4875 ("Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)"):
2008-11-10	1011	Fujitsu Limited's Statement about IPR related to RFC 4875
2008-11-11	1016	Fujitsu Limited's Statement about IPR related to RFC 4875
2009-02-09	1077	Juniper's Statement of IPR related to RFC 4875
2009-03-09	1110	Redback Networks, Inc.'s Statement about IPR related to RFC 4875
2009-05-07	1145	Juniper's Statement of IPR related to RFC 4875

Back to IPR disclosure page