idnits 2.17.1 draft-gould-idn-table-05.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 (October 16, 2017) is 2384 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') ** Downref: Normative reference to an Informational RFC: RFC 7451 Summary: 2 errors (**), 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: April 19, 2018 L. Munoz 6 Uniregistry Corp. 7 October 16, 2017 9 Extensible Provisioning Protocol (EPP) Internationalized Domain Name 10 (IDN) Table Mapping 11 draft-gould-idn-table-05 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 April 19, 2018. 45 Copyright Notice 47 Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . 7 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. Normative References . . . . . . . . . . . . . . . . . . . . 26 90 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 27 91 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 27 92 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 27 93 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 28 94 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 28 95 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 28 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 98 1. Introduction 100 This document describes an extension mapping for version 1.0 of the 101 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 102 provides Internationalized Domain Name (IDN) Table information for 103 the registration of IDNs, using the EPP domain name mapping 104 [RFC5731], and optionally with the IDN mapping extension 105 [I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of 106 characters (code points) that can be used in a domain name. Code 107 points may overlap across IDN Tables and the IDN Tables supported by 108 the servers are up to server policy. This mapping provides the 109 information clients need to register IDNs across a variety of servers 110 with differing IDN policies. The IDN Table Mapping can be used for 111 the following: 113 "Validate IDN Domain Name" Validate that an IDN meets the server IDN 114 policy. The validation can be done prior to submitting a domain 115 create, per [RFC5731]. 116 "Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since 117 IDN Table code points may overlap, the mapping can be used to 118 identify the matching set of IDN Tables (language or script), 119 along with the IDN Table meta-data. 120 "Cache IDN Table Code Points" Clients can query for the complete 121 list of IDN Tables and can get the IDN Table meta-data, based on 122 server policy, to support pre-validation in the client. 123 "Get the IDN Table Identifier to Pass with a Domain Create" Each IDN 124 Table includes a server unique IDN Table Identifier that may be 125 used as the value of the element in the IDN mapping 126 extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the 127 IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the 128 domain name. 130 1.1. Conventions Used in This Document 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 134 document are to be interpreted as described in RFC 2119 [RFC2119]. 136 XML is case sensitive. Unless stated otherwise, XML specifications 137 and examples provided in this document MUST be interpreted in the 138 character case presented in order to develop a conforming 139 implementation. 141 In examples, "C:" represents lines sent by a protocol client and "S:" 142 represents lines returned by a protocol server. Indentation and 143 white space in examples are provided only to illustrate element 144 relationships and are not a REQUIRED feature of this protocol. 146 "idnTable-1.0" is used as an abbreviation for 147 "urn:ietf:params:xml:ns:idnTable-1.0". The XML namespace prefix 148 "idnTable" is used, but implementations MUST NOT depend on it and 149 instead employ a proper namespace-aware XML parser and serializer to 150 interpret and output the XML documents. 152 2. Object Attributes 154 An EPP IDN Table object has attributes and associated values that can 155 help in the registration of IDNs. This section describes each type 156 in detail. The formal syntax for the attribute values described here 157 can be found in the "Formal Syntax" section of this document and in 158 the appropriate normative references. 160 2.1. IDN Table Identifier 162 The IDN Table Identifier is a server-defined unique value for an IDN 163 Table object. It is represented using an element or 164 an element. The IDN Table Identifier is used in the 165 and commands and responses. The IDN Table Identifier 166 MAY also be used as the value for the IDN mapping extension 167 [I-D.ietf-eppext-idnmap] element with a domain create of 168 an IDN object. 170 2.2. Domain Name 172 A Domain Name, as represented by an element, is 173 used to enable validating the code points against the server IDN 174 Tables and IDN policies and for retrieving IDN Table information 175 associated with the domain name. The Domain Name MUST be represented 176 as either a U-label or A-label as defined in [RFC5890]. 178 An OPTIONAL attribute "form" MAY be used to specify the 179 representation. When present, the "form" attribute MUST be set to 180 either "aLabel" for A-label or "uLabel" for U-label, depending on the 181 chosen representation for the domain name. The default "form" 182 attribute is "aLabel" for A-label. 184 3. EPP Command Mapping 186 A detailed description of the EPP syntax and semantics can be found 187 in the EPP core protocol specification [RFC5730]. 189 3.1. EPP Query Commands 191 EPP provides three commands to retrieve object information: 192 to determine if an object is known to the server, to retrieve 193 detailed information associated with an object, and to 194 retrieve object transfer status information. 196 3.1.1. EPP Command 198 There are two forms of the EPP command: the Domain Check Form 199 (Section 3.1.1.1) and the Table Check Form (Section 3.1.1.2). 201 3.1.1.1. Domain Check Form 203 The Domain Check Form is used to check the validity of the domain 204 name against the server IDN Tables and IDN policies, return whether 205 the IDN mapping extension [I-D.ietf-eppext-idnmap] is needed with a 206 domain command, and provide the matching list of IDN 207 Table Identifiers. This mapping is not intended to determine the 208 availability of the domain name. 210 In addition to the standard EPP command elements, the command 211 MUST contain an element that identifies the 212 idnTable namespace. The element in the Domain Check 213 Form contains the following child elements: 215 One or more elements that 216 contain the fully qualified names of the domain objects, as 217 defined in Section 2.2, to validate. 219 Example Domain Check Form command with three IDNs: 221 C: 222 C: 223 C: 224 C: 225 C: 227 C: idn1.example 229 C: idn2.example 231 C: idn3.example 232 C: 233 C: 234 C: ABC-12345 235 C: 236 C: 237 When a command has been processed successfully, the EPP 238 element MUST contain a child element 239 that identifies the idnTable namespace. The 240 element in the Domain Check Form contain one or more 241 elements that contain the following child elements: 243 The fully qualified name of the domain object, as 244 defined in Section 2.2. The element MUST contain a "valid" 245 attribute whose value indicates whether the domain name is valid 246 according to the server IDN Tables and IDN policies. A value of 247 "1" or "true" means that the domain name is valid according to 248 the server IDN Tables and policies. A value of "0" or "false" 249 means that the domain name is not valid according to the server 250 IDN Tables and policies. The element MAY contain an "idnmap" 251 attribute value that indicates whether the server requires the 252 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 253 domain create of the domain name. A value of "1" or "true" means 254 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 255 required using one of the values. A value of 256 "0" or "false" means that the IDN mapping extension 257 [I-D.ietf-eppext-idnmap] is not required. 258 OPTIONAL reason that the domain name is not valid. 259 If present, this element contains server-specific text to help 260 explain why the domain name is not valid. This text MUST be 261 represented in the response language previously negotiated with 262 the client; an OPTIONAL "lang" attribute MAY be present to 263 identify the language if the negotiated value is something other 264 than the default value of "en" (English). 265 Zero or more OPTIONAL elements 266 that contain the server defined IDN Table Identifier, as defined 267 in Section 2.1, that matches the code points of the 268 element. The MAY be used as the 269 value of the element in the IDN mapping extension 270 [I-D.ietf-eppext-idnmap] for creating the IDN object or MAY be 271 used as the value of the element of the 272 Table Info Form (Section 3.1.2.2) command, as described in 273 Section 3.1.2, to retrieve more information about the IDN Table. 275 Example Domain Check Form response with three IDNs: 277 S: 278 S: 279 S: 280 S: 281 S: Command completed successfully 282 S: 283 S: 284 S: 286 S: 287 S: 288 S: idn1.example 289 S: CHI 290 S: 291 S: 292 S: 293 S: idn2.example 294 S: CHI 295 S: JPN 296 S: 297 S: 298 S: 299 S: idn3.example 300 S: Commingled scripts 301 S: 302 S: 303 S: 304 S: 305 S: 306 S: ABC-12345 307 S: 54321-XYZ 308 S: 309 S: 310 S: 312 3.1.1.2. Table Check Form 314 The Table Check Form is used to check the existence of an IDN 315 Table using the IDN Table Identifier represented by the 316 element. 318 In addition to the standard EPP command elements, the command 319 MUST contain an element that identifies the 320 idnTable namespace. The element in the Table Check 321 Form contains the following child elements: 323 One or more elements that contain 324 the IDN Table Identifier, as defined in Section 2.1, to check for 325 existence. 327 Example Table Check Form command with three IDN 328 Table Identifiers: 330 C: 331 C: 332 C: 333 C: 334 C: 336 C: CHI 337 C: JPN 338 C: INVALID 339 C: 340 C: 341 C: ABC-12345 342 C: 343 C: 345 When a command has been processed successfully, the EPP 346 element MUST contain a child element 347 that identifies the idnTable namespace. The 348 element in the Table Check Form contains the following child 349 elements: 351 One or more elements that contain 352 the IDN Table Identifier, as defined in Section 2.1. The element 353 MUST contain an "exists" attribute whose value indicates the 354 existence of the IDN Table Identifier. A value of "1" or "true" 355 means that the IDN Table Identifier exists. A value of "0" or 356 "false" means that the IDN Table Identifier does not exist. 358 Example Table Check Form response with three IDN 359 Table Identifiers: 361 S: 362 S: 363 S: 364 S: 365 S: Command completed successfully 366 S: 367 S: 368 S: 370 S: CHI 371 S: 372 S: JPN 373 S: 374 S: INVALID 375 S: 376 S: 377 S: 378 S: 379 S: ABC-12345 380 S: 54321-XYZ 381 S: 382 S: 383 S: 385 3.1.2. EPP Command 387 There are three forms of the EPP command: the Domain Info Form 388 (Section 3.1.2.1), the Table Info Form (Section 3.1.2.2), and the 389 List Info Form (Section 3.1.2.3). 391 3.1.2.1. Domain Info Form 393 The Domain Info Form is used to validate the domain name code points 394 against the IDN Tables and IDN policies, and to return the matching 395 IDN Table meta-data. The domain name, as defined in Section 2.2 can 396 be provided as either a U-label or A-label. 398 In addition to the standard EPP command elements, the command 399 MUST contain an element that identifies the 400 idnTable namespace. The element in the Domain Info 401 Form contains the following child elements: 403 The domain name, as defined in Section 2.2, to 404 validate against the IDN Tables and IDN policies, and to retrieve 405 the matching IDN Table meta-data. 407 Example Domain Info Form command using a U-label Domain Name: 409 C: 410 C: 411 C: 412 C: 413 C: 415 C: idn1.example 416 C: 417 C: 418 C: ABC-12345 419 C: 420 C: 422 Example Domain Info Form command using an A-label Domain Name: 424 C: 425 C: 426 C: 427 C: 428 C: 430 C: xn--idn1.example 431 C: 432 C: 433 C: ABC-12345 434 C: 435 C: 437 When an command has been processed successfully, the EPP 438 element MUST contain a child element 439 that identifies the idnTable namespace. The 440 element in the Domain Info Form contains the 441 element that contains the following child elements: 443 The fully qualified name of the domain object, as 444 defined in Section 2.2. The element MUST contain a "valid" 445 attribute whose value indicates whether the domain name is valid 446 according to the server IDN Tables and IDN policies. A value of 447 "1" or "true" means that the domain name is valid according to 448 the server IDN Tables and policies. A value of "0" or "false" 449 means that the domain name is not valid according to the server 450 IDN Tables and policies. The element MAY contain an "idnmap" 451 attribute value that indicates whether the server requires the 452 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 453 domain create of the domain name. A value of "1" or "true" means 454 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 455 required using one of the 456 values. A value of "0" or "false" means that the IDN mapping 457 extension [I-D.ietf-eppext-idnmap] is not required. 458 or OPTIONAL U-label or A-label 459 form of the domain name value of the element in 460 the opposite form, as defined in Section 2.2. 461 Zero or more OPTIONAL elements 462 that provide the IDN Table meta-data information. The 463 element contains the following child elements: 465 Server defined IDN Table Identifier, as defined 466 in Section 2.1. 467 The type of the IDN Table with the possible 468 values of "language", to reflect a Language IDN Table, and 469 "script", to reflect a Script IDN Table. 470 Server defined description of the IDN 471 Table. This text MUST be represented in the response 472 language previously negotiated with the client; an OPTIONAL 473 "lang" attribute MAY be present to identify the language if 474 the negotiated value is something other than the default 475 value of "en" (English). 476 OPTIONAL boolean flag indicating that 477 domains created using the IDN Table will have IDN variants 478 generated. The management of variants is up to server 479 policy. 481 Example Domain Info Form response for a U-label Domain Name: 483 S: 484 S: 485 S: 486 S: 487 S: Command completed successfully 488 S: 489 S: 490 S: 492 S: 493 S: idn1.example 494 S: 495 S: xn--idn1.example 496 S: 497 S: THAI 498 S: script 499 S: Thai 500 S: 501 S: false 502 S: 503 S: 504 S: 505 S: 506 S: 507 S: ABC-12345 508 S: 54321-XYZ 509 S: 510 S: 511 S: 512 Example Domain Info Form response for an A-label Domain Name: 514 S: 515 S: 516 S: 517 S: 518 S: Command completed successfully 519 S: 520 S: 521 S: 523 S: 524 S: 525 S: xn--idn1.example 526 S: 527 S: idn1.example 528 S: 529 S: CHI 530 S: language 531 S: Chinese (CHI) 532 S: 533 S: true 534 S: 535 S: 536 S: JPN 537 S: language 538 S: Japanese (JPN) 539 S: 540 S: false 541 S: 542 S: 543 S: 544 S: 545 S: 546 S: ABC-12345 547 S: 54321-XYZ 548 S: 549 S: 550 S: 552 3.1.2.2. Table Info Form 554 The Table Info Form is used to retrieve information associated with 555 an IDN Table object. The information provided meta-data about the 556 IDN Table object. 558 In addition to the standard EPP command elements, the command 559 MUST contain an element that identifies the 560 idnTable namespace. The element in the Table Info 561 Form contains the following child elements: 563 Contains the IDN Table Identifier, as defined in 564 Section 2.1, of the IDN Table object to be queried. 566 Example Table Info Form command for the "CHI" IDN 567 Table Identifier, which represents a Language IDN Table: 569 C: 570 C: 571 C: 572 C: 573 C: 575 C: CHI 576 C: 577 C: 578 C: ABC-12345 579 C: 580 C: 582 Example Table Info Form command for the "THAI" IDN 583 Table Identifier, which represents a Script IDN Table: 585 C: 586 C: 587 C: 588 C: 589 C: 591 C: THAI 592 C: 593 C: 594 C: ABC-12345 595 C: 596 C: 598 When an command has been processed successfully, the EPP 599 element MUST contain a child element 600 that identifies the idnTable namespace. The 601 element in the Table Info Form contains the element 602 that contains the following child elements: 604 Server defined IDN Table Identifier, as defined in 605 Section 2.1. 607 The type of the IDN Table with the possible values 608 of "language", to reflect a Language IDN Table, and "script", to 609 reflect a Script IDN Table. 610 Server defined description of the IDN Table. 611 This text MUST be represented in the response language previously 612 negotiated with the client; an OPTIONAL "lang" attribute MAY be 613 present to identify the language if the negotiated value is 614 something other than the default value of "en" (English). 615 Contains the date and time that the IDN Table was 616 created or last updated. 617 OPTIONAL server defined version number of the IDN 618 Table. 619 OPTIONAL effective date for the IDN Table. 620 OPTIONAL boolean flag indicating that domains 621 created using the IDN Table will have IDN variants generated. 622 The management of variants is up to server policy. 623 OPTIONAL URL for downloading the IDN Table with the 624 applicable set of code points and rules. 626 Example Table Info Form response for the "CHI" IDN 627 Table Identifier, which represents a Language IDN Table: 629 S: 630 S: 631 S: 632 S: 633 S: Command completed successfully 634 S: 635 S: 636 S: 638 S: 639 S: CHI 640 S: language 641 S: Chinese (CHI) 642 S: 643 S: 2015-02-04T09:30:00.0Z 644 S: 645 S: 1.0 646 S: 2014-11-24 647 S: 648 S: true 649 S: 650 S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt 651 S: 652 S: 653 S: 654 S: 655 S: 656 S: ABC-12345 657 S: 54321-XYZ 658 S: 659 S: 660 S: 661 Example Table Info Form response for the "THAI" IDN 662 Table Identifier, which represents a Script IDN Table: 664 S: 665 S: 666 S: 667 S: 668 S: Command completed successfully 669 S: 670 S: 671 S: 673 S: 674 S: THAI 675 S: script 676 S: Thai 677 S: 2014-08-16T09:20:00.0Z 678 S: 679 S: 1.0 680 S: 2014-11-24 681 S: 682 S: false 683 S: 684 S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt 685 S: 686 S: 687 S: 688 S: 689 S: 690 S: ABC-12345 691 S: 54321-XYZ 692 S: 693 S: 694 S: 696 3.1.2.3. List Info Form 698 The List Info Form is used to retrieve the list of IDN Tables 699 supported by the server. The list of IDN Table Identifiers MAY be 700 used to query for the IDN Table information using the Table Info Form 701 (Section 3.1.2.2). 703 In addition to the standard EPP command elements, the command 704 MUST contain an element that identifies the 705 idnTable namespace. The element in the List Info 706 Form contains the following child elements: 708 Empty element used as a marker to the server of the 709 List Info Form to retrieve the list of IDN Tables. 711 Example List Info Form command: 713 C: 714 C: 715 C: 716 C: 717 C: 719 C: 720 C: 721 C: 722 C: ABC-12345 723 C: 724 C: 726 When an command has been processed successfully, the EPP 727 element MUST contain a child element 728 that identifies the idnTable namespace. The 729 element in the List Info Form contains the element 730 that contains the following child elements: 732 Zero or more elements that contain 733 the following child elements: 735 Server defined IDN Table Identifier, as defined 736 in Section 2.1, that is supported by the server. The 737 element value MAY be used as the value of 738 the element value in the Table Info Form 739 (Section 3.1.2.2) command to retrieve the information 740 on the IDN Table. 741 Contains the date and time that the IDN 742 Table was created or last updated. This element can be used 743 to determine whether a client-side cache needs to be 744 refreshed for the IDN Table using the Table Info Form 745 (Section 3.1.2.2). 747 Example List Info Form response that contains three IDN 748 Table Identifiers: 750 S: 751 S: 752 S: 753 S: 754 S: Command completed successfully 755 S: 756 S: 757 S: 759 S: 760 S: 761 S: CHI 762 S: 2015-02-04T09:30:00.0Z 763 S: 764 S: 765 S: 766 S: JPN 767 S: 2015-01-01T09:40:00.0Z 768 S: 769 S: 770 S: 771 S: THAI 772 S: 2014-08-16T09:20:00.0Z 773 S: 774 S: 775 S: 776 S: 777 S: 778 S: 779 S: ABC-12345 780 S: 54321-XYZ 781 S: 782 S: 783 S: 785 3.1.3. EPP Command 787 Transfer semantics do not apply to IDN table objects, so there is no 788 mapping defined for the EPP command. 790 3.2. EPP Transform Commands 792 EPP provides five commands to transform objects: to create 793 an instance of an object, to delete an instance of an 794 object, to extend the validity period of an object, 795 to manage object sponsorship changes, and to 796 change information associated with an object. 798 3.2.1. EPP Command 800 Create semantics do not apply to IDN table objects, so there is no 801 mapping defined for the EPP command. 803 3.2.2. EPP Command 805 Delete semantics do not apply to IDN table objects, so there is no 806 mapping defined for the EPP command. 808 3.2.3. EPP Command 810 Renewal semantics do not apply to IDN table objects, so there is no 811 mapping defined for the EPP command. 813 3.2.4. EPP Command 815 Transfer semantics do not apply to IDN table objects, so there is no 816 mapping defined for the EPP command. 818 3.2.5. EPP Command 820 Update semantics do not apply to IDN table objects, so there is no 821 mapping defined for the EPP command. 823 4. Formal Syntax 825 One schema is presented here that is the EPP IDN Table Mapping 826 schema. 828 The formal syntax presented here is a complete schema representation 829 of the object mapping suitable for automated validation of EPP XML 830 instances. The BEGIN and END tags are not part of the schema; they 831 are used to note the beginning and ending of the schema for URI 832 registration purposes. 834 4.1. IDN Table Mapping Schema 836 BEGIN 837 838 844 845 846 Extensible Provisioning Protocol v1.0 847 IDN Table Mapping. 848 849 851 852 855 858 859 861 864 865 866 867 868 869 871 874 875 876 877 879 880 881 882 885 886 887 888 890 892 893 894 896 899 900 901 902 903 904 905 906 907 909 912 913 915 918 919 920 921 923 925 926 927 928 931 932 933 934 935 936 937 939 942 943 944 945 946 947 948 949 951 954 955 956 957 958 959 961 962 963 965 968 969 970 971 972 973 975 976 977 979 982 983 984 985 986 987 989 990 991 992 993 994 995 997 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1013 1016 1017 1018 1019 1020 1021 1023 1024 1026 1027 1029 1032 1033 1034 1035 1036 1037 1038 1039 1041 1044 1045 1046 1048 1049 1051 1054 1055 1056 1057 1058 1059 1061 1062 1063 END 1065 5. IANA Considerations 1066 5.1. XML Namespace 1068 This document uses URNs to describe XML namespaces and XML schemas 1069 conforming to a registry mechanism described in [RFC3688]. The 1070 following URI assignment is requested of IANA: 1072 URI: urn:ietf:params:xml:ns:idnTable-1.0 1074 Registrant Contact: See the "Author's Address" section of this 1075 document. 1077 XML: See the "Formal Syntax" section of this document. 1079 5.2. EPP Extension Registry 1081 The EPP extension described in this document should be registered by 1082 the IANA in the EPP Extension Registry described in [RFC7451]. The 1083 details of the registration are as follows: 1085 Name of Extension: "Extensible Provisioning Protocol (EPP) 1086 Internationalized Domain Name (IDN) Table Mapping" 1088 Document status: Standards Track 1090 Reference: (insert reference to RFC version of this document) 1092 Registrant Name and Email Address: IESG, 1094 TLDs: Any 1096 IPR Disclosure: None 1098 Status: Active 1100 Notes: None 1102 6. Security Considerations 1104 The mapping extensions described in this document do not provide any 1105 security services beyond those described by EPP [RFC5730] and 1106 protocol layers used by EPP. The security considerations described 1107 in these other specifications apply to this specification as well. 1109 7. Normative References 1111 [I-D.ietf-eppext-idnmap] 1112 Obispo, F., "Internationalized Domain Name Mapping 1113 Extension for the Extensible Provisioning Protocol (EPP)", 1114 draft-ietf-eppext-idnmap-02 (work in progress), January 1115 2015. 1117 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1118 Requirement Levels", BCP 14, RFC 2119, 1119 DOI 10.17487/RFC2119, March 1997, . 1122 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1123 DOI 10.17487/RFC3688, January 2004, . 1126 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1127 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1128 . 1130 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1131 Domain Name Mapping", STD 69, RFC 5731, 1132 DOI 10.17487/RFC5731, August 2009, . 1135 [RFC5890] Klensin, J., "Internationalized Domain Names for 1136 Applications (IDNA): Definitions and Document Framework", 1137 RFC 5890, DOI 10.17487/RFC5890, August 2010, 1138 . 1140 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1141 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1142 February 2015, . 1144 Appendix A. Change History 1146 A.1. Change from 00 to 01 1148 1. Amended XML Namespace section of IANA Considerations, added EPP 1149 Extension Registry section. 1151 A.2. Change from 01 to 02 1153 1. Removed support for returning the idnTable:codePoint and 1154 idnTable:codeRange elements in the table info response based on 1155 the feedback at the Registration Operations Workshop (ROW), held 1156 on March 22, 2015, prior to IETF-92. 1157 2. Fixed info command samples that referenced the element 1158 instead of the element. 1160 A.3. Change from 02 to 03 1162 1. Ping update. 1164 A.4. Change from 03 to 04 1166 1. Ping update. 1168 A.5. Change from 04 to 05 1170 1. Ping update. 1172 Authors' Addresses 1174 James Gould 1175 VeriSign, Inc. 1176 12061 Bluemont Way 1177 Reston, VA 20190 1178 US 1180 Email: jgould@verisign.com 1181 URI: http://www.verisigninc.com 1183 Francisco Obispo 1184 Uniregistry Corp. 1185 3-110 Governors Square 1186 Grand Cayman, Grand Cayman KY1-1108 1187 KY 1189 Email: fobispo@uniregistry.com 1190 URI: http://www.uniregistry.com/ 1192 Luis Enrique Munoz 1193 Uniregistry Corp. 1194 3-110 Governors Square 1195 Grand Cayman, Grand Cayman KY1-1108 1196 KY 1198 Email: fobispo@uniregistry.com 1199 URI: http://www.uniregistry.com/