Slashdot Mirror
Happy 35th birthday, RFC 1!
An anonymous reader writes "On April 7th, 1969, the first ever RFC was published, describing the networking technology behind the then-nascent ARPAnet. In the intervening 35 years, networking technology has come a long way, but it brings perspective to the modern Internet to reflect on how it all began."
Ok, I surely failed but it's funny :)
I'd have thought the first RFC would have been defining the structure of RFC's. :)
Is it too late to raise comments now?
Please read my Canon EOS tech blog at http://www.everyothershot.com
Do we get cake?
It was 19 when I finally got a dialup connection to a server with a shell account. I know my life could have been spent more wisely...had I only been connected sooner.
A feeling of having made the same mistake before: Deja Foobar
Somehow, I get the feeling Al Gore will not be invited to its birthday party.
Reading that RFC is like reading the creation story of the internet, you can see where some of the things they come up with wayyyyy back then, have moved now. Normally I am not much for reading RFC's, but thats really intresting, if for nothing else to see how far we have gone in just 35 years.
snowulf.com
This was posted 5 years ago. It has a birthday every year, folks :)
RP
I see no reason to upgrade to RFC 2, just useless bloat I say. RFC1's worked great for 35 years, and it'll work great for another 35.
Generally, bash is superior to python in those environments where python is not installed.
Wasn't even a fetus by then. Just a mere RFC between my 'rents.
It's in the book. You could look it up (or google).
This one is my favourite:
RFC 1149: A Standard for the Transmission of IP Datagrams on Avian Carriers
The RFC includes an itneresting statment about 'user input from keyboard, Lincoln Wand, etc.'. It appears that a Lincoln Wand is what we now call a stylus...
http://www.packet.cc/files/lincoln-wand.html
Your monitor is staring at you.
If you don't know what an RFC is, then here is what you need to know.
"SRI is currently modifying their on-line retrieval system which will be the major software component on the Network Documentation Center so that it can be operated with model 35 teletypes. The control of the teletypes will be written in DEL. All sites will write DEL compilers and use NLS through the DEL program."
It may be hard to imagine, but back then CRT terminals were a rare beast. Most machine interaction was done via Teletype, punch cards, and line printers.
"To those who are overly cautious, everything is impossible. "
But 0! (zero factorial) is equal to 1, so what's your problem?
If you meant RFC0, I'm working on that right now, and it will be published in 1967 as soon as I can get this flux capacitor to work...
Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
The Connected Internet was operated by committee of the users. engineering details were worked out through the mechanism of issuance of RFCs (request for comment) and comments thereto for the filer and /or committee. the IETF (internet engineering task force) was the body that governed the RFC process, and it just sorta grew out of some chats by the detail wizards working on the Arpanet at the time.
what we have now is not necessarily The Connected Internet as it was known and loved in the 80s and early 90s. but it should remain as such, controlled by the users, not a bunch of pinheaded goddamned government know-nothings pushing alternate agendas.
if this is supposed to be a new economy, how come they still want my old fashioned money?
but he still lives in his parents basement.
hey, now if all 'linked from front page of slashdot' posts were like this, no one would care if they got slashdotted.
.. or even netbeui
3 or os images and 5K of text, hell, even my little p200 'what the hell, it can run linux' can handle that.
This isn't really related to the post, but I find it very interesting the fact that in almost all things, the simplest answers are usually correct.
1. Built HTML that is simple enough to be read by lynx and you'll have a very readable, universally accessable, highly portable and translatable site.
2. Built a simple system of relaying packets with some transport validation mechanism (TCP) and it will take over the world.
of course could you imagine if we had to deal with bridged IPX or LAT based networks
Request for Contraception?
I've just patented the RFC process. You owe me a dollar.
the major advances in civilization are processes which all but wreck the societies in which they occur - A.N. White
Well, at least trolls would be send to bed by their mothers when they do their thing.
Just imagine what a "First Post" thread would look:
- Fris Psot! (by Johny the Troll)
- Johny, I told you a million time not to annoy the nice people on Slashdot. Now go do you're homework!. (by Johny's Mother)
- oh mom, I'll do it after dinner.
- Now listen here young man, you'll do as you're told or do I have to send your father an e-mail?
No, RFC 0 is the meta RFC. Unfortunately, documentation of the 0-based numbering scheme ("see RFC 0"), that has become so popular with computers and their geeks since the 1960s, wasn't submitted to the RFC-editor for years, well after RFC 10. By then, the RFC-editor was forced to reject it, as RFCs document actual implementations, and are merely Requests For Comments from other users of the system, not design documents. The vast preponderance of RFCs had been written (so it seemed - they'd almost completely debugged ARPANet) by RFC 10's era, so it would have been a cruel irony to finish the series merely revising the counting base to recognize the "zeroth" RFC, which indicates that RFCs start at "0".
--
make install -not war
Read RFC1543
Please correct me if I got my facts wrong.
The Model 33 and Model 35 were upper case only; the lower case Model 37 came later.
John Sauter (J_Sauter@Empire.Net)
... in response that RFC.
Lemme get my super-omniscient-archive up and running... oh yes, here it is. Comment #1, in reply to RFC1. Dated 11 seconds after RFC1 was issued:
"It'll never work."
Oddly, Comment #2, which was received within seconds of comment #1, was a cryptic
"Woot! First Comment!"
And th rest, as they say, is history.
help me i've cloned myself and can't remember which one I am
This may be odd, but a quick jaunt through the archive shows that RFC4 seems to predate it by a few days: it was born on March 24th vs. RFC1's April 7th...
-Jack Ash
First RFC! W00t!
It was Al Gore! Just ask him...
Don't blame me, I didn't vote for either of them!
You can tell that open collaboration and communication are at the heart of the Internet, going back to its design. Look at the titling of core documents - "Request for Comment." Even on /., the nature of an article is requesting for comments and further analysis. Because of this legacy, where humans once networked computers, computers network humans.
This process stands today because it works - not perfectly, but we all benefit from the paradigm. It is our responsibility as members (and some of us professionals) in the Internet community to ensure that the spirit of the RFC never leaves. We should not deny the principles which brought us here - openness, communication, collaboration. Let's not forget the future - open source software, free speech, distributed control, and better S:N.
We would be wise to always request for the comments of our peers. It's gotten us this far.
Read RFC 2555. It gives an interesting view of inside of the RFC world. It's written by some of the key people that invented and have made RFC's what they are today.
"Until you do what you believe in, how do you know whether you believe in it or not?" -- Leo Tolstoy