RFC Errata
Found 5 records.
Status: Verified (2)
RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures", March 2017
Note: This RFC has been updated by RFC 8611, RFC 9041, RFC 9570
Source of RFC: mpls (rtg)
Errata ID: 7639
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Greg Mirsky
Date Reported: 2023-09-11
Verifier Name: Andrew Alston
Date Verified: 2023-11-12
Section 4.5 says:
If the Reply Mode in the echo request is "Reply via an IPv4 UDP packet with Router Alert", then the IP header MUST contain the Router Alert IP Option of value 0x0 [RFC2113] for IPv4 or 69 [RFC7506] for IPv6.
It should say:
If the Reply Mode in the echo request is "Reply via an IPv4/IPv6 UDP packet with Router Alert", then the IP header MUST contain the Router Alert IP Option of value 0x0 [RFC2113] for IPv4 or 69 [RFC7506] for IPv6.
Notes:
The description of the Reply Mode recorded in the IANA "Reply Modes" sub-registry of the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry is "Reply via an IPv4/IPv6 UDP packet with Router Alert".
Errata ID: 7892
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Loa Andersson
Date Reported: 2024-04-15
Verifier Name: James Guichard
Date Verified: 2024-04-16
Throughout the document, when it says:
Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
It should say:
Detecting Multiprotocol Label Switched Data-Plane Failures or Detecting Multiprotocol Label Switching (MPLS) Data-Plane Failures.
Notes:
MPLS expands to "Multiprotocol Label Switching", not to "Multiprotocol Label Switched".
Either we can remove the abbreviation in the title or s/Switched/Switching, either of the
alternatives work.
Status: Reported (1)
RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures", March 2017
Note: This RFC has been updated by RFC 8611, RFC 9041, RFC 9570
Source of RFC: mpls (rtg)
Errata ID: 8788
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Adrian Farrel
Date Reported: 2026-02-27
Throughout the document, when it says:
3.4
Address Type
The Address Type indicates if the interface is numbered or
unnumbered. It also determines the length of the Downstream IP
Address and Downstream Interface fields. The Address Type is set
to one of the following values:
Type # Address Type
------ ------------
1 IPv4 Numbered
2 IPv4 Unnumbered
3 IPv6 Numbered
4 IPv6 Unnumbered
3.4
If the interface to the downstream LSR is unnumbered, the Address
Type MUST be IPv4 Unnumbered or IPv6 Unnumbered, the Downstream
Address MUST be the downstream LSR's Router ID, and the Downstream
Interface Address MUST be set to the index assigned by the
upstream LSR to the interface.
If an LSR does not know the IP address of its neighbor, then it
MUST set the Address Type to either IPv4 Unnumbered or IPv6
Unnumbered. For IPv4, it must set the Downstream Address to
127.0.0.1; for IPv6, the address is set to 0::1. In both cases,
the interface index MUST be set to 0. If an LSR receives an Echo
Request packet with either of these addresses in the Downstream
Address field, this indicates that it MUST bypass interface
verification but continue with label validation.
If the originator of an echo request packet wishes to obtain
Downstream Detailed Mapping information but does not know the
expected label stack, then it SHOULD set the Address Type to
either IPv4 Unnumbered or IPv6 Unnumbered. For IPv4, it MUST set
the Downstream Address to 224.0.0.2; for IPv6, the address MUST be
set to FF02::2. In both cases, the interface index MUST be set to
0. If an LSR receives an echo request packet with the all-routers
multicast address, then this indicates that it MUST bypass both
interface and label stack validation but return Downstream Mapping
TLVs using the information provided.
3.6
Address Type
The Address Type indicates if the interface is numbered or
unnumbered. It also determines the length of the IP Address and
Interface fields. The resulting total for the initial part of the
TLV is listed in the table below as "K Octets". The Address Type
is set to one of the following values:
Type # Address Type K Octets
------ ------------ --------
0 Reserved 4
1 IPv4 Numbered 12
2 IPv4 Unnumbered 12
3 IPv6 Numbered 36
4 IPv6 Unnumbered 24
5-250 Unassigned
251-254 Reserved for Experimental Use
255 Reserved
3.7
If the interface is unnumbered, the Address Type MUST be either
IPv4 Unnumbered or IPv6 Unnumbered, the IP Address MUST be the
LSR's Router ID, and the Interface MUST be set to the index
assigned to the interface.
6.2.4
If the interface is unnumbered, the Address Type MUST be either
IPv4 Unnumbered or IPv6 Unnumbered, the IP Address MUST be the
LSR's Router ID, and the Interface MUST be set to the index
assigned to the interface.
6.2.8
Value Meaning Reference
---------- ---------------------------------------- ---------
0 Reserved [RFC8029]
1 IPv4 Numbered [RFC8029]
2 IPv4 Unnumbered [RFC8029]
3 IPv6 Numbered [RFC8029]
4 IPv6 Unnumbered [RFC8029]
5-250 Unassigned
251-254 Experimental Use [RFC8029]
255 Reserved [RFC8029]
A.2
Type # Address Type K Octets
------ ------------ --------
1 IPv4 Numbered 16
2 IPv4 Unnumbered 16
3 IPv6 Numbered 40
4 IPv6 Unnumbered 28
5 Non IP 12
A.2
If the interface to the downstream LSR is unnumbered, the Address
Type MUST be IPv4 Unnumbered or IPv6 Unnumbered, the Downstream IP
Address MUST be the downstream LSR's Router ID, and the Downstream
Interface Address MUST be set to the index assigned by the
upstream LSR to the interface.
If an LSR does not know the IP address of its neighbor, then it
MUST set the Address Type to either IPv4 Unnumbered or IPv6
Unnumbered. For IPv4, it must set the Downstream IP Address to
127.0.0.1; for IPv6, the address is set to 0::1. In both cases,
the interface index MUST be set to 0. If an LSR receives an Echo
Request packet with either of these addresses in the Downstream IP
Address field, this indicates that it MUST bypass interface
verification but continue with label validation.
If the originator of an echo request packet wishes to obtain
Downstream Mapping information but does not know the expected
label stack, then it SHOULD set the Address Type to either IPv4
Unnumbered or IPv6 Unnumbered. For IPv4, it MUST set the
Downstream IP Address to 224.0.0.2; for IPv6, the address MUST be
set to FF02::2. In both cases, the interface index MUST be set to
0. If an LSR receives an echo request packet with the all-routers
multicast address, then this indicates that it MUST bypass both
interface and label stack validation, but return Downstream
Mapping TLVs using the information provided.
It should say:
3.4
Address Type
The Address Type indicates if the interface is numbered or
unnumbered. It also determines the length of the Downstream IP
Address and Downstream Interface fields. The Address Type is set
to one of the following values:
Type # Address Type
------ ------------
1 IPv4 Numbered
2 IPv4 Unnumbered
3 IPv6 Numbered
4 Deprecated
3.4
If the interface to the downstream LSR is unnumbered, the Address
Type MUST be IPv4 Unnumbered, the Downstream
Address MUST be the downstream LSR's Router ID, and the Downstream
Interface Address MUST be set to the index assigned by the
upstream LSR to the interface.
If an LSR does not know the IP address of its neighbor, then it
MUST set the Address Type to IPv4 Unnumbered.
For IPv4, it must set the Downstream Address to
127.0.0.1. In both cases,
the interface index MUST be set to 0. If an LSR receives an Echo
Request packet with this address in the Downstream
Address field, this indicates that it MUST bypass interface
verification but continue with label validation.
If the originator of an echo request packet wishes to obtain
Downstream Detailed Mapping information but does not know the
expected label stack, then it SHOULD set the Address Type to
IPv4 Unnumbered. It MUST set
the Downstream Address to 224.0.0.2.
In this case, the interface index MUST be set to
0. If an LSR receives an echo request packet with the all-routers
multicast address, then this indicates that it MUST bypass both
interface and label stack validation but return Downstream Mapping
TLVs using the information provided.
3.6
Address Type
The Address Type indicates if the interface is numbered or
unnumbered. It also determines the length of the IP Address and
Interface fields. The resulting total for the initial part of the
TLV is listed in the table below as "K Octets". The Address Type
is set to one of the following values:
Type # Address Type K Octets
------ ------------ --------
0 Reserved 4
1 IPv4 Numbered 12
2 IPv4 Unnumbered 12
3 IPv6 Numbered 36
4 Deprecated 24
5-250 Unassigned
251-254 Reserved for Experimental Use
255 Reserved
3.7
If the interface is unnumbered, the Address Type MUST be
IPv4 Unnumbered, the IP Address MUST be the
LSR's Router ID, and the Interface MUST be set to the index
assigned to the interface.
6.2.4
If the interface is unnumbered, the Address Type MUST be
IPv4 Unnumbered, the IP Address MUST be the
LSR's Router ID, and the Interface MUST be set to the index
assigned to the interface.
6.2.8
Value Meaning Reference
---------- ---------------------------------------- ---------
0 Reserved [RFC8029]
1 IPv4 Numbered [RFC8029]
2 IPv4 Unnumbered [RFC8029]
3 IPv6 Numbered [RFC8029]
4 Deprecated [RFC8029]
5-250 Unassigned
251-254 Experimental Use [RFC8029]
255 Reserved [RFC8029]
A.2
Type # Address Type K Octets
------ ------------ --------
1 IPv4 Numbered 16
2 IPv4 Unnumbered 16
3 IPv6 Numbered 40
4 Deprecated 24
5 Non IP 12
A.2
If the interface to the downstream LSR is unnumbered, the Address
Type MUST be IPv4 Unnumbered, the Downstream IP
Address MUST be the downstream LSR's Router ID, and the Downstream
Interface Address MUST be set to the index assigned by the
upstream LSR to the interface.
If an LSR does not know the IP address of its neighbor, then it
MUST set the Address Type to IPv4 Unnumbered.
It must set the Downstream IP Address to
127.0.0.1. In this case,
the interface index MUST be set to 0. If an LSR receives an Echo
Request packet with this address in the Downstream IP
Address field, this indicates that it MUST bypass interface
verification but continue with label validation.
If the originator of an echo request packet wishes to obtain
Downstream Mapping information but does not know the expected
label stack, then it SHOULD set the Address Type to IPv4
Unnumbered. It MUST set the
Downstream IP Address to 224.0.0.2.
In this case, the interface index MUST be set to
0. If an LSR receives an echo request packet with the all-routers
multicast address, then this indicates that it MUST bypass both
interface and label stack validation, but return Downstream
Mapping TLVs using the information provided.
Notes:
There is no such thing as an "IPv6 unnumbered interface".
Description of this should be removed from the document and the code points marked as "Deprecated".
(Note that A2 had the K Octets value mismatched with Section 3.6)
Obviously (?) this report can only be "Held for Document Update"
Status: Held for Document Update (2)
RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures", March 2017
Note: This RFC has been updated by RFC 8611, RFC 9041, RFC 9570
Source of RFC: mpls (rtg)
Errata ID: 5102
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alexander Okonnikov
Date Reported: 2017-08-30
Held for Document Update by: Deborah Brungard
Date Held: 2017-12-12
Section 3.2.5 says:
VPN-IPv4 Network Layer Routing Information (NLRI) is defined in [RFC4365].
It should say:
VPN-IPv4 Network Layer Routing Information (NLRI) is defined in [RFC4364].
Notes:
Incorrect reference.
Errata ID: 5103
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alexander Okonnikov
Date Reported: 2017-08-30
Held for Document Update by: Deborah Brungard
Date Held: 2017-12-12
Section 3.2.6 says:
VPN-IPv6 NLRI is defined in [RFC4365].
It should say:
VPN-IPv6 NLRI is defined in [RFC4659].
Notes:
Incorrect reference.