rfc9078v2.txt   rfc9078.txt 
Internet Engineering Task Force (IETF) D. Crocker Internet Engineering Task Force (IETF) D. Crocker
Request for Comments: 9078 Brandenburg InternetWorking Request for Comments: 9078 Brandenburg InternetWorking
Category: Experimental R. Signes Category: Experimental R. Signes
ISSN: 2070-1721 Fastmail ISSN: 2070-1721 Fastmail
N. Freed N. Freed
Oracle Oracle
July 2021 August 2021
Reaction: Indicating Summary Reaction to a Message Reaction: Indicating Summary Reaction to a Message
Abstract Abstract
The popularity of social media has led to user comfort with easily The popularity of social media has led to user comfort with easily
signaling basic reactions to an author's posting, such as with a signaling basic reactions to an author's posting, such as with a
'thumbs up' or 'smiley' graphic. This specification permits a 'thumbs up' or 'smiley' graphic. This specification permits a
similar facility for Internet Mail. similar facility for Internet Mail.
skipping to change at line 150 skipping to change at line 150
base-emojis = thumbs-up / thumbs-down / grinning-face / base-emojis = thumbs-up / thumbs-down / grinning-face /
frowning-face / crying-face frowning-face / crying-face
; Basic set of emojis, drawn from [Emoji-Seq] ; Basic set of emojis, drawn from [Emoji-Seq]
; thumbs-up = {U+1F44D} ; thumbs-up = {U+1F44D}
; thumbs-down = {U+1F44E} ; thumbs-down = {U+1F44E}
; grinning-face = {U+1F600} ; grinning-face = {U+1F600}
; frowning-face = {U+2639} ; frowning-face = {U+2639}
; crying-face = {U+1F622} ; crying-face = {U+1F622}
The part-content is either the entire content portion of a message's The part-content is either the message's single MIME body or the
single MIME body or the content portion of the first MIME multipart content portion of the first MIME multipart body part.
body part that constitutes a message's body.
The ABNF rule emoji-sequence is inherited from [Emoji-Seq]. It The ABNF rule emoji-sequence is inherited from [Emoji-Seq]. It
defines a set of Unicode code point sequences, which must then be defines a set of Unicode code point sequences, which must then be
encoded as UTF-8. Each sequence forms a single pictograph. The BNF encoded as UTF-8. Each sequence forms a single pictograph. The BNF
syntax used in [Emoji-Seq] differs from [ABNF] and MUST be syntax used in [Emoji-Seq] differs from [ABNF] and MUST be
interpreted as used in Unicode documentation. The referenced interpreted as used in Unicode documentation. The referenced
document describes these as sequences of code points. document describes these as sequences of code points.
| Note: The part-content can first be parsed into candidate | Note: The part-content can first be parsed into candidate
| reactions, separated by WSP. Each candidate reaction that does | reactions, separated by WSP. Each candidate reaction that does
skipping to change at line 342 skipping to change at line 341
Description: Permit a recipient to respond by signaling basic Description: Permit a recipient to respond by signaling basic
reactions to an author's posting, such as with a 'thumbs up' or reactions to an author's posting, such as with a 'thumbs up' or
'smiley' graphic 'smiley' graphic
8. Experimental Goals 8. Experimental Goals
The basic, email-specific mechanics for this capability are well The basic, email-specific mechanics for this capability are well
established and well understood. Points of concern, therefore, are: established and well understood. Points of concern, therefore, are:
* Technical issues in using emojis within a message body part * Technical issues in using emojis within a message body
* Market interest * Market interest
* Usability * Usability
So the questions to answer for this Experimental specification are: So the questions to answer for this Experimental specification are:
* Is there demonstrated interest by MUA developers? * Is there demonstrated interest by MUA developers?
* If MUA developers add this capability, is it used by authors? * If MUA developers add this capability, is it used by authors?
 End of changes. 3 change blocks. 
5 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/