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
rfc4103
Total number of IPR disclosures found: 3.
Date | ID | Statement |
---|---|---|
2004-11-10 | 499 | Cisco's Statement about IPR claimed in draft-ietf-avt-rfc2793bis-09
(Updates ID#: 492) |
2004-10-11 | 492 | Cisco's Statement about IPR claimed in draft-ietf-avt-rfc2793bis-09.txt |
2004-07-13 | 462 | Cisco's Statement about IPR claimed in draft-ietf-avt-rfc2793bis-00 |
Total number of documents searched: 4.
Date | ID | Statement |
---|---|---|
Results for RFC 4103 ("RTP Payload for Text Conversation") | ||
No IPR disclosures have been submitted directly on RFC 4103, but there are disclosures on related documents, listed on this page. | ||
Results for RFC 2793 ("RTP Payload for Text Conversation"), which was obsoleted by RFC 4103 ("RTP Payload for Text Conversation") | ||
No IPR disclosures have been submitted directly on RFC 2793, but there are disclosures on related documents, listed on this page. | ||
Results for draft-ietf-avt-rfc2793bis ("RTP Payload for Text Conversation"), which became rfc RFC 4103 ("RTP Payload for Text Conversation") | ||
2004-07-13 | 462 | Cisco's Statement about IPR claimed in draft-ietf-avt-rfc2793bis-00 |
2004-10-11 | 492 | Cisco's Statement about IPR claimed in draft-ietf-avt-rfc2793bis-09.txt |
2004-11-10 | 499 | Cisco's Statement about IPR claimed in draft-ietf-avt-rfc2793bis-09
(Updates ID#: 492) |
Results for draft-ietf-avt-rtp-text ("RTP Payload for Text Conversation"), which became rfc RFC 2793 ("RTP Payload for Text Conversation") | ||
No IPR disclosures have been submitted directly on draft-ietf-avt-rtp-text, but there are disclosures on related documents, listed on this page. |