There is a working group WPACK which could have taken on the problem of how to package HTML, embedded image, JavaScript libraries in a way that could be interpreted in a sandboxed environment. Maybe what they are doing could be retargeted for such a purpose? -- https://LarryMasinter.net https://interlisp.org > -----Original Message----- > From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of Nick Hilliard > Sent: Tuesday, March 2, 2021 7:55 AM > To: ned+ietf@xxxxxxxxxxxxxxxxx > Cc: IETF Discussion Mailing List <ietf@xxxxxxxx> > Subject: Re: HTML for email > > ned+ietf@xxxxxxxxxxxxxxxxx wrote on 02/03/2021 14:08: > > And like it or not, outside the IETF the HTML horse left the barn a > > long time back. > > Bear in mind that even within the IETF, plenty of people view the entire > HTML email debate as flogging the proverbial dead horse, and when it rolls > around every several months, welcomes it in the same way that you might > welcome an outbreak of cold sores. > > > We can chose to deal with or ignore it, but getting it back in the > > barn is not an option. > Looking at this from a different perspective, in the twenty-something years > of discussion since Content-Type: text/html first appeared, have any > actionable and viable suggestions emerged about how to deal with html > email, other than stripping it off in the archived emails? > > Maybe the people who are upset about html email could form a working > group, take the discussion there and write up an ID with observations and > recommendations for html emails at the ietf? > > Nick
