L2/18-251 Re: Coded Hashes of Arbitrary Images From: Steven R. Loomis Status: Individual Contribution Date: 2018-07-23 Live document: via https://github.com/srl295/srl-unicode-proposals/issues/14 As the coauthor of the original proposal, I appreciate the analyis given in L2/18-203 as well as L2/16-379. As stated in the document, the general intent of the proposal was to move forward the state of the discussion of longer-term goals for UTS#51 Section 8. As such, the entire ecosystem and lifecycle of arbitrary images was not considered in-scope for an initial character encoding proposal. At this point, there has been much discussion of various encoding mechanisms, and some discussion of security considerations. I would agree that for any future proposal (including any revision of L2/16-105R), these ingredients are clearly needed: 1. participation from the major implementers of messaging protocols 2. a viable description of the entire lifecycle of arbitrary images and their interchange 3. more complete analysis of the security and privacy implications of 1. and 2. This co-author does not currently have plans for such a follow-on proposal. Steven ----- References: [UTS#51] - https://www.unicode.org/reports/tr51/ [L2/16-379] - https://www.unicode.org/L2/L2016/16379-hash-fdbk.html (Scherer) [L2/18-203] - https://www.unicode.org/L2/L2018/18203-coded-hashes.pdf (Davis) [L2/16-105R] - https://www.unicode.org/L2/L2016/16105r-unicode-image-hash.pdf (Loomis, Winstein, Lee) [this document] - via https://github.com/srl295/srl-unicode-proposals/issues/14 EOF