rfc

作者介绍了 RFC8950，该标准允许在 IPv6 网络上以 IPv6 下一跳通告 IPv4 路由（无需隧道），使骨干网可以仅运行 IPv6 而将 IPv4 作为边缘可选功能，并给出了基于 FRR 和 Containerlab 的实验演示。

The article explains how Python's str.lower() function can introduce a security vulnerability in IDNA encoding due to mismatched Unicode versions, causing non-compliance with RFC standards and leading to inconsistent domain name handling.

A developer describes a technique of having LLMs write multiple RFC (Request for Comments) markdown documents to better understand complex problems before coding, instead of directly generating solutions.

A new DNS TXT record convention, defined by RFC 10023, allows domain owners to signal that their domain is for sale without disrupting their live site, with support for price and contact tags.

RFC 9851 declares TLS 1.2 to be in feature freeze, allowing only urgent security fixes, new exporter labels, and new ALPN protocol IDs, while encouraging migration to TLS 1.3.

The IAB has published RFC 8890 arguing that the IETF should prioritize the interests of end users in its technical decisions. The article explains the rationale behind this stance and its implications for internet governance.

The article explores the IETF's tradition of publishing humorous RFCs on April Fools' Day, covering famous jokes like IP over carrier pigeons, the evil bit, and HTTP 418.

The article details a newly discovered incompatibility between DMARC's 'np' tag (RFC 9989) and DNSSEC's Compact Denial of Existence (RFC 9824), causing the tag to malfunction for domains using DNSSEC with major DNS providers. The IETF acknowledged the issue but has not yet reached a solution.

The article explains the new HTTP QUERY method defined in RFC 10008, which addresses limitations of GET and POST for complex queries by providing a standard, safe, and idempotent method with a request body.

RFC 10008 defines the new HTTP QUERY method, allowing safe, idempotent, and cacheable requests with a body, addressing limitations of GET and POST for RPC-style APIs.

RFC 10008 defines the HTTP QUERY method, a safe and idempotent request method that allows sending a query payload in the request body, bridging the gap between GET and POST for query operations.

HTTP 418 'I'm a teapot' status code is documented on MDN as a humorous response indicating a server refuses to brew coffee, originating from an April Fools' RFC that was formally reserved in RFC 9110.