IDN over EPP IDN over EPP (IDNPROV)(IDNPROV)
IETF BOF, Washington DCIETF BOF, Washington DCNovember 2004November 2004
AgendaAgenda
Agenda Bashing (5 min)Agenda Bashing (5 min)
IDN / EPP Basics (2 min)IDN / EPP Basics (2 min)
IDN Registration Background (8 min)IDN Registration Background (8 min)
Problem Statement / Discussion (30 min)Problem Statement / Discussion (30 min)
Moving Forward (15 min)Moving Forward (15 min)
IDN BasicsIDN BasicsIDNAIDNA Specifies that ToACE conversion to be managed at Specifies that ToACE conversion to be managed at
the application layer at the client for DNS resolutionthe application layer at the client for DNS resolution
NameprepNameprep Specifies equivalent Unicode Characters to map and Specifies equivalent Unicode Characters to map and
full scope of valid charactersfull scope of valid characters
PunycodePunycode ASCII Compatible Encoding (ACE)ASCII Compatible Encoding (ACE)
ICANN IDN GuidelinesICANN IDN Guidelines Intended Language should be considered at Intended Language should be considered at
registrationregistration Conservativeness PrincipleConservativeness Principle
EPP BasicsEPP BasicsXML based, created with Domain Registration in XML based, created with Domain Registration in mind but extensible for other registriesmind but extensible for other registriesSession Management Commands (2):Session Management Commands (2): Login/LogoutLogin/Logout
Query Commands (4):Query Commands (4): Check, Info, Poll, TransferCheck, Info, Poll, Transfer
Transform Commands (5):Transform Commands (5): Create, Delete, Renew, Transfer, UpdateCreate, Delete, Renew, Transfer, Update
Current Standard Mappings:Current Standard Mappings: Domain MappingDomain Mapping Contact MappingContact Mapping Host MappingHost Mapping
IDN RegistrationsIDN Registrations
What data is to be passed from the What data is to be passed from the Registrar (Client) to the Registry (Server), Registrar (Client) to the Registry (Server), and vice versa?and vice versa? Submitted String (the IDN)Submitted String (the IDN) Provisioning ElementsProvisioning Elements
Language-TagsLanguage-Tags
IDN VariantsIDN Variants Protocol DesignProtocol Design
Submitted IDN StringSubmitted IDN String
Format of IDNFormat of IDN Punycode?Punycode? UTF-8?UTF-8? Others?Others? Allow submission in multiple formats?Allow submission in multiple formats?
““Sanitization” of IDN submittedSanitization” of IDN submitted Must the client submit Nameprep-ed string?Must the client submit Nameprep-ed string? Should the option of sending a non-Should the option of sending a non-
Nameprep-ed string be included in the core Nameprep-ed string be included in the core protocol?protocol?
Provisioning ElementsProvisioning Elements
Language-TagLanguage-Tag ICANN IDN GuidelinesICANN IDN Guidelines RFC3066 (BCP47)RFC3066 (BCP47) Declaration of Intended Language(s)Declaration of Intended Language(s) Multiple Language-Tags for single registrationMultiple Language-Tags for single registration Updating of associated Language-TagsUpdating of associated Language-Tags
Basic Concept of VariantsBasic Concept of VariantsGiven an IDN registration:Given an IDN registration: Submitted String (Primary IDN)Submitted String (Primary IDN) Intended Language (Language-Tag)Intended Language (Language-Tag) Corresponding Language-Table (Character Corresponding Language-Table (Character
Equivalence Mapping Table)Equivalence Mapping Table)
A Set of IDN Variants are Generated. These A Set of IDN Variants are Generated. These Variants may be:Variants may be: Automatically “Activated” and included in zoneAutomatically “Activated” and included in zone Reserved and not available for provisioning by other Reserved and not available for provisioning by other
registrantregistrant ““Activated” to the zone at a later timeActivated” to the zone at a later time
Variants generally inherit the statuses of its Variants generally inherit the statuses of its Primary IDN, and the set can be considered a Primary IDN, and the set can be considered a subordinate.subordinate.
Variants ProvisioningVariants Provisioning
VariantsVariants Client / Server determined variant tables?Client / Server determined variant tables? Conveyance of Variants between Client and Conveyance of Variants between Client and
Server (full list may be very large)Server (full list may be very large) ““Activation” and “Deactivation” of VariantsActivation” and “Deactivation” of Variants Manageability / Inheritance of Variants (status Manageability / Inheritance of Variants (status
values, expiry, name server delegations, etc.)values, expiry, name server delegations, etc.) Host Objects for VariantsHost Objects for Variants
Basic Problem DescriptionBasic Problem DescriptionIDN Registration will likely become a frequent IDN Registration will likely become a frequent transaction and a core functionality for most transaction and a core functionality for most Domain RegistriesDomain RegistriesDiverging Extensions to EPP for the provisioning Diverging Extensions to EPP for the provisioning of IDNs is not in the best interests of the industry of IDNs is not in the best interests of the industry and defeats the purpose of having a and defeats the purpose of having a standardized EPPstandardized EPPIDN Registration requirements relate with IDN Registration requirements relate with Registry Policies, but IDN over EPP extensions Registry Policies, but IDN over EPP extensions should simply allow provisioning of the core should simply allow provisioning of the core elements for IDN registrations to allow Registries elements for IDN registrations to allow Registries to implement their own policiesto implement their own policies
Current StatesCurrent States
Do Nothing (.PL)Do Nothing (.PL) No extensions to EPP for IDNsNo extensions to EPP for IDNs IDNs transported in Punycode formatIDNs transported in Punycode format No Language-Tags requiredNo Language-Tags required Acceptability based on set of valid codepointsAcceptability based on set of valid codepoints
Domain Mapping Extensions (.INFO)Domain Mapping Extensions (.INFO) Extensions for conveyance of Language-TagsExtensions for conveyance of Language-Tags IDNs transported in Punycode formatIDNs transported in Punycode format
New IDN Object (testbed at .TW)New IDN Object (testbed at .TW) Language-Tags and Variants provisioningLanguage-Tags and Variants provisioning IDNs transported in UTF-8 (Nameprep-ed)IDNs transported in UTF-8 (Nameprep-ed)
Our proposalOur proposal
Extend EPP, so provision of IDN “works”Extend EPP, so provision of IDN “works” We already see diversity among solutionsWe already see diversity among solutions
Do this work in a new wg of the IETFDo this work in a new wg of the IETF
Potential Scope for the wgPotential Scope for the wg
Defining a policy-less framework (i.e. set Defining a policy-less framework (i.e. set of core requirements for IDN provisioning)of core requirements for IDN provisioning) What data to be passed between Client and What data to be passed between Client and
ServerServer
Format of Submitted StringFormat of Submitted String Determining standard format(s) to be used Determining standard format(s) to be used
during transportduring transport
Protocol DesignProtocol Design
DeliverablesDeliverables
Architecture specificationArchitecture specification What data is passed between what entitiesWhat data is passed between what entities Overall architecture descriptionOverall architecture description
epp extension specificationepp extension specification Extensions to eppExtensions to epp
What if the wg detect changes to core epp What if the wg detect changes to core epp is needed?is needed? New version of epp after recharteringNew version of epp after rechartering
Thank YouThank You
Edmon ChungEdmon Chung [email protected]@afilias.info
Patrik FalstromPatrik Falstrom [email protected]@cisco.com
Howard ElandHoward Eland [email protected]@afilias.info