I don't disagree that /31 would be useful but i'd rather see the time spent on improving IPv6 support. The number of IPv6 networks we've been doing consulting work on in the last 12 months has skyrocketed. Once dual stack is in place, IPv4 public requirements don't disappear but are certainly diminished.
The only time you really need public IPv4 between routers is when handing off to another ASN, Customer, etc. IPv4 between routers internal to an ASN that would otherwise be public can easily be RFC6598 IP space from 100.64.0.0/10. We've deployed ISP, DC and Enterprise networks around the world with this space successfully for the last 10 years.
Google HQ uses it for campus, Century Link uses it for MPLS L3VPN assginments, TailScale uses it for VPN address assignments.
It's pretty much the new RFC1918.
![Very Happy :D](./images/smilies/icon_biggrin.gif)