Fwd: [EAI] [Errata Verified] RFC6531 (7580)
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> Sent: Friday, November 15, 2024 14:21 To: ua-eai@icann.org; 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 -------------------------------------- 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>
It appears that Mark Svancarek (CELA) via UA-EAI <marksv@microsoft.com> said:
-=-=-=-=-=- -=-=-=-=-=- Hmm, I am not so sure.
Scott, could you clarify the potential impact of this errata report?
I'm not Scott but it's just fixing a minor wording error. The old wording could have been misinterpreted to say that it made EAI mandatory for every mail system. The new wording expresses the reality that EAI is an extension that some mail systems support and some do not. To point out the obvious, the IETF is not the Network Police, and even if they had wanted to say that EAI was mandatory for every mail system, people would just have ignored it. R's, John
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>
-=-=-=-=-=- [Alternative: text/html] -=-=-=-=-=- -=-=-=-=-=-
_______________________________________________ UA-EAI mailing list -- ua-eai@icann.org To unsubscribe send an email to ua-eai-leave@icann.org _______________________________________________ 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. -=-=-=-=-=-
Thanks, that was my impression as well - just fixing ambiguous text -----Original Message----- From: John Levine <john.levine@standcore.com> Sent: Saturday, November 16, 2024 13:34 To: ua-eai@icann.org Cc: Mark Svancarek (CELA) <marksv@microsoft.com> Subject: Re: [UA-EAI] Re: [EXTERNAL] [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580) It appears that Mark Svancarek (CELA) via UA-EAI <marksv@microsoft.com> said:
-=-=-=-=-=- -=-=-=-=-=- Hmm, I am not so sure.
Scott, could you clarify the potential impact of this errata report?
I'm not Scott but it's just fixing a minor wording error. The old wording could have been misinterpreted to say that it made EAI mandatory for every mail system. The new wording expresses the reality that EAI is an extension that some mail systems support and some do not. To point out the obvious, the IETF is not the Network Police, and even if they had wanted to say that EAI was mandatory for every mail system, people would just have ignored it. R's, John
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>
-=-=-=-=-=- [Alternative: text/html] -=-=-=-=-=- -=-=-=-=-=-
_______________________________________________ UA-EAI mailing list -- ua-eai@icann.org To unsubscribe send an email to ua-eai-leave@icann.org _______________________________________________ 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. -=-=-=-=-=-
Dear Mark, Your response to problem was awesome. Thanks, Anil Sent from my iPad
On 18-Nov-2024, at 8:49 AM, Mark Svancarek (CELA) via UA-EAI <ua-eai@icann.org> wrote:
Thanks, that was my impression as well - just fixing ambiguous text
-----Original Message----- From: John Levine <john.levine@standcore.com> Sent: Saturday, November 16, 2024 13:34 To: ua-eai@icann.org Cc: Mark Svancarek (CELA) <marksv@microsoft.com> Subject: Re: [UA-EAI] Re: [EXTERNAL] [UA-discuss] Fwd: [EAI] [Errata Verified] RFC6531 (7580)
It appears that Mark Svancarek (CELA) via UA-EAI <marksv@microsoft.com> said:
-=-=-=-=-=- -=-=-=-=-=- Hmm, I am not so sure.
Scott, could you clarify the potential impact of this errata report?
I'm not Scott but it's just fixing a minor wording error. The old wording could have been misinterpreted to say that it made EAI mandatory for every mail system. The new wording expresses the reality that EAI is an extension that some mail systems support and some do not.
To point out the obvious, the IETF is not the Network Police, and even if they had wanted to say that EAI was mandatory for every mail system, people would just have ignored it.
R's, John
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>
-=-=-=-=-=- [Alternative: text/html] -=-=-=-=-=- -=-=-=-=-=-
_______________________________________________ UA-EAI mailing list -- ua-eai@icann.org To unsubscribe send an email to ua-eai-leave@icann.org _______________________________________________ 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 To unsubscribe send an email to ua-eai-leave@icann.org _______________________________________________ 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.
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> Sent: Friday, November 15, 2024 6:14 PM To: Душан Стојичевић <dusan@dukes.in.rs>; ua-eai@icann.org; ua-discuss@icann.org; Hollenbeck, Scott <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<https://secure-web.cisco.com/1c36W4TyCnZMPETfveBdGnpSZI3eQnmHuvcuQ2X6ma4qHDyROWHO2aaJ0fDyFDgWnm3hJY8ageDE_XIa-Nn_DfnuqQVre7ts7bTwd1ln23m7PZjykFwZ8wpAeGvnLTDpvzSD4Hh9rCRJPRX4mx6v4gdMz0gQPD-nadAM413gQxTrtv_RssANRAkfR4AOj_TwpguJSbMvuB03BH3mtoAK6zbCnRO9C270dGZ2wNbt11oBmKV3JJq5KHd9zFkAiz_CBIPBMR342NX8A4m3mM8MUGh_Z7k7RfUi5c7bxgiknaXb505_T2dAWmP5ibjJrQqYN/https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid7580> -------------------------------------- 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>
That’s what I thought. I’m curious, what inspired you to review this in the year 2024? From: Hollenbeck, Scott <shollenbeck@verisign.com> Sent: Monday, November 18, 2024 5:41 AM To: Mark Svancarek (CELA) <marksv@microsoft.com>; dusan@dukes.in.rs; ua-eai@icann.org; 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<https://secure-web.cisco.com/1c36W4TyCnZMPETfveBdGnpSZI3eQnmHuvcuQ2X6ma4qHDyROWHO2aaJ0fDyFDgWnm3hJY8ageDE_XIa-Nn_DfnuqQVre7ts7bTwd1ln23m7PZjykFwZ8wpAeGvnLTDpvzSD4Hh9rCRJPRX4mx6v4gdMz0gQPD-nadAM413gQxTrtv_RssANRAkfR4AOj_TwpguJSbMvuB03BH3mtoAK6zbCnRO9C270dGZ2wNbt11oBmKV3JJq5KHd9zFkAiz_CBIPBMR342NX8A4m3mM8MUGh_Z7k7RfUi5c7bxgiknaXb505_T2dAWmP5ibjJrQqYN/https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid7580> -------------------------------------- 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>
participants (5)
-
anil Jain -
Hollenbeck, Scott -
John Levine -
Mark Svancarek (CELA) -
Душан Стојичевић