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
draft-ietf-ipfix-reqs
Total number of IPR disclosures found: 5.
Date | ID | Statement |
---|---|---|
2007-05-10 | 844 | InMon Corporation's statement about IPR claimed in RFC 3917
(Updates ID#: 842) |
2007-04-27 | 842 | InMon Corporation's statement about IPR claimed in RFC 3917 |
2007-01-11 | 792 | Cisco's Statement about IPR Claimed in RFC 3917 |
2007-01-03 | 783 | Cisco's Statement about IPR claimed in draft-ietf-ipfix-reqs-16.txt |
2004-08-30 | 431 | Cisco's Statement about IPR claimed in draft-ietf-ipfix-reqs-16 |
Total number of documents searched: 2.
Date | ID | Statement |
---|---|---|
Results for draft-ietf-ipfix-reqs ("Requirements for IP Flow Information Export (IPFIX)") | ||
2004-08-30 | 431 | Cisco's Statement about IPR claimed in draft-ietf-ipfix-reqs-16 |
2007-01-03 | 783 | Cisco's Statement about IPR claimed in draft-ietf-ipfix-reqs-16.txt |
Results for RFC 3917 ("Requirements for IP Flow Information Export (IPFIX)") | ||
2007-01-11 | 792 | Cisco's Statement about IPR Claimed in RFC 3917 |
2007-04-27 | 842 | InMon Corporation's statement about IPR claimed in RFC 3917 |
2007-05-10 | 844 | InMon Corporation's statement about IPR claimed in RFC 3917
(Updates ID#: 842) |