errata logo graphic

Found 6 records.

Status: Verified (6)

RFC6325, "Routing Bridges (RBridges): Base Protocol Specification", July 2011

Source of RFC: trill (int)

Errata ID: 3002

Status: Verified
Type: Technical

Reported By: Donald E. Eastlake, 3rd
Date Reported: 2011-10-25
Verifier Name: Ralph Droms
Date Verified: 2013-03-09

Section 3.7.3 says:

                                   If RB1 chooses nickname x, and RB1
      discovers, through receipt of an LSP for RB2 at any later time,
      that RB2 has also chosen x, then the RBridge or pseudonode with
      the numerically higher IS-IS ID (LAN ID) keeps the nickname, or if
      there is a tie in priority, the RBridge with the numerically
      higher IS-IS System ID keeps the nickname, and the other RBridge
      MUST select a new nickname.

It should say:

If RB1
chooses nickname x, and RB1 discovers, through receipt of an LSP for
RB2 at any later time, that RB2 has also chosen x, then the RBridge or
pseudonode with the numerically higher priority keeps the nickname, or
if there is a tie in priority, the RBridge with the numerically higher
seven-byte IS-IS ID (LAN ID) keeps the nickname, and the other RBridge
MUST select a new nickname.

Notes:

Comparison is primarily by priority and then by IS-IS ID. Since pseudonodes can hold nicknames, the comparison must be by seven-byte IS-IS ID, not six-byte System ID.


Errata ID: 3003

Status: Verified
Type: Technical

Reported By: Donald E. Eastlake, 3rd
Date Reported: 2011-10-25
Verifier Name: Ralph Droms
Date Verified: 2013-03-09

Section 4.6.2 says:

   1. If the Outer.MacDA is All-IS-IS-RBridges and the Ethertype is
      L2-IS-IS, the frame is handled as described in Section 4.6.2.1.

It should say:

   1. If the Ethertype is L2-IS-IS and the Outer.MacDA is either
      All-IS-IS-RBridges or the unicast MAC address of the receiving 
      RBridge port, the frame is handled as described in Section 4.6.2.1

Notes:

TRILL IS-IS MTU PDUs may be unicast as described in Section 4.3.2 of RFC 6325 and Section 5 of RFC 6327. This was not allowed for in the wording of Section 4.6.2 of RFC 6325 but is corrected above.


Errata ID: 3004

Status: Verified
Type: Technical

Reported By: Donald E. Eastlake, 3rd
Date Reported: 2011-10-25
Verifier Name: Ralph Droms
Date Verified: 2013-03-09

Section 4.3.2 says:

                                    The MTU-probe MAY be multicast to
   All-RBridges, or unicast to a specific RBridge.  The MTU-ack is
   normally unicast to the source of the MTU-probe to which it responds
   but MAY be multicast to All-RBridges.

It should say:

                                     The MTU-probe MUST be multicast to
   All-IS-IS-RBridges or unicast to a specific RBridge.  The MTU-ack is
   normally unicast to the source of the MTU-probe to which it responds
   but MAY be multicast to All-IS-IS-RBridges.

Notes:

TRILL IS-IS MTU PDUs are IS-IS PDUs and, when multicast, must be sent to the All-IS-IS-RBridges multicast address.


Errata ID: 3052

Status: Verified
Type: Technical

Reported By: Donald E. Eastlake, 3rd
Date Reported: 2011-12-15
Verifier Name: Ralph Droms
Date Verified: 2013-03-09

Section 4.5.2 says:

(up to the maximum of {j,k})

It should say:

(up to k if j is zero or the minimum of ( j, k) if j is
non-zero)

Errata ID: 3053

Status: Verified
Type: Technical

Reported By: Donald E. Eastlake, 3rd
Date Reported: 2011-12-15
Verifier Name: Ralph Droms
Date Verified: 2013-03-09

Section 4.3.2 says:

If X is not greater than Sz, then RB1 sets the "failed minimum MTU
test" flag for RB2 in RB1's Hello. If size X succeeds, and X > Sz,
then RB1 advertises the largest tested X for each adjacency in the
TRILL Hellos RB1 sends on that link, and RB1 MAY advertise X as an
attribute of the link to RB2 in RB1's LSP.

It should say:

If X is not greater than or equal to Sz, then RB1 sets the "failed
minimum MTU test" flag for RB2 in RB1's Hello. If size X succeeds, and
X >= Sz, then RB1 advertises the largest tested X for each adjacency
in the TRILL Hellos RB1 sends on that link, and RB1 MAY advertise X as
an attribute of the link to RB2 in RB1's LSP.

Errata ID: 3508

Status: Verified
Type: Technical

Reported By: Donald E. Eastlake, 3rd
Date Reported: 2013-03-05
Verifier Name: Ralph Droms
Date Verified: 2013-03-09

Section 4.5.1 says:

In other words, the set of potential parents for N, for the tree
rooted at R, consists of those that give equally minimal cost paths
from N to R and that have distinct IS-IS IDs, based on what is
reported in LSPs.

It should say:

In other words, the set of potential parents for N, for the tree 
rooted at R, consists of those that give equally minimal cost paths 
from R to N and that have distinct IS-IS IDs, based on what is 
reported in LSPs.

Notes:

Link costs can be asymmetric. The above erroneous sentence is inconsistent with the rest of 4.5.1 and normal practice. Furthermore, it is important to fix this and resolve the inconsistency because, if all RBridges in a TRILL campus do not compute the same trees, the reverse path forwarding check for multi-destination TRILL Data packet routing can erroneously discard such packets.


Report New Errata