Diff: draft-gould-idn-table-01.txt - draft-gould-idn-table-02.txt

	< draft-gould-idn-table-01.txt	draft-gould-idn-table-02.txt >

	Network Working Group J. Gould	Network Working Group J. Gould
	Internet-Draft VeriSign, Inc.	Internet-Draft VeriSign, Inc.
	Intended status: Standards Track F. Obispo	Intended status: Standards Track F. Obispo

	Expires: September 3, 2015 L. Munoz	Expires: October 4, 2015 L. Munoz
	Uniregistry Corp.	Uniregistry Corp.

	March 2, 2015	April 2, 2015

	Extensible Provisioning Protocol (EPP) Internationalized Domain Name	Extensible Provisioning Protocol (EPP) Internationalized Domain Name
	(IDN) Table Mapping	(IDN) Table Mapping

	draft-gould-idn-table-01	draft-gould-idn-table-02

	Abstract	Abstract

	This document describes an Extensible Provisioning Protocol (EPP)	This document describes an Extensible Provisioning Protocol (EPP)
	mapping for getting Internationalized Domain Name (IDN)	mapping for getting Internationalized Domain Name (IDN)
	Table information for the registration of IDNs, using the EPP domain	Table information for the registration of IDNs, using the EPP domain
	name mapping, and optionally with the IDN mapping extension. An IDN	name mapping, and optionally with the IDN mapping extension. An IDN
	Table defines the valid set of characters (code points) that can be	Table defines the valid set of characters (code points) that can be
	used in a domain name. Code points may overlap across IDN Tables and	used in a domain name. Code points may overlap across IDN Tables and
	the IDN Tables supported by the servers are up to server policy.	the IDN Tables supported by the servers are up to server policy.

	skipping to change at page 1, line 44 ¶	skipping to change at page 1, line 44 ¶
	Internet-Drafts are working documents of the Internet Engineering	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute	Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-	working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.	Drafts is at http://datatracker.ietf.org/drafts/current/.

	Internet-Drafts are draft documents valid for a maximum of six months	Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any	and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference	time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."	material or to cite them other than as "work in progress."


	This Internet-Draft will expire on September 3, 2015.	This Internet-Draft will expire on October 4, 2015.

	Copyright Notice	Copyright Notice

	Copyright (c) 2015 IETF Trust and the persons identified as the	Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.	document authors. All rights reserved.

	This document is subject to BCP 78 and the IETF Trust's Legal	This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents	Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of	(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents	publication of this document. Please review these documents

	skipping to change at page 2, line 28 ¶	skipping to change at page 2, line 28 ¶
	described in the Simplified BSD License.	described in the Simplified BSD License.

	Table of Contents	Table of Contents

	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Conventions Used in This Document . . . . . . . . . . . . 3	1.1. Conventions Used in This Document . . . . . . . . . . . . 3
	2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4	2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
	2.1. IDN Table Identifier . . . . . . . . . . . . . . . . . . 4	2.1. IDN Table Identifier . . . . . . . . . . . . . . . . . . 4
	2.2. Domain Name . . . . . . . . . . . . . . . . . . . . . . . 4	2.2. Domain Name . . . . . . . . . . . . . . . . . . . . . . . 4
	3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4	3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4

	3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4	3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5
	3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 5	3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 5
	3.1.1.1. Domain Check Form . . . . . . . . . . . . . . . . 5	3.1.1.1. Domain Check Form . . . . . . . . . . . . . . . . 5
	3.1.1.2. Table Check Form . . . . . . . . . . . . . . . . 7	3.1.1.2. Table Check Form . . . . . . . . . . . . . . . . 7
	3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9	3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9
	3.1.2.1. Domain Info Form . . . . . . . . . . . . . . . . 9	3.1.2.1. Domain Info Form . . . . . . . . . . . . . . . . 9
	3.1.2.2. Table Info Form . . . . . . . . . . . . . . . . . 13	3.1.2.2. Table Info Form . . . . . . . . . . . . . . . . . 13

	3.1.2.3. List Info Form . . . . . . . . . . . . . . . . . 18	3.1.2.3. List Info Form . . . . . . . . . . . . . . . . . 17
	3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 19	3.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 19
	3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 20	3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 20
	3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 20	3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 20
	3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20	3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20
	3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20	3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20
	3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20	3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20
	3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 20	3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 20
	4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20	4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20
	4.1. IDN Table Mapping Schema . . . . . . . . . . . . . . . . 21	4.1. IDN Table Mapping Schema . . . . . . . . . . . . . . . . 21

	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
	5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 26	5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 26
	5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 26	5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 26

	6. Security Considerations . . . . . . . . . . . . . . . . . . . 27	6. Security Considerations . . . . . . . . . . . . . . . . . . . 26
	7. Normative References . . . . . . . . . . . . . . . . . . . . 27	7. Normative References . . . . . . . . . . . . . . . . . . . . 26
	Appendix A. Change History . . . . . . . . . . . . . . . . . . . 28	Appendix A. Change History . . . . . . . . . . . . . . . . . . . 27
	A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 28	A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 27
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28	A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 27

		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27

	1. Introduction	1. Introduction

	This document describes an extension mapping for version 1.0 of the	This document describes an extension mapping for version 1.0 of the
	Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping	Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
	provides Internationalized Domain Name (IDN) Table information for	provides Internationalized Domain Name (IDN) Table information for
	the registration of IDNs, using the EPP domain name mapping	the registration of IDNs, using the EPP domain name mapping
	[RFC5731], and optionally with the IDN mapping extension	[RFC5731], and optionally with the IDN mapping extension
	[I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of	[I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of
	characters (code points) that can be used in a domain name. Code	characters (code points) that can be used in a domain name. Code

	skipping to change at page 3, line 28 ¶	skipping to change at page 3, line 30 ¶
	the following:	the following:

	"Validate IDN Domain Name" Validate that an IDN meets the server IDN	"Validate IDN Domain Name" Validate that an IDN meets the server IDN
	policy. The validation can be done prior to submitting a domain	policy. The validation can be done prior to submitting a domain
	create, per [RFC5731].	create, per [RFC5731].
	"Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since	"Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since
	IDN Table code points may overlap, the mapping can be used to	IDN Table code points may overlap, the mapping can be used to
	identify the matching set of IDN Tables (language or script),	identify the matching set of IDN Tables (language or script),
	along with the IDN Table meta-data.	along with the IDN Table meta-data.
	"Cache IDN Table Code Points" Clients can query for the complete	"Cache IDN Table Code Points" Clients can query for the complete

	list of IDN Tables and can get the IDN Table meta-data and	list of IDN Tables and can get the IDN Table meta-data, based on
	optionally the code points, based on server policy, to support	server policy, to support pre-validation in the client.
	pre-validation in the client.
	"Get the IDN Table Identifier to Pass with a Domain Create" Each IDN	"Get the IDN Table Identifier to Pass with a Domain Create" Each IDN
	Table includes a server unique IDN Table Identifier that may be	Table includes a server unique IDN Table Identifier that may be
	used as the value of the <idn:table> element in the IDN mapping	used as the value of the <idn:table> element in the IDN mapping
	extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the	extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the
	IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the	IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the
	domain name.	domain name.

	1.1. Conventions Used in This Document	1.1. Conventions Used in This Document

	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

	skipping to change at page 10, line 14 ¶	skipping to change at page 10, line 14 ¶

	<idnTable:domain> The domain name, as defined in Section 2.2, to	<idnTable:domain> The domain name, as defined in Section 2.2, to
	validate against the IDN Tables and IDN policies, and to retrieve	validate against the IDN Tables and IDN policies, and to retrieve
	the matching IDN Table meta-data.	the matching IDN Table meta-data.

	Example Domain Info Form <info> command using a U-label Domain Name:	Example Domain Info Form <info> command using a U-label Domain Name:

	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>

	C: <check>	C: <info>
	C: <idnTable:info	C: <idnTable:info
	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">
	C: <idnTable:domain>idn1.example</idnTable:domain>	C: <idnTable:domain>idn1.example</idnTable:domain>
	C: </idnTable:info>	C: </idnTable:info>

	C: </check>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	Example Domain Info Form <info> command using an A-label Domain Name:	Example Domain Info Form <info> command using an A-label Domain Name:

	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>

	C: <check>	C: <info>
	C: <idnTable:info	C: <idnTable:info
	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">
	C: <idnTable:domain>xn--idn1.example</idnTable:domain>	C: <idnTable:domain>xn--idn1.example</idnTable:domain>
	C: </idnTable:info>	C: </idnTable:info>

	C: </check>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	When an <info> command has been processed successfully, the EPP	When an <info> command has been processed successfully, the EPP
	<resData> element MUST contain a child <idnTable:infData> element	<resData> element MUST contain a child <idnTable:infData> element
	that identifies the idnTable namespace. The <idnTable:infData>	that identifies the idnTable namespace. The <idnTable:infData>
	element in the Domain Info Form contains the <idnTable:domain>	element in the Domain Info Form contains the <idnTable:domain>
	element that contains the following child elements:	element that contains the following child elements:


	skipping to change at page 13, line 48 ¶	skipping to change at page 13, line 48 ¶
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54321-XYZ</svTRID>	S: <svTRID>54321-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>
	S:</epp>	S:</epp>

	3.1.2.2. Table Info Form	3.1.2.2. Table Info Form

	The Table Info Form is used to retrieve information associated with	The Table Info Form is used to retrieve information associated with
	an IDN Table object. The information provided meta-data about the	an IDN Table object. The information provided meta-data about the

	IDN Table object along with the OPTIONAL code points.	IDN Table object.

	In addition to the standard EPP command elements, the <info> command	In addition to the standard EPP command elements, the <info> command
	MUST contain an <idnTable:info> element that identifies the	MUST contain an <idnTable:info> element that identifies the
	idnTable namespace. The <idnTable:info> element in the Table Info	idnTable namespace. The <idnTable:info> element in the Table Info
	Form contains the following child elements:	Form contains the following child elements:

	<idnTable:table> Contains the IDN Table Identifier, as defined in	<idnTable:table> Contains the IDN Table Identifier, as defined in
	Section 2.1, of the IDN Table object to be queried.	Section 2.1, of the IDN Table object to be queried.

	Example Table Info Form <info> command for the "CHI" IDN	Example Table Info Form <info> command for the "CHI" IDN
	Table Identifier, which represents a Language IDN Table:	Table Identifier, which represents a Language IDN Table:

	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>

	C: <check>	C: <info>
	C: <idnTable:info	C: <idnTable:info
	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">
	C: <idnTable:table>CHI</idnTable:table>	C: <idnTable:table>CHI</idnTable:table>
	C: </idnTable:info>	C: </idnTable:info>

	C: </check>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	Example Table Info Form <info> command for the "THAI" IDN	Example Table Info Form <info> command for the "THAI" IDN
	Table Identifier, which represents a Script IDN Table:	Table Identifier, which represents a Script IDN Table:

	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>

	C: <check>	C: <info>
	C: <idnTable:info	C: <idnTable:info
	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">
	C: <idnTable:table>THAI</idnTable:table>	C: <idnTable:table>THAI</idnTable:table>
	C: </idnTable:info>	C: </idnTable:info>

	C: </check>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	When an <info> command has been processed successfully, the EPP	When an <info> command has been processed successfully, the EPP
	<resData> element MUST contain a child <idnTable:infData> element	<resData> element MUST contain a child <idnTable:infData> element
	that identifies the idnTable namespace. The <idnTable:infData>	that identifies the idnTable namespace. The <idnTable:infData>
	element in the Table Info Form contains the <idnTable:table> element	element in the Table Info Form contains the <idnTable:table> element
	that contains the following child elements:	that contains the following child elements:


	skipping to change at page 15, line 21 ¶	skipping to change at page 15, line 21 ¶
	present to identify the language if the negotiated value is	present to identify the language if the negotiated value is
	something other than the default value of "en" (English).	something other than the default value of "en" (English).
	<idnTable:upDate> Contains the date and time that the IDN Table was	<idnTable:upDate> Contains the date and time that the IDN Table was
	created or last updated.	created or last updated.
	<idnTable:version> OPTIONAL server defined version number of the IDN	<idnTable:version> OPTIONAL server defined version number of the IDN
	Table.	Table.
	<idnTable:effectiveDate> OPTIONAL effective date for the IDN Table.	<idnTable:effectiveDate> OPTIONAL effective date for the IDN Table.
	<idnTable:variantGen> OPTIONAL boolean flag indicating that domains	<idnTable:variantGen> OPTIONAL boolean flag indicating that domains
	created using the IDN Table will have IDN variants generated.	created using the IDN Table will have IDN variants generated.
	The management of variants is up to server policy.	The management of variants is up to server policy.

	<idnTable:url> OPTIONAL URL for downloading the IDN Table.	<idnTable:url> OPTIONAL URL for downloading the IDN Table with the
	<idnTable:codePoint> Zero or more OPTIONAL <idnTable:codePoint>	applicable set of code points and rules.
	elements for returning the code points of the IDN Table. The
	<idnTable:codePoint> element contains the following child
	elements:

	<idnTable:point> or "<idnTable:from> and <idnTable:to>" Contains
	an individual code point or a code point range. The code
	point must be expressed in uppercase, hexadecimal, and zero
	padded to a minimum of 4 digits - in other words according to
	the standard Unicode convention but without the prefix "U+".
	The individual code points and code point ranges MUST NOT
	specify code points that overlap.
	<idnTable:comment> Server defined code point comment. This text
	MUST be represented in the response language previously
	negotiated with the client; an OPTIONAL "lang" attribute MAY
	be present to identify the language if the negotiated value
	is something other than the default value of "en" (English).

	Example Table Info Form <info> response for the "CHI" IDN	Example Table Info Form <info> response for the "CHI" IDN
	Table Identifier, which represents a Language IDN Table:	Table Identifier, which represents a Language IDN Table:

	S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	S: <response>	S: <response>
	S: <result code="1000">	S: <result code="1000">
	S: <msg>Command completed successfully</msg>	S: <msg>Command completed successfully</msg>
	S: </result>	S: </result>

	skipping to change at page 16, line 19 ¶	skipping to change at page 16, line 31 ¶
	S: </idnTable:description>	S: </idnTable:description>
	S: <idnTable:upDate>2015-02-04T09:30:00.0Z	S: <idnTable:upDate>2015-02-04T09:30:00.0Z
	S: </idnTable:upDate>	S: </idnTable:upDate>
	S: <idnTable:version>1.0</idnTable:version>	S: <idnTable:version>1.0</idnTable:version>
	S: <idnTable:effectiveDate>2014-11-24	S: <idnTable:effectiveDate>2014-11-24
	S: </idnTable:effectiveDate>	S: </idnTable:effectiveDate>
	S: <idnTable:variantGen>true</idnTable:variantGen>	S: <idnTable:variantGen>true</idnTable:variantGen>
	S: <idnTable:url>	S: <idnTable:url>
	S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt	S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt
	S: </idnTable:url>	S: </idnTable:url>

	S: <idnTable:codePoint>
	S: <idnTable:point>002D</idnTable:point>
	S: <idnTable:comment lang="en">
	S: HYPHEN-MINUS
	S: </idnTable:comment>
	S: </idnTable:codePoint>
	S: <idnTable:codePoint>
	S: <idnTable:point>0030</idnTable:point>
	S: </idnTable:codePoint>
	S: <idnTable:codeRange>
	S: <idnTable:from>3918</idnTable:from>
	S: <idnTable:to>396E</idnTable:to>
	S: <idnTable:comment lang="en">
	S: CJK Ideograph Extension A
	S: </idnTable:comment>
	S: </idnTable:codeRange>
	S: <idnTable:codeRange>
	S: <idnTable:from>3C6E</idnTable:from>
	S: <idnTable:to>6BA8</idnTable:to>
	S: </idnTable:codeRange>
	S: </idnTable:table>	S: </idnTable:table>
	S: </idnTable:infData>	S: </idnTable:infData>
	S: </resData>	S: </resData>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54321-XYZ</svTRID>	S: <svTRID>54321-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>
	S:</epp>	S:</epp>
	Example Table Info Form <info> response for the "THAI" IDN	Example Table Info Form <info> response for the "THAI" IDN

	skipping to change at page 17, line 29 ¶	skipping to change at page 17, line 29 ¶
	S: <idnTable:description>Thai</idnTable:description>	S: <idnTable:description>Thai</idnTable:description>
	S: <idnTable:upDate>2014-08-16T09:20:00.0Z	S: <idnTable:upDate>2014-08-16T09:20:00.0Z
	S: </idnTable:upDate>	S: </idnTable:upDate>
	S: <idnTable:version>1.0</idnTable:version>	S: <idnTable:version>1.0</idnTable:version>
	S: <idnTable:effectiveDate>2014-11-24	S: <idnTable:effectiveDate>2014-11-24
	S: </idnTable:effectiveDate>	S: </idnTable:effectiveDate>
	S: <idnTable:variantGen>false</idnTable:variantGen>	S: <idnTable:variantGen>false</idnTable:variantGen>
	S: <idnTable:url>	S: <idnTable:url>
	S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt	S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt
	S: </idnTable:url>	S: </idnTable:url>

	S: <idnTable:codePoint>
	S: <idnTable:point>0E01</idnTable:point>
	S: <idnTable:comment>THAI LETTER KO KAI
	S: </idnTable:comment>
	S: </idnTable:codePoint>
	S: <idnTable:codePoint>
	S: <idnTable:point>0E02</idnTable:point>
	S: </idnTable:codePoint>
	S: <idnTable:codeRange>
	S: <idnTable:from>0030</idnTable:from>
	S: <idnTable:to>0039</idnTable:to>
	S: </idnTable:codeRange>
	S: </idnTable:table>	S: </idnTable:table>
	S: </idnTable:infData>	S: </idnTable:infData>
	S: </resData>	S: </resData>
	S: <trID>	S: <trID>
	S: <clTRID>ABC-12345</clTRID>	S: <clTRID>ABC-12345</clTRID>
	S: <svTRID>54321-XYZ</svTRID>	S: <svTRID>54321-XYZ</svTRID>
	S: </trID>	S: </trID>
	S: </response>	S: </response>
	S:</epp>	S:</epp>


	skipping to change at page 18, line 25 ¶	skipping to change at page 18, line 13 ¶
	Form contains the following child elements:	Form contains the following child elements:

	<idnTable:list> Empty element used as a marker to the server of the	<idnTable:list> Empty element used as a marker to the server of the
	List Info Form to retrieve the list of IDN Tables.	List Info Form to retrieve the list of IDN Tables.

	Example List Info Form <info> command:	Example List Info Form <info> command:

	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>	C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">	C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>	C: <command>

	C: <check>	C: <info>
	C: <idnTable:info	C: <idnTable:info
	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">	C: xmlns:idnTable="urn:ietf:params:xml:ns:idnTable-1.0">
	C: <idnTable:list/>	C: <idnTable:list/>
	C: </idnTable:info>	C: </idnTable:info>

	C: </check>	C: </info>
	C: <clTRID>ABC-12345</clTRID>	C: <clTRID>ABC-12345</clTRID>
	C: </command>	C: </command>
	C:</epp>	C:</epp>

	When an <info> command has been processed successfully, the EPP	When an <info> command has been processed successfully, the EPP
	<resData> element MUST contain a child <idnTable:infData> element	<resData> element MUST contain a child <idnTable:infData> element
	that identifies the idnTable namespace. The <idnTable:infData>	that identifies the idnTable namespace. The <idnTable:infData>
	element in the List Info Form contains the <idnTable:list> element	element in the List Info Form contains the <idnTable:list> element
	that contains the following child elements:	that contains the following child elements:


	skipping to change at page 24, line 19 ¶	skipping to change at page 24, line 19 ¶
	<!--	<!--
	Table types	Table types
	-->	-->
	<simpleType name="tableTypeEnumType">	<simpleType name="tableTypeEnumType">
	<restriction base="token">	<restriction base="token">
	<enumeration value="language"/>	<enumeration value="language"/>
	<enumeration value="script"/>	<enumeration value="script"/>
	</restriction>	</restriction>
	</simpleType>	</simpleType>


	<!--
	Table IDN code point.
	-->
	<complexType name="codePointType">
	<sequence>
	<element name="point" type="token"/>
	<element name="comment" type="idnTable:descriptionType"
	minOccurs="0"/>
	</sequence>
	</complexType>

	<!--
	Table IDN code point range.
	-->
	<complexType name="codeRangeType">
	<sequence>
	<element name="from" type="token"/>
	<element name="to" type="token"/>
	<element name="comment" type="idnTable:descriptionType"
	minOccurs="0"/>
	</sequence>
	</complexType>

	<complexType name="descriptionType">	<complexType name="descriptionType">
	<simpleContent>	<simpleContent>
	<extension base="token">	<extension base="token">
	<attribute name="lang" type="language"/>	<attribute name="lang" type="language"/>
	</extension>	</extension>
	</simpleContent>	</simpleContent>
	</complexType>	</complexType>

	<!--	<!--
	Table info response information	Table info response information

	skipping to change at page 25, line 15 ¶	skipping to change at page 24, line 40 ¶
	<complexType name="infTableType">	<complexType name="infTableType">
	<sequence>	<sequence>
	<element name="name" type="eppcom:minTokenType"/>	<element name="name" type="eppcom:minTokenType"/>
	<element name="type" type="idnTable:tableTypeEnumType"/>	<element name="type" type="idnTable:tableTypeEnumType"/>
	<element name="description" type="idnTable:descriptionType"/>	<element name="description" type="idnTable:descriptionType"/>
	<element name="upDate" type="dateTime"/>	<element name="upDate" type="dateTime"/>
	<element name="version" type="token" minOccurs="0"/>	<element name="version" type="token" minOccurs="0"/>
	<element name="effectiveDate" type="date" minOccurs="0"/>	<element name="effectiveDate" type="date" minOccurs="0"/>
	<element name="variantGen" type="boolean" minOccurs="0"/>	<element name="variantGen" type="boolean" minOccurs="0"/>
	<element name="url" type="anyURI" minOccurs="0"/>	<element name="url" type="anyURI" minOccurs="0"/>

	<choice minOccurs="0" maxOccurs="unbounded">
	<element name="codePoint" type="idnTable:codePointType"/>
	<element name="codeRange" type="idnTable:codeRangeType"/>
	</choice>
	</sequence>	</sequence>
	</complexType>	</complexType>

	<!--	<!--
	Domain info response information	Domain info response information
	-->	-->
	<complexType name="infDomainType">	<complexType name="infDomainType">
	<sequence>	<sequence>
	<element name="name" type="idnTable:domainNameType"/>	<element name="name" type="idnTable:domainNameType"/>
	<choice minOccurs="0">	<choice minOccurs="0">

	skipping to change at page 27, line 28 ¶	skipping to change at page 27, line 8 ¶
	The mapping extensions described in this document do not provide any	The mapping extensions described in this document do not provide any
	security services beyond those described by EPP [RFC5730] and	security services beyond those described by EPP [RFC5730] and
	protocol layers used by EPP. The security considerations described	protocol layers used by EPP. The security considerations described
	in these other specifications apply to this specification as well.	in these other specifications apply to this specification as well.

	7. Normative References	7. Normative References

	[I-D.ietf-eppext-idnmap]	[I-D.ietf-eppext-idnmap]
	Obispo, F., "Internationalized Domain Name Mapping	Obispo, F., "Internationalized Domain Name Mapping
	Extension for the Extensible Provisioning Protocol (EPP)",	Extension for the Extensible Provisioning Protocol (EPP)",

	draft-ietf-eppext-idnmap-01 (work in progress), January	draft-ietf-eppext-idnmap-02 (work in progress), January
	2014.	2015.

	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.	Requirement Levels", BCP 14, RFC 2119, March 1997.

	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	January 2004.	January 2004.

	[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",	[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
	STD 69, RFC 5730, August 2009.	STD 69, RFC 5730, August 2009.


	skipping to change at page 28, line 12 ¶	skipping to change at page 27, line 37 ¶
	[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible	[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
	Provisioning Protocol", RFC 7451, February 2015.	Provisioning Protocol", RFC 7451, February 2015.

	Appendix A. Change History	Appendix A. Change History

	A.1. Change from 00 to 01	A.1. Change from 00 to 01

	1. Amended XML Namespace section of IANA Considerations, added EPP	1. Amended XML Namespace section of IANA Considerations, added EPP
	Extension Registry section.	Extension Registry section.


	Authors' Addresses	A.2. Change from 01 to 02


		1. Removed support for returning the idnTable:codePoint and
		idnTable:codeRange elements in the table info response based on
		the feedback at the Registration Operations Workshop (ROW), held
		on March 22, 2015, prior to IETF-92.
		2. Fixed info command samples that referenced the <check> element
		instead of the <info> element.

		Authors' Addresses
	James Gould	James Gould
	VeriSign, Inc.	VeriSign, Inc.
	12061 Bluemont Way	12061 Bluemont Way
	Reston, VA 20190	Reston, VA 20190
	US	US

	Email: jgould@verisign.com	Email: jgould@verisign.com
	URI: http://www.verisigninc.com	URI: http://www.verisigninc.com

	Francisco Obispo	Francisco Obispo

End of changes. 28 change blocks.
	106 lines changed or deleted	40 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/