CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 02:42:59 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=pAS9KR2jz4ZFfeTDl2SPSXww783IKbGEejYsAR.1keE-1760150579-1.0.1.1-hIrBMiky5EuFNebtmW_ObBtt8uCFvFr68Howz2uUOcAIRy8dGqum1JXY4urez7wuan6R0P6mCttGC_hsHepYX4IPekxg.E9vdbV5A5m2OiU; path=/; expires=Sat, 11-Oct-25 03:12:59 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cb01d89fd2c537-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5881 » RFC Editor
Search RFCs
RFC 5881
Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop), June 2010
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5881
Discuss this RFC: Send questions or comments to the mailing list rtg-bfd@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5881
Abstract
This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over IPv4 and IPv6 for single IP hops. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us