The Abstract and Introduction sections of the RFC [0] explain what the point of this is. The "Changes Compared to RFC 5549" section is especially good reading, as it both alerts you to the fact that this is an update to a seventeen year old RFC and explains what changed in the update.
RFC 8950 is quietly useful for operators who want to drop IPv4 addresses from point-to-point links and run an IPv6-only fabric while still carrying IPv4 routes over BGP. How well is it supported in practice across vendors and open-source routing daemons like FRR and BIRD?
https://www.rfc-editor.org/info/rfc8950/
I guess the point with this to facilitate usage of IPv6.
The Abstract and Introduction sections of the RFC [0] explain what the point of this is. The "Changes Compared to RFC 5549" section is especially good reading, as it both alerts you to the fact that this is an update to a seventeen year old RFC and explains what changed in the update.
[0] <https://datatracker.ietf.org/doc/html/rfc8950>
RFC 8950 is quietly useful for operators who want to drop IPv4 addresses from point-to-point links and run an IPv6-only fabric while still carrying IPv4 routes over BGP. How well is it supported in practice across vendors and open-source routing daemons like FRR and BIRD?
Your comment was flagged, I vouched it