IPR Search

Document search

IPR search

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
rfc5393

Total number of IPR disclosures found: 2.

Date ID Statement
2017-06-20 3017 Alcatel Lucent's Statement about IPR related to RFC 5393
2017-06-20 3016 Alcatel Lucent's Statement about IPR related to RFC 5393

IPR declarations exist for related documents, see below. These cannot be assumed to apply to the current document without closer inspection.

Total number of documents searched: 2.

Date ID Statement
Results for RFC 5393 ("Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies")
2017-06-20 3016 Alcatel Lucent's Statement about IPR related to RFC 5393
2017-06-20 3017 Alcatel Lucent's Statement about IPR related to RFC 5393
Results for draft-ietf-sip-fork-loop-fix ("Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies"), which was became rfc draft-ietf-sip-fork-loop-fix ("Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies")
No IPR disclosures have been submitted directly on draft-ietf-sip-fork-loop-fix, but there are disclosures on a related document, listed on this page.
Date ID Statement
2005-05-23 579 AT&T's statement about IPR claimed in RFC 3261
(Updates ID#: 45)

Back