idnits 2.17.1 draft-gould-idn-table-04.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 17, 2017) is 2563 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: October 19, 2017 L. Munoz 6 Uniregistry Corp. 7 April 17, 2017 9 Extensible Provisioning Protocol (EPP) Internationalized Domain Name 10 (IDN) Table Mapping 11 draft-gould-idn-table-04 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 19, 2017. 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 . . . . . . . . . . . . . . . . . 19 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 . . . . . . . . . . . . . . . . 20 85 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 86 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 25 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 . . . . . . . . . . . . . . . . . . 27 94 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 27 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 97 1. Introduction 99 This document describes an extension mapping for version 1.0 of the 100 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 101 provides Internationalized Domain Name (IDN) Table information for 102 the registration of IDNs, using the EPP domain name mapping 103 [RFC5731], and optionally with the IDN mapping extension 104 [I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of 105 characters (code points) that can be used in a domain name. Code 106 points may overlap across IDN Tables and the IDN Tables supported by 107 the servers are up to server policy. This mapping provides the 108 information clients need to register IDNs across a variety of servers 109 with differing IDN policies. The IDN Table Mapping can be used for 110 the following: 112 "Validate IDN Domain Name" Validate that an IDN meets the server IDN 113 policy. The validation can be done prior to submitting a domain 114 create, per [RFC5731]. 115 "Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since 116 IDN Table code points may overlap, the mapping can be used to 117 identify the matching set of IDN Tables (language or script), 118 along with the IDN Table meta-data. 119 "Cache IDN Table Code Points" Clients can query for the complete 120 list of IDN Tables and can get the IDN Table meta-data, based on 121 server policy, to support pre-validation in the client. 122 "Get the IDN Table Identifier to Pass with a Domain Create" Each IDN 123 Table includes a server unique IDN Table Identifier that may be 124 used as the value of the element in the IDN mapping 125 extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the 126 IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the 127 domain name. 129 1.1. Conventions Used in This Document 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in RFC 2119 [RFC2119]. 135 XML is case sensitive. Unless stated otherwise, XML specifications 136 and examples provided in this document MUST be interpreted in the 137 character case presented in order to develop a conforming 138 implementation. 140 In examples, "C:" represents lines sent by a protocol client and "S:" 141 represents lines returned by a protocol server. Indentation and 142 white space in examples are provided only to illustrate element 143 relationships and are not a REQUIRED feature of this protocol. 145 "idnTable-1.0" is used as an abbreviation for 146 "urn:ietf:params:xml:ns:idnTable-1.0". The XML namespace prefix 147 "idnTable" is used, but implementations MUST NOT depend on it and 148 instead employ a proper namespace-aware XML parser and serializer to 149 interpret and output the XML documents. 151 2. Object Attributes 153 An EPP IDN Table object has attributes and associated values that can 154 help in the registration of IDNs. This section describes each type 155 in detail. The formal syntax for the attribute values described here 156 can be found in the "Formal Syntax" section of this document and in 157 the appropriate normative references. 159 2.1. IDN Table Identifier 161 The IDN Table Identifier is a server-defined unique value for an IDN 162 Table object. It is represented using an element or 163 an element. The IDN Table Identifier is used in the 164 and commands and responses. The IDN Table Identifier 165 MAY also be used as the value for the IDN mapping extension 166 [I-D.ietf-eppext-idnmap] element with a domain create of 167 an IDN object. 169 2.2. Domain Name 171 A Domain Name, as represented by an element, is 172 used to enable validating the code points against the server IDN 173 Tables and IDN policies and for retrieving IDN Table information 174 associated with the domain name. The Domain Name MUST be represented 175 as either a U-label or A-label as defined in [RFC5890]. 177 An OPTIONAL attribute "form" MAY be used to specify the 178 representation. When present, the "form" attribute MUST be set to 179 either "aLabel" for A-label or "uLabel" for U-label, depending on the 180 chosen representation for the domain name. The default "form" 181 attribute is "aLabel" for A-label. 183 3. EPP Command Mapping 185 A detailed description of the EPP syntax and semantics can be found 186 in the EPP core protocol specification [RFC5730]. 188 3.1. EPP Query Commands 190 EPP provides three commands to retrieve object information: 191 to determine if an object is known to the server, to retrieve 192 detailed information associated with an object, and to 193 retrieve object transfer status information. 195 3.1.1. EPP Command 197 There are two forms of the EPP command: the Domain Check Form 198 (Section 3.1.1.1) and the Table Check Form (Section 3.1.1.2). 200 3.1.1.1. Domain Check Form 202 The Domain Check Form is used to check the validity of the domain 203 name against the server IDN Tables and IDN policies, return whether 204 the IDN mapping extension [I-D.ietf-eppext-idnmap] is needed with a 205 domain command, and provide the matching list of IDN 206 Table Identifiers. This mapping is not intended to determine the 207 availability of the domain name. 209 In addition to the standard EPP command elements, the command 210 MUST contain an element that identifies the 211 idnTable namespace. The element in the Domain Check 212 Form contains the following child elements: 214 One or more elements that 215 contain the fully qualified names of the domain objects, as 216 defined in Section 2.2, to validate. 218 Example Domain Check Form command with three IDNs: 220 C: 221 C: 222 C: 223 C: 224 C: 226 C: idn1.example 228 C: idn2.example 230 C: idn3.example 231 C: 232 C: 233 C: ABC-12345 234 C: 235 C: 236 When a command has been processed successfully, the EPP 237 element MUST contain a child element 238 that identifies the idnTable namespace. The 239 element in the Domain Check Form contain one or more 240 elements that contain the following child elements: 242 The fully qualified name of the domain object, as 243 defined in Section 2.2. The element MUST contain a "valid" 244 attribute whose value indicates whether the domain name is valid 245 according to the server IDN Tables and IDN policies. A value of 246 "1" or "true" means that the domain name is valid according to 247 the server IDN Tables and policies. A value of "0" or "false" 248 means that the domain name is not valid according to the server 249 IDN Tables and policies. The element MAY contain an "idnmap" 250 attribute value that indicates whether the server requires the 251 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 252 domain create of the domain name. A value of "1" or "true" means 253 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 254 required using one of the values. A value of 255 "0" or "false" means that the IDN mapping extension 256 [I-D.ietf-eppext-idnmap] is not required. 257 OPTIONAL reason that the domain name is not valid. 258 If present, this element contains server-specific text to help 259 explain why the domain name is not valid. This text MUST be 260 represented in the response language previously negotiated with 261 the client; an OPTIONAL "lang" attribute MAY be present to 262 identify the language if the negotiated value is something other 263 than the default value of "en" (English). 264 Zero or more OPTIONAL elements 265 that contain the server defined IDN Table Identifier, as defined 266 in Section 2.1, that matches the code points of the 267 element. The MAY be used as the 268 value of the element in the IDN mapping extension 269 [I-D.ietf-eppext-idnmap] for creating the IDN object or MAY be 270 used as the value of the element of the 271 Table Info Form (Section 3.1.2.2) command, as described in 272 Section 3.1.2, to retrieve more information about the IDN Table. 274 Example Domain Check Form response with three IDNs: 276 S: 277 S: 278 S: 279 S: 280 S: Command completed successfully 281 S: 282 S: 283 S: 285 S: 286 S: 287 S: idn1.example 288 S: CHI 289 S: 290 S: 291 S: 292 S: idn2.example 293 S: CHI 294 S: JPN 295 S: 296 S: 297 S: 298 S: idn3.example 299 S: Commingled scripts 300 S: 301 S: 302 S: 303 S: 304 S: 305 S: ABC-12345 306 S: 54321-XYZ 307 S: 308 S: 309 S: 311 3.1.1.2. Table Check Form 313 The Table Check Form is used to check the existence of an IDN 314 Table using the IDN Table Identifier represented by the 315 element. 317 In addition to the standard EPP command elements, the command 318 MUST contain an element that identifies the 319 idnTable namespace. The element in the Table Check 320 Form contains the following child elements: 322 One or more elements that contain 323 the IDN Table Identifier, as defined in Section 2.1, to check for 324 existence. 326 Example Table Check Form command with three IDN 327 Table Identifiers: 329 C: 330 C: 331 C: 332 C: 333 C: 335 C: CHI 336 C: JPN 337 C: INVALID 338 C: 339 C: 340 C: ABC-12345 341 C: 342 C: 344 When a command has been processed successfully, the EPP 345 element MUST contain a child element 346 that identifies the idnTable namespace. The 347 element in the Table Check Form contains the following child 348 elements: 350 One or more elements that contain 351 the IDN Table Identifier, as defined in Section 2.1. The element 352 MUST contain an "exists" attribute whose value indicates the 353 existence of the IDN Table Identifier. A value of "1" or "true" 354 means that the IDN Table Identifier exists. A value of "0" or 355 "false" means that the IDN Table Identifier does not exist. 357 Example Table Check Form response with three IDN 358 Table Identifiers: 360 S: 361 S: 362 S: 363 S: 364 S: Command completed successfully 365 S: 366 S: 367 S: 369 S: CHI 370 S: 371 S: JPN 372 S: 373 S: INVALID 374 S: 375 S: 376 S: 377 S: 378 S: ABC-12345 379 S: 54321-XYZ 380 S: 381 S: 382 S: 384 3.1.2. EPP Command 386 There are three forms of the EPP command: the Domain Info Form 387 (Section 3.1.2.1), the Table Info Form (Section 3.1.2.2), and the 388 List Info Form (Section 3.1.2.3). 390 3.1.2.1. Domain Info Form 392 The Domain Info Form is used to validate the domain name code points 393 against the IDN Tables and IDN policies, and to return the matching 394 IDN Table meta-data. The domain name, as defined in Section 2.2 can 395 be provided as either a U-label or A-label. 397 In addition to the standard EPP command elements, the command 398 MUST contain an element that identifies the 399 idnTable namespace. The element in the Domain Info 400 Form contains the following child elements: 402 The domain name, as defined in Section 2.2, to 403 validate against the IDN Tables and IDN policies, and to retrieve 404 the matching IDN Table meta-data. 406 Example Domain Info Form command using a U-label Domain Name: 408 C: 409 C: 410 C: 411 C: 412 C: 414 C: idn1.example 415 C: 416 C: 417 C: ABC-12345 418 C: 419 C: 421 Example Domain Info Form command using an A-label Domain Name: 423 C: 424 C: 425 C: 426 C: 427 C: 429 C: xn--idn1.example 430 C: 431 C: 432 C: ABC-12345 433 C: 434 C: 436 When an command has been processed successfully, the EPP 437 element MUST contain a child element 438 that identifies the idnTable namespace. The 439 element in the Domain Info Form contains the 440 element that contains the following child elements: 442 The fully qualified name of the domain object, as 443 defined in Section 2.2. The element MUST contain a "valid" 444 attribute whose value indicates whether the domain name is valid 445 according to the server IDN Tables and IDN policies. A value of 446 "1" or "true" means that the domain name is valid according to 447 the server IDN Tables and policies. A value of "0" or "false" 448 means that the domain name is not valid according to the server 449 IDN Tables and policies. The element MAY contain an "idnmap" 450 attribute value that indicates whether the server requires the 451 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 452 domain create of the domain name. A value of "1" or "true" means 453 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 454 required using one of the 455 values. A value of "0" or "false" means that the IDN mapping 456 extension [I-D.ietf-eppext-idnmap] is not required. 457 or OPTIONAL U-label or A-label 458 form of the domain name value of the element in 459 the opposite form, as defined in Section 2.2. 460 Zero or more OPTIONAL elements 461 that provide the IDN Table meta-data information. The 462 element contains the following child elements: 464 Server defined IDN Table Identifier, as defined 465 in Section 2.1. 466 The type of the IDN Table with the possible 467 values of "language", to reflect a Language IDN Table, and 468 "script", to reflect a Script IDN Table. 469 Server defined description of the IDN 470 Table. This text MUST be represented in the response 471 language previously negotiated with the client; an OPTIONAL 472 "lang" attribute MAY be present to identify the language if 473 the negotiated value is something other than the default 474 value of "en" (English). 475 OPTIONAL boolean flag indicating that 476 domains created using the IDN Table will have IDN variants 477 generated. The management of variants is up to server 478 policy. 480 Example Domain Info Form response for a U-label Domain Name: 482 S: 483 S: 484 S: 485 S: 486 S: Command completed successfully 487 S: 488 S: 489 S: 491 S: 492 S: idn1.example 493 S: 494 S: xn--idn1.example 495 S: 496 S: THAI 497 S: script 498 S: Thai 499 S: 500 S: false 501 S: 502 S: 503 S: 504 S: 505 S: 506 S: ABC-12345 507 S: 54321-XYZ 508 S: 509 S: 510 S: 511 Example Domain Info Form response for an A-label Domain Name: 513 S: 514 S: 515 S: 516 S: 517 S: Command completed successfully 518 S: 519 S: 520 S: 522 S: 523 S: 524 S: xn--idn1.example 525 S: 526 S: idn1.example 527 S: 528 S: CHI 529 S: language 530 S: Chinese (CHI) 531 S: 532 S: true 533 S: 534 S: 535 S: JPN 536 S: language 537 S: Japanese (JPN) 538 S: 539 S: false 540 S: 541 S: 542 S: 543 S: 544 S: 545 S: ABC-12345 546 S: 54321-XYZ 547 S: 548 S: 549 S: 551 3.1.2.2. Table Info Form 553 The Table Info Form is used to retrieve information associated with 554 an IDN Table object. The information provided meta-data about the 555 IDN Table object. 557 In addition to the standard EPP command elements, the command 558 MUST contain an element that identifies the 559 idnTable namespace. The element in the Table Info 560 Form contains the following child elements: 562 Contains the IDN Table Identifier, as defined in 563 Section 2.1, of the IDN Table object to be queried. 565 Example Table Info Form command for the "CHI" IDN 566 Table Identifier, which represents a Language IDN Table: 568 C: 569 C: 570 C: 571 C: 572 C: 574 C: CHI 575 C: 576 C: 577 C: ABC-12345 578 C: 579 C: 581 Example Table Info Form command for the "THAI" IDN 582 Table Identifier, which represents a Script IDN Table: 584 C: 585 C: 586 C: 587 C: 588 C: 590 C: THAI 591 C: 592 C: 593 C: ABC-12345 594 C: 595 C: 597 When an command has been processed successfully, the EPP 598 element MUST contain a child element 599 that identifies the idnTable namespace. The 600 element in the Table Info Form contains the element 601 that contains the following child elements: 603 Server defined IDN Table Identifier, as defined in 604 Section 2.1. 606 The type of the IDN Table with the possible values 607 of "language", to reflect a Language IDN Table, and "script", to 608 reflect a Script IDN Table. 609 Server defined description of the IDN Table. 610 This text MUST be represented in the response language previously 611 negotiated with the client; an OPTIONAL "lang" attribute MAY be 612 present to identify the language if the negotiated value is 613 something other than the default value of "en" (English). 614 Contains the date and time that the IDN Table was 615 created or last updated. 616 OPTIONAL server defined version number of the IDN 617 Table. 618 OPTIONAL effective date for the IDN Table. 619 OPTIONAL boolean flag indicating that domains 620 created using the IDN Table will have IDN variants generated. 621 The management of variants is up to server policy. 622 OPTIONAL URL for downloading the IDN Table with the 623 applicable set of code points and rules. 625 Example Table Info Form response for the "CHI" IDN 626 Table Identifier, which represents a Language IDN Table: 628 S: 629 S: 630 S: 631 S: 632 S: Command completed successfully 633 S: 634 S: 635 S: 637 S: 638 S: CHI 639 S: language 640 S: Chinese (CHI) 641 S: 642 S: 2015-02-04T09:30:00.0Z 643 S: 644 S: 1.0 645 S: 2014-11-24 646 S: 647 S: true 648 S: 649 S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt 650 S: 651 S: 652 S: 653 S: 654 S: 655 S: ABC-12345 656 S: 54321-XYZ 657 S: 658 S: 659 S: 660 Example Table Info Form response for the "THAI" IDN 661 Table Identifier, which represents a Script IDN Table: 663 S: 664 S: 665 S: 666 S: 667 S: Command completed successfully 668 S: 669 S: 670 S: 672 S: 673 S: THAI 674 S: script 675 S: Thai 676 S: 2014-08-16T09:20:00.0Z 677 S: 678 S: 1.0 679 S: 2014-11-24 680 S: 681 S: false 682 S: 683 S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt 684 S: 685 S: 686 S: 687 S: 688 S: 689 S: ABC-12345 690 S: 54321-XYZ 691 S: 692 S: 693 S: 695 3.1.2.3. List Info Form 697 The List Info Form is used to retrieve the list of IDN Tables 698 supported by the server. The list of IDN Table Identifiers MAY be 699 used to query for the IDN Table information using the Table Info Form 700 (Section 3.1.2.2). 702 In addition to the standard EPP command elements, the command 703 MUST contain an element that identifies the 704 idnTable namespace. The element in the List Info 705 Form contains the following child elements: 707 Empty element used as a marker to the server of the 708 List Info Form to retrieve the list of IDN Tables. 710 Example List Info Form command: 712 C: 713 C: 714 C: 715 C: 716 C: 718 C: 719 C: 720 C: 721 C: ABC-12345 722 C: 723 C: 725 When an command has been processed successfully, the EPP 726 element MUST contain a child element 727 that identifies the idnTable namespace. The 728 element in the List Info Form contains the element 729 that contains the following child elements: 731 Zero or more elements that contain 732 the following child elements: 734 Server defined IDN Table Identifier, as defined 735 in Section 2.1, that is supported by the server. The 736 element value MAY be used as the value of 737 the element value in the Table Info Form 738 (Section 3.1.2.2) command to retrieve the information 739 on the IDN Table. 740 Contains the date and time that the IDN 741 Table was created or last updated. This element can be used 742 to determine whether a client-side cache needs to be 743 refreshed for the IDN Table using the Table Info Form 744 (Section 3.1.2.2). 746 Example List Info Form response that contains three IDN 747 Table Identifiers: 749 S: 750 S: 751 S: 752 S: 753 S: Command completed successfully 754 S: 755 S: 756 S: 758 S: 759 S: 760 S: CHI 761 S: 2015-02-04T09:30:00.0Z 762 S: 763 S: 764 S: 765 S: JPN 766 S: 2015-01-01T09:40:00.0Z 767 S: 768 S: 769 S: 770 S: THAI 771 S: 2014-08-16T09:20:00.0Z 772 S: 773 S: 774 S: 775 S: 776 S: 777 S: 778 S: ABC-12345 779 S: 54321-XYZ 780 S: 781 S: 782 S: 784 3.1.3. EPP Command 786 Transfer semantics do not apply to IDN table objects, so there is no 787 mapping defined for the EPP command. 789 3.2. EPP Transform Commands 791 EPP provides five commands to transform objects: to create 792 an instance of an object, to delete an instance of an 793 object, to extend the validity period of an object, 794 to manage object sponsorship changes, and to 795 change information associated with an object. 797 3.2.1. EPP Command 799 Create semantics do not apply to IDN table objects, so there is no 800 mapping defined for the EPP command. 802 3.2.2. EPP Command 804 Delete semantics do not apply to IDN table objects, so there is no 805 mapping defined for the EPP command. 807 3.2.3. EPP Command 809 Renewal semantics do not apply to IDN table objects, so there is no 810 mapping defined for the EPP command. 812 3.2.4. EPP Command 814 Transfer semantics do not apply to IDN table objects, so there is no 815 mapping defined for the EPP command. 817 3.2.5. EPP Command 819 Update semantics do not apply to IDN table objects, so there is no 820 mapping defined for the EPP command. 822 4. Formal Syntax 824 One schema is presented here that is the EPP IDN Table Mapping 825 schema. 827 The formal syntax presented here is a complete schema representation 828 of the object mapping suitable for automated validation of EPP XML 829 instances. The BEGIN and END tags are not part of the schema; they 830 are used to note the beginning and ending of the schema for URI 831 registration purposes. 833 4.1. IDN Table Mapping Schema 835 BEGIN 836 837 842 843 844 Extensible Provisioning Protocol v1.0 845 IDN Table Mapping. 846 847 849 850 853 856 857 859 862 863 864 865 866 867 869 872 873 874 875 877 878 879 881 884 885 886 887 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 929 932 933 934 935 937 938 939 941 944 945 946 947 948 949 950 951 953 956 957 958 959 960 961 963 964 965 967 970 971 972 973 974 975 976 977 978 980 983 984 985 986 987 988 990 991 992 993 994 995 996 998 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1014 1017 1018 1019 1020 1021 1022 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 1067 5.1. XML Namespace 1069 This document uses URNs to describe XML namespaces and XML schemas 1070 conforming to a registry mechanism described in [RFC3688]. The 1071 following URI assignment is requested of IANA: 1073 URI: urn:ietf:params:xml:ns:idnTable-1.0 1075 Registrant Contact: See the "Author's Address" section of this 1076 document. 1078 XML: See the "Formal Syntax" section of this document. 1080 5.2. EPP Extension Registry 1082 The EPP extension described in this document should be registered by 1083 the IANA in the EPP Extension Registry described in [RFC7451]. The 1084 details of the registration are as follows: 1086 Name of Extension: "Extensible Provisioning Protocol (EPP) 1087 Internationalized Domain Name (IDN) Table Mapping" 1089 Document status: Standards Track 1091 Reference: (insert reference to RFC version of this document) 1093 Registrant Name and Email Address: IESG, 1095 TLDs: Any 1097 IPR Disclosure: None 1099 Status: Active 1101 Notes: None 1103 6. Security Considerations 1105 The mapping extensions described in this document do not provide any 1106 security services beyond those described by EPP [RFC5730] and 1107 protocol layers used by EPP. The security considerations described 1108 in these other specifications apply to this specification as well. 1110 7. Normative References 1112 [I-D.ietf-eppext-idnmap] 1113 Obispo, F., "Internationalized Domain Name Mapping 1114 Extension for the Extensible Provisioning Protocol (EPP)", 1115 draft-ietf-eppext-idnmap-02 (work in progress), January 1116 2015. 1118 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1119 Requirement Levels", BCP 14, RFC 2119, 1120 DOI 10.17487/RFC2119, March 1997, 1121 . 1123 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1124 DOI 10.17487/RFC3688, January 2004, 1125 . 1127 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1128 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1129 . 1131 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1132 Domain Name Mapping", STD 69, RFC 5731, 1133 DOI 10.17487/RFC5731, August 2009, 1134 . 1136 [RFC5890] Klensin, J., "Internationalized Domain Names for 1137 Applications (IDNA): Definitions and Document Framework", 1138 RFC 5890, DOI 10.17487/RFC5890, August 2010, 1139 . 1141 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1142 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1143 February 2015, . 1145 Appendix A. Change History 1147 A.1. Change from 00 to 01 1149 1. Amended XML Namespace section of IANA Considerations, added EPP 1150 Extension Registry section. 1152 A.2. Change from 01 to 02 1154 1. Removed support for returning the idnTable:codePoint and 1155 idnTable:codeRange elements in the table info response based on 1156 the feedback at the Registration Operations Workshop (ROW), held 1157 on March 22, 2015, prior to IETF-92. 1158 2. Fixed info command samples that referenced the element 1159 instead of the element. 1161 A.3. Change from 02 to 03 1163 1. Ping update. 1165 A.4. Change from 03 to 04 1167 1. Ping update. 1169 Authors' Addresses 1170 James Gould 1171 VeriSign, Inc. 1172 12061 Bluemont Way 1173 Reston, VA 20190 1174 US 1176 Email: jgould@verisign.com 1177 URI: http://www.verisigninc.com 1179 Francisco Obispo 1180 Uniregistry Corp. 1181 3-110 Governors Square 1182 Grand Cayman, Grand Cayman KY1-1108 1183 KY 1185 Email: fobispo@uniregistry.com 1186 URI: http://www.uniregistry.com/ 1188 Luis Enrique Munoz 1189 Uniregistry Corp. 1190 3-110 Governors Square 1191 Grand Cayman, Grand Cayman KY1-1108 1192 KY 1194 Email: fobispo@uniregistry.com 1195 URI: http://www.uniregistry.com/