Roberto Polli
Roberto Polli
Hi folks, if there is some interest in the connexion community we can continue to work on it....
I don't know if the workaround I wrote is good enough to cover all cases: iirc delving deeper in the subject that was more complex than it seemed (that's why...
It would be great to support ratelimiting via the [new ratelimit standardization proposal](https://tools.ietf.org/id/draft-polli-ratelimit-headers-01.html). The proposal was: - recently presented at the [HTTP Workgroup during the IETF Meeting](http://bit.ly/2qWhwwD) - implemented by...
For HTTP I think subsecond precision is an overkill due to RTT / intermediaries.
> The level of processing speed where just a (sub)second unstructured value > would help goes IMHO into the space of CoAP, not HTTP Seems reasonable to me. > Aka:...
I personally support (2) `Date: @2022-02-02T12:12:12Z` or `Date: @2022-02-02` because it covers similar use cases than HTTP-date. In case of (3) I think we can just use an Integer SF,...
Can we align on this for new spec? I think it improves readability...
I'd add the following tasks: - [ ] add an example of request-response - [ ] add paragraph in Security Considerations An `(audience)` can be reasonable as that decouples the...
cc: @mnot guidance welcome
Note: this has been fixed. the IANA Digest Algorithm Registry Note not to mention "message body" since it's not even mentioned in RFC3230. > This registry lists the algorithms that...