- UA-discuss - lists.icann.org

ICANN81
by anil Jain 11 Dec '24

11 Dec '24

Dear UASG friends, Recently we had 26th AGM of ICANN at Istanbul, Turkey. Snapshot of ICANN81 wrt UA is as follows: ICANN conducted its 26th AGM in Istanbul from 9th September 2024 to 14th September 2024. 1. I, along with Nitin Walia (Vice Chair, UASG), Nabil Benamar (Vice Chair, UASG), Satish Babu (Chair, Tech WG), Raymond (Vice Chair, Comm WG), Sandra (Vice Chair, Comm WG), Abdalmonem (Chair, ccNSO UAC), and Maria (Chair, CIS/EE LI), attended various sessions on Universal Acceptance (UA). 2. The UASG activities began on 30th October 2024 with a Community Update during Pre-ICANN week. During ICANN, we had a joint session with ccNSO UAC, where we discussed cooperation between UASG and ccNSO in promoting UA. 3. A 75-minute panel discussion on UA Strategy was the highlight of ICANN81. There were two panels, namely on UA Day and UA Academic Curricula. The session started with a brief introduction by Sarmad Hussain. One panel on UA Day was coordinated by Seda, whereas the other panel on UA Academic Curricula was coordinated by Gerald Ferreira from ICANN Org. • UA Day panel presenters were Anil Kumar Jain (myself), Satish Babu, and Abdalmonem. • Presenters for the UA Curricula panel were Dr. Nabil, Dr. Eunice Alejandra from Maxico and Sami Mohamed Ali from Bahrain. BIUAWG ( Board IDN/UA Working group) was kind enough to give UASG a 60-minute slot, which was attended by myself, Nitin, Nabil, Satish Babu, Qing chai, Maria, Raymond, Sarika and Sandra. I began the discussion by briefing the BIUAWG on the general holistic efforts and achievements of UASG. Nabil (Measurement), Nitin (EAI), and Satish (Tech) briefed the Board about technical achievements and ongoing work. The discussions were very positive. The following issues were given focus during the discussions: a) The five-year strategic plans of UA for BIUAWG.Hence, UASG’s five-year plans are required to align accordingly. b) The appointment of special full-time officers by ICANN Org to execute outreach to Big Tech, open source orgs and academia. c) SOI implementations, ICANN-accepted standard behaviors, and the decision-making process of the Coordination WG within UASG. The BIUAWG appreciated UASG’s efforts on these fronts. d) Possible plans to celebrate 10 years of UASG, including the possible update of the UASG Charter. e) Achievements of UA Day 2024 and preparations of UA Day 2025. In addition to ICANN Board directors who attended this meeting, namely Edmond Chung, Maarten Botterman, Alan Barrett, Herald Alvestrand,Jim Calvin,Patricio Poblete , Ms. Theresa, Sarmad, ,Seda and other ICANN staff joined the call in person from ICANN Org. Special mention of achievements by the UA Day program was made by both the Chair of the ICANN Board, Tripti Sinha, and Interim President and CEO of ICANN, Ms. Sally Costerton, in their welcome address to the entire ICANN community. It is worth noting that “Promotion of IDA and UA” is given a special place in ICANN’s five-year strategic plans starting from 2026. Sarmad Hussain conducted a session on IDN policy readiness for the upcoming gTLD round, giving details of efforts by gTLD and ccNSO teams in this direction. The ccNSO, GAC, and ALAC have started special groups to work on Universal Acceptance. The Board’s IDN/UA WG provides oversight and directions for uptake of UA.ICANN Org is reaching out to Big techs & academia and Open source community. The Government engagement is thru the Government Engagement and the Global Stackholder Engagement teams of ICANN Org. I can confidently vouch that today the entire ICANN community is committed to the development of Universal Acceptance and is working sincerely toward that goal. In summery, a special focus was given to UA related discussions, information sharing and consensus building. Five year strategic plans of ICANN & BIUAWG are very promising and futuristic for UA related development and implementation. ICANN board members and staff appreciated efforts of UASG for last one year and promised to extend all help in future. UASG programmes like Self EAI testing tools, UA academic curriculum and UA Day were widely appreciated by community at large. This testufy efforts by all of us in UASG comminty. ICANN 81 gave encouragement to UASG volunteers and community to continue efforts of UASG which are in right direction. Thanks, Anil Kumar Jain Sent from my iPad

1 1

UA testing on Ecommerce Platforms and Email Deliverability study
by Seda Akbulut 10 Dec '24

10 Dec '24

Dear all, Thanks to RADIX and UASG Ambassador, Aman Masjide, there are now two studies to test email deliverability and e-commerce tools using email IDs on new long, new short and IDN email addresses. Both these studies are attached for reference and are available for your review. Today, Aman will present this work at the Measurement WG meeting at 14:00 UTC. Please join us from the following link: Topic: UA Measurement WG 10 December Tuesday at 14:00 UTC Join Zoom Meeting https://icann.zoom.us/j/93206510166?pwd=YXhYQ2ZnNSt0alkxMXFHZlZLWDk1UT09 Meeting ID: 932 0651 0166 Passcode: E@+MN0Np&s Best regards, Seda

1 0

A chance to improve UA - Call for review of Unicode Linkification draft UTS #58
by Jim DeLaHunt 07 Dec '24

07 Dec '24

Universal Acceptance colleagues: We have an opportunity to review a potentially very influential tool for promoting UA. The Unicode Consortium is drafting a proposed Unicode Technical Standard, #58, "Unicode Linkification". As you know, linkification is the process of recognising URLs in plain text, and turning those URLs into active hyperlinks. A big UA problem is that many pieces of software do not linkify Internationalised Domain Names, or globally inclusive email addresses. This is based in part on a limited conception that only latin script letters can appear in domain names or email addresses, and that only a few top level domains are valid. I believe that Unicode Technical Standards are very authoritative in the parts of the software world which we seek to influence. If this UTS gets linkification right, it will be a tool we can use to persuade apps which fall short to do better. If the UTS gets linkification wrong, it will be difficult for us to persuade apps to ignore the UTS and instead do what we say is right. The Unicode Consortium has published a draft of UTS #58, "Unicode Linkification", at <https://www.unicode.org/reports/tr58/>. It is a detailed technical document, including algorithms for detecting the beginning and end of links, and escaping, and data on characters properties. They welcome feedback via a form they link to in the draft. I encourage all UASG participants, with ideas on how linkification should work in order to promote Universal Acceptance, to review the draft and to submit comments. I do not see a specific deadline, but we should not delay. Best regards, —Jim DeLaHunt, Vancouver, Canada -- --Jim DeLaHunt,jdlh(a)jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant, Vancouver, Canada

2 1

Request for feedback: UASG's FY25 Action Plan
by Seda Akbulut 06 Dec '24

06 Dec '24

Dear UASG members, UASG working groups have developed a work plan for the next year. Input from each working group was collated and reviewed by the UASG Coordination team to develop a Draft FY25 Action Plan, which incrementally builds on FY24 Action Plan. The Draft FY25 Action Plan is now published at uasg.tech home page. You may access the report directly from here: https://uasg.tech/wp-content/uploads/2024/12/UASG-FY25-Action-Plan.pdf Kindly review the action plan and provide your feedback through the webform by 16 December 2024. The webform is placed on the first page of the report. For your convenience, I have added the link here: https://docs.google.com/forms/d/e/1FAIpQLScVzOl3IgebBr-xv2NObaXTfNkTXcw0N-8… UASG Coordination team review your input and finalize the FY25 Action Plan. The final action plan will then be published at uasg.tech. Your feedback is very important to us. We look forward to receiving from you. Regards, Seda Akbulut (on behalf of UASG Coordination team)

1 0

Fw : Join Open Forum Event #36 : Challenges & Opportunities for a Multilingual Internet, at IGF2024.
by Nitin Walia 04 Dec '24

04 Dec '24

Dear UASG Community Members, I hope this message finds you well. I am forwarding an invitation from Mr. T. Santhosh of the Government of India, for an important Open Forum session at IGF 2024 titled "Challenges &amp Opportunities for a Multilingual Internet." This session is scheduled for Tuesday, December 17, 2024, from 10:30 to 12:00 UTC (13:30 to 15:00 local Riyadh time) in a hybrid format . The session will feature case studies and insights from governments of India, Egypt, the U.K., and the U.S. on promoting multilingualism online, Universal Acceptance, local content development, and Internationalized Domain Names (IDNs). It is an excellent opportunity to engage in discussions that align with our shared mission of fostering a multilingual and inclusive Internet . Further details, including the session agenda and registration link, can be found below. Warm Regards Nitin Walia | LinkedIn TwitterVC: https://bridge01.videomeet.in - room: nitin pwd: 10000भाषाकीआजादी - Bridging the Digital Divide, Getting Next billion online From: T Santhosh MailId : [145295004]To: Subject: Join Open Forum Event #36 : Challenges &amp Opportunities for a Multilingual Internet, at IGF2024.Date: 04 Dec 2024 06:30:33 PM Dear Mr. Nitin Kind request to share this email with UASG community . Warm RegardsT. Santhosh ( He/ Him)Scientist FMinistry of Electronics &ampITGovernment of IndiaNew Delhiphone : +91-11-24364741+91-11-24301375 ============ Forwarded Message ============From : t.santhosh(a)gov.inTo : ua-discuss(a)icann.orgCc : manal@tra.gov.eg,nigel.hickson@dsit.gov.uk,prisberg@ntia.gov,ofletcher@ntia.gov,aflavin@ntia.gov,jwray@ntia.gov,SChalmers@ntia.gov,pradeep.verma@meity.gov.in,igsim.ta1@cdac.inDate : Tue, 03 Dec 2024 23:20:32 +0530Subject : Join Open Forum Event #36 : Challenges &amp Opportunities for a Multilingual Internet, at IGF2024 . Dear UASG Members This mail is to kindly invite you to an upcoming event ofOpen Forum Session 36 during the 19th Internet Governance Forum(IGF) on "Building our Multistakeholder Digital Future" to be held at the King Abdulaziz International Conference Center (KAICC) in Riyadh, Kingdom of Saudi Arabia, from 15 to 19 December 2024. on&ldquo Challenges&amp Opportunities for a Multilingual Internet&rdquo, This is an Open Forum Sessionwhich has been scheduled onTuesday, December 17, 2024 at Workshop Room Number 10, from 10:30 to 12:00 UTC (13.30 to 15:00Local Riyadh Time) in hybrid format . Theaforementioned session on Multilingual Internet focusing upon the Challenges and Opportunities for Multilingual Internet along with various case studies. This will be followed by a Q &amp A Session and a subsequent Open floor for discussions involving the online participants. The agenda of the open forum session 36 is attached for kind reference . One of the main themes of IGF 2024 viz. Advancing Human Right and Inclusion in the digital age entails the aspect of Multilingual Internet.During this Open Forum, Government representatives from Egypt, India, the U.K., and the U.S. will present on their projects to promote the multilingual Internet, including on efforts to promote local content development, universal acceptance, and the uptake of Internationalized Domain Names. Insights will be shared by presenting Governments informing upon the primary challenges faced in the achievement of a multilingual Internet and will highlight the lessons learned so far . It will also encompass the discussions on the distinct role of the Governments in advancing multilingualism and empowering the communities across the globe, the steps taken by them and the successful projects as the case studies for the world to look upon. While discussing the challenges faced by multi-stakeholders, the actionable way forwards tobuild momentum and raise awareness of this critical issue will be the focus . It is a delightful opportunity and an honour to host you seeking your valuable views/inputs on this. Hope this event proves to be an engaging and informative one for you . Details of the session focusing upon the Challenges and Opportunities for Multilingual Internet can be accessed using the following link: https://igf2024.sched.com/event/1sYc1/open-forum-36-challenges-opportunitie… Kindly grace the event by your invaluable presence.For any further query or information, please do contact the Mr. Pradeep Kumar Verma, email id: pradeep.verma(a)meity.gov.inor PearlRisberg, email id: prisberg(a)ntia.gov Preliminary Agenda: Open Forum Session which has been scheduled on Tuesday, December 17, 2024 at Workshop Room Number 10, from 10:30 to 12:00 UTC (13.30 to 15:00 Local Riyadh Time) in hybrid format . Local Riyadh Time-13.30 to 15:00 UTC- 10:30 to 12:00 Session Flow 13:30-13:33 10:30-10:33 Owen Fletcher (US Gov) starts the session and introduces Jaisha Wray 13:33-13:40 10:33-10:40 Opening Remarks &ndash Jaisha Wray (US Gov) 13:40-13:45 10:40-10:45 Session overview and introduction of speakers &ndash Owen Fletcher (US Gov) 13:45-14:00 10:45-11:00 India case study &ndash T.Santhosh (Gov of India) 14:00-14:10 11:00-11:10 Egypt case study &ndash Manal Ismail (Gov of Egypt) 14:10-14:20 11:10-11:20 UK case study &ndash Nigel Hickson (UK Gov 14:20-14:50 11:20-11:50 Q&ampA &ndash moderated by Owen Fle tcher (US Gov) 14:50-14:57 11:50-11:57 Final remarks from all speakers 14:57-15:00 11:57-12:00 Closing &ndash Owen Fletcher (US Gov) Warm Regards T.Santhosh (He/Him) Scientist F Ministry of Electronics and Information Technology Government of India Electronics Niketan 6 CGO Complex New Delhi - 110003 (India) Tel: +91-11-24364741 24301375 Do not Remove:[HID]20241204183033629[-HID]

2 1

Fwd: [wsis20] GP Digital insights into WSIS+20
by anil Jain 21 Nov '24

21 Nov '24

Dear all, Following information on GDC and WSIS+20 may be useful to you. Thanks, Anil Kumar Jain Sent from my iPad Begin forwarded message: > From: Jordan Carter via wsis20 <wsis20(a)icann.org> > Date: 21 November 2024 at 4:45:32 AM IST > To: ICANN wsis20 <wsis20(a)icann.org> > Subject: [wsis20] GP Digital insights into WSIS+20 > Reply-To: Jordan Carter <jordan.carter(a)auda.org.au> > > > Hi all, hope those of you travelling back from ICANN had a good trip. > > An excellent analysis from GP Digital about the WSIS+20 substance and process came into my inbox and it’s worth a read: > > https://www.gp-digital.org/everything-you-need-to-know-about-the-wsis20-rev… > > They have also published a nice calendar of what is happening when: > > https://www.gp-digital.org/digital-technology-governance-calendar/ > > cheers > Jordan > > _______________________________________________ > > > Learn more about the WSIS+20 Outreach Network and review relevant resources: https://go.icann.org/wsis20 > > Read the public archives for this mailing list: https://mm.icann.org/pipermail/wsis20/ > > _______________________________________________ > 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.

1 0

Re: [UA-EAI] Re: [EXTERNAL] RE: Fwd: [EAI] [Errata Verified] RFC6531 (7580)
by Arnt Gulbrandsen 19 Nov '24

19 Nov '24

Hi, There are a few IETF documents moving, actually. More activity than five years ago. One document enables use of Unicode addresses in domain contact addresses. Scott is the hero who may finally be able to push that over the finishing line, which would require reviewing some older documents. Arnt From: "Mark Svancarek (CELA) via UA-EAI" <ua-eai(a)icann.org> Reply-To: "Mark Svancarek (CELA)" <marksv(a)microsoft.com> Date: Tuesday, 19 November 2024 at 00:49 To: "Hollenbeck, Scott" <shollenbeck(a)verisign.com>, "dusan(a)dukes.in.rs" <dusan(a)dukes.in.rs>, "ua-eai(a)icann.org" <ua-eai(a)icann.org>, "ua-discuss(a)icann.org" <ua-discuss(a)icann.org> Subject: [UA-EAI] Re: [EXTERNAL] RE: [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) That’s what I thought. I’m curious, what inspired you to review this in the year 2024? From: Hollenbeck, Scott <shollenbeck(a)verisign.com> Sent: Monday, November 18, 2024 5:41 AM To: Mark Svancarek (CELA) <marksv(a)microsoft.com>; dusan(a)dukes.in.rs; ua-eai(a)icann.org; ua-discuss(a)icann.org Subject: [EXTERNAL] RE: [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) An RFC that updates another one makes a “must incorporate” change to the original specification. RFC 6531 does not update RFC 5321, it describes a new, optional capability that’s described as an extension in the very title of the RFC. That’s why I believe that the original text in 6531 is misleading and why I submitted the report. The correction should help make it clear that the extension does not formally update RFC 5321. Scott From: Mark Svancarek (CELA) <marksv(a)microsoft.com<mailto:marksv@microsoft.com>> Sent: Friday, November 15, 2024 6:14 PM To: Душан Стојичевић <dusan(a)dukes.in.rs<mailto:dusan@dukes.in.rs>>; ua-eai(a)icann.org<mailto:ua-eai@icann.org>; ua-discuss(a)icann.org<mailto:ua-discuss@icann.org>; Hollenbeck, Scott <shollenbeck(a)verisign.com<mailto:shollenbeck@verisign.com>> Subject: [EXTERNAL] RE: [EXTERNAL] [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hmm, I am not so sure. Scott, could you clarify the potential impact of this errata report? /marksv From: Душан Стојичевић via UA-discuss <ua-discuss(a)icann.org<mailto:ua-discuss@icann.org>> Sent: Friday, November 15, 2024 14:21 To: ua-eai(a)icann.org<mailto:ua-eai@icann.org>; ua-discuss(a)icann.org<mailto:ua-discuss@icann.org> Subject: [EXTERNAL] [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) If I am reading this correctly, we will get huge change in EAI. My two cents, Dusan ---------- Прослеђена порука ---------- Од: RFC Errata System <rfc-editor(a)rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> Датум: 15. 11. 2024. 22:52 Наслов: [EAI] [Errata Verified] RFC6531 (7580) Коме: shollenbeck@verisign.com,yaojk@cnnic.cn,maowei_ietf@cnnic.cn<mailto:shollenbeck@verisign.com,yaojk@cnnic.cn,maowei_ietf@cnnic.cn> Копија: orie@transmute.industries,iesg@ietf.org,ima@ietf.org,iana@iana.org,rfc-editor@rfc-editor.org<mailto:orie@transmute.industries,iesg@ietf.org,ima@ietf.org,iana@iana.org,rfc-editor@rfc-editor.org> The following errata report has been verified for RFC6531, "SMTP Extension for Internationalized Email". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7580 [secure-web.cisco.com]<https://urldefense.com/v3/__https:/secure-web.cisco.com/1c36W4TyCnZMPETfveB…> -------------------------------------- Status: Verified Type: Technical Reported by: Scott Hollenbeck <shollenbeck(a)verisign.com<mailto:shollenbeck@verisign.com>> Date Reported: 2023-07-31 Verified by: Orie Steele (IESG) Sections 3.3 and 3.7.3 say: Original Text ------------- The <Mailbox> ABNF rule is imported from RFC 5321 and updated in order to support the internationalized email address. The following ABNF rules imported from RFC 5321, Section 4.1.2, are updated directly or indirectly by this document: This document updates <Mailbox> and <Domain> to support non-ASCII characters. Corrected Text -------------- The <Mailbox> ABNF rule is imported from RFC 5321 and extended in order to support the internationalized email address. The following ABNF rules imported from RFC 5321, Section 4.1.2, are extended directly or indirectly by this document: This document extends <Mailbox> and <Domain> to support non-ASCII characters. Notes ----- The original text can be incorrectly interpreted to suggest that the definitions found in RFC 6531 formally update the definitions found in RFC 5321. RFC 6531 does not formally update RFC 5321. As such, a word like "extends" may be less prone to misinterpretation than "updates". -------------------------------------- RFC6531 (draft-ietf-eai-rfc5336bis-16) -------------------------------------- Title : SMTP Extension for Internationalized Email Publication Date : February 2012 Author(s) : J. Yao, W. Mao Category : PROPOSED STANDARD Source : Email Address Internationalization Stream : IETF Verifying Party : IESG _______________________________________________ IMA mailing list -- ima(a)ietf.org<mailto:ima@ietf.org> To unsubscribe send an email to ima-leave(a)ietf.org<mailto:ima-leave@ietf.org>

2 2

Re: [EXTERNAL] RE: Fwd: [EAI] [Errata Verified] RFC6531 (7580)
by Mark Svancarek (CELA) 18 Nov '24

18 Nov '24

That’s what I thought. I’m curious, what inspired you to review this in the year 2024? From: Hollenbeck, Scott <shollenbeck(a)verisign.com> Sent: Monday, November 18, 2024 5:41 AM To: Mark Svancarek (CELA) <marksv(a)microsoft.com>; dusan(a)dukes.in.rs; ua-eai(a)icann.org; ua-discuss(a)icann.org Subject: [EXTERNAL] RE: [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) An RFC that updates another one makes a “must incorporate” change to the original specification. RFC 6531 does not update RFC 5321, it describes a new, optional capability that’s described as an extension in the very title of the RFC. That’s why I believe that the original text in 6531 is misleading and why I submitted the report. The correction should help make it clear that the extension does not formally update RFC 5321. Scott From: Mark Svancarek (CELA) <marksv(a)microsoft.com<mailto:marksv@microsoft.com>> Sent: Friday, November 15, 2024 6:14 PM To: Душан Стојичевић <dusan(a)dukes.in.rs<mailto:dusan@dukes.in.rs>>; ua-eai(a)icann.org<mailto:ua-eai@icann.org>; ua-discuss(a)icann.org<mailto:ua-discuss@icann.org>; Hollenbeck, Scott <shollenbeck(a)verisign.com<mailto:shollenbeck@verisign.com>> Subject: [EXTERNAL] RE: [EXTERNAL] [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hmm, I am not so sure. Scott, could you clarify the potential impact of this errata report? /marksv From: Душан Стојичевић via UA-discuss <ua-discuss(a)icann.org<mailto:ua-discuss@icann.org>> Sent: Friday, November 15, 2024 14:21 To: ua-eai(a)icann.org<mailto:ua-eai@icann.org>; ua-discuss(a)icann.org<mailto:ua-discuss@icann.org> Subject: [EXTERNAL] [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) If I am reading this correctly, we will get huge change in EAI. My two cents, Dusan ---------- Прослеђена порука ---------- Од: RFC Errata System <rfc-editor(a)rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> Датум: 15. 11. 2024. 22:52 Наслов: [EAI] [Errata Verified] RFC6531 (7580) Коме: shollenbeck@verisign.com,yaojk@cnnic.cn,maowei_ietf@cnnic.cn<mailto:shollenbeck@verisign.com,yaojk@cnnic.cn,maowei_ietf@cnnic.cn> Копија: orie@transmute.industries,iesg@ietf.org,ima@ietf.org,iana@iana.org,rfc-editor@rfc-editor.org<mailto:orie@transmute.industries,iesg@ietf.org,ima@ietf.org,iana@iana.org,rfc-editor@rfc-editor.org> The following errata report has been verified for RFC6531, "SMTP Extension for Internationalized Email". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7580<https://secure-web.cisco.com/1c36W4TyCnZMPETfveBdGnpSZI3eQnmHuvcuQ2X6ma4qHD…> -------------------------------------- Status: Verified Type: Technical Reported by: Scott Hollenbeck <shollenbeck(a)verisign.com<mailto:shollenbeck@verisign.com>> Date Reported: 2023-07-31 Verified by: Orie Steele (IESG) Sections 3.3 and 3.7.3 say: Original Text ------------- The <Mailbox> ABNF rule is imported from RFC 5321 and updated in order to support the internationalized email address. The following ABNF rules imported from RFC 5321, Section 4.1.2, are updated directly or indirectly by this document: This document updates <Mailbox> and <Domain> to support non-ASCII characters. Corrected Text -------------- The <Mailbox> ABNF rule is imported from RFC 5321 and extended in order to support the internationalized email address. The following ABNF rules imported from RFC 5321, Section 4.1.2, are extended directly or indirectly by this document: This document extends <Mailbox> and <Domain> to support non-ASCII characters. Notes ----- The original text can be incorrectly interpreted to suggest that the definitions found in RFC 6531 formally update the definitions found in RFC 5321. RFC 6531 does not formally update RFC 5321. As such, a word like "extends" may be less prone to misinterpretation than "updates". -------------------------------------- RFC6531 (draft-ietf-eai-rfc5336bis-16) -------------------------------------- Title : SMTP Extension for Internationalized Email Publication Date : February 2012 Author(s) : J. Yao, W. Mao Category : PROPOSED STANDARD Source : Email Address Internationalization Stream : IETF Verifying Party : IESG _______________________________________________ IMA mailing list -- ima(a)ietf.org<mailto:ima@ietf.org> To unsubscribe send an email to ima-leave(a)ietf.org<mailto:ima-leave@ietf.org>

1 0

Fwd: [EAI] [Errata Verified] RFC6531 (7580)
by Душан Стојичевић 15 Nov '24

15 Nov '24

2 1

FW: ICANN81: UA Strategy Capacity Building Initiatives
by Seda Akbulut 10 Nov '24

10 Nov '24

Dear all, You are cordially invited to join the “ICANN81: UA Strategy Capacity Building Initiatives” session on Monday 11 November at 10:45 am local time (or 7:45 am UTC). Session link: https://icann81.sched.com/event/1p2Cn/ua-strategy-capacity-building-initiat… Location: B2 Floor Beylerbeyi (Secondary Ballroom) Slide deck: https://static.sched.com/hosted_files/icann81/05/UA%20Strategy_Capacity%20B… Best regards Seda

1 0