RFC 8900 cites a measurement in which at least 28% of sampled paths did not convey packets containing the IPv6 Fragment extension header.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- IPv6 fragmentation
- Deployment
- on-premises, multi-tenant
- Region
- not restricted
- Release range
- BCP 230 as published; measurement predates 2020
- Checked
- 2026-10-02
Sources
- RFC 8900: IP Fragmentation Considered Fragile — RFC Editor (IETF) · tier 1 standards and regulators · Section 3.9
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc8900-ipv6-frag-28pct. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc8900-ipv6-frag-28pct
BibTeX
@misc{warmtransfer-claim-sip-fragmentation-troubleshooting-rfc8900-ipv6-frag-28pct,
title = {Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc8900-ipv6-frag-28pct},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc8900-ipv6-frag-28pct},
note = {Source note sip-fragmentation-troubleshooting-rfc8900-ipv6-frag-28pct, checked 2026-10-02}
}