I also object.
This document is better than most IETF documents. I don't understand the
GenArt review here, and I know more about JSON than most humans on earth.
thanks,
Rob
On Thu, Aug 10, 2023 at 1:14 PM James wrote:
> (speaking only for myself here as a JSON Path enthusiast)
>
> Thank you
Hi,
I put up a PR:
https://github.com/httpwg/http-extensions/pull/2561
The current text is something one would hear in spoken American English,
but it's not usually done in writing, and it mixes pluralization and the
passive voice in an unidiomatic way.
I'm not attached to my suggestion, but
On Sun, Dec 29, 2019 at 5:51 AM Mohit Sethi via Datatracker <
nore...@ietf.org> wrote:
> The document seems focused on TLS 1.2 (and does not talk about TLS 1.3).
>
That seems extremely odd.
TLS 1.2 is RFC 5246, from 2008. https://tools.ietf.org/html/rfc5246
TLS 1.3 is RFC 8446, from 2018.
There is a typo in section 3.
"(though ISOC employees may independently continue to make technical
--> contributuins <-- as individuals)"
thanks,
Rob
On Thu, Aug 22, 2019 at 12:08 PM Livingood, Jason <
jason_living...@comcast.com> wrote:
> Thanks - all of that resolved in a -06 update to
