Skip to main content

62 docs tagged with "rfc"

View all tags

RFC 1157 - A Simple Network Management Protocol (SNMP)

RFC 1157 defines the Simple Network Management Protocol (SNMP) version 1, used for monitoring and managing network devices. Provides Get, Set, Trap operations to query and modify device status. It is the foundation protocol for network management, widely used in routers, switches, servers and other equipment.

RFC 2616 - HTTP/1.1 (Classic)

RFC 2616 is the classic HTTP/1.1 specification published in 1999, which dominated the Web for over a decade. Although superseded by RFC 7230-7235 series, it remains the most classic document for understanding HTTP.

RFC 3629 - UTF-8, a transformation format of ISO 10646

RFC 3629 defines the UTF-8 character encoding, a transformation format of ISO 10646. It details encoding rules, byte sequence syntax, security considerations, etc. It is a fundamental standard for modern Internet text processing.

RFC 4648 - The Base16, Base32, and Base64 Data Encodings

RFC 4648 defines three commonly used base encoding schemes - Base16, Base32, and Base64. It provides detailed specifications of encoding algorithms, character sets, padding rules, and security considerations. Essential foundation for understanding JWT, MIME, URL encoding, and other technologies.

RFC 6749 - The OAuth 2.0 Authorization Framework

RFC 6749 defines the complete specification of the OAuth 2.0 authorization framework, including four authorization grant types - authorization code, implicit, resource owner password credentials, and client credentials. This is the foundational standard for modern API security and authentication.

RFC 7231 - HTTP/1.1语义与内容

RFC 7231定义了HTTP/1.1消息的语义,包括请求方法、请求头字段、响应状态码、响应头字段,以及消息载荷(元数据和主体内容)和内容协商机制。

RFC 7578 - Returning Values from Forms: multipart/form-data

RFC 7578 defines the multipart/form-data media type used for HTML form submission, particularly for file upload scenarios. It specifies the encoding format for form data, Content-Disposition headers, filename handling, and other details. This is the core standard for implementing file upload functionality in web development.

RFC 8555 - Automatic Certificate Management Environment (ACME)

RFC 8555 defines the Automatic Certificate Management Environment (ACME) protocol for automating SSL/TLS certificate application, validation, and issuance. Let's Encrypt widely adopts this protocol to enable free HTTPS certificate automation, significantly advancing web encryption adoption.

RFC 8820 - URI 设计和所有权

RFC 8820 提供 URI 设计的最佳实践指南,规范了 URI 结构设计、命名空间管理、路径设计原则等,是标准规范制定者的重要参考文档。