Source note · SIP call forwarding and routing loops
RFC 5393 (December 2008, Standards Track) normatively updates RFC 3261 to fix an amplification vulnerability in which forking proxies without loop detection turn a few requests into very large amounts of proxy-to-proxy traffic.
Checked 2026-09-25
- Vendor
- IETF
- Product
- SIP
- Subsystem
- forking proxy loop detection
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 5393 onward
- Checked
- 2026-09-25
Sources
- RFC 5393: Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies — IETF / RFC Editor · tier 1 standards and regulators · Abstract; Section 3 (Vulnerability)
Cite this note
APA
WarmTransfer. (2026, September 25). SIP call forwarding and routing loops: source note sip-forwarding-loops-rfc5393-updates-3261. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-forwarding-loops-rfc5393-updates-3261
BibTeX
@misc{warmtransfer-claim-sip-forwarding-loops-rfc5393-updates-3261,
title = {SIP call forwarding and routing loops: source note sip-forwarding-loops-rfc5393-updates-3261},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-forwarding-loops-rfc5393-updates-3261},
note = {Source note sip-forwarding-loops-rfc5393-updates-3261, checked 2026-09-25}
}