CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 20:15:44 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=phn9c7p1gl9eed4h1i62uimsvm; path=/
set-cookie: __cf_bm=1hF1.1Ry5e1M8hAdlD7EPImI_hRjwVEG5UIme2SKk3U-1760213744-1.0.1.1-LvLSqjoY3hMPkQLIJAHAp.dRwzs.Ahi.VgOBbPL7MCJ.XOuUtHFzbCMDmTyxK3j790w5Ury62kbo29MYsfpOQ.DYAXOUM.SP7LJiCD9sv.0; path=/; expires=Sat, 11-Oct-25 20:45:44 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
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
server: cloudflare
cf-ray: 98d107f79bded817-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
Found 2 records.
Status: Held for Document Update (2)
RFC 7130, "Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces", February 2014
Source of RFC: bfd (rtg)
Errata ID: 5741
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Anoop Ghanwani
Date Reported: 2019-05-30
Held for Document Update by: Martin Vigoureux
Date Held: 2019-06-17
Section 1 says:
While there are native Ethernet mechanisms to detect failures (802.1ax, .3ah)
It should say:
While there are native Ethernet mechanisms to detect failures (802.1AX, 802.3ah)
Notes:
ax should be capitalized.
Errata ID: 5742
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Anoop Ghanwani
Date Reported: 2019-05-30
Held for Document Update by: Martin Vigoureux
Date Held: 2019-06-17
Section 2.3 says:
Micro-BFD packets SHOULD always be sent untagged. However, when the LAG is operating in the context of IEEE 802.1q or IEEE 802.qinq,
It should say:
Micro-BFD packets SHOULD always be sent untagged. However, when the LAG is operating in the context of IEEE 802.1Q or IEEE 802.1ad,
Notes:
q should be capitalized. The IEEE standard for QinQ is IEEE 802.1ad.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us