Roberto Polli

Thanks @ioquatix for your detailed analysis! ## hyphens and single-header > To be consistent, it should be Foo-Bar-Baz. I'd see `RateLimit` more like `ETag` :) > if it's possible just...

> Regarding HPACK, it applies to both request and response headers equally. True, see the gain gap between requests and response though https://blog.cloudflare.com/hpack-the-silent-killer-feature-of-http-2/

> regarding the FAQ entry, I don't think I was advocating for a single header Before writing the draft I considered the single-header stuff we thought too when first dealing...

Since last year, we have now various implementers (see #1); changing field names will be impractical now.

@mnot tomorrow we'll present the draft to the new httpapi-wg: we hope to call for adoption :) Reopening as requested.

cc: @dlongley @msporny is this still maintained?

Seems reasonable. I'll provide further comment in the code though.

#### Compliant implementations: Zalando, IBM, 3scale, Kong, Dutch government, pipedrive, Envoy Explicit support via `RateLimit-*` or `X-RateLimit-*` from: - [x] [Red Hat 3scale](https://issues.redhat.com/browse/THREESCALE-3795) - [x] [Kong](https://github.com/Kong/kong/pull/5335) - [x] [Envoy proxy](https://github.com/envoyproxy/envoy/pull/12410)...

@bungle great work! Is there an ETA for the 2.0.0? Kudos to the Kong Team!

https://github.com/line/armeria Java API framework is implementing this spec. See https://github.com/line/armeria/blob/master/bucket4j/src/main/java/com/linecorp/armeria/common/throttling/ThrottlingHeaders.java#L24