RFC Errata
Found 4 records.
Status: Held for Document Update (3)
RFC 8960, "A YANG Data Model for MPLS Base", December 2020
Source of RFC: mpls (rtg)
Errata ID: 7059
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Jan Lindblad
Date Reported: 2022-07-29
Held for Document Update by: James N Guichard
Date Held: 2023-05-31
Section 2.5 says:
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" {
description
"Augments the 'simple-next-hop' case in IP unicast routes.";
uses nhlfe-single-contents {
when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route"
+ "/mpls:mpls-enabled = 'true'";
}
}
It should say:
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" {
description
"Augments the 'simple-next-hop' case in IP unicast routes.";
uses nhlfe-single-contents {
when "../../../mpls:mpls-enabled = 'true'";
}
}
Notes:
The original YANG statements make the "uses" statement apply to all rt:rib and all rt:route instances as soon as there is at least one instance that has mpls:mpls-enabled set to true. I suspect this is not the author's intent.
The corrected YANG statements make the "uses" statement only apply to the specific route instances that have mpls:mpls-enabled set to true. There are also other ways to fix this issue.
Errata ID: 7060
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Jan Lindblad
Date Reported: 2022-07-29
Held for Document Update by: James N Guichard
Date Held: 2023-05-31
Section 2.5 says:
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:next-hop-list/"
+ "rt:next-hop-list/rt:next-hop" {
description
"This leaf augments the 'next-hop-list' case of IP unicast
routes.";
uses nhlfe-multiple-contents {
when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route"
+ "/mpls:mpls-enabled = 'true'";
}
}
It should say:
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:next-hop-list/"
+ "rt:next-hop-list/rt:next-hop" {
description
"This leaf augments the 'next-hop-list' case of IP unicast
routes.";
uses nhlfe-multiple-contents {
when "../../../../../mpls:mpls-enabled = 'true'";
}
}
Notes:
The original YANG statements make the "uses" statement apply to all rt:rib and all rt:route instances as soon as there is at least one instance that has mpls:mpls-enabled set to true. I suspect this is not the author's intent.
The corrected YANG statements make the "uses" statement only apply to the specific route instances that have mpls:mpls-enabled set to true. There are also other ways to fix this issue.
Errata ID: 8333
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: John Scudder
Date Reported: 2025-03-17
Held for Document Update by: John Scudder
Date Held: 2025-03-17
Section 2.2 says:
2. The operation to perform on the packet's label stack. This can
be one of the following operations:
It should say:
2. The operation to perform on the packet's label stack which
is implicitly derived from the mpls-label-stack container
(in nhlfe-single-contents/nhlfe-multiple-contents) and the
"mpls-local-label" leaf. This can be one of the following
operations:
Notes:
A previous erratum, number 7944, was opened and ultimately closed as erroneous. In the discussion of that erratum, https://mailarchive.ietf.org/arch/msg/mpls/hzb3iO0Mn_Z4eyaPiUkMig_8JkE/ the clarification found in this report was suggested.
Status: Rejected (1)
RFC 8960, "A YANG Data Model for MPLS Base", December 2020
Source of RFC: mpls (rtg)
Errata ID: 7944
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Erik Kline
Date Reported: 2024-05-19
Rejected by: John Scudder
Date Rejected: 2025-03-17
Section 2.5 says:
grouping nhlfe-single-contents {
description
"A grouping that describes a single Next Hop Label Forwarding
Entry (NHLFE) and its associated parameters as described in
the MPLS architecture. This grouping is specific to the case
when a single next hop is associated with the route.";
uses rt-types:mpls-label-stack;
}
It should say:
grouping nhlfe-single-contents {
description
"A grouping that describes a single Next Hop Label Forwarding
Entry (NHLFE) and its associated parameters as described in
the MPLS architecture. This grouping is specific to the case
when a single next hop is associated with the route.";
<some reference to an mpls-operations-type>
uses rt-types:mpls-label-stack;
}
Notes:
Section 2.2 states that the NHLFE contains the packet's next hop and "[t]he operation to perform on the packet's label stack."
Section 2.5 defines an mpls-operations-type typedef, but then it is never referenced by anything else in the YANG module.
I *think* it should be associated with nhlfe-single-contents, alongside the rt-types:mpls-label-stack used there. My YANG skills are too poor to craft any plausibly correct syntax, though.
--VERIFIER NOTES--
See https://mailarchive.ietf.org/arch/msg/mpls/hzb3iO0Mn_Z4eyaPiUkMig_8JkE/