Find the lower-layer gate
05Partial transport coverage helps only if an error-prone link supports suitable partial error detection. A packet dropped by the link never reaches UDP-Lite.
Separate ESP-encrypted packet: the link cannot inspect UDP-Lite coverage and requires the full check.
Source for this drawing: RFC 3828 · Read RFC section 4 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
Strong link integrity checking MUST be used by default for IP traffic (§1). A link without suitable partial detection MUST check the whole packet and discard damaged packets.
- Strong link integrity checking MUST be used by default for IP traffic (§1). A link without suitable partial detection MUST check the whole packet and discard damaged packets.
- A suitable lower layer MUST strongly check the sensitive part from the first IP-header octet through the end of the covered UDP-Lite prefix, and discard damage there. Coverage MAY be used as a hint.
- With ESP payload encryption hiding the transport, the link MUST check the entire IP packet and payload; UDP-Lite provides no benefit in that case (§6).
The partial-link path is a chosen supported policy, not a requirement that links forward errors. Encryption/authentication protections must not be removed to make damaged packets pass.
Read the RFC section ↗