惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
The Blog of Author Tim Ferriss
S
Schneier on Security
H
Help Net Security
aimingoo的专栏
aimingoo的专栏
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
MongoDB | Blog
MongoDB | Blog
云风的 BLOG
云风的 BLOG
H
Hacker News: Front Page
C
Check Point Blog
P
Privacy International News Feed
IT之家
IT之家
爱范儿
爱范儿
AWS News Blog
AWS News Blog
The Hacker News
The Hacker News
Stack Overflow Blog
Stack Overflow Blog
Project Zero
Project Zero
Microsoft Azure Blog
Microsoft Azure Blog
量子位
The Cloudflare Blog
P
Proofpoint News Feed
Hugging Face - Blog
Hugging Face - Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
C
Cybersecurity and Infrastructure Security Agency CISA
I
Intezer
Martin Fowler
Martin Fowler
Scott Helme
Scott Helme
酷 壳 – CoolShell
酷 壳 – CoolShell
A
Arctic Wolf
T
Threat Research - Cisco Blogs
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
T
The Exploit Database - CXSecurity.com
B
Blog
Simon Willison's Weblog
Simon Willison's Weblog
U
Unit 42
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Microsoft Security Blog
Microsoft Security Blog
博客园_首页
J
Java Code Geeks
K
Kaspersky official blog
Webroot Blog
Webroot Blog
C
CERT Recently Published Vulnerability Notes
H
Heimdal Security Blog
G
Google Developers Blog
T
Tor Project blog
W
WeLiveSecurity
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Blog — PlanetScale
Blog — PlanetScale
小众软件
小众软件
有赞技术团队
有赞技术团队

Lobsters

Lunacy | Red Vice CIFSwitch: a non-universal Linux local root vulnerability RIPE NCC session fixation: poaching logins with an Atlas probe GNOME 2.20 but its Web Components Agentic Search for Context Engineering – Leonie Monigatti Garnix is shutting down [not OC] akashina.tngl.sh/jjc Concerning Emacs (and Jazz) Nitpicking the shell history scene in ‘Tron: Legacy’ What's cooking on SourceHut? Q2 2026 The tenth OpenPGP email summit Package managers that package package managers Clojure on Fennel part three: parsing WordPress at 23 Finding Miscompiles for Fun, Not Profit GitHub - creusot-rs/creusot: Creusot helps you prove your Rust code is correct. Announcing Rust 1.96.0 | Rust Blog A Love Letter to Neovim sqlite AGENTS.md Am I a Bad Friend? CSS vs. JavaScript • Josh W. Comeau Erlang Ecosystem Foundation - Supporting the BEAM community A brief note about slot access cost in Common Lisp Keyboard latency probe Rethinking the GNOME clipboard issues Back to the Building Blocks’ Building Blocks Tech Notes: Theseus: translating win32 to wasm Fast is better than slow Content-addressed Rust builds (or, what kache actually caches) Intent to Prototype: Embedding API Canada’s Bill C-22 and the security cost of collecting more data 5 PostgreSQL locking behaviors that trip people up okmij.org Stop advertising in your commits! | AksDev GitHub - mplsllc/macsurf: A modern web browser for Classic Mac OS 9 PowerPC. Real CSS3, ES5 JavaScript, native HTTPS — built with CodeWarrior on the Carbon API. Introducing DoomBench - Can Your Data Stack Run DOOM? What are some of your favourite developer tools? Building a Scalable Ingestion Pipeline with Temporal (Part 1) Converting shallow Git bundles into normal repositories Are you a member of any professional associations? What is a harmonic? An interactive comic about additive synthesis How Virtual Tables Work in the Itanium C++ ABI Using SwiftUI to Build a Mac-assed App in 2026 Rust (and Slint) on a jailbroken Kindle. ~jack/lambda-on-lambda - Serverless Haskell on AWS - sourcehut git Human proof for FOSS contributions Extremely simple internet radio controlled via IRC Announcing BABLR Splitting Konsole views from Helix to run tools | AksDev GitHub - yugr/rust-slides Serving files over HTTP three ways: synchronous, epoll, and io_uring update docs with information about building with build.py (#979) · astral-sh/python-build-standalone@c9c40c5 A Simple Makefile Tutorial On C extensions, portability, and alternative compilers Switching to Colemak | Pedro Alves Just How Bad Was The Intel IAPX432? Nix's Substituter List Is Not a Routing Table Accelerating copy_if using SIMD Lambda on Lambda: Serverless Haskell on AWS | Blog Announcing feed-repeat v1.0 Scaling Akvorado BMP RIB with sharding EYG news: A host of CLI improvements, new guides and new effects The social contract of writing JS Crossword C array types are weird; and related topics Flatpak will depend on systemd – OSnews Migrating from Go to Rust | corrode Rust Consulting A portentous reunion Vivado Licensing Options How my minimal, memory-safe Go rsync steers clear of vulnerabilities the entropy layer of a wavelet codec, on its own GitHub - nferhat/fht-compositor: A dynamic tiling Wayland compositor. Debian SE Linux and PinTheft Does bulk memmove speed up std::remove_if? (No.) 声明式部分更新 | Blog | Chrome for Developers Fully in-browser container builds Dianne Skoll's Web Site - Remind The Architecture of Open Source Applications (Volume 1)Berkeley DB Pardon MIE? - ironPeak Blog “Long-Term Support” doesn’t mean what you think Jira IS Turing-Complete May I recommend thinking of Emacs as your Fortress of Solitude hershey Floodgap Gopher-HTTP gateway gopher://thelambdalab.xyz/1cuneiforth/ HP QuickWeb, Singular And Pointless That one time I used Go panics for flow control From the Tabletop… The Digital Antiquarian Building a Host-Tuned GCC to Make GCC Compile Faster Are we self-sovereign PKI yet? Claw Patrol: an open-source security firewall for agents | Deno Revised^7 Report on Scheme, Large: Procedural Fascicle Draft is now public A Network Allow-List Won't Stop Exfiltration — André Graf From AFSK to Goertzel – µArt.cz Software For My New Home Server Introducing Neptune: Direct3D virtualization for QEMU AI Agent Bankrupted Their Operator While Trying to Scan DN42 - Lan Tian @ Blog mimalloc: A new, high-performance, scalable memory allocator for the modern era Making wl_shm fast The Soul of Maintaining a New Machine - Third Draft | Books in Progress What is Git made of?
A new suite of modern tools coming for editing and publishing RFCs
ietf.org via · 2026-05-23 · via Lobsters

Filter by topic and date

12 May 2026

After a number of years of work, the initial rollout of a modern suite of tools for editing and publishing RFCs, including an entirely new rfc-editor.org website, will take place in May 2026.

UPDATE 12 May 2026: Launch of the new tools for editing and publishing RFCs originally anticipated for 13 May has been deferred until the week of 18 May.

Since its inception in 1969 with the publication of RFC 1, the RFC Series has had a formal editing and management function that has evolved through multiple iterations, as the series has itself evolved, to the RFC Editor function that we have today. Now with over 9000 documents in the series, RFCs are authored in a variety of tools, often tracked through formal version control, published in RFCXML, and rendered into multiple presentation formats. The role of the RFC Production Center (RPC), the team that delivers the RFC Editor function, has changed significantly as a result.

In recent years it became clear that the tools used by the RPC could not adapt as needed to support these changes. The underlying database was too old, too rigid and too fragile, the editing tools were a large collection of unrelated and hard to maintain scripts, and the rfc-editor.org website was built on a platform far too old to add new functionality and improve usability. In particular, it was clear that the current tools could not support the editing or publication of RFC 10,000 and beyond.

In mid-2022 the IETF Administration LLC began a project to completely rewrite all of the RPC tools and add the new functionality that authors and the community had long been asking for, comprising the following:

  • The RPC database and workflow system will be migrated into a new application tightly integrated with Datatracker and using the existing Datatracker database of RFCs. The work on this has included:
    • Many hours of manually reconciling differences in data between the RPC and Datatracker databases to provide a single source of truth.
    • Implementing a new flexible state management system to allow for RPC processes to quickly adapt to meet future needs. This was in direct response to the many editorial process changes that have either been hard to implement or taken years longer than expected. This also provides for full end-to-end measurement of the RFC editing process, which has not been possible before now, and higher granularity measurement of individual parts of the process. 
    • An authors’ (public) view of the editing status of every document in the publication queue through the new subsite queue.rfc-editor.org.

screenshot of queue.rfc-editor.org update in May 2026

A screenshot of the new RFC Editor queue website that provides improved display of document status.

  • The RFC Editor website will migrate to an entirely new site that is designed around the needs of RFC consumers and sets the scene for more advanced features to be added. The work on this has included:
    • Using professional UX designers and accessibility specialists to completely redesign and test the website experience, and then implementing that in a modern web framework. The site will be a high-quality, authoritative and accessible site for RFCs.
    • Connecting to the new database and front-end object stores through all new APIs to support five-digit RFCs and beyond, faster page delivery under heavy load, and more efficient bulk access. 
    • Implementing a new errata system at errata.rfc-editor.org. This is substantively the same as the existing system with improved screening of reports and new login integration with Datatracker.
    • Implementing a new search system with both full text and enhanced metadata searching.

screenshot of www.rfc-editor.org update in May 2026

The new www.rfc-editor.org website makes RFCs easier to find and read with improved search and accessibility for those with sight impairments, and is friendlier to use on mobile devices.

  • The RPC will migrate to a new editing tool, DraftForge, a Visual Studio Code plugin that provides a one-stop user interface for all their editing tools. The work on this has included:
    • Rewriting the tens of individual scripts (some of which are in Tcl and 40+ years old) and adapting them to use a common user interface.
    • Connecting existing plugins that provide necessary functionality (e.g. RelaxNG validation) and adding new functionality to access the new RPC database.
    • Creating a plugin with two modes, one tuned for the RPC and one that authors might elect to use when writing RFCs.

This comprehensive overhaul has built on the work and close collaboration of the IETF Tools team and the RPC. The RPC has dedicated significant resources to specifying their requirements, reviewing plans, testing releases, migrating data and work in progress, and training staff to use the new tools.

Progress on the updated www.rfc-editor.org website has been previously shared over the past year during community calls and with a hands-on demo during the IETF 124 Montreal meeting. 

In the week beginning May 18, 2026, the initial rollout of these new tools will take place, with rfc-editor.org updated on May 20. With any rollout of this scale and degree of change we are expecting some complications and staff will be ready to address any serious issues quickly in order to minimise the impact on the IETF Community and RFC Consumers. There will be subsequent phases to this rollout in the months following and the last phase of the rollout is expected to be in December 2026.

In addition to the benefits above, this rollout provides the platform for two further improvements to the RFC Editor function. The first is that it allows us to collect the data needed for a better RPC SLA, and consultation on what that should be will start soon. The second is for an extensive set of new features for the rfc-editor.org website intended to support implementers, researchers, and others using RFCs. Work on this is well underway with the design phase completed and implementation in progress.

The update is not expected to result in any downtime for the www.rfc-editor.org website; there may be a one-day pause of submitting and processing errata.

Additional details Should the schedule change, further details will be provided closer to 20 May.

Editors note: This post was originally published on 5 May and was updated on 12 May to reflect the change in launch date of the RPC tools and rfc-editor.org website.