Handle failures without assuming route truth
05Session and UPDATE errors require specified handling, and transport protection is distinct from route authorization.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 6 ↗
RFC 4271 · § 6EXAMPLE
3 / 3
03
Withdraw affected routes and recompute from remaining candidates.
Withdraw affected routes and recompute from remaining candidates.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
KEEPALIVEs and the Hold Timer detect a peer that stops communicating.
- KEEPALIVEs and the Hold Timer detect a peer that stops communicating.
- A syntactically valid AS_PATH does not cryptographically prove prefix ownership or path authorization.
RFC 7606 later revises UPDATE error handling. Follow updates rather than assuming every malformed UPDATE always requires the original full session reset.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy