There is an RFC for everything, but #Japan 😬🇯🇵
https://www.ietf.org/rfc/rfc2142.txt
Lai Jiangshan posted a RFC patch-set introducing a new hypervisor called #PVM:
https://lore.kernel.org/lkml/20240226143630.33643-1-jiangshanlai@gmail.com/…
Before jurisdictions attempt to regulate the operation of internet services in other jurisdictions, they should probably oblige the access providers in their region to publish RFC 8805 feeds.
Unexpected potential application of generative-AI technology; looks attractive in theory: https://www.rfc-editor.org/rfc/rfc9564.html
“The recent advances in artificial intelligence (AI) such as large language models enable the design of the Faster than LIght speed Protocol (FLIP) for Internet. FLIP provides a way to avoid congestion, enhance security, and deliver faster packets on the Internet by using AI to predict future packets at the receiving peer before they arrive.”
RFC 9564
Faster Than Light Speed Protocol (FLIP)
[PATCH RFC 0/7] block: Introduce CBD (CXL Block Device)
https://lore.kernel.org/all/20240422071606.52637-1-dongsheng.yang@easystack.cn/
"'As shared memory is supported in CXL3.0 spec, we can transfer data via CXL shared mem…
Interesting proposal for a top-level domain (TLD) that you could use internally on your LAN that will never be available out on the public Internet. So you could give your servers names ending in “.internal” and those addresses would not conflict with public addresses.
There are a number of similar “special use domains” in RFC6761 - https://www.
Apple Mail doesn't support the auto-unsubscribe links provided by Sendgrid clients.
This is because Sendgrid has chosen to Q-encode (RFC 2047) the List-Unsubscribe: header, but since the header (RFC 2369) isn't defined using BNF, none of the criteria for encoding are met. So it's either fine, or it isn’t. Implementor’s choice.
Standards!