RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 6 records.

Status: Verified (3)

RFC 4684, "Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)", November 2006

Source of RFC: l3vpn (int)

Errata ID: 18

Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: RFC Editor
Date Reported: 2006-11-28
Report Text:

This RFC was briefly posted with a misspelling in the title.
It was reposted with "Internet Protcol" corrected to "Internet Protocol".

Errata ID: 964
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Tom Petch
Date Reported: 2006-11-29

Section 6 says: 

withdrawls

It should say:

withdrawals

Notes:

from pending

Errata ID: 6246
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Robert Raszuk
Date Reported: 2020-07-31
Verifier Name: Eric Vyncke
Date Verified: 2021-02-08

Section 4 says: 

 This prefix is structured as follows:

        +-------------------------------+
        | origin as        (4 octets)   |
        +-------------------------------+
        | route target     (8 octets)   |
        +                               +
        |                               |
        +-------------------------------+

It should say:

 This prefix is structured as follows:

        +-------------------------------+
        | origin as       (4 octets)    |
        +-------------------------------+
        | route target   (0-8 octets)   |
        +                               +
        |                               |
        +-------------------------------+

Notes:

The text defines route target as prefix however figure in section 4 does not reflect this correctly. This is editorial change, but apparently causing a lot of confusion in the community.

-- Verifier note --
The submitter is one of the author and the original text causes confusion, it is marked as verified.

Status: Held for Document Update (2)

RFC 4684, "Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)", November 2006

Source of RFC: l3vpn (int)

Errata ID: 962
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Tom Petch
Date Reported: 2006-11-29
Held for Document Update by: Brian Haberman

Section 3.2 says: 

and the Next-hop attribute shall be set of the local
address for that session.

It should say:

[see below]

Notes:

Changing 'set of' to 'set to' does not help as it begs the question what
session? Route reflectors have BGP sessions with route reflector clients, other
route reflectors and with other BGP speakers that are not involved with route
reflection. Looking at the I-D, this is precisely the end of a line and I
wonder if it is a line or two of text that has gone missing. So change of to to
and I might raise an erratum on the grounds that it does not make sense:-)

from pending

Errata ID: 963
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Tom Petch
Date Reported: 2006-11-29
Held for Document Update by: Brian Haberman

Section 4 says: 

As the origin-as field cannot be interpreted as a prefix.

It should say:

[see below]

Notes:

I cannot parse as a sentence (note that, in this memo, 'as' is sometimes the English conjunction, sometimes an abbreviation for Autonomous System)

from pending

Status: Rejected (1)

RFC 4684, "Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)", November 2006

Source of RFC: l3vpn (int)

Errata ID: 6226
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alexander ("Sasha") Vainshtein
Date Reported: 2020-07-09
Rejected by: Martin Vigoureux
Date Rejected: 2020-07-09

Section 4 says: 

   The NLRI field in the MP_REACH_NLRI and MP_UNREACH_NLRI is a prefix
   of 0 to 96 bits, encoded as defined in Section 4 of [5].

It should say:

   The NLRI field in the MP_REACH_NLRI and MP_UNREACH_NLRI is a prefix
   of 0 to 96 bits, encoded as defined in Section 5 of [5].

Notes:

Reference [5] points to RFC 4760.
Encoding of prefixes in NLRI is defined in Section 5 "NLRI Encoding" of this document and not it Section 4.
--VERIFIER NOTES--
[5] points to rfc2858, and Section 4 in that rfc is the correct section to look into.

Report New Errata



Advanced Search