idnits 2.17.1 draft-gould-idn-table-02.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 2, 2015) is 3305 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 4, 2015 L. Munoz 6 Uniregistry Corp. 7 April 2, 2015 9 Extensible Provisioning Protocol (EPP) Internationalized Domain Name 10 (IDN) Table Mapping 11 draft-gould-idn-table-02 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 4, 2015. 45 Copyright Notice 47 Copyright (c) 2015 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 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 96 1. Introduction 98 This document describes an extension mapping for version 1.0 of the 99 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 100 provides Internationalized Domain Name (IDN) Table information for 101 the registration of IDNs, using the EPP domain name mapping 102 [RFC5731], and optionally with the IDN mapping extension 103 [I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of 104 characters (code points) that can be used in a domain name. Code 105 points may overlap across IDN Tables and the IDN Tables supported by 106 the servers are up to server policy. This mapping provides the 107 information clients need to register IDNs across a variety of servers 108 with differing IDN policies. The IDN Table Mapping can be used for 109 the following: 111 "Validate IDN Domain Name" Validate that an IDN meets the server IDN 112 policy. The validation can be done prior to submitting a domain 113 create, per [RFC5731]. 114 "Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since 115 IDN Table code points may overlap, the mapping can be used to 116 identify the matching set of IDN Tables (language or script), 117 along with the IDN Table meta-data. 118 "Cache IDN Table Code Points" Clients can query for the complete 119 list of IDN Tables and can get the IDN Table meta-data, based on 120 server policy, to support pre-validation in the client. 121 "Get the IDN Table Identifier to Pass with a Domain Create" Each IDN 122 Table includes a server unique IDN Table Identifier that may be 123 used as the value of the element in the IDN mapping 124 extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the 125 IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the 126 domain name. 128 1.1. Conventions Used in This Document 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 132 document are to be interpreted as described in RFC 2119 [RFC2119]. 134 XML is case sensitive. Unless stated otherwise, XML specifications 135 and examples provided in this document MUST be interpreted in the 136 character case presented in order to develop a conforming 137 implementation. 139 In examples, "C:" represents lines sent by a protocol client and "S:" 140 represents lines returned by a protocol server. Indentation and 141 white space in examples are provided only to illustrate element 142 relationships and are not a REQUIRED feature of this protocol. 144 "idnTable-1.0" is used as an abbreviation for 145 "urn:ietf:params:xml:ns:idnTable-1.0". The XML namespace prefix 146 "idnTable" is used, but implementations MUST NOT depend on it and 147 instead employ a proper namespace-aware XML parser and serializer to 148 interpret and output the XML documents. 150 2. Object Attributes 152 An EPP IDN Table object has attributes and associated values that can 153 help in the registration of IDNs. This section describes each type 154 in detail. The formal syntax for the attribute values described here 155 can be found in the "Formal Syntax" section of this document and in 156 the appropriate normative references. 158 2.1. IDN Table Identifier 160 The IDN Table Identifier is a server-defined unique value for an IDN 161 Table object. It is represented using an element or 162 an element. The IDN Table Identifier is used in the 163 and commands and responses. The IDN Table Identifier 164 MAY also be used as the value for the IDN mapping extension 165 [I-D.ietf-eppext-idnmap] element with a domain create of 166 an IDN object. 168 2.2. Domain Name 170 A Domain Name, as represented by an element, is 171 used to enable validating the code points against the server IDN 172 Tables and IDN policies and for retrieving IDN Table information 173 associated with the domain name. The Domain Name MUST be represented 174 as either a U-label or A-label as defined in [RFC5890]. 176 An OPTIONAL attribute "form" MAY be used to specify the 177 representation. When present, the "form" attribute MUST be set to 178 either "aLabel" for A-label or "uLabel" for U-label, depending on the 179 chosen representation for the domain name. The default "form" 180 attribute is "aLabel" for A-label. 182 3. EPP Command Mapping 184 A detailed description of the EPP syntax and semantics can be found 185 in the EPP core protocol specification [RFC5730]. 187 3.1. EPP Query Commands 189 EPP provides three commands to retrieve object information: 190 to determine if an object is known to the server, to retrieve 191 detailed information associated with an object, and to 192 retrieve object transfer status information. 194 3.1.1. EPP Command 196 There are two forms of the EPP command: the Domain Check Form 197 (Section 3.1.1.1) and the Table Check Form (Section 3.1.1.2). 199 3.1.1.1. Domain Check Form 201 The Domain Check Form is used to check the validity of the domain 202 name against the server IDN Tables and IDN policies, return whether 203 the IDN mapping extension [I-D.ietf-eppext-idnmap] is needed with a 204 domain command, and provide the matching list of IDN 205 Table Identifiers. This mapping is not intended to determine the 206 availability of the domain name. 208 In addition to the standard EPP command elements, the command 209 MUST contain an element that identifies the 210 idnTable namespace. The element in the Domain Check 211 Form contains the following child elements: 213 One or more elements that 214 contain the fully qualified names of the domain objects, as 215 defined in Section 2.2, to validate. 217 Example Domain Check Form command with three IDNs: 219 C: 220 C: 221 C: 222 C: 223 C: 225 C: idn1.example 227 C: idn2.example 229 C: idn3.example 230 C: 231 C: 232 C: ABC-12345 233 C: 234 C: 235 When a command has been processed successfully, the EPP 236 element MUST contain a child element 237 that identifies the idnTable namespace. The 238 element in the Domain Check Form contain one or more 239 elements that contain the following child elements: 241 The fully qualified name of the domain object, as 242 defined in Section 2.2. The element MUST contain a "valid" 243 attribute whose value indicates whether the domain name is valid 244 according to the server IDN Tables and IDN policies. A value of 245 "1" or "true" means that the domain name is valid according to 246 the server IDN Tables and policies. A value of "0" or "false" 247 means that the domain name is not valid according to the server 248 IDN Tables and policies. The element MAY contain an "idnmap" 249 attribute value that indicates whether the server requires the 250 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 251 domain create of the domain name. A value of "1" or "true" means 252 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 253 required using one of the values. A value of 254 "0" or "false" means that the IDN mapping extension 255 [I-D.ietf-eppext-idnmap] is not required. 256 OPTIONAL reason that the domain name is not valid. 257 If present, this element contains server-specific text to help 258 explain why the domain name is not valid. This text MUST be 259 represented in the response language previously negotiated with 260 the client; an OPTIONAL "lang" attribute MAY be present to 261 identify the language if the negotiated value is something other 262 than the default value of "en" (English). 263 Zero or more OPTIONAL elements 264 that contain the server defined IDN Table Identifier, as defined 265 in Section 2.1, that matches the code points of the 266 element. The MAY be used as the 267 value of the element in the IDN mapping extension 268 [I-D.ietf-eppext-idnmap] for creating the IDN object or MAY be 269 used as the value of the element of the 270 Table Info Form (Section 3.1.2.2) command, as described in 271 Section 3.1.2, to retrieve more information about the IDN Table. 273 Example Domain Check Form response with three IDNs: 275 S: 276 S: 277 S: 278 S: 279 S: Command completed successfully 280 S: 281 S: 282 S: 284 S: 285 S: 286 S: idn1.example 287 S: CHI 288 S: 289 S: 290 S: 291 S: idn2.example 292 S: CHI 293 S: JPN 294 S: 295 S: 296 S: 297 S: idn3.example 298 S: Commingled scripts 299 S: 300 S: 301 S: 302 S: 303 S: 304 S: ABC-12345 305 S: 54321-XYZ 306 S: 307 S: 308 S: 310 3.1.1.2. Table Check Form 312 The Table Check Form is used to check the existence of an IDN 313 Table using the IDN Table Identifier represented by the 314 element. 316 In addition to the standard EPP command elements, the command 317 MUST contain an element that identifies the 318 idnTable namespace. The element in the Table Check 319 Form contains the following child elements: 321 One or more elements that contain 322 the IDN Table Identifier, as defined in Section 2.1, to check for 323 existence. 325 Example Table Check Form command with three IDN 326 Table Identifiers: 328 C: 329 C: 330 C: 331 C: 332 C: 334 C: CHI 335 C: JPN 336 C: INVALID 337 C: 338 C: 339 C: ABC-12345 340 C: 341 C: 343 When a command has been processed successfully, the EPP 344 element MUST contain a child element 345 that identifies the idnTable namespace. The 346 element in the Table Check Form contains the following child 347 elements: 349 One or more elements that contain 350 the IDN Table Identifier, as defined in Section 2.1. The element 351 MUST contain an "exists" attribute whose value indicates the 352 existence of the IDN Table Identifier. A value of "1" or "true" 353 means that the IDN Table Identifier exists. A value of "0" or 354 "false" means that the IDN Table Identifier does not exist. 356 Example Table Check Form response with three IDN 357 Table Identifiers: 359 S: 360 S: 361 S: 362 S: 363 S: Command completed successfully 364 S: 365 S: 366 S: 368 S: CHI 369 S: 370 S: JPN 371 S: 372 S: INVALID 373 S: 374 S: 375 S: 376 S: 377 S: ABC-12345 378 S: 54321-XYZ 379 S: 380 S: 381 S: 383 3.1.2. EPP Command 385 There are three forms of the EPP command: the Domain Info Form 386 (Section 3.1.2.1), the Table Info Form (Section 3.1.2.2), and the 387 List Info Form (Section 3.1.2.3). 389 3.1.2.1. Domain Info Form 391 The Domain Info Form is used to validate the domain name code points 392 against the IDN Tables and IDN policies, and to return the matching 393 IDN Table meta-data. The domain name, as defined in Section 2.2 can 394 be provided as either a U-label or A-label. 396 In addition to the standard EPP command elements, the command 397 MUST contain an element that identifies the 398 idnTable namespace. The element in the Domain Info 399 Form contains the following child elements: 401 The domain name, as defined in Section 2.2, to 402 validate against the IDN Tables and IDN policies, and to retrieve 403 the matching IDN Table meta-data. 405 Example Domain Info Form command using a U-label Domain Name: 407 C: 408 C: 409 C: 410 C: 411 C: 413 C: idn1.example 414 C: 415 C: 416 C: ABC-12345 417 C: 418 C: 420 Example Domain Info Form command using an A-label Domain Name: 422 C: 423 C: 424 C: 425 C: 426 C: 428 C: xn--idn1.example 429 C: 430 C: 431 C: ABC-12345 432 C: 433 C: 435 When an command has been processed successfully, the EPP 436 element MUST contain a child element 437 that identifies the idnTable namespace. The 438 element in the Domain Info Form contains the 439 element that contains the following child elements: 441 The fully qualified name of the domain object, as 442 defined in Section 2.2. The element MUST contain a "valid" 443 attribute whose value indicates whether the domain name is valid 444 according to the server IDN Tables and IDN policies. A value of 445 "1" or "true" means that the domain name is valid according to 446 the server IDN Tables and policies. A value of "0" or "false" 447 means that the domain name is not valid according to the server 448 IDN Tables and policies. The element MAY contain an "idnmap" 449 attribute value that indicates whether the server requires the 450 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 451 domain create of the domain name. A value of "1" or "true" means 452 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 453 required using one of the 454 values. A value of "0" or "false" means that the IDN mapping 455 extension [I-D.ietf-eppext-idnmap] is not required. 456 or OPTIONAL U-label or A-label 457 form of the domain name value of the element in 458 the opposite form, as defined in Section 2.2. 459 Zero or more OPTIONAL elements 460 that provide the IDN Table meta-data information. The 461 element contains the following child elements: 463 Server defined IDN Table Identifier, as defined 464 in Section 2.1. 465 The type of the IDN Table with the possible 466 values of "language", to reflect a Language IDN Table, and 467 "script", to reflect a Script IDN Table. 468 Server defined description of the IDN 469 Table. This text MUST be represented in the response 470 language previously negotiated with the client; an OPTIONAL 471 "lang" attribute MAY be present to identify the language if 472 the negotiated value is something other than the default 473 value of "en" (English). 474 OPTIONAL boolean flag indicating that 475 domains created using the IDN Table will have IDN variants 476 generated. The management of variants is up to server 477 policy. 479 Example Domain Info Form response for a U-label Domain Name: 481 S: 482 S: 483 S: 484 S: 485 S: Command completed successfully 486 S: 487 S: 488 S: 490 S: 491 S: idn1.example 492 S: 493 S: xn--idn1.example 494 S: 495 S: THAI 496 S: script 497 S: Thai 498 S: 499 S: false 500 S: 501 S: 502 S: 503 S: 504 S: 505 S: ABC-12345 506 S: 54321-XYZ 507 S: 508 S: 509 S: 510 Example Domain Info Form response for an A-label Domain Name: 512 S: 513 S: 514 S: 515 S: 516 S: Command completed successfully 517 S: 518 S: 519 S: 521 S: 522 S: 523 S: xn--idn1.example 524 S: 525 S: idn1.example 526 S: 527 S: CHI 528 S: language 529 S: Chinese (CHI) 530 S: 531 S: true 532 S: 533 S: 534 S: JPN 535 S: language 536 S: Japanese (JPN) 537 S: 538 S: false 539 S: 540 S: 541 S: 542 S: 543 S: 544 S: ABC-12345 545 S: 54321-XYZ 546 S: 547 S: 548 S: 550 3.1.2.2. Table Info Form 552 The Table Info Form is used to retrieve information associated with 553 an IDN Table object. The information provided meta-data about the 554 IDN Table object. 556 In addition to the standard EPP command elements, the command 557 MUST contain an element that identifies the 558 idnTable namespace. The element in the Table Info 559 Form contains the following child elements: 561 Contains the IDN Table Identifier, as defined in 562 Section 2.1, of the IDN Table object to be queried. 564 Example Table Info Form command for the "CHI" IDN 565 Table Identifier, which represents a Language IDN Table: 567 C: 568 C: 569 C: 570 C: 571 C: 573 C: CHI 574 C: 575 C: 576 C: ABC-12345 577 C: 578 C: 580 Example Table Info Form command for the "THAI" IDN 581 Table Identifier, which represents a Script IDN Table: 583 C: 584 C: 585 C: 586 C: 587 C: 589 C: THAI 590 C: 591 C: 592 C: ABC-12345 593 C: 594 C: 596 When an command has been processed successfully, the EPP 597 element MUST contain a child element 598 that identifies the idnTable namespace. The 599 element in the Table Info Form contains the element 600 that contains the following child elements: 602 Server defined IDN Table Identifier, as defined in 603 Section 2.1. 605 The type of the IDN Table with the possible values 606 of "language", to reflect a Language IDN Table, and "script", to 607 reflect a Script IDN Table. 608 Server defined description of the IDN Table. 609 This text MUST be represented in the response language previously 610 negotiated with the client; an OPTIONAL "lang" attribute MAY be 611 present to identify the language if the negotiated value is 612 something other than the default value of "en" (English). 613 Contains the date and time that the IDN Table was 614 created or last updated. 615 OPTIONAL server defined version number of the IDN 616 Table. 617 OPTIONAL effective date for the IDN Table. 618 OPTIONAL boolean flag indicating that domains 619 created using the IDN Table will have IDN variants generated. 620 The management of variants is up to server policy. 621 OPTIONAL URL for downloading the IDN Table with the 622 applicable set of code points and rules. 624 Example Table Info Form response for the "CHI" IDN 625 Table Identifier, which represents a Language IDN Table: 627 S: 628 S: 629 S: 630 S: 631 S: Command completed successfully 632 S: 633 S: 634 S: 636 S: 637 S: CHI 638 S: language 639 S: Chinese (CHI) 640 S: 641 S: 2015-02-04T09:30:00.0Z 642 S: 643 S: 1.0 644 S: 2014-11-24 645 S: 646 S: true 647 S: 648 S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt 649 S: 650 S: 651 S: 652 S: 653 S: 654 S: ABC-12345 655 S: 54321-XYZ 656 S: 657 S: 658 S: 659 Example Table Info Form response for the "THAI" IDN 660 Table Identifier, which represents a Script IDN Table: 662 S: 663 S: 664 S: 665 S: 666 S: Command completed successfully 667 S: 668 S: 669 S: 671 S: 672 S: THAI 673 S: script 674 S: Thai 675 S: 2014-08-16T09:20:00.0Z 676 S: 677 S: 1.0 678 S: 2014-11-24 679 S: 680 S: false 681 S: 682 S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt 683 S: 684 S: 685 S: 686 S: 687 S: 688 S: ABC-12345 689 S: 54321-XYZ 690 S: 691 S: 692 S: 694 3.1.2.3. List Info Form 696 The List Info Form is used to retrieve the list of IDN Tables 697 supported by the server. The list of IDN Table Identifiers MAY be 698 used to query for the IDN Table information using the Table Info Form 699 (Section 3.1.2.2). 701 In addition to the standard EPP command elements, the command 702 MUST contain an element that identifies the 703 idnTable namespace. The element in the List Info 704 Form contains the following child elements: 706 Empty element used as a marker to the server of the 707 List Info Form to retrieve the list of IDN Tables. 709 Example List Info Form command: 711 C: 712 C: 713 C: 714 C: 715 C: 717 C: 718 C: 719 C: 720 C: ABC-12345 721 C: 722 C: 724 When an command has been processed successfully, the EPP 725 element MUST contain a child element 726 that identifies the idnTable namespace. The 727 element in the List Info Form contains the element 728 that contains the following child elements: 730 Zero or more elements that contain 731 the following child elements: 733 Server defined IDN Table Identifier, as defined 734 in Section 2.1, that is supported by the server. The 735 element value MAY be used as the value of 736 the element value in the Table Info Form 737 (Section 3.1.2.2) command to retrieve the information 738 on the IDN Table. 739 Contains the date and time that the IDN 740 Table was created or last updated. This element can be used 741 to determine whether a client-side cache needs to be 742 refreshed for the IDN Table using the Table Info Form 743 (Section 3.1.2.2). 745 Example List Info Form response that contains three IDN 746 Table Identifiers: 748 S: 749 S: 750 S: 751 S: 752 S: Command completed successfully 753 S: 754 S: 755 S: 757 S: 758 S: 759 S: CHI 760 S: 2015-02-04T09:30:00.0Z 761 S: 762 S: 763 S: 764 S: JPN 765 S: 2015-01-01T09:40:00.0Z 766 S: 767 S: 768 S: 769 S: THAI 770 S: 2014-08-16T09:20:00.0Z 771 S: 772 S: 773 S: 774 S: 775 S: 776 S: 777 S: ABC-12345 778 S: 54321-XYZ 779 S: 780 S: 781 S: 783 3.1.3. EPP Command 785 Transfer semantics do not apply to IDN table objects, so there is no 786 mapping defined for the EPP command. 788 3.2. EPP Transform Commands 790 EPP provides five commands to transform objects: to create 791 an instance of an object, to delete an instance of an 792 object, to extend the validity period of an object, 793 to manage object sponsorship changes, and to 794 change information associated with an object. 796 3.2.1. EPP Command 798 Create semantics do not apply to IDN table objects, so there is no 799 mapping defined for the EPP command. 801 3.2.2. EPP Command 803 Delete semantics do not apply to IDN table objects, so there is no 804 mapping defined for the EPP command. 806 3.2.3. EPP Command 808 Renewal semantics do not apply to IDN table objects, so there is no 809 mapping defined for the EPP command. 811 3.2.4. EPP Command 813 Transfer semantics do not apply to IDN table objects, so there is no 814 mapping defined for the EPP command. 816 3.2.5. EPP Command 818 Update semantics do not apply to IDN table objects, so there is no 819 mapping defined for the EPP command. 821 4. Formal Syntax 823 One schema is presented here that is the EPP IDN Table Mapping 824 schema. 826 The formal syntax presented here is a complete schema representation 827 of the object mapping suitable for automated validation of EPP XML 828 instances. The BEGIN and END tags are not part of the schema; they 829 are used to note the beginning and ending of the schema for URI 830 registration purposes. 832 4.1. IDN Table Mapping Schema 834 BEGIN 835 836 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 880 883 884 885 886 888 890 891 892 894 897 898 899 900 901 902 903 904 905 907 910 911 913 916 917 918 919 921 923 924 925 926 929 930 931 932 933 934 935 937 940 941 942 943 944 945 946 947 949 952 953 954 955 956 957 959 960 961 963 966 967 968 969 970 971 973 974 975 977 980 981 982 983 984 985 987 988 989 990 991 992 993 995 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1011 1014 1015 1016 1017 1018 1019 1021 1022 1024 1025 1027 1030 1031 1032 1033 1034 1035 1036 1037 1039 1042 1043 1044 1046 1047 1049 1052 1053 1054 1055 1056 1057 1059 1060 1061 END 1063 5. IANA Considerations 1064 5.1. XML Namespace 1066 This document uses URNs to describe XML namespaces and XML schemas 1067 conforming to a registry mechanism described in [RFC3688]. The 1068 following URI assignment is requested of IANA: 1070 URI: urn:ietf:params:xml:ns:idnTable-1.0 1072 Registrant Contact: See the "Author's Address" section of this 1073 document. 1075 XML: See the "Formal Syntax" section of this document. 1077 5.2. EPP Extension Registry 1079 The EPP extension described in this document should be registered by 1080 the IANA in the EPP Extension Registry described in [RFC7451]. The 1081 details of the registration are as follows: 1083 Name of Extension: "Extensible Provisioning Protocol (EPP) 1084 Internationalized Domain Name (IDN) Table Mapping" 1086 Document status: Standards Track 1088 Reference: (insert reference to RFC version of this document) 1090 Registrant Name and Email Address: IESG, 1092 TLDs: Any 1094 IPR Disclosure: None 1096 Status: Active 1098 Notes: None 1100 6. Security Considerations 1102 The mapping extensions described in this document do not provide any 1103 security services beyond those described by EPP [RFC5730] and 1104 protocol layers used by EPP. The security considerations described 1105 in these other specifications apply to this specification as well. 1107 7. Normative References 1109 [I-D.ietf-eppext-idnmap] 1110 Obispo, F., "Internationalized Domain Name Mapping 1111 Extension for the Extensible Provisioning Protocol (EPP)", 1112 draft-ietf-eppext-idnmap-02 (work in progress), January 1113 2015. 1115 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1116 Requirement Levels", BCP 14, RFC 2119, March 1997. 1118 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1119 January 2004. 1121 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1122 STD 69, RFC 5730, August 2009. 1124 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1125 Domain Name Mapping", STD 69, RFC 5731, August 2009. 1127 [RFC5890] Klensin, J., "Internationalized Domain Names for 1128 Applications (IDNA): Definitions and Document Framework", 1129 RFC 5890, August 2010. 1131 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1132 Provisioning Protocol", RFC 7451, February 2015. 1134 Appendix A. Change History 1136 A.1. Change from 00 to 01 1138 1. Amended XML Namespace section of IANA Considerations, added EPP 1139 Extension Registry section. 1141 A.2. Change from 01 to 02 1143 1. Removed support for returning the idnTable:codePoint and 1144 idnTable:codeRange elements in the table info response based on 1145 the feedback at the Registration Operations Workshop (ROW), held 1146 on March 22, 2015, prior to IETF-92. 1147 2. Fixed info command samples that referenced the element 1148 instead of the element. 1150 Authors' Addresses 1151 James Gould 1152 VeriSign, Inc. 1153 12061 Bluemont Way 1154 Reston, VA 20190 1155 US 1157 Email: jgould@verisign.com 1158 URI: http://www.verisigninc.com 1160 Francisco Obispo 1161 Uniregistry Corp. 1162 3-110 Governors Square 1163 Grand Cayman, Grand Cayman KY1-1108 1164 KY 1166 Email: fobispo@uniregistry.com 1167 URI: http://www.uniregistry.com/ 1169 Luis Enrique Munoz 1170 Uniregistry Corp. 1171 3-110 Governors Square 1172 Grand Cayman, Grand Cayman KY1-1108 1173 KY 1175 Email: fobispo@uniregistry.com 1176 URI: http://www.uniregistry.com/