I can't believe I've waited this long to create this stupid shell function:
```
rfc() {
local rfc="rfc${1##rfc}";
curl -s "https://www.rfc-editor.org/rfc/${rfc}.txt" | ${PAGER:-more}
}
```
I can't believe I've waited this long to create this stupid shell function:
```
rfc() {
local rfc="rfc${1##rfc}";
curl -s "https://www.rfc-editor.org/rfc/${rfc}.txt" | ${PAGER:-more}
}
```
@jschauma Mine also opens the index if you say `rfc index`.
(I also have them local via the rsync download which I suppose is less important than it was ten years ago.)
@partim Yeah, I started out with a local copy of all RFCs as well.
For others stumbling on this thread:
https://www.rfc-editor.org/retrieve/rsync/
E.g., from cron:
0 0 1 * * rsync -az --include '*.txt' --exclude '*' rsync.rfc-editor.org::rfcs-text-only /usr/local/share/rfcs/.
@jschauma When you want it in plain text for the canonical document, great!
Invoking a browser with the URL https://datatracker.ietf.org/doc/html/rfc1925 has a view that includes things like a clickable table of contents. I tend to use the "open" shortcut on mac for this.
This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
@jschauma I'm never sure how much self-promotion is appropriate for this, but: https://github.com/paulehoffman/ietf-cli
rfc, draft (with partial name), tracker (for almost anything there), and so on. Issues and PRs welcome (but I admit my Python style here is a tad twee).
@jschauma
same but with a better navigation!
Heh. I had something similar in my .bashrc for a long time.
A couple of years ago, I upgraded to https://github.com/bfontaine/rfc