Skip to content
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.

IETF RFCs #18

Open
jbenet opened this issue Sep 15, 2015 · 17 comments
Open

IETF RFCs #18

jbenet opened this issue Sep 15, 2015 · 17 comments
Labels

Comments

@jbenet
Copy link
Contributor

jbenet commented Sep 15, 2015

All RFCs! \o/

@jbenet jbenet mentioned this issue Sep 15, 2015
@eminence
Copy link
Collaborator

As a start, I've copied the .txt versions of all RFCs here:

QmNdozNckkKUAC2YfTLDMyASRsF8bKpyYgZrBR1Syiv2XK

Using this hacky python script: QmWg26A8LRR7tvHkKXRM7r9ZVPgAACudd5qs2LobjbtWaH

Edit: See below for more recent versions of this archive

@davidar
Copy link
Collaborator

davidar commented Sep 16, 2015

@eminence Awesome, thankyou. Pinning now :)

@rht
Copy link

rht commented Sep 16, 2015

There is ftp link updated weekly here https://www.rfc-editor.org/download.html, which can be updated with rsync.

@davidar
Copy link
Collaborator

davidar commented Sep 16, 2015

@rht yeah, we need an ipfs-rsync tool that can automate the update process, i.e.

$ ipfs-rsync ftp.rfc-editor.org::rfcs-text-only <old-hash>
Updated X files using Y MB.
Added to <new-hash>

Edit: wouldn't it be cool if there was a language where that ^ was actually the program :)

@rht
Copy link

rht commented Sep 16, 2015

(That intersects with gx, dag versioning(, dat?))

@eminence
Copy link
Collaborator

Thanks for the pointer about the download bundle. I was foolish and didn't even bother to look for it last night.

The download bundle includes .pdf and .ps versions, which I've now included. The new root is QmeZnaoktRvs3Ek8pQNyj8BbrkKuJ5Ez6JHi32dazL7cEJ

At this point, I'm not sure what the best way to mark the previous hash as obsolete (other than editing my github comment, which I've done)

@jbenet
Copy link
Contributor Author

jbenet commented Sep 16, 2015

@eminence this is great!

@ion1
Copy link

ion1 commented Sep 16, 2015

Here’s a command that replicates the same directory structure:

% rsync -Pav --delete -f '+ /rfc-index.txt' -f '+ /rfc[0-9]*' -f '- *' ftp.rfc-editor.org::rfcs/ rfcs/ && ipfs add -r rfcs 
…
added Qmew9eTZSvPPJVZcv9WLdH7VJ9nKe4QVxxsi4iSLXNhkrq rfcs

(They have added three new RFCs since the previous pointer.)

@eminence
Copy link
Collaborator

Thanks @ion for that useful rsync command. I've updated the RFC directory, and have published it under my peer name. I will endeavor to keep it up-to-date.

The new location for these is now the follow IPNS URL (which should remain unchanged as this folder is updated)

http://ipfs.io/ipns/QmbuG3dYjX5KjfAMaFQEPrRmTRkJupNUGRn1DXCgKK5ogD/archives/RFCs

@jbenet
Copy link
Contributor Author

jbenet commented Sep 17, 2015

nice! we're in the middle of fixing ipns so you can have more keys, too

related to #5

@eminence
Copy link
Collaborator

Here's a simple front-end to the RFC archive

http://ipfs.io/ipfs/Qmee6stB1LMDBnguijenmhk9eMeqi1er8L5CjFiuut1LJL/frontend.html

@ghost
Copy link

ghost commented Dec 14, 2015

This is pretty cool! I thought there'd be no RFCs though, until I used the search :)

@rht
Copy link

rht commented Jan 16, 2017

It appears that the copyright license for the RFCs since nov 10 2008 is spec-ed in https://tools.ietf.org/html/rfc5378.

@leerspace
Copy link
Contributor

leerspace commented Mar 11, 2017

edit: the hash on the archives.ipfs.io website (QmTZeE4yTiDd76YxbWvenneqSf5VhooNnA46WWWHtHcu5n) is now available again thanks to eminence. That's now the one I've pinned to my main ipfs node.

original post:
The hash on archives.ipfs.io seems to have become unavailable (QmTZeE4yTiDd76YxbWvenneqSf5VhooNnA46WWWHtHcu5n). I'm not sure how it was created, so I re-ran the creation script that ion1 posted earlier in this thread and pinned it to my node (QmZHbZahTjnPTNXJaNnaVw5KusGuCL1EbbGp7qM4AxP4hG).

It doesn't fix the hash on the archives site, but now almost all of the files in QmeZnaoktRvs3Ek8pQNyj8BbrkKuJ5Ez6JHi32dazL7cEJ (posted by eminence) are available again; all except for the rfc-index.txt file.

@eminence
Copy link
Collaborator

Sorry about that. my ipfs node had been offline for a few months due to hardware issues (which have now been fixed), but tonight i ran into troubles getting my ipfs daemon running (repo migration errors). i'll continue to try to get it running again

@whyrusleeping
Copy link
Contributor

@eminence We talked on IRC, but did you file an issue somewhere about that? I very much want to figure out the problem you were having

@eminence
Copy link
Collaborator

Sorry for the delay. All issues are now resolved, and this archive is back online.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

8 participants