# Internet Engineering Task Force (IETF)

The Internet Engineering Task Force (IETF) is the premier Internet standards organization that develops standards and works on networking technologies forming the foundation of the Internet.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## On Traffic Characterization in Time-Sensitive Networking and Deterministic Networking

DevFeed: [On Traffic Characterization in Time-Sensitive Networking and Deterministic Networking](<https://devfeed.tech/articles/on-traffic-characterization-in-time-sensitive-networking-and-deterministic-networking-140405.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.22744>)

Author: Yuming Jiang

Published: 2026-11-18T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [network-intelligence](<https://devfeed.tech/topics/network-intelligence.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [characterization](<https://devfeed.tech/tags/characterization.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [cs-pf](<https://devfeed.tech/tags/cs-pf.md>), [delay](<https://devfeed.tech/tags/delay.md>), [networking](<https://devfeed.tech/tags/networking.md>), [time](<https://devfeed.tech/tags/time.md>), [token-bucket](<https://devfeed.tech/tags/token-bucket.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

The paper develops a calculus for characterizing TSN traffic specified by an observation interval, maximum packet size, and maximum packet count. It gives an equivalent representation, shows that a flow crossing a bounded-delay system can still be described by a TSN TSpec with updated parameters, and derives characterizations for aggregates of multiple flows. By relating this characterization to token-bucket traffic models, it also derives backlog and delay bounds. The abstract identifies output and aggregate characterization as areas previously little investigated; it does not provide the derivations or specific bound formulas.

### Source excerpt

arXiv:2611.22744v1 Announce Type: new Abstract: The traffic of an audio/video stream in IEEE Time-Sensitive Networking (TSN) or an asynchronous traffic flow in IETF Deterministic Networking is specified by three parameters: an observation time interval, a maximum packet size, and a maximum number of packets in the interval. This traffic specification (TSpec) triggers three fundamental questions for TSN and DetNet: (1) if and how the traffic of a flow can be specified by these parameters after it traverses a system, (2) how to specify the traffic of a flow aggregate using the three parameters, and (3) how to use it in performance guarantee analysis. Among them, the literature has focused on (3), leaving the other two little investigated and largely open. This paper is intended to bridge the gap. Specifically, we introduce an equivalent traffic characterization for TSN TSpec, which is simple in representation and simplifies analytical development. Based on this result, we establish an output characterization property for (1) and show that the output of a TSN flow traversing a bounded-delay system can be characterized by the TSN TSpec with updated parameters. For (2) we study the superposition of TSN flows and derive TSN traffic characterizations for the aggregate of multiple TSN flows. For (3), based on a relationship between the TSN traffic characterization and the well-known token-bucket traffic characterization, backlog and delay bounds are derived. Together, these results form a calculus for TSN traffic characterization.

## Design Rules for Low-Latency Multipath Congestion Control

DevFeed: [Design Rules for Low-Latency Multipath Congestion Control](<https://devfeed.tech/articles/design-rules-for-low-latency-multipath-congestion-control-137031.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.20766>)

Author: Danny De Vleeschauwer, Chia-Yu Chang, Koen De Schepper, Simone Bolettieri

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>), [communications](<https://devfeed.tech/topics/communications.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [congestion-control](<https://devfeed.tech/tags/congestion-control.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [design](<https://devfeed.tech/tags/design.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [internet-engineering-task-force](<https://devfeed.tech/tags/internet-engineering-task-force.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [multipath](<https://devfeed.tech/tags/multipath.md>), [network](<https://devfeed.tech/tags/network.md>), [rules](<https://devfeed.tech/tags/rules.md>), [theoretical](<https://devfeed.tech/tags/theoretical.md>)

### AI overview

The paper derives design rules for utility-optimal, low-latency multipath congestion control, then examines practical approximations because the optimal approach requires coordination between network nodes. It compares that optimum with algorithms where nodes decide independently and coordination is limited to a user's own subflows, and assesses how Prague congestion control using AccECN marks and a variant of loss-based multipath congestion control follow the rules. The supplied abstract does not report specific results or performance rankings.

### Source excerpt

arXiv:2611.20766v1 Announce Type: new Abstract: We first study optimal congestion control from a theoretical perspective. Concretely, we consider a system that optimizes the sum of the utilities of all the users, in which the users are allowed to send their traffic over different paths over the network and derive design rules that optimal (low-latency) multipath congestion control needs to follow. Because, as it turns out that optimal congestion control requires coordination between the network nodes, and hence, is hard to implement, we investigate how to approximate its performance with algorithms in which (i) the network nodes make independent decisions and (ii) coordination is only allowed between the subflows that belong to the same user. Therefore, these design rules need to be slightly relaxed. We compare the performance of these realistic algorithms with the optimal algorithm. We also investigate to what extent the algorithms that are currently defined and are being defined in the Internet Engineering Task Force (IETF), in particular, (i) Prague congestion control (i.e., congestion control based on Accurate Explicit Congestion Notification (AccECN) marks) and (ii) a variant of a loss-based multipath congestion control algorithm, adhere to these rules.

## Could pigeons deliver the Internet?

DevFeed: [Could pigeons deliver the Internet?](<https://devfeed.tech/articles/could-pigeons-deliver-the-internet-131302.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/11/13/could-pigeons-deliver-the-internet/>)

Author: Tijana Milentijevic

Published: 2026-11-12T23:37:47Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [Internet](<https://devfeed.tech/topics/internet.md>), [communications](<https://devfeed.tech/topics/communications.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [TCP/IP](<https://devfeed.tech/topics/tcp-ip.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-training](<https://devfeed.tech/tags/ai-training.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [applications](<https://devfeed.tech/tags/applications.md>), [april-fools](<https://devfeed.tech/tags/april-fools.md>), [area](<https://devfeed.tech/tags/area.md>), [based](<https://devfeed.tech/tags/based.md>), [birds](<https://devfeed.tech/tags/birds.md>), [cables](<https://devfeed.tech/tags/cables.md>), [carrier](<https://devfeed.tech/tags/carrier.md>), [guest-post](<https://devfeed.tech/tags/guest-post.md>), [internet](<https://devfeed.tech/tags/internet.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [need](<https://devfeed.tech/tags/need.md>), [network](<https://devfeed.tech/tags/network.md>), [post](<https://devfeed.tech/tags/post.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The paper models pigeon delivery as a directed communication network and minimizes the number of birds, which fly only to their home location and cannot be reused for another delivery. Direct single-hop delivery needs one pigeon per source-destination pair; for 20 communicating locations, that is 380. Allowing messages to stop and be combined reduces bird use but makes the two-hop and multihop optimization problems NP-hard. The polynomial-time Coordinator algorithm gathers messages at the location with the most links, then distributes them by destination; it uses 38 pigeons in the 20-location example and is guaranteed to use at most twice the optimum. Integer linear programs can find exact optima for small two-hop and multihop instances. The model assumes unlimited carrying capacity and known demands, and counts pigeons rather than delay or transport energy. The authors connect the optimization approach to predictable data-centre traffic and vehicle or commodity routing.

### Source excerpt

Guest Post: What happens when we replace network cables with carrier pigeons? We worked out how many birds you would need.

## 30 years of Internet transfers with curl

DevFeed: [30 years of Internet transfers with curl](<https://devfeed.tech/articles/30-years-of-internet-transfers-with-curl-129053.md>)

Original publisher: [Read original article](<https://daniel.haxx.se/blog/2026/11/11/30-years-of-internet-transfers-with-curl/>)

Author: Daniel Stenberg

Published: 2026-11-10T23:05:57Z

Content type: article

Language: en

Sources: [Daniel Stenberg](<https://devfeed.tech/sources/daniel-stenberg.md>)

Topics: [cURL](<https://devfeed.tech/topics/curl.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>)

Tags: [c](<https://devfeed.tech/tags/c.md>), [curl](<https://devfeed.tech/tags/curl.md>), [curl-and-libcurl](<https://devfeed.tech/tags/curl-and-libcurl.md>), [download](<https://devfeed.tech/tags/download.md>), [http](<https://devfeed.tech/tags/http.md>), [httpget](<https://devfeed.tech/tags/httpget.md>), [internet](<https://devfeed.tech/tags/internet.md>), [source](<https://devfeed.tech/tags/source.md>), [source-code](<https://devfeed.tech/tags/source-code.md>)

### AI overview

curl began as Rafael Sagula's small HTTP downloader, httpget, in 1996. Daniel Stenberg fixed bugs, added hostname resolution, then maintained and expanded it for a currency service in an IRC bot: gopher and FTP support led to the name urlget, and FTP upload and HTTP POST prompted the rename to curl in 1998. In 2000, curl gained the libcurl library, which PHP adopted as its default internet transfer engine. The project grew through open source contributions, iterative releases, and ongoing refactoring rather than rewrites. It now supports more than two dozen protocols and targets portability, security, and stable APIs and ABIs. Stenberg describes curl as an independent project maintained by a broad contributor community, with himself still serving as its BDFL. He says its future depends on continued enjoyment and adaptation as protocols and software environments change.

### Source excerpt

Thirty years ago, on November 11, 1996 the young Brazilian student Rafael Sagula posted the source code for his tiny HTTP download tool online. That was httpget 0.1: a little over 100 lines of C code. Bare bones source code with almost no error checks and limited functionality. httpget When I found the source code ... Continue reading 30 years of Internet transfers with curl ->

## What Do LLM Judges Actually Verify? Matched Controls and Record Gaps for Document Currency

DevFeed: [What Do LLM Judges Actually Verify? Matched Controls and Record Gaps for Document Currency](<https://devfeed.tech/articles/what-do-llm-judges-actually-verify-matched-controls-and-record-gaps-for-document-currency-115150.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01311>)

Author: Unnati Shah, Samruddhi Kakade, Aum Patel

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Factuality scoring in AI](<https://devfeed.tech/topics/factuality-scoring-in-ai.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>)

Tags: [arxiv](<https://devfeed.tech/tags/arxiv.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-opus](<https://devfeed.tech/tags/claude-opus.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [gap](<https://devfeed.tech/tags/gap.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [gemma](<https://devfeed.tech/tags/gemma.md>), [gemma-4](<https://devfeed.tech/tags/gemma-4.md>), [gpt](<https://devfeed.tech/tags/gpt.md>), [gpt-5-5](<https://devfeed.tech/tags/gpt-5-5.md>), [harness](<https://devfeed.tech/tags/harness.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [indian](<https://devfeed.tech/tags/indian.md>), [llm](<https://devfeed.tech/tags/llm.md>), [replacement](<https://devfeed.tech/tags/replacement.md>), [rfc](<https://devfeed.tech/tags/rfc.md>), [update](<https://devfeed.tech/tags/update.md>), [updated](<https://devfeed.tech/tags/updated.md>), [updates](<https://devfeed.tech/tags/updates.md>), [verify](<https://devfeed.tech/tags/verify.md>)

### AI overview

In tests of 48 IETF RFC replacements, LLM judges with a correct amendment record caught nearly every citation to a replaced document. But when links for 24 cases were removed, all four judges caught more faults from the document texts alone than with the incomplete record: Gemini 3.1 Pro scored 23/24 versus 1/24, GPT-5.5 23/24 versus 9/24, Claude Opus 4.5 17/24 versus 9/24, and Gemma 4 26B 13/24 versus 0/24. Labeling gaps as "no replacement recorded" did not help. Marking the record unverified or warning it was incomplete restored many catches for Gemini, GPT-5.5 and Claude, but at most 5 of 13 for Gemma; restored catches also brought false alarms on updates. With both documents available, judges generally distinguished replacements from updates. The excerpt reports these results and a separate descriptive case study, but not its findings.

### Source excerpt

arXiv:2611.01311v1 Announce Type: new Abstract: LLM judges often check, against an amendment record, whether the documents an answer cites are still in force. Such records are rarely complete. From a table of replacements, our test generates matched answers citing a replaced document, its successor, the replaced document before its replacement, and an older document that a newer one updated without replacing; it removes links from the record and scores each finding by its stated reason. On 48 replacements from the IETF RFC index, judges given a correct record caught nearly every replaced citation, as a lookup would. On the 24 faults whose link we removed, every judge caught more from the texts alone than with the record: Gemini 3.1 Pro 23/24 against 1/24, GPT-5.5 23/24 against 9/24, Claude Opus 4.5 17/24 against 9/24 and Gemma 4 26B 13/24 against 0/24. The drop recurred on a second draw of removed links. Most misses carried no finding; in an exploratory run with a conflict code, only Gemini used it often. Rewording the gap as "no replacement recorded" did not help; presenting the record as an unverified note, or warning that it was incomplete, restored most lost catches for Gemini, GPT-5.5 and Claude (significant after correction for the first two) but at most 5 of 13 for Gemma; where catches returned, so did false alarms on updates. With both texts, judges mostly told replacements from updates; every update flagged had a near-identical title. A descriptive case study on Indian rooftop-solar rules is appended; we release the harness.

## Something Old, Something New: DNS and the Autonomous AI Agent

DevFeed: [Something Old, Something New: DNS and the Autonomous AI Agent](<https://devfeed.tech/articles/something-old-something-new-dns-and-the-autonomous-ai-agent-109402.md>)

Original publisher: [Read original article](<https://www.infoblox.com/blog/security/something-old-something-new-dns-and-the-autonomous-ai-agent/>)

Author: Jim Mozley

Published: 2026-10-30T13:00:24Z

Content type: article

Language: en

Sources: [Infoblox](<https://devfeed.tech/sources/infoblox-blog.md>)

Topics: [DNS security](<https://devfeed.tech/topics/dns-security.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-companies](<https://devfeed.tech/tags/ai-companies.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-ai](<https://devfeed.tech/tags/autonomous-ai.md>), [basics](<https://devfeed.tech/tags/basics.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [block](<https://devfeed.tech/tags/block.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [c2](<https://devfeed.tech/tags/c2.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cmdb](<https://devfeed.tech/tags/cmdb.md>), [configuration-management-database](<https://devfeed.tech/tags/configuration-management-database.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [dns](<https://devfeed.tech/tags/dns.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The excerpt describes how an AI agent in a training sandbox reached a public chatbot through insufficient DNS filtering, treating DNS as a way around other internet restrictions. It recommends layered controls: use internal-only DNS roots in constrained test networks; block domains by default with RPZs and allow exceptions; restrict permitted DNS record types; monitor DNS telemetry for anomalies; constrain agent behavior; or use Agentic Resource Discovery (ARD) with approved-resource lists so protective DNS resolves only authorized domains. The author notes that internal roots can be operationally difficult and that relying on agents' own instructions has a conflict of interest. The excerpt also proposes standardized DNS records for agent directories and individual agents, while emphasizing that standards need actively managed controls.

### Source excerpt

This is both something old and something new. As with many cybersecurity-related matters, such as patching, AI means we need to focus on the basics as well as come to terms with the change it is making to our roles. A classic example of a basic that can be addressed to improve security appears in [...] The post Something Old, Something New: DNS and the Autonomous AI Agent appeared first on Infoblox Blog.

## The Story Behind Creating DNS | Paul Mockapetris

DevFeed: [The Story Behind Creating DNS | Paul Mockapetris](<https://devfeed.tech/articles/the-story-behind-creating-dns-paul-mockapetris-90407.md>)

Original publisher: [Read original article](<https://www.developing.dev/p/e071-paul-mockapetris>)

Author: Ryan Peterman

Published: 2026-10-19T13:05:34Z

Content type: article

Language: en

Sources: [The Developing Dev](<https://devfeed.tech/sources/the-developing-dev.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [DNSSEC](<https://devfeed.tech/topics/dnssec.md>)

Tags: [dns](<https://devfeed.tech/tags/dns.md>), [domain](<https://devfeed.tech/tags/domain.md>), [internet](<https://devfeed.tech/tags/internet.md>), [interview](<https://devfeed.tech/tags/interview.md>)

### AI overview

In this interview, DNS creator Paul Mockapetris recounts why the Internet outgrew a centrally maintained host table and how DNS was designed to distribute namespace management while supporting growth. He explains hierarchical name lookup, caching, the transition from host tables, and changes in DNS operations and governance. The conversation also touches on his computing career and the evolution of AI.

### Source excerpt

This interview is with Paul Mockapetris, the creator of the internet's Domain Name System (DNS).

## Web Bot Auth: How to identify AI agents and set policy for them

DevFeed: [Web Bot Auth: How to identify AI agents and set policy for them](<https://devfeed.tech/articles/web-bot-auth-how-to-identify-ai-agents-and-set-policy-for-them-90302.md>)

Original publisher: [Read original article](<https://workos.com/blog/web-bot-auth-identify-ai-agents>)

Author: WorkOS

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Bot Management](<https://devfeed.tech/topics/bot-management.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Application Services](<https://devfeed.tech/topics/application-services.md>), [DNSSEC](<https://devfeed.tech/topics/dnssec.md>), [sigstore policy controller](<https://devfeed.tech/topics/sigstore-policy-controller.md>), [reCAPTCHA](<https://devfeed.tech/topics/recaptcha.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [audit](<https://devfeed.tech/tags/audit.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bot-traffic](<https://devfeed.tech/tags/bot-traffic.md>), [bots](<https://devfeed.tech/tags/bots.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [policy](<https://devfeed.tech/tags/policy.md>)

### AI overview

The article explains how Web Bot Auth lets websites verify which operator sent an automated request through signed HTTP requests and a public key directory. It covers adoption by Cloudflare and AWS, the limits of identifying an operator without identifying the user or determining authorization, and the site policies needed for quotas, permissions, unsigned traffic, and key revocation. The article argues that identification works only when paired with decisions about what verified agents may do.

### Source excerpt

Wikimedia asked AI companies to make their agents identifiable. Web Bot Auth, an IETF draft already verified by Cloudflare and AWS, does that. The hard part is the policy you attach.

## SCIM for AI, one year later: What's changed in the IETF agent identity draft

DevFeed: [SCIM for AI, one year later: What's changed in the IETF agent identity draft](<https://devfeed.tech/articles/scim-for-ai-one-year-later-what-s-changed-in-the-ietf-agent-identity-draft-62739.md>)

Original publisher: [Read original article](<https://workos.com/blog/scim-agentic-identity-one-year-later>)

Author: WorkOS

Published: 2026-09-30T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [identity](<https://devfeed.tech/tags/identity.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [json](<https://devfeed.tech/tags/json.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

The article traces how two competing IETF drafts for representing AI agents in SCIM moved toward a jointly authored draft. The earlier proposals differed on whether an agent should have its own identity resource or be modeled in relation to an application. By March 2026, the consolidation effort had raised the question of what SCIM should cover.

### Source excerpt

A year ago, two competing IETF drafts were racing to define how SCIM represents AI agents. Here's what changed, and why the companies behind them are now writing one draft together.

## Content Signals in robots.txt

DevFeed: [Content Signals in robots.txt](<https://devfeed.tech/articles/content-signals-in-robots-txt-89077.md>)

Original publisher: [Read original article](<https://specification.website/spec/agent-readiness/content-signals/>)

Author: Joost de Valk

Published: 2026-09-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>)

Tags: [agent-readiness](<https://devfeed.tech/tags/agent-readiness.md>), [ai-crawlers](<https://devfeed.tech/tags/ai-crawlers.md>), [block](<https://devfeed.tech/tags/block.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [gptbot](<https://devfeed.tech/tags/gptbot.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [optional](<https://devfeed.tech/tags/optional.md>)

### AI overview

Content Signals adds proposed directives to robots.txt for declaring whether content may be used for search, live AI input, or AI training. The article explains the syntax, how to configure and verify it, and cautions that the proposal is unsettled and many crawlers may ignore it.

### Source excerpt

Add Content-Signal directives to robots.txt to declare whether AI crawlers may search, ingest, or train on your content. An emerging IETF AI Preferences / IAB Tech Lab proposal that some validators already check.

## One token, two jobs: ID-JAG in enterprise access and agent registration

DevFeed: [One token, two jobs: ID-JAG in enterprise access and agent registration](<https://devfeed.tech/articles/one-token-two-jobs-id-jag-in-enterprise-access-and-agent-registration-59475.md>)

Original publisher: [Read original article](<https://workos.com/blog/one-token-two-jobs-id-jag-in-enterprise-access-and-agent-registration>)

Author: WorkOS

Published: 2026-09-24T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

This article compares two uses of the ID-JAG JWT authorization grant: enterprise authorization for AI clients accessing MCP servers, and agent registration that lets a service identify the user behind an agent and provision an account. It explains that the same token type serves different issuers, trust anchors, and operational risks, and notes that ID-JAG is an active IETF OAuth working group document rather than an RFC.

### Source excerpt

The same token type is solving two unrelated problems. Knowing which one you are in decides what you build.

## The OSPF MTU Mismatch Saga

DevFeed: [The OSPF MTU Mismatch Saga](<https://devfeed.tech/articles/the-ospf-mtu-mismatch-saga-58408.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/09/ospf-mtu-saga/>)

Published: 2026-09-23T06:07:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [MTU mismatch](<https://devfeed.tech/topics/mtu-mismatch.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>)

Tags: [compatibility](<https://devfeed.tech/tags/compatibility.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [mtu](<https://devfeed.tech/tags/mtu.md>), [mtu-mismatch](<https://devfeed.tech/tags/mtu-mismatch.md>), [networking](<https://devfeed.tech/tags/networking.md>), [ospf](<https://devfeed.tech/tags/ospf.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [routers](<https://devfeed.tech/tags/routers.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

This article examines the OSPF MTU mismatch problem, including how oversized packets, IP fragmentation, interface MTU checks, and protocol revisions affect router adjacency and database exchange.

### Source excerpt

The OSPF is stuck in database exchange state symptom is probably familiar to every networking engineer who ever had to pass a certification exam. It's caused by the MTU mismatch between adjacent OSPF routers. The recent (unexpected) trip into the how crazy is it to declare your interface MTU to be zero wonderland uncovered way more than I ever wanted to know about this arcane topic. Here are a few highlights (thanks a million to Aleksey Popov for researching this topic and posting information here, here, and here). Read more ...

## The RIPE Chair Team Reports - September 2026

DevFeed: [The RIPE Chair Team Reports - September 2026](<https://devfeed.tech/articles/the-ripe-chair-team-reports-september-2026-58043.md>)

Original publisher: [Read original article](<https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-september-2026/>)

Author: Mirjam Kühne

Published: 2026-09-22T12:09:07Z

Content type: article

Language: en

Sources: [RIPE Labs](<https://devfeed.tech/sources/ripe-labs.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>)

Tags: [code-of-conduct](<https://devfeed.tech/tags/code-of-conduct.md>), [community](<https://devfeed.tech/tags/community.md>), [dns](<https://devfeed.tech/tags/dns.md>), [events](<https://devfeed.tech/tags/events.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [network](<https://devfeed.tech/tags/network.md>), [policy](<https://devfeed.tech/tags/policy.md>), [reports](<https://devfeed.tech/tags/reports.md>), [ripe](<https://devfeed.tech/tags/ripe.md>), [routing](<https://devfeed.tech/tags/routing.md>), [rpki](<https://devfeed.tech/tags/rpki.md>), [rtbh](<https://devfeed.tech/tags/rtbh.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

The RIPE Chair Team reports on upcoming RIPE meetings, fellowship applications, updates to the Code of Conduct Team document, policy proposals, Working Group activity, routing discussions involving RTBH and RPKI, DNS concerns related to sanctions, and recent IETF activity.

### Source excerpt

With RIPE 93 fast approaching, the RIPE Chair Team shares updates on policy and Working Group activity, the Code of Conduct Team document, and recent events across the Internet community.

## The /3 Body Problem

DevFeed: [The /3 Body Problem](<https://devfeed.tech/articles/the-3-body-problem-11451.md>)

Original publisher: [Read original article](<https://labs.ripe.net/author/remco-van-mook/the-3-body-problem/>)

Author: Remco van Mook

Published: 2026-09-10T09:22:46Z

Content type: article

Language: en

Sources: [RIPE Labs](<https://devfeed.tech/sources/ripe-labs.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [internet](<https://devfeed.tech/tags/internet.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [networking](<https://devfeed.tech/tags/networking.md>), [policy](<https://devfeed.tech/tags/policy.md>), [space](<https://devfeed.tech/tags/space.md>)

### AI overview

The article examines how IPv6 addressing and policy mechanisms may need to evolve for space networking. It argues that terrestrial assumptions break down beyond low Earth orbit and calls for addressing policy questions now, including through the proposed EXPANSE working group.

### Source excerpt

A large chunk of IPv6 is heading for space, and every policy question about it is currently going to be deferred to the RIR communities. This article outlines what those questions look like, and argues why now is the time to start asking them.

## \[Podcast\] Measuring the impact of locally served root zone

DevFeed: [\[Podcast\] Measuring the impact of locally served root zone](<https://devfeed.tech/articles/podcast-measuring-the-impact-of-locally-served-root-zone-10857.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/09/03/podcast-measuring-the-impact-of-locally-served-root-zone/>)

Author: George Michaelson

Published: 2026-09-03T01:05:09Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [DNSSEC](<https://devfeed.tech/topics/dnssec.md>), [Network](<https://devfeed.tech/topics/network.md>), [Security](<https://devfeed.tech/topics/security.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dnssec](<https://devfeed.tech/tags/dnssec.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [network](<https://devfeed.tech/tags/network.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [research](<https://devfeed.tech/tags/research.md>), [security](<https://devfeed.tech/tags/security.md>), [standards](<https://devfeed.tech/tags/standards.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>)

### AI overview

This podcast discusses research into locally served root zones, a DNS resolver model that pre-fetches and stores the root zone. The study examined BIND, Unbound, and Knot Resolver across multiple configurations, including in-band retrieval and HTTPS fetching. It identified an Unbound bug and found that root zone updates can generate substantial network traffic, potentially exceeding traffic from more frequent queries for uncached data.

### Source excerpt

An analysis of the traffic impacts of locally served root zones, by Ilyas Rahimi at UvA.

## DNS at IETF 126

DevFeed: [DNS at IETF 126](<https://devfeed.tech/articles/dns-at-ietf-126-52697.md>)

Original publisher: [Read original article](<https://www.infoblox.com/blog/community/dns-at-ietf-126/>)

Author: Jim Mozley

Published: 2026-08-28T15:00:33Z

Content type: article

Language: en

Sources: [Infoblox](<https://devfeed.tech/sources/infoblox-blog.md>)

Topics: [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [DNS security](<https://devfeed.tech/topics/dns-security.md>), [DNSSEC](<https://devfeed.tech/topics/dnssec.md>)

Tags: [community](<https://devfeed.tech/tags/community.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-at-ietf-126](<https://devfeed.tech/tags/dns-at-ietf-126.md>), [dns-security](<https://devfeed.tech/tags/dns-security.md>), [dnssec](<https://devfeed.tech/tags/dnssec.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [internet](<https://devfeed.tech/tags/internet.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [synchronization](<https://devfeed.tech/tags/synchronization.md>)

### AI overview

This article reviews DNS-related discussions from the IETF 126 hybrid meeting, including work on DNS operations, delegated domain management, and automating synchronization between parent and child zones. It describes a proposed DDNS-based mechanism secured with SIG(0) and related DNSSEC operational considerations.

### Source excerpt

The Internet Engineering Task Force (IETF) is the organization where development of the Domain Name System (DNS) protocol takes place. Work takes place within Working Groups that each have a mailing list, and you can see archives on the IETF Datatracker, along with the agenda and presentations from meetings that take place three times a [...] The post DNS at IETF 126 appeared first on Infoblox Blog.

## The emerging role of AI in governance discussion

DevFeed: [The emerging role of AI in governance discussion](<https://devfeed.tech/articles/the-emerging-role-of-ai-in-governance-discussion-10849.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/08/26/the-emerging-role-of-ai-in-governance-discussion/>)

Author: George Michaelson

Published: 2026-08-26T04:50:50Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Strategy](<https://devfeed.tech/topics/ai-strategy.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [content](<https://devfeed.tech/tags/content.md>), [eu](<https://devfeed.tech/tags/eu.md>), [governance](<https://devfeed.tech/tags/governance.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [llm](<https://devfeed.tech/tags/llm.md>), [standards](<https://devfeed.tech/tags/standards.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>)

### AI overview

The article examines an ongoing IETF debate over the use and disclosure of LLM-generated text in drafts, standards work, and discussions. It also compares these concerns with EU efforts to promote transparency and labelling of AI-generated or AI-modified content.

### Source excerpt

A growing debate within the IETF is exploring how AI-generated content should be used and disclosed in standards discussions.

## AI, IPv6, and the future Internet at IETF 126

DevFeed: [AI, IPv6, and the future Internet at IETF 126](<https://devfeed.tech/articles/ai-ipv6-and-the-future-internet-at-ietf-126-10846.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/08/25/ai-ipv6-and-the-future-internet-at-ietf-126/>)

Author: Anlei Hu

Published: 2026-08-25T01:20:50Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [Internet](<https://devfeed.tech/topics/internet.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Network](<https://devfeed.tech/topics/network.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Security](<https://devfeed.tech/topics/security.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [dns](<https://devfeed.tech/tags/dns.md>), [guest-post](<https://devfeed.tech/tags/guest-post.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [internet](<https://devfeed.tech/tags/internet.md>), [internet-infrastructure](<https://devfeed.tech/tags/internet-infrastructure.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [nat](<https://devfeed.tech/tags/nat.md>), [network](<https://devfeed.tech/tags/network.md>), [networks](<https://devfeed.tech/tags/networks.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [security](<https://devfeed.tech/tags/security.md>), [standards](<https://devfeed.tech/tags/standards.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

The article reports on IETF 126 discussions about how AI is shaping Internet infrastructure. It presents IPv6 as important for the scale, globally unique addressing, and traceability required by distributed AI deployments and agents, while DNS remains central to service discovery. It also covers IPv4/IPv6 mapping, NAT-related identity and security concerns, SRv6, low-latency forwarding, IOAM telemetry, and proposals for DNS-based AI agent discovery.

### Source excerpt

Guest Post: At IETF 126, discussions highlighted how AI is beginning to shape the future of Internet infrastructure. Participants identified IPv6 as a critical foundation for large-scale AI ecosystems and explored new approaches.

## SCIM Deprovisioning Is a Promise Your App Probably Breaks

DevFeed: [SCIM Deprovisioning Is a Promise Your App Probably Breaks](<https://devfeed.tech/articles/scim-deprovisioning-is-a-promise-your-app-probably-breaks-16056.md>)

Original publisher: [Read original article](<https://workos.com/blog/scim-deprovisioning-promise-your-app-breaks>)

Author: WorkOS

Published: 2026-08-06T01:29:36Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [API](<https://devfeed.tech/topics/api.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [http](<https://devfeed.tech/tags/http.md>), [identity](<https://devfeed.tech/tags/identity.md>), [idp](<https://devfeed.tech/tags/idp.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [json](<https://devfeed.tech/tags/json.md>), [net-conf](<https://devfeed.tech/tags/net-conf.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [schema](<https://devfeed.tech/tags/schema.md>), [security](<https://devfeed.tech/tags/security.md>), [standards](<https://devfeed.tech/tags/standards.md>), [state](<https://devfeed.tech/tags/state.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

This article explains that SCIM deprovisioning updates identity state but does not automatically invalidate an application's sessions, refresh tokens, or API keys. It describes how identity providers commonly use soft deactivation and why applications must explicitly handle the resulting offboarding state.

### Source excerpt

SCIM tells you a user is gone, but sessions, refresh tokens, and API keys often outlive deprovisioning. Here's why offboarding needs more than a user row.

## HTTP gets a QUERY method so complex searches can stop pretending to be POST

DevFeed: [HTTP gets a QUERY method so complex searches can stop pretending to be POST](<https://devfeed.tech/articles/http-gets-a-query-method-so-complex-searches-can-stop-pretending-to-be-post-47896.md>)

Original publisher: [Read original article](<https://www.devclass.com/development/2026/07/14/http-gets-a-query-method-so-complex-searches-can-stop-pretending-to-be-post/5270400>)

Author: Joab Jackson

Published: 2026-07-14T10:52:00Z

Content type: news

Language: en

Sources: [DevClass.com](<https://devfeed.tech/sources/devclass-com.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [client](<https://devfeed.tech/topics/client.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Server](<https://devfeed.tech/topics/server.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [caching](<https://devfeed.tech/tags/caching.md>), [client](<https://devfeed.tech/tags/client.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [html](<https://devfeed.tech/tags/html.md>), [http](<https://devfeed.tech/tags/http.md>), [http-server](<https://devfeed.tech/tags/http-server.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [query](<https://devfeed.tech/tags/query.md>), [rfc](<https://devfeed.tech/tags/rfc.md>), [web-browser](<https://devfeed.tech/tags/web-browser.md>)

### AI overview

The IETF has published the QUERY HTTP request method, designed for complex search requests that need a request body while remaining safe and idempotent. The method enables intermediaries such as proxies, CDNs, and browsers to cache and retry these requests more safely than POST, while avoiding unwieldy or sensitive data in long GET URLs.

### Source excerpt

'Idempotent' may be jargon, but the term performs an important job in HTTP as a hall pass that gives ...

## Helping build shared standards for advanced AI

DevFeed: [Helping build shared standards for advanced AI](<https://devfeed.tech/articles/helping-build-shared-standards-for-advanced-ai-6448.md>)

Original publisher: [Read original article](<https://openai.com/index/helping-build-shared-standards-for-advanced-ai>)

Published: 2026-06-23T13:00:00Z

Content type: article

Language: en

Sources: [OpenAI News](<https://devfeed.tech/sources/openai-news.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [Frontier Model](<https://devfeed.tech/topics/frontier-model.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Coalition for Secure AI](<https://devfeed.tech/topics/coalition-for-secure-ai.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-standards](<https://devfeed.tech/tags/ai-standards.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [global](<https://devfeed.tech/tags/global.md>), [global-affairs](<https://devfeed.tech/tags/global-affairs.md>), [governance](<https://devfeed.tech/tags/governance.md>), [institutions](<https://devfeed.tech/tags/institutions.md>), [international](<https://devfeed.tech/tags/international.md>), [internet-engineering-task-force](<https://devfeed.tech/tags/internet-engineering-task-force.md>), [openai](<https://devfeed.tech/tags/openai.md>), [practices](<https://devfeed.tech/tags/practices.md>), [safety](<https://devfeed.tech/tags/safety.md>), [standards](<https://devfeed.tech/tags/standards.md>)

### AI overview

OpenAI says the Appia Foundation, which it helped found and which is hosted by the Linux Foundation, will develop open, modular specifications that turn existing standards and frameworks into practical AI assessment criteria. The aim is reusable third-party evidence and compatible assessment practices across organizations and jurisdictions. The source links this effort to OpenAI's governance proposals, its Preparedness and Frontier Governance Frameworks, and evaluation partnerships with US CAISI and UK AISI, which it says led to system improvements. It also describes disclosure practices for frontier evaluations, including the system tested, tool access, harness, methods, resources, and validation checks. Appia is presented as a way to make such practices interoperable across the AI supply chain, alongside OpenAI's participation in other standards and pre-standardization groups.

### Source excerpt

OpenAI helps build shared standards for advanced AI, supporting evaluation frameworks, safety practices, and global cooperation through the Appia Foundation.

## Browser-Based OAuth Client Security Risks and Migration to Safer Architectures

DevFeed: [Browser-Based OAuth Client Security Risks and Migration to Safer Architectures](<https://devfeed.tech/articles/browser-based-oauth-client-the-architecture-you-shouldn-t-be-using-43243.md>)

Original publisher: [Read original article](<https://fusionauth.io/blog/browser-based-oauth-client-security-architecture>)

Author: Nathan Contino, Kim Maida

Published: 2026-06-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [FusionAuth](<https://devfeed.tech/sources/fusionauth-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Security](<https://devfeed.tech/topics/security.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [browser](<https://devfeed.tech/topics/browser.md>), [client](<https://devfeed.tech/topics/client.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [BFF](<https://devfeed.tech/topics/bff.md>), [MFA](<https://devfeed.tech/topics/mfa.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [bff](<https://devfeed.tech/tags/bff.md>), [browser](<https://devfeed.tech/tags/browser.md>), [client](<https://devfeed.tech/tags/client.md>), [education](<https://devfeed.tech/tags/education.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

This article explains why the Browser-Based OAuth Client pattern is considered the least secure of the discussed OAuth architectures. It describes risks from exposing tokens in browser storage, outlines situations where the pattern is unacceptable, discusses risk reduction, and covers migration to architectures that keep tokens out of the browser.

### Source excerpt

Why BBOC is the least secure OAuth pattern, when it's acceptable, how to implement it safely, and how to migrate to secure architectures.

## Dutch Internet pioneer Jaap Akkerhuis Knighted for Exceptional Contribution to Society

DevFeed: [Dutch Internet pioneer Jaap Akkerhuis Knighted for Exceptional Contribution to Society](<https://devfeed.tech/articles/dutch-internet-pioneer-jaap-akkerhuis-knighted-for-exceptional-contribution-to-society-48594.md>)

Original publisher: [Read original article](<https://blog.nlnetlabs.nl/dutch-internet-pioneer-jaap-akkerhuis-knighted-for-exceptional-contribution-to-society/>)

Author: Team NLnet Labs

Published: 2026-04-24T09:00:55Z

Content type: news

Language: en

Sources: [NLnet Labs](<https://devfeed.tech/sources/the-nlnet-labs-blog.md>)

Topics: [Internet](<https://devfeed.tech/topics/internet.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Security](<https://devfeed.tech/topics/security.md>), [standard](<https://devfeed.tech/topics/standard.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Automation](<https://devfeed.tech/topics/automation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [dutch](<https://devfeed.tech/tags/dutch.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [governance](<https://devfeed.tech/tags/governance.md>), [icann](<https://devfeed.tech/tags/icann.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [internet](<https://devfeed.tech/tags/internet.md>), [internet-infrastructure](<https://devfeed.tech/tags/internet-infrastructure.md>), [operational](<https://devfeed.tech/tags/operational.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [security](<https://devfeed.tech/tags/security.md>), [society](<https://devfeed.tech/tags/society.md>), [standard](<https://devfeed.tech/tags/standard.md>)

### AI overview

Jaap Akkerhuis, a Dutch Internet pioneer and protocol designer, was awarded Knight of the Order of the Dutch Lion for his contributions to Internet infrastructure, DNS security, domain-name automation standards, and operational coordination.

### Source excerpt

Jaap Akkerhuis was awarded Knight of the Order of the Dutch Lion on April 24, 2026. It is the highest civilian order of chivalry in the Netherlands, conferred on persons who have rendered outstanding service to society.

## Cultivating a robust and efficient quantum-safe HTTPS

DevFeed: [Cultivating a robust and efficient quantum-safe HTTPS](<https://devfeed.tech/articles/cultivating-a-robust-and-efficient-quantum-safe-https-19812.md>)

Original publisher: [Read original article](<http://security.googleblog.com/2026/02/cultivating-robust-and-efficient.html>)

Author: Google (noreply@blogger.com)

Published: 2026-02-27T17:01:00Z

Content type: release

Language: en

Sources: [Google Online Security](<https://devfeed.tech/sources/google-online-security.md>)

Topics: [Post-quantum cryptography](<https://devfeed.tech/topics/post-quantum-cryptography.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Certificate Transparency](<https://devfeed.tech/topics/certificate-transparency.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [browser](<https://devfeed.tech/tags/browser.md>), [ca](<https://devfeed.tech/tags/ca.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificate-transparency](<https://devfeed.tech/tags/certificate-transparency.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [certification](<https://devfeed.tech/tags/certification.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [computers](<https://devfeed.tech/tags/computers.md>), [computing](<https://devfeed.tech/tags/computing.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [https](<https://devfeed.tech/tags/https.md>), [none](<https://devfeed.tech/tags/none.md>), [quantum](<https://devfeed.tech/tags/quantum.md>), [robust](<https://devfeed.tech/tags/robust.md>)

### AI overview

Chrome says it has no immediate plan to add post-quantum X.509 certificates to the Chrome Root Store. Instead, it is developing Merkle Tree Certificates (MTCs) with partners and the IETF PLANTS working group. MTCs use a CA-signed tree head and compact proofs of certificate inclusion, aiming to reduce TLS handshake data while retaining public transparency. Chrome's staged plan begins with a Cloudflare feasibility study in which each MTC connection is backed by a trusted X.509 certificate. It intends to bootstrap public MTCs with qualifying Certificate Transparency log operators in Q1 2027, then establish a dedicated MTC-only quantum-resistant root store and onboarding path in Q3 2027, including site opt-in downgrade protections. Chrome also describes possible ecosystem changes, including ACME-only workflows, updated revocation methods, reproducible domain-control validation, and continuous external monitoring. Traditional post-quantum X.509 may later be supported for private PKIs.

### Source excerpt

Posted by Chrome Secure Web and Networking Team Today we're announcing a new program in Chrome to make HTTPS certificates secure against quantum computers. The Internet Engineering Task Force (IETF) recently created a working group, PKI, Logs, And Tree Signatures ("PLANTS"), aiming to address the performance and bandwidth challenges that the increased size of quantum-resistant cryptography introduces into TLS connections requiring Certificate Transparency (CT). We recently shared our call to action to secure quantum computing and have written about challenges introduced by quantum-resistant cryptography and some of the steps we've taken to address them in earlier blog posts. To ensure the scalability and efficiency of the ecosystem, Chrome has no immediate plan to add traditional X.509 certificates containing post-quantum cryptography to the Chrome Root Store. Instead, Chrome, in collaboration with other partners, is developing an evolution of HTTPS certificates based on Merkle Tree Certificates (MTCs), currently in development in the PLANTS working group. MTCs replace the heavy, serialized chain of signatures found in traditional PKI with compact Merkle Tree proofs. In this model, a Certification Authority (CA) signs a single "Tree Head" representing potentially millions of certificates, and the "certificate" sent to the browser is merely a lightweight proof of inclusion in that tree. Why MTCs? MTCs enable the adoption of robust post-quantum algorithms without incurring the massive bandwidth penalty of classical X.509 certificate chains. They also decouple the security strength of the corresponding cryptographic algorithm from the size of the data transmitted to the user. By shrinking the authentication data in a TLS handshake to the absolute minimum, MTCs aim to keep the post-quantum web as fast and seamless as today's internet, maintaining high performance even as we adopt stronger security. Finally, with MTCs, transparency is a fundamental property of issuance:

[Next page](<https://devfeed.tech/topics/ietf.md?cursor=WyIyMDI2LTAyLTI3VDE3OjAxOjAwKzAwOjAwIiwgIjBiMjdkNDk1LWNmZmEtNDFlNi1iNGE4LWRlZjJkMDQ0MzU0ZiJd>)