@techreport{vasylenko-e2ee-http-00,
    number =    {draft-vasylenko-e2ee-http-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-vasylenko-e2ee-http/00/},
    author =    {Vitaliy Vasylenko},
    title =     {{End-to-End Encryption for HTTP APIs Using X25519 and AES-GCM}},
    pagetotal = 32,
    year =      2026,
    month =     jun,
    day =       4,
    abstract =  {This document specifies an application-layer end-to-end encryption (E2EE) scheme for HTTP APIs. The scheme uses X25519 Elliptic Curve Diffie-Hellman (ECDH) for key agreement, HKDF-SHA256 for key derivation, and AES-GCM (with 128-, 192-, or 256-bit keys) for authenticated encryption of request and response payloads. Server public keys are discovered through a Well-Known URI and authenticated either by TLS or by a stronger out-of-band trust mechanism, depending on the deployment threat model. The scheme is designed to provide confidentiality and integrity of payloads independent of, and in addition to, transport-layer security such as TLS. It provides replay protection and key rotation.},
}