Misleading title, at least for the link — but it uncovers highly interesting material, as OP notes below. The internet draft expired last year and hasn’t been

Misleading title, at least for the link — but it uncovers highly interesting material, as OP notes below. The internet draft expired last year and hasn’t been renewed. Direct quote warning others not to overstate it: > Note: This isn't a proposal that's well thought out, and stamped solidly with the Google Seal of Approval. It's a collection of interesting ideas for discussion, nothing more, nothing less. A better link would be to the Cookie Store API proposal, or to the mailing list post linked by OP: https://groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/bBdx2xIB7OQ/k2fMXf-WAAAJ https://groups.google.com/a/chromium.org/forum/m/#!msg/blink... > Although there are long term plans to deprecate cookies, we recognize that with the existing heavy usage of cookies, it will take a long time for this to happen. We think that by introducing this API now, it will help the current state of cookies by allowing developers to use them more judiciously and make better decisions about security while also improving performance. They do link “deprecate cookies” to that same expired spec, but it isn’t really good context for what their plans are, compared to the above list post.