I have gone through and updated all existing EIPs to match this rule, including EIP-1.
In some cases, people were using markdown citations, I suspect because the long-form was a bit verbose to inline. Since the relative path is quite short, I moved these to inline but I wouldn't be opposed to putting them back to citation format if that is desired by the authors.
In doing the migration/cleanup, I found some EIP references to EIPs that don't actually exist. In these cases I tried to excise the reference from the EIP as best I could.
It is worth noting that the Readme actually already had this rule, it just wasn't expressed properly in EIP-1 and the "Citation Format" section of the readme I think caused people a bit of confusion (when citing externally, you should use the citation format).
* Updated to Last Call
This Networking EIP is confirmed already active on the network. I will put it through Last Call to activate the RSS Feed.
* Update last call deadline to be 14 days from today
Co-authored-by: Alex Beregszaszi <alex@rtfs.hu>
* EIP 2124: Zero RTT netsplit on chain mismatch
* Assign number to EIP 2124
* Address review comments on EIP 2124.
* Rename EIP 2124 to better reflect content
* Fix cardinality
* Fix email address in 2124
* Update fork identifier EIP based on review discussions.
* Fixup EIP name for the fork identifier.
* Remove stale mention of ENR from forkid EIP.
* Add RLP encoding test cases for forkid EIP.
* Add Felix too to the forkid EIP author list.
* Get rid of mentioning the MTU stuffin the forkid EIP.
