Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI
This is what I have now: Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. See https://tools.ietf.org/html/rfc3492 From: Mark Svancarek <marksv@microsoft.com> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn>, Don Hollander <don.hollander@icann.org>, "ua-eai@icann.org" <ua-eai@icann.org> Cc: "ua-coordination@icann.org" <ua-coordination@icann.org> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation. From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org>; ua-eai@icann.org Cc: ua-coordination@icann.org Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Hello, The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment. xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--". ======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form." "An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org]) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org]), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org]] and hence a maximum of 59 ASCII characters in length. " Jiankang Yao From: Don Hollander Date: 2017-01-22 17:33 To: ua-eai@icann.org CC: Tan Tanaka, Dennis; Mark Svancarek via UA-Coordination; Dr. AJAY D A T A; Stuart Stuple Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI. This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis. These enhancements were mostly focused on the Email Service Provider. I have revised the source document which is attached. And for reference, I’m also including the formatted earlier draft. Could I please get any final comments by the end of this week (25th)? Thanks. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander
What is meant by “bi-directional” in this context? I think you mean “can handle bi-directional domain names”. ASCII characters are inherently Left-to-right and hence never bidirectional. From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Monday, January 23, 2017 11:28 AM To: Mark Svancarek <marksv@microsoft.com>; HEALTH Yao <yaojk@cnnic.cn>; ua-eai@icann.org Cc: ua-coordination@icann.org Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI This is what I have now: Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. See https://tools.ietf.org/html/rfc3492<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc3492&data=02%7C01%7Cstuartst%40exchange.microsoft.com%7C36a667bd28d74362262008d443c5ebde%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636207964727009377&sdata=WjtnPYPKNEpGDJS%2ByeUCwtiIcZrPN0A9Kfi65FJG%2FLs%3D&reserved=0> From: Mark Svancarek <marksv@microsoft.com<mailto:marksv@microsoft.com>> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>>, Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>, "ua-eai@icann.org<mailto:ua-eai@icann.org>" <ua-eai@icann.org<mailto:ua-eai@icann.org>> Cc: "ua-coordination@icann.org<mailto:ua-coordination@icann.org>" <ua-coordination@icann.org<mailto:ua-coordination@icann.org>> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation. From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org<mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Hello, The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment. xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--". ======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form." "An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>] and hence a maximum of 59 ASCII characters in length. " ________________________________ Jiankang Yao From: Don Hollander<mailto:don.hollander@icann.org> Date: 2017-01-22 17:33 To: ua-eai@icann.org<mailto:ua-eai@icann.org> CC: Tan Tanaka, Dennis<mailto:dtantanaka@verisign.com>; Mark Svancarek via UA-Coordination<mailto:ua-coordination@icann.org>; Dr. AJAY D A T A<mailto:ajay@data.in>; Stuart Stuple<mailto:stuartst@exchange.microsoft.com> Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI. This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis. These enhancements were mostly focused on the Email Service Provider. I have revised the source document which is attached. And for reference, I’m also including the formatted earlier draft. Could I please get any final comments by the end of this week (25th)? Thanks. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander
OK, I guess not good enough ☺ Let’s say “reversible” rather than “bidirectional”? From: Stuart Stuple Sent: Monday, January 23, 2017 12:56 PM To: Don Hollander <don.hollander@icann.org>; Mark Svancarek <marksv@microsoft.com>; HEALTH Yao <yaojk@cnnic.cn>; ua-eai@icann.org Cc: ua-coordination@icann.org Subject: RE: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI What is meant by “bi-directional” in this context? I think you mean “can handle bi-directional domain names”. ASCII characters are inherently Left-to-right and hence never bidirectional. From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Monday, January 23, 2017 11:28 AM To: Mark Svancarek <marksv@microsoft.com<mailto:marksv@microsoft.com>>; HEALTH Yao <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org<mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI This is what I have now: Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. See https://tools.ietf.org/html/rfc3492<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc3492&data=02%7C01%7Cstuartst%40exchange.microsoft.com%7C36a667bd28d74362262008d443c5ebde%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636207964727009377&sdata=WjtnPYPKNEpGDJS%2ByeUCwtiIcZrPN0A9Kfi65FJG%2FLs%3D&reserved=0> From: Mark Svancarek <marksv@microsoft.com<mailto:marksv@microsoft.com>> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>>, Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>, "ua-eai@icann.org<mailto:ua-eai@icann.org>" <ua-eai@icann.org<mailto:ua-eai@icann.org>> Cc: "ua-coordination@icann.org<mailto:ua-coordination@icann.org>" <ua-coordination@icann.org<mailto:ua-coordination@icann.org>> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation. From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org<mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Hello, The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment. xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--". ======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form." "An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>] and hence a maximum of 59 ASCII characters in length. " ________________________________ Jiankang Yao From: Don Hollander<mailto:don.hollander@icann.org> Date: 2017-01-22 17:33 To: ua-eai@icann.org<mailto:ua-eai@icann.org> CC: Tan Tanaka, Dennis<mailto:dtantanaka@verisign.com>; Mark Svancarek via UA-Coordination<mailto:ua-coordination@icann.org>; Dr. AJAY D A T A<mailto:ajay@data.in>; Stuart Stuple<mailto:stuartst@exchange.microsoft.com> Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI. This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis. These enhancements were mostly focused on the Email Service Provider. I have revised the source document which is attached. And for reference, I’m also including the formatted earlier draft. Could I please get any final comments by the end of this week (25th)? Thanks. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander
That it can convert from IDN to Punycode and from Punycode to IDN - that’s what we mean by bi-directional. I would welcome suggestions for a better phrasing. Don
On 24/01/2017, at 9:55 AM, Stuart Stuple <stuartst@exchange.microsoft.com> wrote:
What is meant by “bi-directional” in this context? I think you mean “can handle bi-directional domain names”. ASCII characters are inherently Left-to-right and hence never bidirectional. <> From: ua-eai-bounces@icann.org <mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org <mailto:ua-eai-bounces@icann.org>] On Behalf Of Don Hollander Sent: Monday, January 23, 2017 11:28 AM To: Mark Svancarek <marksv@microsoft.com <mailto:marksv@microsoft.com>>; HEALTH Yao <yaojk@cnnic.cn <mailto:yaojk@cnnic.cn>>; ua-eai@icann.org <mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org <mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI
This is what I have now:
Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. Seehttps://tools.ietf.org/html/rfc3492[na01.safelinks.protection.outlook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protecti...>
From: Mark Svancarek <marksv@microsoft.com <mailto:marksv@microsoft.com>> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn <mailto:yaojk@cnnic.cn>>, Don Hollander <don.hollander@icann.org <mailto:don.hollander@icann.org>>, "ua-eai@icann.org <mailto:ua-eai@icann.org>" <ua-eai@icann.org <mailto:ua-eai@icann.org>> Cc: "ua-coordination@icann.org <mailto:ua-coordination@icann.org>" <ua-coordination@icann.org <mailto:ua-coordination@icann.org>> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI
Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation.
From: ua-eai-bounces@icann.org <mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org <mailto:ua-eai-bounces@icann.org>] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org <mailto:don.hollander@icann.org>>; ua-eai@icann.org <mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org <mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI
Hello,
The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment.
xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--".
======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form."
"An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org][na01.safelinks.protection.outlook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protecti...>) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org][na01.safelinks.protection.outlook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protecti...>), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org][na01.safelinks.protection.outlook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protecti...>] and hence a maximum of 59 ASCII characters in length. "
Jiankang Yao
From: Don Hollander <mailto:don.hollander@icann.org> Date: 2017-01-22 17:33 To: ua-eai@icann.org <mailto:ua-eai@icann.org> CC: Tan Tanaka, Dennis <mailto:dtantanaka@verisign.com>; Mark Svancarek via UA-Coordination <mailto:ua-coordination@icann.org>; Dr. AJAY D A T A <mailto:ajay@data.in>; Stuart Stuple <mailto:stuartst@exchange.microsoft.com> Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI.
This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis.
These enhancements were mostly focused on the Email Service Provider.
I have revised the source document which is attached.
And for reference, I’m also including the formatted earlier draft.
Could I please get any final comments by the end of this week (25th)?
Thanks.
Don
Don Hollander Universal Acceptance Steering Group Skype: don_hollander
Don Hollander Universal Acceptance Steering Group Skype: don_hollander
or we may just use the definition in the abstract of rfc3492, Punycode is a simple and efficient transfer encoding syntax designed for use with Internationalized Domain Names in Applications (IDNA). Jiankang Yao From: Don Hollander Date: 2017-01-24 12:07 To: Stuart Stuple CC: Mark Svancarek; yaojk; ua-eai@icann.org Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI That it can convert from IDN to Punycode and from Punycode to IDN - that’s what we mean by bi-directional. I would welcome suggestions for a better phrasing. Don On 24/01/2017, at 9:55 AM, Stuart Stuple <stuartst@exchange.microsoft.com> wrote: What is meant by “bi-directional” in this context? I think you mean “can handle bi-directional domain names”. ASCII characters are inherently Left-to-right and hence never bidirectional. From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Monday, January 23, 2017 11:28 AM To: Mark Svancarek <marksv@microsoft.com>; HEALTH Yao <yaojk@cnnic.cn>; ua-eai@icann.org Cc: ua-coordination@icann.org Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI This is what I have now: Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. Seehttps://tools.ietf.org/html/rfc3492[na01.safelinks.protection.outlook.com] From: Mark Svancarek <marksv@microsoft.com> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn>, Don Hollander <don.hollander@icann.org>, "ua-eai@icann.org" <ua-eai@icann.org> Cc: "ua-coordination@icann.org" <ua-coordination@icann.org> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation. From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org>; ua-eai@icann.org Cc: ua-coordination@icann.org Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Hello, The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment. xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--". ======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form." "An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org][na01.safelinks.protection.outlook.com]) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org][na01.safelinks.protection.outlook.com]), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org][na01.safelinks.protection.outlook.com]] and hence a maximum of 59 ASCII characters in length. " Jiankang Yao From: Don Hollander Date: 2017-01-22 17:33 To: ua-eai@icann.org CC: Tan Tanaka, Dennis; Mark Svancarek via UA-Coordination; Dr. AJAY D A T A; Stuart Stuple Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI. This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis. These enhancements were mostly focused on the Email Service Provider. I have revised the source document which is attached. And for reference, I’m also including the formatted earlier draft. Could I please get any final comments by the end of this week (25th)? Thanks. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander Don Hollander Universal Acceptance Steering Group Skype: don_hollander
If we are trying to encourage adoption, I’d avoid terms such as “simple and efficient” as those (understandably) scare many IT administrators as being too “black box” and marketing-oriented. I think the concept that you are trying to convey is that “Punycode is a two-way encoding/decoding algorithm; if the message travels through a mail system that only understands ASCII, the original EAI can be restored from the Punycode representation.” From: Jiankang Yao [mailto:yaojk@cnnic.cn] Sent: Monday, January 23, 2017 8:34 PM To: Don Hollander <don.hollander@icann.org>; Stuart Stuple <stuartst@exchange.microsoft.com> Cc: Mark Svancarek <marksv@microsoft.com>; ua-eai@icann.org Subject: Re: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI or we may just use the definition in the abstract of rfc3492, Punycode is a simple and efficient transfer encoding syntax designed for use with Internationalized Domain Names in Applications (IDNA). ________________________________ Jiankang Yao From: Don Hollander<mailto:don.hollander@icann.org> Date: 2017-01-24 12:07 To: Stuart Stuple<mailto:stuartst@exchange.microsoft.com> CC: Mark Svancarek<mailto:marksv@microsoft.com>; yaojk<mailto:yaojk@cnnic.cn>; ua-eai@icann.org<mailto:ua-eai@icann.org> Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI That it can convert from IDN to Punycode and from Punycode to IDN - that’s what we mean by bi-directional. I would welcome suggestions for a better phrasing. Don On 24/01/2017, at 9:55 AM, Stuart Stuple <stuartst@exchange.microsoft.com<mailto:stuartst@exchange.microsoft.com>> wrote: What is meant by “bi-directional” in this context? I think you mean “can handle bi-directional domain names”. ASCII characters are inherently Left-to-right and hence never bidirectional. From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Monday, January 23, 2017 11:28 AM To: Mark Svancarek <marksv@microsoft.com<mailto:marksv@microsoft.com>>; HEALTH Yao <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org<mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [Ext] RE: [UA-Coordination] Revised UASG013 - Quick Guide to EAI This is what I have now: Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. Seehttps://tools.ietf.org/html/rfc3492[na01.safelinks.protection.outlook.com]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Ftools.ietf.org-252Fhtml-252Frfc3492-26data-3D02-257C01-257Cstuartst-2540exchange.microsoft.com-257C36a667bd28d74362262008d443c5ebde-257C72f988bf86f141af91ab2d7cd011db47-257C1-257C0-257C636207964727009377-26sdata-3DWjtnPYPKNEpGDJS-252ByeUCwtiIcZrPN0A9Kfi65FJG-252FLs-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3DFmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM%26r%3DYI0XKyKCabKQi3GVWLvuoyCWjH9WBgEBxLbMnmhSRwo%26m%3Dl3y3GwCosKJMZjh_BWVqo9aMg3v9s_y7uvSIL9z4sy8%26s%3D_mZy2Dbm5obQM__CCc-dfDC2Kn8UNz2EuAPR6BALao0%26e%3D&data=02%7C01%7Cstuartst%40exchange.microsoft.com%7Cdf4a20a77d1a416d1e4008d444123ff7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636208292565556283&sdata=NK1N5p1bGdmCjPVOpqqZg8skaFzkSDnRb%2BDfCl1I5Q0%3D&reserved=0> From: Mark Svancarek <marksv@microsoft.com<mailto:marksv@microsoft.com>> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>>, Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>, "ua-eai@icann.org<mailto:ua-eai@icann.org>" <ua-eai@icann.org<mailto:ua-eai@icann.org>> Cc: "ua-coordination@icann.org<mailto:ua-coordination@icann.org>" <ua-coordination@icann.org<mailto:ua-coordination@icann.org>> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation. From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org<mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Hello, The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment. xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--". ======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form." "An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org][na01.safelinks.protection.outlook.com]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org][na01.safelinks.protection.outlook.com]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org][na01.safelinks.protection.outlook.com]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense....>] and hence a maximum of 59 ASCII characters in length. " ________________________________ Jiankang Yao From: Don Hollander<mailto:don.hollander@icann.org> Date: 2017-01-22 17:33 To: ua-eai@icann.org<mailto:ua-eai@icann.org> CC: Tan Tanaka, Dennis<mailto:dtantanaka@verisign.com>; Mark Svancarek via UA-Coordination<mailto:ua-coordination@icann.org>; Dr. AJAY D A T A<mailto:ajay@data.in>; Stuart Stuple<mailto:stuartst@exchange.microsoft.com> Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI. This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis. These enhancements were mostly focused on the Email Service Provider. I have revised the source document which is attached. And for reference, I’m also including the formatted earlier draft. Could I please get any final comments by the end of this week (25th)? Thanks. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander Don Hollander Universal Acceptance Steering Group Skype: don_hollander
Seems good From: Don Hollander [mailto:don.hollander@icann.org] Sent: Monday, January 23, 2017 11:28 AM To: Mark Svancarek <marksv@microsoft.com>; HEALTH Yao <yaojk@cnnic.cn>; ua-eai@icann.org Cc: ua-coordination@icann.org Subject: Re: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI This is what I have now: Punycode is an algorithm that converts a non-ASCII domain string into an ASCII string. ASCII strings that have gone through the Punycode process can be identified by a prefix of xn--. The Punycode algorithm is bi-directional. See https://tools.ietf.org/html/rfc3492 From: Mark Svancarek <marksv@microsoft.com<mailto:marksv@microsoft.com>> Date: Tuesday, 24 January 2017 at 8:23 AM To: HEALTH Yao <yaojk@cnnic.cn<mailto:yaojk@cnnic.cn>>, Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>, "ua-eai@icann.org<mailto:ua-eai@icann.org>" <ua-eai@icann.org<mailto:ua-eai@icann.org>> Cc: "ua-coordination@icann.org<mailto:ua-coordination@icann.org>" <ua-coordination@icann.org<mailto:ua-coordination@icann.org>> Subject: [Ext] RE: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Good catch. The ACE prefix indicates to a parser that the following string is the Punycoded transformation of an IDNA-compatible Unicode string, but is not actually a part of that transformation. From: ua-eai-bounces@icann.org<mailto:ua-eai-bounces@icann.org> [mailto:ua-eai-bounces@icann.org] On Behalf Of Jiankang Yao Sent: Sunday, January 22, 2017 6:27 PM To: Don Hollander <don.hollander@icann.org<mailto:don.hollander@icann.org>>; ua-eai@icann.org<mailto:ua-eai@icann.org> Cc: ua-coordination@icann.org<mailto:ua-coordination@icann.org> Subject: Re: [UA-EAI] [UA-Coordination] Revised UASG013 - Quick Guide to EAI Hello, The definition "Punycode is an algorithm that converts an IDN into an ASCII string that starts with xn--. The Punycode algorithm is bi-directional. " needs some adjustment. xn--abcdeddaa where "xn--" is a prefix and "abcdeddaa" is output of the Punycode algorithm. So Punycode output does not include "xn--". ======================================following are texts from RFC5890=============================== " the string following "xn--" must be the valid output of the Punycode algorithm and must be convertible into valid U-label form." "An "A-label" is the ASCII-Compatible Encoding (ACE, see Section 2.3.2.5[tools.ietf.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc...>) form of an IDNA-valid string. It must be a complete label: IDNA is defined for labels, not for parts of them and not for complete domain names. This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--" (see Section 2.3.2.5[tools.ietf.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc...>), followed by a string that is a valid output of the Punycode algorithm [RFC3492[tools.ietf.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc...>] and hence a maximum of 59 ASCII characters in length. " ________________________________ Jiankang Yao From: Don Hollander<mailto:don.hollander@icann.org> Date: 2017-01-22 17:33 To: ua-eai@icann.org<mailto:ua-eai@icann.org> CC: Tan Tanaka, Dennis<mailto:dtantanaka@verisign.com>; Mark Svancarek via UA-Coordination<mailto:ua-coordination@icann.org>; Dr. AJAY D A T A<mailto:ajay@data.in>; Stuart Stuple<mailto:stuartst@exchange.microsoft.com> Subject: [UA-Coordination] Revised UASG013 - Quick Guide to EAI Last month I sent out a formatted Quick Guide to EAI. This resulted in a number of comments from Ajay, Stuart, Mark, Lars & Dennis. These enhancements were mostly focused on the Email Service Provider. I have revised the source document which is attached. And for reference, I’m also including the formatted earlier draft. Could I please get any final comments by the end of this week (25th)? Thanks. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander
participants (4)
-
Don Hollander -
Jiankang Yao -
Mark Svancarek -
Stuart Stuple