HTTP RateLimit headers | Lobsters

I see that RateLimit-Policy tries to cover wide scenarios and that results in a complex header. Some examples taken from the draft:

RateLimit-Policy: "burst";q=100;w=60,"daily";q=1000;w=86400
RateLimit-Policy: "default";q=100;w=10
RateLimit-Policy: "peruser";q=65535;qu="content-bytes";w=10;pk=:sdfjLJUOUH==:

A header must to carry metadata about a request or response, like RateLimit, not a complex policy that belongs to a group of requests, in this case with the same partition key. Headers were designed to be frugal.

But with the current scenario, as suggestion, maybe extend (a bit more) Content-Security-Policy with a simple definition combined with an static file in /.well-known/ratelimit.