The very first RFCs including RFC 1 were published in 1969. Although the "host software" technology discussed in RFC 1 has long since become obsolete, documents like this one offer an interesting glimpse into the early days of computer networking. Even today, the plain-text format of the RFC remains essentially the same as it has since the beginning.
Many popular computer networking technologies in their early stages of development have been documented in RFCs over the years including
- Internet domain name concepts (RFC 1034)
- Address allocation for private intranets (RFC 1918)
- HTTP (RFC 1945)
- DHCP (RFC 2131)
- IPv6 (RFC 2460)
Do Non-Engineers Need to Worry About RFCs?
Because the IETF is staffed with professional engineers, and because it tends to move very slowly, the average Internet user doesn't need to focus on reading RFCs. These standards documents are intended to support the underlying infrastructure of the Internet; unless you're a programmer dabbling in networking technologies, you're likely to never need to read them or even be familiar with their content.However, the fact that the world's network engineers do adhere to RFC standards means that the technologies we take for granted -- Web browsing, sending and receiving email, using domain names -- are global, interoperable and seamless for consumers.
So thats it. Hope you guys like it. If yes then please .. comment down below and do not forgot to like follow and share our social media platforms.
Facebook Page:- https://www.facebook.com/theprogrammer.harshit/
0 comments:
Post a Comment