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

Document IPR search results for draft-ietf-avt-ulp

Total number of IPR disclosures found: 3.

Date	ID	Statement
2006-04-04	704	Colin Perkins's statement about possible IPR claimed in draft-ietf-avt-ulp-17.txt belonging to Lucent Technologies
2006-04-04	703	Colin Perkins's statement about possible IPR claimed in draft-ietf-avt-ulp-17.txt belonging to International Computer Science Institute
2004-01-01	339	Rosenberg's Statement about possible IPR claimed in draft-ietf-avt-ulp and RFC 2733 belonging to Lucent Technologies

Total number of documents searched: 7.

Date	ID	Statement
Results for RFC3009 ("Registration of parityfec MIME types"):
		No IPR disclosures have been submitted directly on RFC 3009, but there are disclosures on related documents, listed on this page.
Results for draft-li-ulp ("An RTP Payload Format for Generic FEC with Uneven Level Protection"), that was replaced by draft-ietf-avt-ulp ("RTP Payload Format for Generic Forward Error Correction"):
		No IPR disclosures have been submitted directly on draft-li-ulp, but there are disclosures on related documents, listed on this page.
Results for draft-ietf-avt-fec ("An RTP Payload Format for Generic Forward Error Correction"), that was obsoleted by draft-ietf-avt-ulp ("RTP Payload Format for Generic Forward Error Correction"):
		No IPR disclosures have been submitted directly on draft-ietf-avt-fec, but there are disclosures on related documents, listed on this page.
Results for RFC2733 ("An RTP Payload Format for Generic Forward Error Correction"), that was obsoleted by draft-ietf-avt-ulp ("RTP Payload Format for Generic Forward Error Correction"):
2004-01-01	339	Rosenberg's Statement about possible IPR claimed in draft-ietf-avt-ulp and RFC 2733 belonging to Lucent Technologies
Results for draft-ietf-avt-ulp ("RTP Payload Format for Generic Forward Error Correction"):
2004-01-01	339	Rosenberg's Statement about possible IPR claimed in draft-ietf-avt-ulp and RFC 2733 belonging to Lucent Technologies
2006-04-04	703	Colin Perkins's statement about possible IPR claimed in draft-ietf-avt-ulp-17.txt belonging to International Computer Science Institute
2006-04-04	704	Colin Perkins's statement about possible IPR claimed in draft-ietf-avt-ulp-17.txt belonging to Lucent Technologies
Results for RFC5109 ("RTP Payload Format for Generic Forward Error Correction"):
		No IPR disclosures have been submitted directly on RFC 5109, but there are disclosures on related documents, listed on this page.
Results for draft-ietf-avt-fecmime ("Registration of parityfec MIME types"), that was obsoleted by draft-ietf-avt-ulp ("RTP Payload Format for Generic Forward Error Correction"):
		No IPR disclosures have been submitted directly on draft-ietf-avt-fecmime, but there are disclosures on related documents, listed on this page.

Back to IPR disclosure page