-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update EIP-1: Add IETF as a permissible origin #7113
Conversation
File
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks for following up on this since I never got back to it. I'll convert mine to focus just on WHATWG since I'm going to what to reference it in EIP-6963
sounds good 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, I think we should ensure that EIP authors use the right reference (RFC X
)
@@ -252,6 +252,24 @@ Permitted Networking Specifications URLs must anchor to a specific commit, and s | |||
^https://github.com/ethereum/devp2p/blob/[0-9a-f]{40}/.*$ | |||
``` | |||
|
|||
### Internet Engineering Task Force (IETF) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, would mildly prefer thr following:
### Internet Engineering Task Force (IETF) | |
### IETF Request for Comments (RFC) |
Originally from #6691 by @kdenhartog.
Splitting out so it can be discussed separately.
Changed slightly with my review feedback.