RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Held for Document Update (1)

RFC 5003, "Attachment Individual Identifier (AII) Types for Aggregation", September 2007

Source of RFC: pwe3 (int)

Errata ID: 3411

Status: Held for Document Update
Type: Technical

Reported By: Rajiv Asati
Date Reported: 2012-11-15
Held for Document Update by: Brian Haberman

Section 3.2 says:


     o Prefix = The 32-bit prefix is a value assigned by the provider or
       it can be automatically derived from the PE's /32 IPv4 loopback
       address.  Note that, for IP reachability, it is not required that
       the 32-bit prefix have any association with the IPv4 address
       space used in the provider's IGP or BGP.

It should say:


     o Prefix = The 32-bit prefix is a value assigned by the provider or
       it can be automatically derived from the PE's router-id i.e. LSR Id.
       Note that it is not required that
       the 32-bit prefix is IP routable or have any association with the 
       IPv4 address space used in the provider's IGP or BGP. 

Notes:

The intent of this RFC is to treat the 32bit prefix as a number that provides uniqueness in the network (within the ASN). While it can be derived from the IPv4 /32 Loopback address, it causes confusion when routers are configured with no IPv4. It is better to suggest using router-id used by LDP for calculating the LSR identifier. How is router-id calculated is outside the scope of this document.`

Report New Errata