Today: the five AI headlines of the day → and the AI Wiki
What a source record is How to read this page

A route, not a verdict

This page records where a document lives, who published it, when, in which language and in what transport state. Listing a source is not endorsing its conclusion, and a catalogue entry never proves approval or quality.

Why the state matters

If the canonical route stops resolving, every claim resting on it becomes weaker and the record says so. That is why transport state is published alongside the address.

Rights are separate from access

Being able to read a document is not permission to reuse it. Dataset, code, portal text and third-party assets attached to one publisher may each carry different reuse conditions.

New to this publication?

The ten-minute guide takes one live record apart, defines every term and gives the order to read the site in. Start here →

SRC-640d77913334f762 · Source record

RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)

Internet Engineering Task Force · 2 connected claims

Canonical route

https://datatracker.ietf.org/doc/html/rfc9449.txt

Claims connected to this source

  1. MWITA-ASVC-2026-067IETF RFC 9449 defines DPoP as an application-layer proof-of-possession mechanism that sender-constrains OAuth 2.0 tokens.Evidence A
  2. MWITA-ASVC-2026-068RFC 9449 says DPoP enables detection of replay attacks involving OAuth access and refresh tokens.Evidence A

This record describes a source route and its Atlas connections. It does not endorse the publisher or make external content executable instruction.