CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 20:20:31 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=b4JEFNhOKLsxrdeFClp2mvGDf0xZilGJAXBTK9EInVo-1760127631-1.0.1.1-9QOeqpUvpCgjhkDA.CY.B9_QwSD9xgXHEvrOBIfCpK6lMn9Ki4Ikn4AmkasIze1FPt6IKfICPw8bqz42uVBtVcG4RsxahvWv_SPNExLDFaQ; path=/; expires=Fri, 10-Oct-25 20:50:31 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c8d1975c9ad86d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5883 » RFC Editor
Search RFCs
RFC 5883
Bidirectional Forwarding Detection (BFD) for Multihop Paths, June 2010
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5883
Discuss this RFC: Send questions or comments to the mailing list rtg-bfd@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5883
Abstract
This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over multihop paths, including unidirectional links. [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