Skip to main content

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
rfc3446

Total number of IPR disclosures found: 2.

Date ID Statement
2006-10-06 750 Certicom's Statement about IPR claimed in RFC 3446, RFC 2409, draft-ietf-tls-ecc-12, draft-ietf-ipsec-ike-auth-ecdsa-05, and draft-ietf-ipsec-ecp-groups-02
2006-02-01 695 Certicom's Statement about IPR Claimed in RFC 3446, RFC 2409, draft-ietf-tls-ecc-12, draft-ietf-ipsec-ike-auth-ecdsa-05, and draft-ietf-ipsec-ike-ecp-groups-02 and other IETF specifications using ECC technology

Total number of documents searched: 2.

Date ID Statement
Results for RFC 3446 ("Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)")
2006-02-01 695 Certicom's Statement about IPR Claimed in RFC 3446, RFC 2409, draft-ietf-tls-ecc-12, draft-ietf-ipsec-ike-auth-ecdsa-05, and draft-ietf-ipsec-ike-ecp-groups-02 and other IETF specifications using ECC technology
2006-10-06 750 Certicom's Statement about IPR claimed in RFC 3446, RFC 2409, draft-ietf-tls-ecc-12, draft-ietf-ipsec-ike-auth-ecdsa-05, and draft-ietf-ipsec-ecp-groups-02
Results for draft-ietf-mboned-anycast-rp ("Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)"), which became rfc RFC 3446 ("Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)")
No IPR disclosures have been submitted directly on draft-ietf-mboned-anycast-rp, but there are disclosures on a related document, listed on this page.

Back