Oblivious Relay Feedback
draft-rdb-ohai-feedback-to-proxy-09
| Document | Type |
Expired Internet-Draft
(candidate for ohai WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tirumaleswar Reddy.K , Dan Wing , Mohamed Boucadair , Roberto Polli | ||
| Last updated | 2023-11-15 (Latest revision 2023-05-14) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Servers often rate-limit incoming requests, for example, rate-limit based upon the source IP address to provide equitable service to clients. However, oblivious HTTP removes the ability for the server to distinguish amongst clients so the server can only rate-limit traffic from an Oblivious Relay Resource. This harms all clients behind that Oblivious Relay Resource. This specification enables a server to convey rate-limit information to an Oblivious Relay Resource, which can use it to apply rate-limit policies on clients. Cooperating Oblivious Relay Resources can thus provide more equitable service to their distinguishable clients without impacting on all clients behind that Oblivious Relay Resource.
Authors
Tirumaleswar Reddy.K
Dan Wing
Mohamed Boucadair
Roberto Polli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)