RFC
A numbered document published by the RFC Editor, many of which are the official standards for internet protocols such as HTTP.
In more detail
RFC stands for Request for Comments, a name kept from the series’ informal beginnings. Published RFCs never change; a revision gets a new number and the old one is marked obsoleted, which is how RFC 9457 replaced RFC 7807.
Examples
from modp2048 import P, G # RFC 3526 group 14: public, the same for everyoneRFC 9457 defines Problem Details for HTTP APIs.RFC 9457 defines Problem Details for HTTP APIsRelated terms
- IETF — The Internet Engineering Task Force, the open standards body that develops most internet protocols, including HTTP, TLS and OAuth, and publishes them as RFCs.
- Problem Details — A standard JSON shape for HTTP error responses, defined in RFC 9457, with members such as type, title, status, detail and instance.
- TLS — The encryption that protects data travelling over a network, the S in HTTPS.
- JSON Web Token — A compact signed token made of three base64url parts separated by dots: a header, a payload of claims and a signature.
- protocol — An agreed set of rules for how computers format, send and respond to messages, so that different systems can understand each other.
- MODP group — A published set of public Diffie-Hellman numbers, a large prime and a generator, that anyone can reuse for key exchange.
- HTTP — The protocol web browsers and web servers use to send requests and responses.
- RFC 3339 — The internet standard timestamp format, such as 2025-01-02T03:04:05Z, that machines and people can both read without ambiguity.
- protocol — An agreed set of rules for how two programs exchange messages, such as HTTP, TCP or WebSocket.
- WebSocket — A protocol that turns an HTTP connection into a long-lived, two-way channel where client and server can each send messages at any time.
- JSON — A simple text format for structured data made of keys, values, lists and nested objects.
Taught in
- Designing Tools A Model Can Use — AI Engineering: LLM Apps, RAG & Agents
- Problem Details: RFC 9457 — Modern API Architecture: REST, GraphQL & gRPC
- Envelope Encryption & Data Protection with KMS — Cloud Security & DevSecOps Engineering
- Asymmetric Cryptography: RSA, ECC & Diffie-Hellman — Cybersecurity Fundamentals, GRC & Cryptography
- Global Exception Handling and Problem Details — Modern .NET Core, C# & Enterprise Microservices
- Authentication: JWTs and Claims — Modern .NET Core, C# & Enterprise Microservices
- Type-Safe RPC Architectures: tRPC & Procedures — Production Full-Stack Engineering
- Resilient Error Handling: Problem Details & Envelopes — Production Full-Stack Engineering
- The time Package — Concurrent Systems Programming with Go
- Exception Handling To Problem Details — Modern Java: Virtual Threads & High-Throughput Services
- Native WebSockets: Bidirectional Real-Time Streams — Node.js Internals & Backend Services
- Identity: Joiners, Federation And MFA — CompTIA Security+ (SY0-801) Exam Prep
- Governance Artifacts: From Policy To Runbook — CompTIA Security+ (SY0-801) Exam Prep
- The Spine Artifact: Generating Typed Models From OpenAPI — Production TypeScript
- Addresses, Subnets And Ports — LPIC-1 Linux Administrator (101-500 and 102-500) Exam Prep
References
- RFC Editor: About
- RFC 2026: The Internet Standards Process
- IETF: RFCs
- NIST glossary: request for comments
- RFC 9280: RFC Editor Model (Version 3)
- RFC Editor
- RFC 9457: Problem Details for HTTP APIs