RFC 3550 defines the cumulative number of packets lost relative to the packets expected, so the value can be negative when duplicate packets arrive.
Checked 2026-09-24
- Vendor
- IETF
- Product
- RTP
- Subsystem
- RTCP report blocks
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3550
- Checked
- 2026-09-24
Sources
- RFC 3550 RTP: A Transport Protocol for Real-Time Applications — IETF / RFC Editor · tier 1 standards and regulators · Section 6.4.1, 'cumulative number of packets lost' field definition
Cite this note
APA
WarmTransfer. (2026, September 24). SIP capture and analysis with Wireshark and sngrep and HOMER: source note sip-capture-analysis-rfc3550-lost-negative. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-capture-analysis-rfc3550-lost-negative
BibTeX
@misc{warmtransfer-claim-sip-capture-analysis-rfc3550-lost-negative,
title = {SIP capture and analysis with Wireshark and sngrep and HOMER: source note sip-capture-analysis-rfc3550-lost-negative},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-capture-analysis-rfc3550-lost-negative},
note = {Source note sip-capture-analysis-rfc3550-lost-negative, checked 2026-09-24}
}