I quickly looked at draft-crocker-inreply-react-11 (actually at the
diffs between that and -10).
Just a nit:
In
The unicode character, represented here as "{U+1F44E}" for
readability, would actually be sent as the UTF-8-encoded character.
definitely 'unicode' should be capitalized. This is the only occasion
where 'unicode' appears in lower case except for an URI, where lower
case is what you want.
(It would have been great if this draft used actual Unicode; it's
exactly the kind of draft for which all the work on allowing full
Unicode in RFCs was done.)
Regards, Martin.
On 11/03/2021 02:21, Dave Crocker wrote:
On 3/8/2021 8:32 AM, Dave Crocker wrote:
Diff: https://www.ietf.org/rfcdiff?url2=draft-crocker-inreply-react-10
Are there any significant concerns that this version does not resolve?
If so, please explain how their resolution is essential to the utility
of this document.
d/
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
