Search RFCs

RFC Editor

Found 2 records.

Status:Verified (1)

RFC 6107, "Procedures for Dynamically Signaled Hierarchical Label Switched Paths", February 2011

Errata ID:3018
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alan Davey
Date Reported: 2011-11-10
Verifier Name: Adrian Farrel
Date Verified: 2011-11-12

Section 3.2 says:

   If the P-flag in the Actions field in the LSP_TUNNEL_INTERFACE_ID   object in a Resv message is set (i.e., one) indicating that the LSP   is not to be advertised as a link, this TLV SHOULD NOT be present and   MUST be ignored if encountered.

It should say:

   If the P-flag in the Actions field in the LSP_TUNNEL_INTERFACE_ID   object in a Path message is set (i.e., one) indicating that the LSP   is not to be advertised as a link, this TLV SHOULD NOT be present and   MUST be ignored if encountered.

Notes:

The change is s/Resv/Path/

Status:Held for Document Update (1)

RFC 6107, "Procedures for Dynamically Signaled Hierarchical Label Switched Paths", February 2011

Errata ID:3412
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Kris Michielsen
Date Reported: 2012-11-16
Held for Document Update by: Adrian Farrel

Section 3.1.2 says:

           Type (16 bits)             The identifier of the TLV.  Two type values are defined in             this document:             1  IGP Instance Identifier TLV             2  Unnumbered Component Link Identifier TLV             3  IPv4 Numbered Component Link Identifier TLV             4  IPv6 Numbered Component Link Identifier TLV

It should say:

           Type (16 bits)             The identifier of the TLV.  Four type values are defined in             this document:             1  IGP Instance Identifier TLV             2  Unnumbered Component Link Identifier TLV             3  IPv4 Numbered Component Link Identifier TLV             4  IPv6 Numbered Component Link Identifier TLV

Notes:

s/Two/Four/

Report New Errata