Greg Colvin

> @gcolvin is still your preferred apporach or did you switch to implementing static validation on top of EIP-2315, and this one should be just closed? I'm not concerned with...

I'm generally OK with this, but if would cause a less clutter as a footnote. I'd be even happier to make this a general policy that applies to all EIPs,...

> > I'd be even happier to make this a general policy that applies to all EIPs, and doesn't need to be repeated in every one of them. > >...

> 1. > If I was dictator... > What?! > > I am not involved in this EIP, but I find the statements above extremely worrying. How come no one...

Dear bot. Close this if you must, I suppose it will remain in the system. @axic asked that I make this PR here to lay out a proposed improvement to...

This is a draft for future discussion that mostly hasn't happened yet, @xinbenlv

Dear bot: discussion is ongoing.

@djrtwo Do you still want this merged? @lightclient Have the changes you requested been made?

There is also a good argument for _not_ copying RFCs. The RFC Editor maintains a canonical list at . For each RFC there is an Info page with TXT, PDF,...

> @gcolvin Where in the style guide does it say that third parties referring to RFCs should not include the raw text? @MicahZoltu It doesn't. It requires that links to...