idnits 2.17.1 draft-gould-idn-table-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 16, 2018) is 2202 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Experimental draft: draft-ietf-eppext-idnmap (ref. 'I-D.ietf-eppext-idnmap') Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Standards Track F. Obispo 5 Expires: October 18, 2018 L. Munoz 6 Uniregistry Corp. 7 April 16, 2018 9 Extensible Provisioning Protocol (EPP) Internationalized Domain Name 10 (IDN) Table Mapping 11 draft-gould-idn-table-06 13 Abstract 15 This document describes an Extensible Provisioning Protocol (EPP) 16 mapping for getting Internationalized Domain Name (IDN) 17 Table information for the registration of IDNs, using the EPP domain 18 name mapping, and optionally with the IDN mapping extension. An IDN 19 Table defines the valid set of characters (code points) that can be 20 used in a domain name. Code points may overlap across IDN Tables and 21 the IDN Tables supported by the servers are up to server policy. 23 The IDN Table information can be used to validate an IDN prior to 24 registration, can be cached by the client for pre-validation, can be 25 used to select the best IDN Table for the IDN, and can be used to 26 know if and what IDN Table Identifier to pass in a domain create. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on October 18, 2018. 45 Copyright Notice 47 Copyright (c) 2018 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 64 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 65 2.1. IDN Table Identifier . . . . . . . . . . . . . . . . . . 4 66 2.2. Domain Name . . . . . . . . . . . . . . . . . . . . . . . 4 67 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 68 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5 69 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 5 70 3.1.1.1. Domain Check Form . . . . . . . . . . . . . . . . 5 71 3.1.1.2. Table Check Form . . . . . . . . . . . . . . . . 8 72 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 9 73 3.1.2.1. Domain Info Form . . . . . . . . . . . . . . . . 9 74 3.1.2.2. Table Info Form . . . . . . . . . . . . . . . . . 13 75 3.1.2.3. List Info Form . . . . . . . . . . . . . . . . . 17 76 3.1.3. EPP Command . . . . . . . . . . . . . . . 19 77 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 20 78 3.2.1. EPP Command . . . . . . . . . . . . . . . . 20 79 3.2.2. EPP Command . . . . . . . . . . . . . . . . 20 80 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 20 81 3.2.4. EPP Command . . . . . . . . . . . . . . . 20 82 3.2.5. EPP Command . . . . . . . . . . . . . . . . 20 83 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20 84 4.1. IDN Table Mapping Schema . . . . . . . . . . . . . . . . 21 85 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 86 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 26 87 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 26 88 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 89 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 90 7.1. Normative References . . . . . . . . . . . . . . . . . . 27 91 7.2. Informative References . . . . . . . . . . . . . . . . . 27 92 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 27 93 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 27 94 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 28 95 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 28 96 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 28 97 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 28 98 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 28 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 101 1. Introduction 103 This document describes an extension mapping for version 1.0 of the 104 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 105 provides Internationalized Domain Name (IDN) Table information for 106 the registration of IDNs, using the EPP domain name mapping 107 [RFC5731], and optionally with the IDN mapping extension 108 [I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of 109 characters (code points) that can be used in a domain name. Code 110 points may overlap across IDN Tables and the IDN Tables supported by 111 the servers are up to server policy. This mapping provides the 112 information clients need to register IDNs across a variety of servers 113 with differing IDN policies. The IDN Table Mapping can be used for 114 the following: 116 "Validate IDN Domain Name" Validate that an IDN meets the server IDN 117 policy. The validation can be done prior to submitting a domain 118 create, per [RFC5731]. 119 "Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since 120 IDN Table code points may overlap, the mapping can be used to 121 identify the matching set of IDN Tables (language or script), 122 along with the IDN Table meta-data. 123 "Cache IDN Table Code Points" Clients can query for the complete 124 list of IDN Tables and can get the IDN Table meta-data, based on 125 server policy, to support pre-validation in the client. 126 "Get the IDN Table Identifier to Pass with a Domain Create" Each IDN 127 Table includes a server unique IDN Table Identifier that may be 128 used as the value of the element in the IDN mapping 129 extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the 130 IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the 131 domain name. 133 1.1. Conventions Used in This Document 135 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 136 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 137 document are to be interpreted as described in RFC 2119 [RFC2119]. 139 XML is case sensitive. Unless stated otherwise, XML specifications 140 and examples provided in this document MUST be interpreted in the 141 character case presented in order to develop a conforming 142 implementation. 144 In examples, "C:" represents lines sent by a protocol client and "S:" 145 represents lines returned by a protocol server. Indentation and 146 white space in examples are provided only to illustrate element 147 relationships and are not a REQUIRED feature of this protocol. 149 "idnTable-1.0" is used as an abbreviation for 150 "urn:ietf:params:xml:ns:idnTable-1.0". The XML namespace prefix 151 "idnTable" is used, but implementations MUST NOT depend on it and 152 instead employ a proper namespace-aware XML parser and serializer to 153 interpret and output the XML documents. 155 2. Object Attributes 157 An EPP IDN Table object has attributes and associated values that can 158 help in the registration of IDNs. This section describes each type 159 in detail. The formal syntax for the attribute values described here 160 can be found in the "Formal Syntax" section of this document and in 161 the appropriate normative references. 163 2.1. IDN Table Identifier 165 The IDN Table Identifier is a server-defined unique value for an IDN 166 Table object. It is represented using an element or 167 an element. The IDN Table Identifier is used in the 168 and commands and responses. The IDN Table Identifier 169 MAY also be used as the value for the IDN mapping extension 170 [I-D.ietf-eppext-idnmap] element with a domain create of 171 an IDN object. 173 2.2. Domain Name 175 A Domain Name, as represented by an element, is 176 used to enable validating the code points against the server IDN 177 Tables and IDN policies and for retrieving IDN Table information 178 associated with the domain name. The Domain Name MUST be represented 179 as either a U-label or A-label as defined in [RFC5890]. 181 An OPTIONAL attribute "form" MAY be used to specify the 182 representation. When present, the "form" attribute MUST be set to 183 either "aLabel" for A-label or "uLabel" for U-label, depending on the 184 chosen representation for the domain name. The default "form" 185 attribute is "aLabel" for A-label. 187 3. EPP Command Mapping 189 A detailed description of the EPP syntax and semantics can be found 190 in the EPP core protocol specification [RFC5730]. 192 3.1. EPP Query Commands 194 EPP provides three commands to retrieve object information: 195 to determine if an object is known to the server, to retrieve 196 detailed information associated with an object, and to 197 retrieve object transfer status information. 199 3.1.1. EPP Command 201 There are two forms of the EPP command: the Domain Check Form 202 (Section 3.1.1.1) and the Table Check Form (Section 3.1.1.2). 204 3.1.1.1. Domain Check Form 206 The Domain Check Form is used to check the validity of the domain 207 name against the server IDN Tables and IDN policies, return whether 208 the IDN mapping extension [I-D.ietf-eppext-idnmap] is needed with a 209 domain command, and provide the matching list of IDN 210 Table Identifiers. This mapping is not intended to determine the 211 availability of the domain name. 213 In addition to the standard EPP command elements, the command 214 MUST contain an element that identifies the 215 idnTable namespace. The element in the Domain Check 216 Form contains the following child elements: 218 One or more elements that 219 contain the fully qualified names of the domain objects, as 220 defined in Section 2.2, to validate. 222 Example Domain Check Form command with three IDNs: 224 C: 225 C: 226 C: 227 C: 228 C: 230 C: idn1.example 232 C: idn2.example 234 C: idn3.example 235 C: 236 C: 237 C: ABC-12345 238 C: 239 C: 241 When a command has been processed successfully, the EPP 242 element MUST contain a child element 243 that identifies the idnTable namespace. The 244 element in the Domain Check Form contain one or more 245 elements that contain the following child elements: 247 The fully qualified name of the domain object, as 248 defined in Section 2.2. The element MUST contain a "valid" 249 attribute whose value indicates whether the domain name is valid 250 according to the server IDN Tables and IDN policies. A value of 251 "1" or "true" means that the domain name is valid according to 252 the server IDN Tables and policies. A value of "0" or "false" 253 means that the domain name is not valid according to the server 254 IDN Tables and policies. The element MAY contain an "idnmap" 255 attribute value that indicates whether the server requires the 256 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 257 domain create of the domain name. A value of "1" or "true" means 258 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 259 required using one of the values. A value of 260 "0" or "false" means that the IDN mapping extension 261 [I-D.ietf-eppext-idnmap] is not required. 262 OPTIONAL reason that the domain name is not valid. 263 If present, this element contains server-specific text to help 264 explain why the domain name is not valid. This text MUST be 265 represented in the response language previously negotiated with 266 the client; an OPTIONAL "lang" attribute MAY be present to 267 identify the language if the negotiated value is something other 268 than the default value of "en" (English). 270 Zero or more OPTIONAL elements 271 that contain the server defined IDN Table Identifier, as defined 272 in Section 2.1, that matches the code points of the 273 element. The MAY be used as the 274 value of the element in the IDN mapping extension 275 [I-D.ietf-eppext-idnmap] for creating the IDN object or MAY be 276 used as the value of the element of the 277 Table Info Form (Section 3.1.2.2) command, as described in 278 Section 3.1.2, to retrieve more information about the IDN Table. 280 Example Domain Check Form response with three IDNs: 282 S: 283 S: 284 S: 285 S: 286 S: Command completed successfully 287 S: 288 S: 289 S: 291 S: 292 S: 293 S: idn1.example 294 S: CHI 295 S: 296 S: 297 S: 298 S: idn2.example 299 S: CHI 300 S: JPN 301 S: 302 S: 303 S: 304 S: idn3.example 305 S: Commingled scripts 306 S: 307 S: 308 S: 309 S: 310 S: 311 S: ABC-12345 312 S: 54321-XYZ 313 S: 314 S: 315 S: 317 3.1.1.2. Table Check Form 319 The Table Check Form is used to check the existence of an IDN 320 Table using the IDN Table Identifier represented by the 321 element. 323 In addition to the standard EPP command elements, the command 324 MUST contain an element that identifies the 325 idnTable namespace. The element in the Table Check 326 Form contains the following child elements: 328 One or more elements that contain 329 the IDN Table Identifier, as defined in Section 2.1, to check for 330 existence. 332 Example Table Check Form command with three IDN 333 Table Identifiers: 335 C: 336 C: 337 C: 338 C: 339 C: 341 C: CHI 342 C: JPN 343 C: INVALID 344 C: 345 C: 346 C: ABC-12345 347 C: 348 C: 350 When a command has been processed successfully, the EPP 351 element MUST contain a child element 352 that identifies the idnTable namespace. The 353 element in the Table Check Form contains the following child 354 elements: 356 One or more elements that contain 357 the IDN Table Identifier, as defined in Section 2.1. The element 358 MUST contain an "exists" attribute whose value indicates the 359 existence of the IDN Table Identifier. A value of "1" or "true" 360 means that the IDN Table Identifier exists. A value of "0" or 361 "false" means that the IDN Table Identifier does not exist. 363 Example Table Check Form response with three IDN 364 Table Identifiers: 366 S: 367 S: 368 S: 369 S: 370 S: Command completed successfully 371 S: 372 S: 373 S: 375 S: CHI 376 S: 377 S: JPN 378 S: 379 S: INVALID 380 S: 381 S: 382 S: 383 S: 384 S: ABC-12345 385 S: 54321-XYZ 386 S: 387 S: 388 S: 390 3.1.2. EPP Command 392 There are three forms of the EPP command: the Domain Info Form 393 (Section 3.1.2.1), the Table Info Form (Section 3.1.2.2), and the 394 List Info Form (Section 3.1.2.3). 396 3.1.2.1. Domain Info Form 398 The Domain Info Form is used to validate the domain name code points 399 against the IDN Tables and IDN policies, and to return the matching 400 IDN Table meta-data. The domain name, as defined in Section 2.2 can 401 be provided as either a U-label or A-label. 403 In addition to the standard EPP command elements, the command 404 MUST contain an element that identifies the 405 idnTable namespace. The element in the Domain Info 406 Form contains the following child elements: 408 The domain name, as defined in Section 2.2, to 409 validate against the IDN Tables and IDN policies, and to retrieve 410 the matching IDN Table meta-data. 412 Example Domain Info Form command using a U-label Domain Name: 414 C: 415 C: 416 C: 417 C: 418 C: 420 C: idn1.example 421 C: 422 C: 423 C: ABC-12345 424 C: 425 C: 427 Example Domain Info Form command using an A-label Domain Name: 429 C: 430 C: 431 C: 432 C: 433 C: 435 C: xn--idn1.example 436 C: 437 C: 438 C: ABC-12345 439 C: 440 C: 442 When an command has been processed successfully, the EPP 443 element MUST contain a child element 444 that identifies the idnTable namespace. The 445 element in the Domain Info Form contains the 446 element that contains the following child elements: 448 The fully qualified name of the domain object, as 449 defined in Section 2.2. The element MUST contain a "valid" 450 attribute whose value indicates whether the domain name is valid 451 according to the server IDN Tables and IDN policies. A value of 452 "1" or "true" means that the domain name is valid according to 453 the server IDN Tables and policies. A value of "0" or "false" 454 means that the domain name is not valid according to the server 455 IDN Tables and policies. The element MAY contain an "idnmap" 456 attribute value that indicates whether the server requires the 457 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 458 domain create of the domain name. A value of "1" or "true" means 459 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 460 required using one of the 461 values. A value of "0" or "false" means that the IDN mapping 462 extension [I-D.ietf-eppext-idnmap] is not required. 463 or OPTIONAL U-label or A-label 464 form of the domain name value of the element in 465 the opposite form, as defined in Section 2.2. 466 Zero or more OPTIONAL elements 467 that provide the IDN Table meta-data information. The 468 element contains the following child elements: 470 Server defined IDN Table Identifier, as defined 471 in Section 2.1. 472 The type of the IDN Table with the possible 473 values of "language", to reflect a Language IDN Table, and 474 "script", to reflect a Script IDN Table. 475 Server defined description of the IDN 476 Table. This text MUST be represented in the response 477 language previously negotiated with the client; an OPTIONAL 478 "lang" attribute MAY be present to identify the language if 479 the negotiated value is something other than the default 480 value of "en" (English). 481 OPTIONAL boolean flag indicating that 482 domains created using the IDN Table will have IDN variants 483 generated. The management of variants is up to server 484 policy. 486 Example Domain Info Form response for a U-label Domain Name: 488 S: 489 S: 490 S: 491 S: 492 S: Command completed successfully 493 S: 494 S: 495 S: 497 S: 498 S: idn1.example 499 S: 500 S: xn--idn1.example 501 S: 502 S: THAI 503 S: script 504 S: Thai 505 S: 506 S: false 507 S: 508 S: 509 S: 510 S: 511 S: 512 S: ABC-12345 513 S: 54321-XYZ 514 S: 515 S: 516 S: 517 Example Domain Info Form response for an A-label Domain Name: 519 S: 520 S: 521 S: 522 S: 523 S: Command completed successfully 524 S: 525 S: 526 S: 528 S: 529 S: 530 S: xn--idn1.example 531 S: 532 S: idn1.example 533 S: 534 S: CHI 535 S: language 536 S: Chinese (CHI) 537 S: 538 S: true 539 S: 540 S: 541 S: JPN 542 S: language 543 S: Japanese (JPN) 544 S: 545 S: false 546 S: 547 S: 548 S: 549 S: 550 S: 551 S: ABC-12345 552 S: 54321-XYZ 553 S: 554 S: 555 S: 557 3.1.2.2. Table Info Form 559 The Table Info Form is used to retrieve information associated with 560 an IDN Table object. The information provided meta-data about the 561 IDN Table object. 563 In addition to the standard EPP command elements, the command 564 MUST contain an element that identifies the 565 idnTable namespace. The element in the Table Info 566 Form contains the following child elements: 568 Contains the IDN Table Identifier, as defined in 569 Section 2.1, of the IDN Table object to be queried. 571 Example Table Info Form command for the "CHI" IDN 572 Table Identifier, which represents a Language IDN Table: 574 C: 575 C: 576 C: 577 C: 578 C: 580 C: CHI 581 C: 582 C: 583 C: ABC-12345 584 C: 585 C: 587 Example Table Info Form command for the "THAI" IDN 588 Table Identifier, which represents a Script IDN Table: 590 C: 591 C: 592 C: 593 C: 594 C: 596 C: THAI 597 C: 598 C: 599 C: ABC-12345 600 C: 601 C: 603 When an command has been processed successfully, the EPP 604 element MUST contain a child element 605 that identifies the idnTable namespace. The 606 element in the Table Info Form contains the element 607 that contains the following child elements: 609 Server defined IDN Table Identifier, as defined in 610 Section 2.1. 612 The type of the IDN Table with the possible values 613 of "language", to reflect a Language IDN Table, and "script", to 614 reflect a Script IDN Table. 615 Server defined description of the IDN Table. 616 This text MUST be represented in the response language previously 617 negotiated with the client; an OPTIONAL "lang" attribute MAY be 618 present to identify the language if the negotiated value is 619 something other than the default value of "en" (English). 620 Contains the date and time that the IDN Table was 621 created or last updated. 622 OPTIONAL server defined version number of the IDN 623 Table. 624 OPTIONAL effective date for the IDN Table. 625 OPTIONAL boolean flag indicating that domains 626 created using the IDN Table will have IDN variants generated. 627 The management of variants is up to server policy. 628 OPTIONAL URL for downloading the IDN Table with the 629 applicable set of code points and rules. 631 Example Table Info Form response for the "CHI" IDN 632 Table Identifier, which represents a Language IDN Table: 634 S: 635 S: 636 S: 637 S: 638 S: Command completed successfully 639 S: 640 S: 641 S: 643 S: 644 S: CHI 645 S: language 646 S: Chinese (CHI) 647 S: 648 S: 2015-02-04T09:30:00.0Z 649 S: 650 S: 1.0 651 S: 2014-11-24 652 S: 653 S: true 654 S: 655 S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt 656 S: 657 S: 658 S: 659 S: 660 S: 661 S: ABC-12345 662 S: 54321-XYZ 663 S: 664 S: 665 S: 666 Example Table Info Form response for the "THAI" IDN 667 Table Identifier, which represents a Script IDN Table: 669 S: 670 S: 671 S: 672 S: 673 S: Command completed successfully 674 S: 675 S: 676 S: 678 S: 679 S: THAI 680 S: script 681 S: Thai 682 S: 2014-08-16T09:20:00.0Z 683 S: 684 S: 1.0 685 S: 2014-11-24 686 S: 687 S: false 688 S: 689 S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt 690 S: 691 S: 692 S: 693 S: 694 S: 695 S: ABC-12345 696 S: 54321-XYZ 697 S: 698 S: 699 S: 701 3.1.2.3. List Info Form 703 The List Info Form is used to retrieve the list of IDN Tables 704 supported by the server. The list of IDN Table Identifiers MAY be 705 used to query for the IDN Table information using the Table Info Form 706 (Section 3.1.2.2). 708 In addition to the standard EPP command elements, the command 709 MUST contain an element that identifies the 710 idnTable namespace. The element in the List Info 711 Form contains the following child elements: 713 Empty element used as a marker to the server of the 714 List Info Form to retrieve the list of IDN Tables. 716 Example List Info Form command: 718 C: 719 C: 720 C: 721 C: 722 C: 724 C: 725 C: 726 C: 727 C: ABC-12345 728 C: 729 C: 731 When an command has been processed successfully, the EPP 732 element MUST contain a child element 733 that identifies the idnTable namespace. The 734 element in the List Info Form contains the element 735 that contains the following child elements: 737 Zero or more elements that contain 738 the following child elements: 740 Server defined IDN Table Identifier, as defined 741 in Section 2.1, that is supported by the server. The 742 element value MAY be used as the value of 743 the element value in the Table Info Form 744 (Section 3.1.2.2) command to retrieve the information 745 on the IDN Table. 746 Contains the date and time that the IDN 747 Table was created or last updated. This element can be used 748 to determine whether a client-side cache needs to be 749 refreshed for the IDN Table using the Table Info Form 750 (Section 3.1.2.2). 752 Example List Info Form response that contains three IDN 753 Table Identifiers: 755 S: 756 S: 757 S: 758 S: 759 S: Command completed successfully 760 S: 761 S: 762 S: 764 S: 765 S: 766 S: CHI 767 S: 2015-02-04T09:30:00.0Z 768 S: 769 S: 770 S: 771 S: JPN 772 S: 2015-01-01T09:40:00.0Z 773 S: 774 S: 775 S: 776 S: THAI 777 S: 2014-08-16T09:20:00.0Z 778 S: 779 S: 780 S: 781 S: 782 S: 783 S: 784 S: ABC-12345 785 S: 54321-XYZ 786 S: 787 S: 788 S: 790 3.1.3. EPP Command 792 Transfer semantics do not apply to IDN table objects, so there is no 793 mapping defined for the EPP command. 795 3.2. EPP Transform Commands 797 EPP provides five commands to transform objects: to create 798 an instance of an object, to delete an instance of an 799 object, to extend the validity period of an object, 800 to manage object sponsorship changes, and to 801 change information associated with an object. 803 3.2.1. EPP Command 805 Create semantics do not apply to IDN table objects, so there is no 806 mapping defined for the EPP command. 808 3.2.2. EPP Command 810 Delete semantics do not apply to IDN table objects, so there is no 811 mapping defined for the EPP command. 813 3.2.3. EPP Command 815 Renewal semantics do not apply to IDN table objects, so there is no 816 mapping defined for the EPP command. 818 3.2.4. EPP Command 820 Transfer semantics do not apply to IDN table objects, so there is no 821 mapping defined for the EPP command. 823 3.2.5. EPP Command 825 Update semantics do not apply to IDN table objects, so there is no 826 mapping defined for the EPP command. 828 4. Formal Syntax 830 One schema is presented here that is the EPP IDN Table Mapping 831 schema. 833 The formal syntax presented here is a complete schema representation 834 of the object mapping suitable for automated validation of EPP XML 835 instances. The BEGIN and END tags are not part of the schema; they 836 are used to note the beginning and ending of the schema for URI 837 registration purposes. 839 4.1. IDN Table Mapping Schema 841 BEGIN 842 843 849 850 851 Extensible Provisioning Protocol v1.0 852 IDN Table Mapping. 853 854 856 857 860 863 864 866 869 870 871 872 873 874 876 879 880 881 882 884 885 886 887 890 891 892 893 895 897 898 899 901 904 905 906 907 908 909 910 911 912 914 917 918 920 923 924 925 926 928 930 931 932 933 936 937 938 939 940 941 942 944 947 948 949 950 951 952 953 954 956 959 960 961 962 963 964 966 967 968 970 973 974 975 976 977 978 980 981 982 984 987 988 989 990 991 992 994 995 996 997 998 999 1000 1002 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1018 1021 1022 1023 1024 1025 1026 1028 1029 1031 1032 1034 1037 1038 1039 1040 1041 1042 1043 1044 1046 1049 1050 1051 1053 1054 1056 1059 1060 1061 1062 1063 1064 1066 1067 1068 END 1070 5. IANA Considerations 1071 5.1. XML Namespace 1073 This document uses URNs to describe XML namespaces and XML schemas 1074 conforming to a registry mechanism described in [RFC3688]. The 1075 following URI assignment is requested of IANA: 1077 URI: urn:ietf:params:xml:ns:idnTable-1.0 1079 Registrant Contact: See the "Author's Address" section of this 1080 document. 1082 XML: See the "Formal Syntax" section of this document. 1084 5.2. EPP Extension Registry 1086 The EPP extension described in this document should be registered by 1087 the IANA in the EPP Extension Registry described in [RFC7451]. The 1088 details of the registration are as follows: 1090 Name of Extension: "Extensible Provisioning Protocol (EPP) 1091 Internationalized Domain Name (IDN) Table Mapping" 1093 Document status: Standards Track 1095 Reference: (insert reference to RFC version of this document) 1097 Registrant Name and Email Address: IESG, 1099 TLDs: Any 1101 IPR Disclosure: None 1103 Status: Active 1105 Notes: None 1107 6. Security Considerations 1109 The mapping extensions described in this document do not provide any 1110 security services beyond those described by EPP [RFC5730] and 1111 protocol layers used by EPP. The security considerations described 1112 in these other specifications apply to this specification as well. 1114 7. References 1115 7.1. Normative References 1117 [I-D.ietf-eppext-idnmap] 1118 Obispo, F., "Internationalized Domain Name Mapping 1119 Extension for the Extensible Provisioning Protocol (EPP)", 1120 draft-ietf-eppext-idnmap-02 (work in progress), January 1121 2015. 1123 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1124 Requirement Levels", BCP 14, RFC 2119, 1125 DOI 10.17487/RFC2119, March 1997, . 1128 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1129 DOI 10.17487/RFC3688, January 2004, . 1132 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1133 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1134 . 1136 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1137 Domain Name Mapping", STD 69, RFC 5731, 1138 DOI 10.17487/RFC5731, August 2009, . 1141 [RFC5890] Klensin, J., "Internationalized Domain Names for 1142 Applications (IDNA): Definitions and Document Framework", 1143 RFC 5890, DOI 10.17487/RFC5890, August 2010, 1144 . 1146 7.2. Informative References 1148 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1149 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1150 February 2015, . 1152 Appendix A. Change History 1154 A.1. Change from 00 to 01 1156 1. Amended XML Namespace section of IANA Considerations, added EPP 1157 Extension Registry section. 1159 A.2. Change from 01 to 02 1161 1. Removed support for returning the idnTable:codePoint and 1162 idnTable:codeRange elements in the table info response based on 1163 the feedback at the Registration Operations Workshop (ROW), held 1164 on March 22, 2015, prior to IETF-92. 1165 2. Fixed info command samples that referenced the element 1166 instead of the element. 1168 A.3. Change from 02 to 03 1170 1. Ping update. 1172 A.4. Change from 03 to 04 1174 1. Ping update. 1176 A.5. Change from 04 to 05 1178 1. Ping update. 1180 A.6. Change from 05 to 06 1182 1. Moved RFC 7451 to an informational reference based on a check 1183 done by the Idnits Tool. 1185 Authors' Addresses 1187 James Gould 1188 VeriSign, Inc. 1189 12061 Bluemont Way 1190 Reston, VA 20190 1191 US 1193 Email: jgould@verisign.com 1194 URI: http://www.verisigninc.com 1196 Francisco Obispo 1197 Uniregistry Corp. 1198 3-110 Governors Square 1199 Grand Cayman, Grand Cayman KY1-1108 1200 KY 1202 Email: fobispo@uniregistry.com 1203 URI: http://www.uniregistry.com/ 1204 Luis Enrique Munoz 1205 Uniregistry Corp. 1206 3-110 Governors Square 1207 Grand Cayman, Grand Cayman KY1-1108 1208 KY 1210 Email: fobispo@uniregistry.com 1211 URI: http://www.uniregistry.com/