Found 3 records.

Status: Reported (3)

RFC 8028, "First-Hop Router Selection by Hosts in a Multi-Prefix Network", November 2016

Errata ID: 6035
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Fernando Gont
Date Reported: 2020-04-01

Section 3.1 says:

It should say:

In the context of this document, it is clear that the prefix information becomes more associated with the sending router, than with the link as a whole. As such, the PIO lifetimes should be interpreted to indicate the view of the router sending the Router Advertisement, as opposed to absolute information about a prefix.

For example, if two routers (say, Router A and Router B), advertise the prefix 2001:db8::/64 as:

* Router A:
A=1, L=1, PIO: 2001:db8::/64, Valid Lifetime=0, Preferred Lifetime=0

* Router B:
A=1, L=1, PIO: 2001:db8::/64, Valid Lifetime=X, Preferred Lifetime=Z

then, addresses should be configured/maintained with a Valid Lifetime of X, and a Preferred Lifetime of Z. Furthermore, the prefix should be considered on-link with a Valid Lifetime of X.  And Router B should be employed as the preferred next hop for packets sourced from the prefix 2001:db8::/64, since it advertises the prefix with a non-zero Valid Lifetime and non-zero Preferred Lifetime (as opposed to Router A).

As long as one router on the local subnet considers a prefix to be Valid (and possibly Preferred), the prefix should be considered Valid (and Preferred, if applicable). Similarly, as long as one router on the local subnet considers the prefix to be on-link and/or usable for auto-configuration, the prefix should be considered as such.

Notes:

This is not a bug in RFC 8028, but rather a clarification on what's likely a desired behavior. As such, and if considered appropriate, this errata is meant to be "held for document update".

I would like to thank Fred Baker and Brian Carpenter for taking the time to answer my questions on RFC 8028.

Errata ID: 7009
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Brian Carpenter
Date Reported: 2022-06-30

Section Abstract says:

However, the selection of the source address for a
packet is done before the first-hop router for that packet is chosen.

It should say:

However, the selection of the source address for a
packet is done in some cases before the first-hop router
for that packet is chosen.

Notes:

This change recognizes the fact that while server applications commonly
bind to a specific source address before sending a packet, client
applications commonly do not do so. (Also see following erratum.)

Errata ID: 7010
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Brian Carpenter
Date Reported: 2022-06-30

Section 3.3 says:

There is an interaction with Default Address Selection [RFC6724].

It should say:

There is an interaction with Default Address Selection [RFC6724] in the
case that an application does not explicitly specify the source address
to be used.

Notes:

This change recognizes the fact that while server applications commonly
bind to a specific source address before sending a packet, client
applications commonly do not do so. (See previous erratum)

Report New Errata