draft-ambekar-oauth-epop
JSON Web Token (JWT) Profile for OAuth 2.0 Enveloped Proof of Possession (EPOP)
This specification defines a profile for OAuth 2.0 sender-constrained
credentials in which authorization codes, access tokens, and refresh
tokens are cryptographically bound to the client's private key as a
single inseparable envelope. The profile extends sender-constraining
beyond HTTP to non-HTTP transports including MQTT, Kafka, the Model
Context Protocol (MCP), gRPC, and SASL-based protocols such as those
defined in [RFC7628]. It introduces atomic proof-of-possession key
rotation, enabling clients to rotate key pairs without disrupting
active sessions, and an offline-derived client nonce (cnonce) that
eliminates the server-issued nonce round-trip required by existing
mechanisms — enabling stateless proof validation critical for non-
HTTP and high-throughput deployments. Authorization servers,
resource servers, and clients from different vendors can implement
this profile interoperably.