<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>RFC Explained</title>
  <subtitle>IETF RFCs explained in plain English: the TL;DR, the problem each standard solves, its status and the parts people get wrong.</subtitle>
  <id>https://rfc-explained.com/</id>
  <link href="https://rfc-explained.com/en/" />
  <link rel="self" type="application/atom+xml" href="https://rfc-explained.com/feed.xml" />
  <updated>2026-07-08T00:00:00Z</updated>
  <author><name>Noel Lang</name></author>
  <entry>
    <title>RFC 5321: The protocol that actually delivers your email.</title>
    <link href="https://rfc-explained.com/en/5321" />
    <id>https://rfc-explained.com/en/5321</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 5321 is SMTP, the protocol that moves email between servers. It defines the envelope (MAIL FROM, RCPT TO) and the delivery conversation, separate from the message itself.</summary>
  </entry>
  <entry>
    <title>RFC 3164: The syslog format that was never really a standard.</title>
    <link href="https://rfc-explained.com/en/3164" />
    <id>https://rfc-explained.com/en/3164</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 3164 documented the old BSD syslog format: the &lt;PRI&gt; number, a year-less timestamp, free-text message. Informational, obsoleted by RFC 5424, still everywhere.</summary>
  </entry>
  <entry>
    <title>RFC 2822: The email format's in-between edition.</title>
    <link href="https://rfc-explained.com/en/2822" />
    <id>https://rfc-explained.com/en/2822</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 2822 was the 2001 revision of the email message format, between RFC 822 and RFC 5322. It fixed the two-digit year and tidied the syntax. Now obsolete.</summary>
  </entry>
  <entry>
    <title>RFC 1123: The RFC that let hostnames start with a digit.</title>
    <link href="https://rfc-explained.com/en/1123" />
    <id>https://rfc-explained.com/en/1123</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 1123 corrects email, DNS, FTP and Telnet for real hosts. It legalised hostnames starting with a digit and defined the date format HTTP still calls rfc1123-date.</summary>
  </entry>
  <entry>
    <title>RFC 1122: Ten years of TCP/IP bug reports, written down.</title>
    <link href="https://rfc-explained.com/en/1122" />
    <id>https://rfc-explained.com/en/1122</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 1122 tells hosts what they MUST do with IP, TCP and UDP. Half of STD 3, home of the Robustness Principle, and the reason independent TCP stacks interoperate.</summary>
  </entry>
  <entry>
    <title>RFC 822: The shape of every email, defined in 1982.</title>
    <link href="https://rfc-explained.com/en/822" />
    <id>https://rfc-explained.com/en/822</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 822 defined the email message format in 1982: header fields, a blank line, then the body. Obsoleted by RFC 2822 and 5322, but its structure survives everywhere.</summary>
  </entry>
  <entry>
    <title>RFC 768: UDP, the protocol that promises nothing.</title>
    <link href="https://rfc-explained.com/en/768" />
    <id>https://rfc-explained.com/en/768</id>
    <updated>2026-07-08T00:00:00Z</updated>
    <published>2026-07-08T00:00:00Z</published>
    <summary>RFC 768 defines UDP: an eight-byte header, no handshake, no retransmission, no ordering. Why DNS, video and HTTP/3 all choose the protocol that guarantees nothing.</summary>
  </entry>
  <entry>
    <title>RFC 9110: What HTTP means, no matter how it travels.</title>
    <link href="https://rfc-explained.com/en/9110" />
    <id>https://rfc-explained.com/en/9110</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 9110 defines HTTP semantics: methods, status codes and headers, independent of version. The 2022 Internet Standard (STD 97) that reorganized 25 years of HTTP.</summary>
  </entry>
  <entry>
    <title>RFC 6749: How apps get access without getting your password.</title>
    <link href="https://rfc-explained.com/en/6749" />
    <id>https://rfc-explained.com/en/6749</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 6749 defines OAuth 2.0: how apps get scoped, revocable access tokens to act on your behalf without handling your password. The framework behind every 'Sign in with' button.</summary>
  </entry>
  <entry>
    <title>RFC 6598: The fourth private range nobody voted for.</title>
    <link href="https://rfc-explained.com/en/6598" />
    <id>https://rfc-explained.com/en/6598</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 6598 reserves 100.64.0.0/10 as Shared Address Space for carrier-grade NAT. Why your ISP hands you a 100.x address, and how to tell you are behind CGN.</summary>
  </entry>
  <entry>
    <title>RFC 5424: Syslog, with a real timestamp at last.</title>
    <link href="https://rfc-explained.com/en/5424" />
    <id>https://rfc-explained.com/en/5424</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 5424 defines the modern syslog message format: precise timestamps, structured data and clear fields. It replaced the loose BSD syslog of RFC 3164.</summary>
  </entry>
  <entry>
    <title>RFC 5322: The anatomy of an email, and why the From line can lie.</title>
    <link href="https://rfc-explained.com/en/5322" />
    <id>https://rfc-explained.com/en/5322</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 5322 defines the email message format: headers, body and valid address syntax. Why the From line can lie, and how it differs from SMTP (RFC 5321).</summary>
  </entry>
  <entry>
    <title>RFC 3339: The timestamp format you google ten times a week.</title>
    <link href="https://rfc-explained.com/en/3339" />
    <id>https://rfc-explained.com/en/3339</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 3339 is the internet timestamp format, like 2026-07-05T14:30:00Z. A strict profile of ISO 8601 with a required offset, used across JSON APIs, logs and databases.</summary>
  </entry>
  <entry>
    <title>RFC 2544: The MOT test for network boxes, explained.</title>
    <link href="https://rfc-explained.com/en/2544" />
    <id>https://rfc-explained.com/en/2544</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 2544 is the standard bench test for switches and routers: throughput, latency, frame loss and back-to-back, run across fixed frame sizes so a datasheet claim can be verified.</summary>
  </entry>
  <entry>
    <title>RFC 2119: MUST, SHOULD and MAY, defined once and for all.</title>
    <link href="https://rfc-explained.com/en/2119" />
    <id>https://rfc-explained.com/en/2119</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 2119 defines what MUST, SHOULD, MAY and their negatives mean in a spec. The keyword dictionary behind almost every RFC, updated by RFC 8174.</summary>
  </entry>
  <entry>
    <title>RFC 1918: Private IP addresses, explained like you're new here.</title>
    <link href="https://rfc-explained.com/en/1918" />
    <id>https://rfc-explained.com/en/1918</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 1918 reserves 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 for private networks. What that means and why your router is 192.168.0.1, in plain English.</summary>
  </entry>
  <entry>
    <title>RFC 793: TCP, the protocol that turns postcards into a phone call.</title>
    <link href="https://rfc-explained.com/en/793" />
    <id>https://rfc-explained.com/en/793</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 793 defines TCP: the three-way handshake, sequence numbers and retransmission that make delivery reliable and ordered. The 1981 spec was replaced by RFC 9293 in 2022. Same protocol on the wire.</summary>
  </entry>
  <entry>
    <title>RFC 791: IPv4, the envelope every packet travels in.</title>
    <link href="https://rfc-explained.com/en/791" />
    <id>https://rfc-explained.com/en/791</id>
    <updated>2026-07-05T00:00:00Z</updated>
    <published>2026-07-05T00:00:00Z</published>
    <summary>RFC 791 defines IPv4: the 32-bit addresses, the packet header and how routers forward and fragment datagrams. The 1981 spec still runs most of the internet.</summary>
  </entry>
</feed>
