RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 4090, "Fast Reroute Extensions to RSVP-TE for LSP Tunnels", May 2005

Source of RFC: mpls (rtg)

Errata ID: 4203
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Yakov Rekhter
Date Reported: 2014-12-17
Verifier Name: Alia Atlas
Date Verified: 2015-01-06

Section 6 says:

Whenever the PLR has a backup path available, the PLR MUST set
the "local protection available" flag.

It should say:

Whenever the PLR has a backup path available, the PLR MUST set
the "local protection available" flag.  For example, if the PLR 
has determined to use a bypass tunnel and set up the necessary 
local forwarding state to be able to use it as a backup path, 
then that PLR has a backup path available.

Notes:

In the case of facility-based FRR the PLR must set the "local protection available" flag if it has the bypass tunnel available and the local forwarding state is set up.

Status: Reported (1)

RFC 4090, "Fast Reroute Extensions to RSVP-TE for LSP Tunnels", May 2005

Source of RFC: mpls (rtg)

Errata ID: 6203
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Mihir Amrelia
Date Reported: 2020-06-03

Section 6 says:

If the "bandwidth protection guaranteed" flag is set, the PLR SHOULD try to
provide a bandwidth guarantee; if this is not feasible, the PLR SHOULD then try
to provide a backup without a guarantee of the full bandwidth.


It should say:

If the "Bandwidth Protection Desired" flag is set in SESSION_ATTRIBUTE, the PLR
SHOULD try to provide a bandwidth guarantee; if this is not feasible, the PLR
SHOULD then try to provide a backup without a guarantee of the full bandwidth.


Notes:

Correcting flag info to consider bandwidth protection.

Report New Errata