Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by 's Address
The Single-Stack 100/50 Principle: Formal Definitions for IPv4 Retirement in Dual-Stack Networks
Internet-Draft Single-Stack 100/50 Principle September 2026 Sun Expires 6 March 2027 [Page] Workgroup: Network Working Group Internet-Draft: draft-sun-single-stack-100-50-01 Published: 2 September 2026 Intended Status: Informational Expires: 6 March 2027 Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).
Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2
8. Non-ephemeral finite field DH cipher suites (TLS_DH_*), as well as ephemeral key reuse for finite field DH cipher suites, are prohibited due to the Raccoon attack [RACCOON]. Both are already considered bad practice since they do not provide forward secrecy.
The SLAX Scripting Language: An Alternate Syntax for XSLT
The SLAX Scripting Language: An Alternate Syntax for XSLT slax-manual SLAX is an alternate syntax for XSLT, the W3C standard XML-to-XML transformation. XSLT is a powerful language, but uses an XML-based syntax that is painful to read and write. SLAX uses a syntax modeled after PERL and C which promotes the basic concepts of XSLT into first class language constructs. The result is scripts that are easier to develop and maintain.
Meow
Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts.
Internet Protocol Version 8 (IPv8)
Internet-Draft IPv8 April 2026 Thain Expires 16 October 2026 [Page] Workgroup: Network Working Group Internet-Draft: draft-thain-ipv8-00 Published: 14 April 2026 Intended Status: Standards Track Expires: 16 October 2026 Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts.
AI URI Scheme
3. Many user agents will not natively implement the ai scheme or the Artificial Intelligence Internet Protocol (AIIP). To enable immediate interoperability, deployments MAY expose ai:// resources via HTTPS gateways so that end users remain on conventional websites while backends or trusted intermediaries invoke AIIP.
AI Content Disclosure Header
Internet-Draft AI-Disclosure Header April 2025 Abaris Expires 1 November 2025 [Page] Workgroup: Independent Submission Internet-Draft: draft-abaris-aicdh-00 Published: 30 April 2025 Intended Status: Informational Expires: 1 November 2025 Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).
Faster Than Light Speed Protocol (FLIP)
RFC 9564 FLIP April 2024 Blanchet Informational [Page] Stream: Independent Submission RFC: 9564 Category: Informational Published: 1 April 2024 ISSN: 2070-1721 Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes.¶ This is a contribution to the RFC Series, independently of any other RFC stream.
Centralization, Decentralization, and Internet Standards
The potential damaging effects of centralization listed above are widely appreciated. Less widely explored is the reliance on centralization by some protocols and applications to deliver their functionality.¶ Centralization is often present due to technical necessity.
libxo: The Easy Way to Generate text, XML, JSON, and HTML output
You can retrieve the source for libxo in two ways: A) Use a "distfile" for a specific release. We use github to maintain our releases. Visit github release page (https://github.com/Juniper/libxo/releases) to see the list of releases. To download the latest, look for the release with the green "Latest release" button and the green "libxo‑RELEASE.tar.gz" button under that section.
HTTP Response Header Field: Carbon-Emissions-Scope-2
The "Carbon-Emissions-Scope-2" header field is a response header field that indicates the amount of carbon emissions associated with the processing of a given HTTP request, as calculated according to the Scope 2 protocol outlined in [ISO14064-1]. The value of this header field MUST be a non-negative decimal number expressed in grams of CO2-eq (carbon dioxide equivalent).¶ A server MAY include the "Carbon-Emissions-Scope-2" header field in any response to an HTTP request.
Transmission Control Protocol (TCP)
3.8.5. As a result of implementation differences and middlebox interactions, new applications SHOULD NOT employ the TCP urgent mechanism (SHLD-13). However, TCP implementations MUST still include support for the urgent mechanism (MUST-30).
Centralization, Decentralization, and Internet Standards
2.2.2. Some protocols and applications have goals that require the introduction of a centralized function.
More Instant Messaging Interoperability (MIMI) Identity Concepts
1. Introduction The IETF began standardization work on interoperable Instant Messaging in the late 1990s, but since that period, the typical feature set of these systems has expanded widely and was largely driven by the industry without much standardization or interoperability.
RFC 9114: HTTP/3
10.5. An HTTP/3 connection can demand a greater commitment of resources to operate than an HTTP/1.1 or HTTP/2 connection. The use of field compression and flow control depend on a commitment of resources for storing a greater amount of state. Settings for these features ensure that memory commitments for these features are strictly bounded.¶ The number of PUSH_PROMISE frames is constrained in a similar fashion.
Centralization and Internet Standards
4.2. Some protocols introduce centralization risk that is unavoidable, because the protocol's goals requires a centralized function.¶ For example, when there is a need for a single, globally coordinated "source of truth", that function is by nature centralized -- such as in the Domain Name System (DNS), which allows human-friendly naming to be converted into network addresses in a globally consistent fashion.¶ IP addresses allocation is another example of a function having this kind of...
The Harmful Consequences of the Robustness Principle
Internet-Draft Protocol Maintenance July 2021 Thomson Expires 13 January 2022 [Page] Abstract The robustness principle, often phrased as "be conservative in what you send, and liberal in what you accept", has long guided the design and implementation of Internet protocols. The posture this statement advocates promotes interoperability in the short term, but can negatively affect the protocol ecosystem over time.
Centralization and Internet Standards
4.2. Some protocols introduce centralization risk that is unavoidable by nature.¶ For example, when there is a need for a single, globally coordinated "source of truth", that function is by nature centralized -- such as in the Domain Name System (DNS), which allows human-friendly naming to be converted into network addresses in a globally consistent fashion.¶ IP addresses allocation is another example of a necessary function having centralization risk.
RFC 8890: The Internet is for End Users
The IETF community does not have any unique insight into what is "good for end users", and it is not uncommon for us to be at a further disadvantage because of our close understanding of some -- but not all -- aspects of the Internet.¶ At the same time, we have a culture of considerable deference to a broader "Internet community" -- roughly what this document calls end users -- in our decision-making processes.
Avoiding Internet Centralization
Internet-Draft Avoiding Internet Centralization December 2021 Nottingham Expires 12 June 2022 [Page] Abstract Avoiding centralization is an important goal for Internet protocols.
id3v2-chapters-1.0 - ID3.org
Informal standard Document: id3v2-chapters-1.0.html C. Newell 2 December 2005 1.1. Status of this document This document is an addendum to the ID3v2.3 and ID3v2.4 standards. Distribution of this document is unlimited. 1.2. Abstract This document describes a method for signalling chapters and a table of contents within an audio file using two new ID3v2 frames.
The Internet is for End Users
The Internet is for End Users draft-iab-for-the-users-latest This document explains why the IAB believes the IETF should consider end-users as its highest priority concern, and how that can be done. The issues list for this draft can be found at https://github.com/intarchboard/for-the-users/issuess. The most recent (often, unpublished) draft is at https://intarchboard.github.io/for-the-users/. Recent changes are listed at https://github.com/intarchboard/for-the-users/commits/master.
Incrementally Better Cookies
Incrementally Better Cookies draft-west-cookie-incrementalism-latest This document proposes two changes to cookies inspired by the properties of the HTTP State Tokens mechanism proposed in . First, cookies should be treated as SameSite=Lax by default. Second, cookies that explicitly assert SameSite=None in order to enable cross-site delivery should also be marked as Secure. This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with 's
Contact 's, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack