RFC 8900 (BCP 230, September 2020) says developers SHOULD NOT develop new protocols or applications that rely on IP fragmentation.
Checked 2026-10-02
Developers SHOULD NOT develop new protocols or applications that rely on IP fragmentation.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- IP fragmentation
- Deployment
- on-premises, multi-tenant
- Region
- not restricted
- Release range
- BCP 230 as published
- Checked
- 2026-10-02
Sources
- RFC 8900: IP Fragmentation Considered Fragile — RFC Editor (IETF) · tier 1 standards and regulators · Section 6.1
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc8900-no-frag-reliance. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc8900-no-frag-reliance
BibTeX
@misc{warmtransfer-claim-sip-fragmentation-troubleshooting-rfc8900-no-frag-reliance,
title = {Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc8900-no-frag-reliance},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc8900-no-frag-reliance},
note = {Source note sip-fragmentation-troubleshooting-rfc8900-no-frag-reliance, checked 2026-10-02}
}