Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use rfc-editor.org for IETF specs 8650+ #342

Closed
dontcallmedom opened this issue Jul 5, 2021 · 0 comments · Fixed by #349
Closed

Use rfc-editor.org for IETF specs 8650+ #342

dontcallmedom opened this issue Jul 5, 2021 · 0 comments · Fixed by #349

Comments

@dontcallmedom
Copy link
Member

dontcallmedom commented Jul 5, 2021 •
edited
Loading

As pointed out in the discussion on adding IETF specs, and starting from RFC8650, IETF RFCs get a much nicer HTML rendering on rfc-editor.org than they get on datatracker.ietf.org.

We should thus point toward these URLs (at least via nightly as we currently do for httpwg.org URLs?) at least for these RFCs - but maybe more generally.

This is probably a discussion that should start upstream in specref.
dontcallmedom added a commit to dontcallmedom/specref that referenced this issue Jul 5, 2021
@dontcallmedom
Use rfc-editor.org URLs instead of datatracker.ietf.org for IETF RFCs
50d4ca4 
Both are as authoritative as it gets, and from RFC8650 onwards, rfc-editor.org provide much nicer HTML rendering, as described in https://www.rfc-editor.org/format-live/

See also w3c/browser-specs#342
@dontcallmedom dontcallmedom mentioned this issue Jul 5, 2021
Merged
tobie pushed a commit to tobie/specref that referenced this issue Jul 12, 2021
@dontcallmedom
Use rfc-editor.org URLs instead of datatracker.ietf.org for IETF RFCs (…
bb72065 
…#676)

Both are as authoritative as it gets, and from RFC8650 onwards, rfc-editor.org provide much nicer HTML rendering, as described in https://www.rfc-editor.org/format-live/

See also w3c/browser-specs#342
dontcallmedom added a commit that referenced this issue Jul 12, 2021
@dontcallmedom
Switch RFC URLs to rfc-editor.org
bb1ca81 
close #342
@dontcallmedom dontcallmedom mentioned this issue Jul 12, 2021
Merged
tidoust pushed a commit that referenced this issue Jul 12, 2021
@dontcallmedom
Switch RFC URLs to rfc-editor.org (#349)
95794a4 
close #342
dontcallmedom added a commit to dontcallmedom/browser-compat-data that referenced this issue Jul 12, 2021
@dontcallmedom
Use rfc-editor.org as URL targets for IETF RFCs
93f1863 
Starting from 8650, they're much more readable on rfc-editor.org than on datatracker.ietf.org; browser-specs is aligning to using this as the default target w3c/browser-specs#342
@dontcallmedom dontcallmedom mentioned this issue Jul 12, 2021
Merged
Elchi3 pushed a commit to mdn/browser-compat-data that referenced this issue Jul 13, 2021
@dontcallmedom
Use rfc-editor.org as URL targets for IETF RFCs (#11488)
c44db14 
Starting from 8650, they're much more readable on rfc-editor.org than on datatracker.ietf.org; browser-specs is aligning to using this as the default target w3c/browser-specs#342
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch RFC URLs to rfc-editor.org w3c/browser-specs
1 participant
@dontcallmedom