Goodday! Just checking if we are meeting today ? Shalom Adv Ntsaluba [e-mail-sig-photo] [cid:image002.gif@01DB3A97.C879F4B0] [cid:image003.png@01DB3A97.C879F4B0] Advocate Nandipha Ntsaluba BSc;BEd,PGDEd(UNITRA);MEd (UOVS),PBL,MBL, LLB(UNISA),PLT,PMT, Public Notary Certificate LLM (IPlaw & Cyberlaw)(UP) LLM(Extractive Industries Law in Africa) UP SANDF Senior Leadership Course( Defence College) Civil-Military Relations Certificate(Ottawa,Canada) Lecturer College of Law Department of Mercantile Law Intellectual Property, Cyberlaw and Corporate Law Muckleneuk Campus E-mail:entsaln@unisa.ac.za OCIRD: https://orcid.org/0000-0001-8085-146X From: Arnt Gulbrandsen via UA-EAI <ua-eai@icann.org> Sent: Tuesday, November 19, 2024 10:34 AM To: Mark Svancarek (CELA) <marksv@microsoft.com>; Hollenbeck, Scott <shollenbeck@verisign.com>; dusan@dukes.in.rs; ua-eai@icann.org; ua-discuss@icann.org Subject: [UA-EAI] Re: [EXTERNAL] RE: [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) 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@icann.org<mailto:ua-eai@icann.org>> Reply-To: "Mark Svancarek (CELA)" <marksv@microsoft.com<mailto:marksv@microsoft.com>> Date: Tuesday, 19 November 2024 at 00:49 To: "Hollenbeck, Scott" <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>>, "dusan@dukes.in.rs<mailto:dusan@dukes.in.rs>" <dusan@dukes.in.rs<mailto:dusan@dukes.in.rs>>, "ua-eai@icann.org<mailto:ua-eai@icann.org>" <ua-eai@icann.org<mailto:ua-eai@icann.org>>, "ua-discuss@icann.org<mailto:ua-discuss@icann.org>" <ua-discuss@icann.org<mailto:ua-discuss@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@verisign.com<mailto:shollenbeck@verisign.com>> Sent: Monday, November 18, 2024 5:41 AM To: Mark Svancarek (CELA) <marksv@microsoft.com<mailto:marksv@microsoft.com>>; dusan@dukes.in.rs<mailto:dusan@dukes.in.rs>; ua-eai@icann.org<mailto:ua-eai@icann.org>; ua-discuss@icann.org<mailto:ua-discuss@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@microsoft.com<mailto:marksv@microsoft.com>> Sent: Friday, November 15, 2024 6:14 PM To: Душан Стојичевић <dusan@dukes.in.rs<mailto:dusan@dukes.in.rs>>; ua-eai@icann.org<mailto:ua-eai@icann.org>; ua-discuss@icann.org<mailto:ua-discuss@icann.org>; Hollenbeck, Scott <shollenbeck@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@icann.org<mailto:ua-discuss@icann.org>> Sent: Friday, November 15, 2024 14:21 To: ua-eai@icann.org<mailto:ua-eai@icann.org>; ua-discuss@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@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://protect.checkpoint.com/v2/r02/___https://urldefense.com/v3/__https:/...> -------------------------------------- Status: Verified Type: Technical Reported by: Scott Hollenbeck <shollenbeck@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@ietf.org<mailto:ima@ietf.org> To unsubscribe send an email to ima-leave@ietf.org<mailto:ima-leave@ietf.org> The authenticity, confidentiality, and integrity of this UNISA email are preserved by these terms. https://www.unisa.ac.za/disclaimer
