RFC Errata
RFC 2328, "OSPF Version 2", April 1998
Note: This RFC has been updated by RFC 5709, RFC 6549, RFC 6845, RFC 6860, RFC 7474, RFC 8042, RFC 9355, RFC 9454
Source of RFC: ospf (rtg)
Errata ID: 5956
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Marcelo Bustani
Date Reported: 2020-01-08
Rejected by: Alvaro Retana
Date Rejected: 2020-03-18
Section 12.4.1 says:
Router-LSAs If the state of the interface is Loopback, add a Type 3 link (stub network) as long as this is not an interface to an unnumbered point-to-point network. The Link ID should be set to the IP interface address, the Link Data set to the mask 0xffffffff (indicating a host route), and the cost set to 0. =================================== 12.4.1.4. Describing Point-to-MultiPoint interfaces For operational Point-to-MultiPoint interfaces, one or more link descriptions are added to the router-LSA as follows: o A single Type 3 link (stub network) is added with Link ID set to the router's own IP interface address, Link Data set to the mask 0xffffffff (indicating a host route), and cost set to 0. ============================================================================= C.3 Router interface parameters Interface output cost The cost of sending a packet on the interface, expressed in the link state metric. This is advertised as the link cost for this interface in the router's router-LSA. The interface output cost must always be greater than 0.
It should say:
"cost set to 0" to at least "greater than 0"
Notes:
The section 12.4.1 and 12.4.1.4 are inconsistent with the appendix c.3.
These both section we find the cost to stub networks have to be set to 0, but in appendix c.3 we see that the interfaces must have greater than 0.
--VERIFIER NOTES--
A discussion on the WG list (lsr) resulted a consensus of no change needed.
https://mailarchive.ietf.org/arch/msg/lsr/FFiqi15XPunSwOV5BO1pl4o5xYY/