Embed Size (px)
Citation preview
International DomainNames
Implementation notesMichel SuignardMicrosoft Corp
االمارات افغانستان Հայաստան АзəрбајҹанآذربايجانБосна-и-Херцеговина বাংলােদশ Българияبروني البحرين འ ག ལБеларусь ᑲᓇᑕ中国 Србија-и-Црна-Гора Κύπρος مصر الجزائر جيبوتي
الصحراءالغربية ኤርትራ إريتريا ኢትዮጵያ საქართველო Ελλάδα香港 إسرائيلישראל भारत ভারত ਭਾਰਤભારત இநதியா రత ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত األردن ايران العراق بھارت 日本
Кыргызстан កមពជា 조선한국القمر الكويت Қазақстан ລາວ لبنان ශ ලංකාஇலஙைக ليبياالمغرب Македонија Монгол-улсᠮᠣ ᠨ ᠭ ᠣ ᠯ澳門 ދވހ موريتانية नपाल قطر فلسطين پاکستان عمانРоссия السودان السعودية 新加坡 சிஙகப ர تشاد سوريا ประเทศไทย Тоҷикистон Туркменистан台灣臺灣تونس Україна Украина Ўзбекистон اليمن
IDNA status at Microsoftbull IDNA solves a major customer demand
by making both resources and pointers (IRI-URI) written in native languagesndash http味の素jpndash httpثبتدامنهايرانir
bull Appropriate layers provided by platform services (Windows XP Vista)ndash Support for IDNA RFCs (ToASCII ToUnicode)ndash Script helpers (Script in text Script per locale)
bull Used by IE7 and forthcoming version of Outlook
bull User locale and customization determines visual experience
Language preference
bull List of languages that are intelligible to the user
bull Add suffix to the domain name
Preventing homograph spoofing attacks
bull IDN names with contents not familiar to the user are shown in Punycode formndash Scripts unknown to a user (locale based)ndash Mixed scripts (unless customary for the
languagelocale)
http味の素jp OK for a Japanese user although it contains both Kanji (Han) and Hiragana
httpигроshopcom always shows ashttpxn--shop-k4d3a7bpcom
Mixed scripts example
IDN issuesbull Cannot support improvement beyond
Unicode 32ndash Existing scripts (Ethiopic Greek Khmer Latin
etchellip)ndash New scripts (NrsquoKo Tai Le Tifinagh etchellip)
bull At least one script (Myanmar) is going through a major revision since 32
bull Removal of ZWJ ZWNJ by IDN process is problematic forndash Sindhi ශ ලංකා versus ශර ලංකාndash Myanmar မရနမာ versus ndash Persian
bull No serious security threat mitigation
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
IDNA status at Microsoftbull IDNA solves a major customer demand
by making both resources and pointers (IRI-URI) written in native languagesndash http味の素jpndash httpثبتدامنهايرانir
bull Appropriate layers provided by platform services (Windows XP Vista)ndash Support for IDNA RFCs (ToASCII ToUnicode)ndash Script helpers (Script in text Script per locale)
bull Used by IE7 and forthcoming version of Outlook
bull User locale and customization determines visual experience
Language preference
bull List of languages that are intelligible to the user
bull Add suffix to the domain name
Preventing homograph spoofing attacks
bull IDN names with contents not familiar to the user are shown in Punycode formndash Scripts unknown to a user (locale based)ndash Mixed scripts (unless customary for the
languagelocale)
http味の素jp OK for a Japanese user although it contains both Kanji (Han) and Hiragana
httpигроshopcom always shows ashttpxn--shop-k4d3a7bpcom
Mixed scripts example
IDN issuesbull Cannot support improvement beyond
Unicode 32ndash Existing scripts (Ethiopic Greek Khmer Latin
etchellip)ndash New scripts (NrsquoKo Tai Le Tifinagh etchellip)
bull At least one script (Myanmar) is going through a major revision since 32
bull Removal of ZWJ ZWNJ by IDN process is problematic forndash Sindhi ශ ලංකා versus ශර ලංකාndash Myanmar မရနမာ versus ndash Persian
bull No serious security threat mitigation
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Language preference
bull List of languages that are intelligible to the user
bull Add suffix to the domain name
Preventing homograph spoofing attacks
bull IDN names with contents not familiar to the user are shown in Punycode formndash Scripts unknown to a user (locale based)ndash Mixed scripts (unless customary for the
languagelocale)
http味の素jp OK for a Japanese user although it contains both Kanji (Han) and Hiragana
httpигроshopcom always shows ashttpxn--shop-k4d3a7bpcom
Mixed scripts example
IDN issuesbull Cannot support improvement beyond
Unicode 32ndash Existing scripts (Ethiopic Greek Khmer Latin
etchellip)ndash New scripts (NrsquoKo Tai Le Tifinagh etchellip)
bull At least one script (Myanmar) is going through a major revision since 32
bull Removal of ZWJ ZWNJ by IDN process is problematic forndash Sindhi ශ ලංකා versus ශර ලංකාndash Myanmar မရနမာ versus ndash Persian
bull No serious security threat mitigation
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Preventing homograph spoofing attacks
bull IDN names with contents not familiar to the user are shown in Punycode formndash Scripts unknown to a user (locale based)ndash Mixed scripts (unless customary for the
languagelocale)
http味の素jp OK for a Japanese user although it contains both Kanji (Han) and Hiragana
httpигроshopcom always shows ashttpxn--shop-k4d3a7bpcom
Mixed scripts example
IDN issuesbull Cannot support improvement beyond
Unicode 32ndash Existing scripts (Ethiopic Greek Khmer Latin
etchellip)ndash New scripts (NrsquoKo Tai Le Tifinagh etchellip)
bull At least one script (Myanmar) is going through a major revision since 32
bull Removal of ZWJ ZWNJ by IDN process is problematic forndash Sindhi ශ ලංකා versus ශර ලංකාndash Myanmar မရနမာ versus ndash Persian
bull No serious security threat mitigation
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Mixed scripts example
IDN issuesbull Cannot support improvement beyond
Unicode 32ndash Existing scripts (Ethiopic Greek Khmer Latin
etchellip)ndash New scripts (NrsquoKo Tai Le Tifinagh etchellip)
bull At least one script (Myanmar) is going through a major revision since 32
bull Removal of ZWJ ZWNJ by IDN process is problematic forndash Sindhi ශ ලංකා versus ශර ලංකාndash Myanmar မရနမာ versus ndash Persian
bull No serious security threat mitigation
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
IDN issuesbull Cannot support improvement beyond
Unicode 32ndash Existing scripts (Ethiopic Greek Khmer Latin
etchellip)ndash New scripts (NrsquoKo Tai Le Tifinagh etchellip)
bull At least one script (Myanmar) is going through a major revision since 32
bull Removal of ZWJ ZWNJ by IDN process is problematic forndash Sindhi ශ ලංකා versus ශර ලංකාndash Myanmar မရနမာ versus ndash Persian
bull No serious security threat mitigation
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Recommendations for IDN future
bull Extend support to Unicode 50 or even future version 5x to support Myanmar
bull De-emphasize role of the complex IDN Nameprep process
bull Focus on the output list insteadbull Restrict problematic characters from the IDN
namespacendash symbolsndash not in modern-use scripts or script elementsndash combining characters not in first label letter
bull Standardize the IDN namespace as an ISO 10646 character collection
bull Establish script based guidelines for constituencies with worldwide reach (such as gTLDs)
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Guidelines for IDN repertoire for generic TLDsbull Worldwide name space
ndash All modern writing systems can be represented in IDNbull Multi-script coverage
ndash All modern scripts are availablebull Secure environment
ndash Mixed script prohibited in labels (with exceptions)ndash Repertoire restriction
bull Equal accessndash Put all gTLDs on same footingndash Compatible with ccTLDs practice
bull Based on Idncharstxtndash 37199 characters
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
IDNIDNbull Technical issue
ndash Trivial for disjoint domains (making sure root level label lt= 63)
ndash Joint domains should behave as a single domain from a security point of view
bull Alternate names for many TLDs is obviousndash jp 日本
ndash ma المغرب ndash np नपाल
bull Name policies need to be defined for multilingual regionscountries (how many)ndash India भारत ভারত ਭਾਰਤ ભારત இநதிய రత
ಭಾರತ ഭാരത भारतम ଭାରତ ভাৰত بھارتbull gTLD policies need to be established
ndash How manyndash Ownership (博物館 by MuseDoma)
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Resources
bull httpwwwmicrosoftcomwindowsieie7ie7betaredirectmspxndash IE7 Beta 2
bull httpmsdnmicrosoftcomlibraryen-usintlnls_IDNaspndash IdnDLdll (down level scripts APIs)ndash Normalizdll (IDN and normalization functions)
bull httpblogsmsdncomiendash Recent developments on IE7
bull httpwwwunicodeorgreportstr36tr36-4htmlndash Information about confusables IDncharstxt hellip
bull httpwwwunicodeorgreportstr24tr24-7htmlndash Script tables
Questions
Questions
![Maroussi, 1-3-2018 DECISION: 843/2 DECISION · Domain Name that may be subject to assignment by EETT, i.e. all 2nd level [.gr] or [.ελ] Domain Names and all 3rd level [.gr] Domain](https://img.pdfslide.tips/doc/110x75/6003f2ec3175f641c53ed88d/maroussi-1-3-2018-decision-8432-decision-domain-name-that-may-be-subject-to-assignment.jpg)
