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-sip-fork-loop-fix
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 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. | ||
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 |
Date | ID | Statement |
---|---|---|
2005-05-23 | 579 | AT&T's statement about IPR claimed in RFC 3261
(Updates ID#: 45) |
2002-02-01 | 62 | AT&T's Patent Statement pertaining to draft-ietf-sip-rfc2543bis |