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
rfc5109
Total number of IPR disclosures found: 3.
Total number of documents searched: 6.
| Date | ID | Statement |
|---|---|---|
| Results for RFC 5109 ("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 RFC 3009 ("Registration of parityfec MIME types"), which was obsoleted by RFC 5109 ("RTP Payload Format for Generic Forward Error Correction") | ||
| No IPR disclosures have been submitted directly on RFC 3009, but there are disclosures on related documents, listed on this page. | ||
| Results for RFC 2733 ("An RTP Payload Format for Generic Forward Error Correction"), which was obsoleted by RFC 5109 ("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"), which became rfc RFC 5109 ("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 draft-ietf-avt-fecmime ("Registration of parityfec MIME types"), which became rfc RFC 3009 ("Registration of parityfec MIME types") | ||
| No IPR disclosures have been submitted directly on draft-ietf-avt-fecmime, 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"), which became rfc RFC 2733 ("An 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. | ||