TechKnowSurge
CompTIA Network+ 1.4 Cisco CCST Networking 1.5 Cisco CCNA 1.5
VideoNetworkFree

Request for Comment (RFC)

RFCs (Requests for Comments) are the official documents that define networking protocols and standards, serving as the authoritative reference for how technologies like IPv6 are designed and implemented. Understanding RFCs allows IT professionals to verify technical information at the source and gain accurate insight into how protocols actually work.

Complete this video to capture a CTF flag worth 1 point.

About this video

RFCs, or Requests for Comments, are the official technical documents that define the standards behind networking protocols and the broader infrastructure of the internet. What began as informal proposals circulated among engineers seeking peer feedback has evolved into the authoritative body of specifications that the industry relies on when designing and implementing technology. When a vendor or engineer builds a solution that uses IPv6, for instance, they reference the relevant RFC to ensure their implementation conforms to the defined standard, which is what makes interoperability across different systems and vendors possible. Each RFC documents the precise technical requirements of a protocol, including detailed specifications like address formats and packet header structures. As protocols evolve, new RFCs are published to extend or update existing ones rather than replacing the originals, creating a traceable record of how a standard has developed over time. This layered structure means that understanding a protocol fully often requires familiarity with multiple related RFCs that build on one another. For IT and networking professionals, RFCs serve as an essential primary source for accurate technical knowledge. Because secondary sources, documentation, and third-party explanations can sometimes contain errors or outdated information, being able to reference the original RFC provides a reliable foundation for troubleshooting, design decisions, and exam preparation. Developing comfort with reading RFCs is a practical skill that supports more rigorous and informed work across networking and cybersecurity disciplines.

What you'll learn

What's covered

RFC Overview

Aligned to

CompTIA Network+
1.4 Explain common networking ports, protocols, services, and traffic types.
Cisco CCST Networking
1.5 Describe common network applications and protocols.
Cisco CCNA
1.5 Compare TCP to UDP

Key terms

Protocol
A set of rules governing the format and transmission of data between devices.
Internet Protocol
IP
The principal communications protocol for routing packets across network boundaries.
Request for Comments
RFC
A formally published document from the IETF that defines standards, protocols, and best practices governing internet technologies and IP addressing.
Packet
A unit of data formatted for transmission over a network, containing a header, payload, and sometimes a trailer.

Transcript

A lot of these protocols are defined by RFCs, or requests for comments. But what are RFCs?

I've pulled up the RFC for IP version 6. This is what defines IP version 6. It is one of the initial IP version 6 documents, and this was created in December of 1998. It says what it obsoletes and it also says what it's related to, so it has some of that information here at the top. But essentially, what this is is it outlines what an IP version 6 address is and what it should look like. It even gets to the point of, this is an IP version 6 header format, and shows you what the format of a header is going to look like.

So it outlines all the details that people are supposed to conform to. As long as everybody conforms to this, then IP version 6 will function correctly. Everybody looks at these to do their engineering. They look at these to make sure that whatever solutions they're creating, they're engineering it correctly to work into these RFCs.

Why it's called request for comment

Originally it was called request for comment because it would be something that they would put out there as a, hey, could you look this over and tell me what you think? It was a way for engineers to bounce ideas off of each other. In fact, some of the stuff they put in here is kind of goofy, actually.

But what it's become now is more of a source for the standard of how we're going to implement things. So now when we see RFCs like this, this is implementing IP version 6 and how to implement it. There are also some additions: as IP version 6 has grown and changed, we've added to this, and now there are additional standards that we add to it, but we add to it by creating more RFCs that add to this standard.

Going back to the source

One reason why this is important is that there is some misinformation out there. Getting sources from other sources and from other people is a good way to get knowledge, but you have to take some of that with a grain of salt. So it's nice to come back to the actual source and do some research on it.

I love actually geeking out over these things. I can imagine some people would think that they're a little dry, but there are some really cool aspects to how these protocols work and come together. So I think it's actually a pretty cool source of information for us to learn about these different protocols.

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →