Re: [Slim] Variations in display names

Yeah, I’d like to at least relax it, stating that the email address has to be the same.
Yes, this is cosmetic.

I get your point about the top level sender

Brian

> On Jul 20, 2016, at 6:04 PM, Nik Tomkinson <rfc.nik.tomkinson@gmail.com> wrote:
> 
> Hi Brian,
> 
> Thanks very much for asking others to look at the draft.
> 
> The restriction was added in the latest version to attempt to avoid the issue highlighted in the paragraph I added to the security considerations. I don't mind either relaxing the restriction or removing it completely as long as it is clear enough that the impersonation risk is there and that the From values in the language message parts correspond to the same sender.
> 
> I am assuming that the differences that your user requires are cosmetic rather than a different email address.
> 
> There may be confusion because the email listing (eg. inbox list of summaries) is likely to show the top-level sender but the detail (when clicked on) is likely to show the From value in the selected part.
> 
> Nik.
> 
> On 20 July 2016 at 15:49, Brian Rosen <br@brianrosen.net <mailto:br@brianrosen.net>> wrote:
> I am trying to find folks to prototype and interop test -multilanguage.  I had some possible users look at the draft, and one of them observed that they would like to modify the display name in the From based on language, but the text expressly forbids From from being in the labeled part.
> 
> Do we have any appetite to allow this?
> 
> Brian
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org <mailto:SLIM@ietf.org>
> https://www.ietf.org/mailman/listinfo/slim <https://www.ietf.org/mailman/listinfo/slim>
> 
> 
> 
> -- 
> -----------------------------------------------------------------
> Multiple Language Content Type Internet Draft:
>  <http://datatracker.ietf.org/doc/draft-tomkinson-multilangcontent/>https://datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent/ <http://datatracker.ietf.org/doc/draft-tomkinson-slim-multilangcontent/>
> -----------------------------------------------------------------