Harsha:

Thank you for following up on our discussion in the meeting. I like it when people use the email lists for this. We can get more done if we continue discussions between meetings.

That said,

As agreed at the meeting on the 2nd of August, I went through the RFC 6532 and checked whether header fields inherit the text encoding (UTF-8) from an Operating System of a device. Having tested with multiple devices with different OSs, It looks that header fields inherit from the Operating System for Sinhala.
RFC 6532 and other relevant RFCs state as either System or Systems where encoding is inherited.…

I'm sorry, I don't follow you.

If I were to summaries RFC 6532 <https://datatracker.ietf.org/doc/rfc6532/>, it would be "You can use UTF-8 in email headers". I don't see RFC 6532 talking about inheriting anything. Nor about permitting any additional encoding apart from UTF-8. Nor about getting information about encoding from systems.

Would you mind giving references to specific sections of RFC 6532, and/or give examples of what headers are interesting for Sinhala?

Therefore, IETF should clarify the above with more elaboration.

What sections of RFC 6532 would you have IETF change, and how?

I do not know Sinhala at all, so any explanations I can get will help me learn more.

Best regards,
    —Jim DeLaHunt

Dear Mark, Jim, and Seda,
As agreed at the meeting on the 2nd of August, I went through the RFC 6532 and checked whether header fields inherit the text encoding (UTF-8) from an Operating System of a device. Having tested with multiple devices with different OSs, It looks that header fields inherit from the Operating System for Sinhala.
RFC 6532 and other relevant RFCs state as either System or Systems where encoding is inherited. Therefore, IETF should clarify the above with more elaboration.
Thanks and regards
Harsha Wijayawardhana

On Tue, Aug 9, 2022 at 7:56 PM Seda Akbulut via UA-EAI <ua-eai@icann.org> wrote:

Dear EAI WG members,

 

Enclosed please find the meeting notes for the last meeting (02 Aug 2022).

 

Looking forward to meeting today (9 Aug) at 14:30 UTC.

 

Best regards,

Seda Akbulut

 

_______________________________________________
UA-EAI mailing list
UA-EAI@icann.org
https://mm.icann.org/mailman/listinfo/ua-eai
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

_______________________________________________
UA-EAI mailing list
UA-EAI@icann.org
https://mm.icann.org/mailman/listinfo/ua-eai
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

-- 
.   --Jim DeLaHunt, jdlh@jdlh.com     http://blog.jdlh.com/ (http://jdlh.com/)
      multilingual websites consultant

      2201-1000 Beach Ave, Vancouver BC V6E 4M2, Canada
         Canada mobile +1-604-376-8953