idnits 2.17.1 draft-gould-idn-table-07.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 15, 2018) is 2019 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Experimental draft: draft-ietf-eppext-idnmap (ref. 'I-D.ietf-eppext-idnmap') Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Standards Track F. Obispo 5 Expires: April 18, 2019 L. Munoz 6 Uniregistry Corp. 7 October 15, 2018 9 Extensible Provisioning Protocol (EPP) Internationalized Domain Name 10 (IDN) Table Mapping 11 draft-gould-idn-table-07 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 18, 2019. 45 Copyright Notice 47 Copyright (c) 2018 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 64 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 65 2.1. IDN Table Identifier . . . . . . . . . . . . . . . . . . 4 66 2.2. Domain Name . . . . . . . . . . . . . . . . . . . . . . . 4 67 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 68 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5 69 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 5 70 3.1.1.1. Domain Check Form . . . . . . . . . . . . . . . . 5 71 3.1.1.2. Table Check Form . . . . . . . . . . . . . . . . 8 72 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 9 73 3.1.2.1. Domain Info Form . . . . . . . . . . . . . . . . 9 74 3.1.2.2. Table Info Form . . . . . . . . . . . . . . . . . 13 75 3.1.2.3. List Info Form . . . . . . . . . . . . . . . . . 17 76 3.1.3. EPP Command . . . . . . . . . . . . . . . 19 77 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 20 78 3.2.1. EPP Command . . . . . . . . . . . . . . . . 20 79 3.2.2. EPP Command . . . . . . . . . . . . . . . . 20 80 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 20 81 3.2.4. EPP Command . . . . . . . . . . . . . . . 20 82 3.2.5. EPP Command . . . . . . . . . . . . . . . . 20 83 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20 84 4.1. IDN Table Mapping Schema . . . . . . . . . . . . . . . . 21 85 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 86 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 26 87 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 26 88 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 26 89 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 27 90 7. Security Considerations . . . . . . . . . . . . . . . . . . . 27 91 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 92 8.1. Normative References . . . . . . . . . . . . . . . . . . 27 93 8.2. Informative References . . . . . . . . . . . . . . . . . 28 94 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 28 95 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 28 96 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 29 97 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 29 98 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 29 99 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 29 100 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 29 101 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 29 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 104 1. Introduction 106 This document describes an extension mapping for version 1.0 of the 107 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 108 provides Internationalized Domain Name (IDN) Table information for 109 the registration of IDNs, using the EPP domain name mapping 110 [RFC5731], and optionally with the IDN mapping extension 111 [I-D.ietf-eppext-idnmap]. An IDN Table defines the valid set of 112 characters (code points) that can be used in a domain name. Code 113 points may overlap across IDN Tables and the IDN Tables supported by 114 the servers are up to server policy. This mapping provides the 115 information clients need to register IDNs across a variety of servers 116 with differing IDN policies. The IDN Table Mapping can be used for 117 the following: 119 "Validate IDN Domain Name" Validate that an IDN meets the server IDN 120 policy. The validation can be done prior to submitting a domain 121 create, per [RFC5731]. 122 "Get IDN Tables Matching IDN Domain Name Along with Meta-Data" Since 123 IDN Table code points may overlap, the mapping can be used to 124 identify the matching set of IDN Tables (language or script), 125 along with the IDN Table meta-data. 126 "Cache IDN Table Code Points" Clients can query for the complete 127 list of IDN Tables and can get the IDN Table meta-data, based on 128 server policy, to support pre-validation in the client. 129 "Get the IDN Table Identifier to Pass with a Domain Create" Each IDN 130 Table includes a server unique IDN Table Identifier that may be 131 used as the value of the element in the IDN mapping 132 extension [I-D.ietf-eppext-idnmap]. A flag indicates whether the 133 IDN mapping extension [I-D.ietf-eppext-idnmap] is needed for the 134 domain name. 136 1.1. Conventions Used in This Document 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in RFC 2119 [RFC2119]. 142 XML is case sensitive. Unless stated otherwise, XML specifications 143 and examples provided in this document MUST be interpreted in the 144 character case presented in order to develop a conforming 145 implementation. 147 In examples, "C:" represents lines sent by a protocol client and "S:" 148 represents lines returned by a protocol server. Indentation and 149 white space in examples are provided only to illustrate element 150 relationships and are not a REQUIRED feature of this protocol. 152 "idnTable-1.0" is used as an abbreviation for 153 "urn:ietf:params:xml:ns:idnTable-1.0". The XML namespace prefix 154 "idnTable" is used, but implementations MUST NOT depend on it and 155 instead employ a proper namespace-aware XML parser and serializer to 156 interpret and output the XML documents. 158 2. Object Attributes 160 An EPP IDN Table object has attributes and associated values that can 161 help in the registration of IDNs. This section describes each type 162 in detail. The formal syntax for the attribute values described here 163 can be found in the "Formal Syntax" section of this document and in 164 the appropriate normative references. 166 2.1. IDN Table Identifier 168 The IDN Table Identifier is a server-defined unique value for an IDN 169 Table object. It is represented using an element or 170 an element. The IDN Table Identifier is used in the 171 and commands and responses. The IDN Table Identifier 172 MAY also be used as the value for the IDN mapping extension 173 [I-D.ietf-eppext-idnmap] element with a domain create of 174 an IDN object. 176 2.2. Domain Name 178 A Domain Name, as represented by an element, is 179 used to enable validating the code points against the server IDN 180 Tables and IDN policies and for retrieving IDN Table information 181 associated with the domain name. The Domain Name MUST be represented 182 as either a U-label or A-label as defined in [RFC5890]. 184 An OPTIONAL attribute "form" MAY be used to specify the 185 representation. When present, the "form" attribute MUST be set to 186 either "aLabel" for A-label or "uLabel" for U-label, depending on the 187 chosen representation for the domain name. The default "form" 188 attribute is "aLabel" for A-label. 190 3. EPP Command Mapping 192 A detailed description of the EPP syntax and semantics can be found 193 in the EPP core protocol specification [RFC5730]. 195 3.1. EPP Query Commands 197 EPP provides three commands to retrieve object information: 198 to determine if an object is known to the server, to retrieve 199 detailed information associated with an object, and to 200 retrieve object transfer status information. 202 3.1.1. EPP Command 204 There are two forms of the EPP command: the Domain Check Form 205 (Section 3.1.1.1) and the Table Check Form (Section 3.1.1.2). 207 3.1.1.1. Domain Check Form 209 The Domain Check Form is used to check the validity of the domain 210 name against the server IDN Tables and IDN policies, return whether 211 the IDN mapping extension [I-D.ietf-eppext-idnmap] is needed with a 212 domain command, and provide the matching list of IDN 213 Table Identifiers. This mapping is not intended to determine the 214 availability of the domain name. 216 In addition to the standard EPP command elements, the command 217 MUST contain an element that identifies the 218 idnTable namespace. The element in the Domain Check 219 Form contains the following child elements: 221 One or more elements that 222 contain the fully qualified names of the domain objects, as 223 defined in Section 2.2, to validate. 225 Example Domain Check Form command with three IDNs: 227 C: 228 C: 229 C: 230 C: 231 C: 233 C: idn1.example 235 C: idn2.example 237 C: idn3.example 238 C: 239 C: 240 C: ABC-12345 241 C: 242 C: 244 When a command has been processed successfully, the EPP 245 element MUST contain a child element 246 that identifies the idnTable namespace. The 247 element in the Domain Check Form contain one or more 248 elements that contain the following child elements: 250 The fully qualified name of the domain object, as 251 defined in Section 2.2. The element MUST contain a "valid" 252 attribute whose value indicates whether the domain name is valid 253 according to the server IDN Tables and IDN policies. A value of 254 "1" or "true" means that the domain name is valid according to 255 the server IDN Tables and policies. A value of "0" or "false" 256 means that the domain name is not valid according to the server 257 IDN Tables and policies. The element MAY contain an "idnmap" 258 attribute value that indicates whether the server requires the 259 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 260 domain create of the domain name. A value of "1" or "true" means 261 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 262 required using one of the values. A value of 263 "0" or "false" means that the IDN mapping extension 264 [I-D.ietf-eppext-idnmap] is not required. 265 OPTIONAL reason that the domain name is not valid. 266 If present, this element contains server-specific text to help 267 explain why the domain name is not valid. This text MUST be 268 represented in the response language previously negotiated with 269 the client; an OPTIONAL "lang" attribute MAY be present to 270 identify the language if the negotiated value is something other 271 than the default value of "en" (English). 273 Zero or more OPTIONAL elements 274 that contain the server defined IDN Table Identifier, as defined 275 in Section 2.1, that matches the code points of the 276 element. The MAY be used as the 277 value of the element in the IDN mapping extension 278 [I-D.ietf-eppext-idnmap] for creating the IDN object or MAY be 279 used as the value of the element of the 280 Table Info Form (Section 3.1.2.2) command, as described in 281 Section 3.1.2, to retrieve more information about the IDN Table. 283 Example Domain Check Form response with three IDNs: 285 S: 286 S: 287 S: 288 S: 289 S: Command completed successfully 290 S: 291 S: 292 S: 294 S: 295 S: 296 S: idn1.example 297 S: CHI 298 S: 299 S: 300 S: 301 S: idn2.example 302 S: CHI 303 S: JPN 304 S: 305 S: 306 S: 307 S: idn3.example 308 S: Commingled scripts 309 S: 310 S: 311 S: 312 S: 313 S: 314 S: ABC-12345 315 S: 54321-XYZ 316 S: 317 S: 318 S: 320 3.1.1.2. Table Check Form 322 The Table Check Form is used to check the existence of an IDN 323 Table using the IDN Table Identifier represented by the 324 element. 326 In addition to the standard EPP command elements, the command 327 MUST contain an element that identifies the 328 idnTable namespace. The element in the Table Check 329 Form contains the following child elements: 331 One or more elements that contain 332 the IDN Table Identifier, as defined in Section 2.1, to check for 333 existence. 335 Example Table Check Form command with three IDN 336 Table Identifiers: 338 C: 339 C: 340 C: 341 C: 342 C: 344 C: CHI 345 C: JPN 346 C: INVALID 347 C: 348 C: 349 C: ABC-12345 350 C: 351 C: 353 When a command has been processed successfully, the EPP 354 element MUST contain a child element 355 that identifies the idnTable namespace. The 356 element in the Table Check Form contains the following child 357 elements: 359 One or more elements that contain 360 the IDN Table Identifier, as defined in Section 2.1. The element 361 MUST contain an "exists" attribute whose value indicates the 362 existence of the IDN Table Identifier. A value of "1" or "true" 363 means that the IDN Table Identifier exists. A value of "0" or 364 "false" means that the IDN Table Identifier does not exist. 366 Example Table Check Form response with three IDN 367 Table Identifiers: 369 S: 370 S: 371 S: 372 S: 373 S: Command completed successfully 374 S: 375 S: 376 S: 378 S: CHI 379 S: 380 S: JPN 381 S: 382 S: INVALID 383 S: 384 S: 385 S: 386 S: 387 S: ABC-12345 388 S: 54321-XYZ 389 S: 390 S: 391 S: 393 3.1.2. EPP Command 395 There are three forms of the EPP command: the Domain Info Form 396 (Section 3.1.2.1), the Table Info Form (Section 3.1.2.2), and the 397 List Info Form (Section 3.1.2.3). 399 3.1.2.1. Domain Info Form 401 The Domain Info Form is used to validate the domain name code points 402 against the IDN Tables and IDN policies, and to return the matching 403 IDN Table meta-data. The domain name, as defined in Section 2.2 can 404 be provided as either a U-label or A-label. 406 In addition to the standard EPP command elements, the command 407 MUST contain an element that identifies the 408 idnTable namespace. The element in the Domain Info 409 Form contains the following child elements: 411 The domain name, as defined in Section 2.2, to 412 validate against the IDN Tables and IDN policies, and to retrieve 413 the matching IDN Table meta-data. 415 Example Domain Info Form command using a U-label Domain Name: 417 C: 418 C: 419 C: 420 C: 421 C: 423 C: idn1.example 424 C: 425 C: 426 C: ABC-12345 427 C: 428 C: 430 Example Domain Info Form command using an A-label Domain Name: 432 C: 433 C: 434 C: 435 C: 436 C: 438 C: xn--idn1.example 439 C: 440 C: 441 C: ABC-12345 442 C: 443 C: 445 When an command has been processed successfully, the EPP 446 element MUST contain a child element 447 that identifies the idnTable namespace. The 448 element in the Domain Info Form contains the 449 element that contains the following child elements: 451 The fully qualified name of the domain object, as 452 defined in Section 2.2. The element MUST contain a "valid" 453 attribute whose value indicates whether the domain name is valid 454 according to the server IDN Tables and IDN policies. A value of 455 "1" or "true" means that the domain name is valid according to 456 the server IDN Tables and policies. A value of "0" or "false" 457 means that the domain name is not valid according to the server 458 IDN Tables and policies. The element MAY contain an "idnmap" 459 attribute value that indicates whether the server requires the 460 use of the IDN mapping extension [I-D.ietf-eppext-idnmap] with a 461 domain create of the domain name. A value of "1" or "true" means 462 that the IDN mapping extension [I-D.ietf-eppext-idnmap] is 463 required using one of the 464 values. A value of "0" or "false" means that the IDN mapping 465 extension [I-D.ietf-eppext-idnmap] is not required. 466 or OPTIONAL U-label or A-label 467 form of the domain name value of the element in 468 the opposite form, as defined in Section 2.2. 469 Zero or more OPTIONAL elements 470 that provide the IDN Table meta-data information. The 471 element contains the following child elements: 473 Server defined IDN Table Identifier, as defined 474 in Section 2.1. 475 The type of the IDN Table with the possible 476 values of "language", to reflect a Language IDN Table, and 477 "script", to reflect a Script IDN Table. 478 Server defined description of the IDN 479 Table. This text MUST be represented in the response 480 language previously negotiated with the client; an OPTIONAL 481 "lang" attribute MAY be present to identify the language if 482 the negotiated value is something other than the default 483 value of "en" (English). 484 OPTIONAL boolean flag indicating that 485 domains created using the IDN Table will have IDN variants 486 generated. The management of variants is up to server 487 policy. 489 Example Domain Info Form response for a U-label Domain Name: 491 S: 492 S: 493 S: 494 S: 495 S: Command completed successfully 496 S: 497 S: 498 S: 500 S: 501 S: idn1.example 502 S: 503 S: xn--idn1.example 504 S: 505 S: THAI 506 S: script 507 S: Thai 508 S: 509 S: false 510 S: 511 S: 512 S: 513 S: 514 S: 515 S: ABC-12345 516 S: 54321-XYZ 517 S: 518 S: 519 S: 520 Example Domain Info Form response for an A-label Domain Name: 522 S: 523 S: 524 S: 525 S: 526 S: Command completed successfully 527 S: 528 S: 529 S: 531 S: 532 S: 533 S: xn--idn1.example 534 S: 535 S: idn1.example 536 S: 537 S: CHI 538 S: language 539 S: Chinese (CHI) 540 S: 541 S: true 542 S: 543 S: 544 S: JPN 545 S: language 546 S: Japanese (JPN) 547 S: 548 S: false 549 S: 550 S: 551 S: 552 S: 553 S: 554 S: ABC-12345 555 S: 54321-XYZ 556 S: 557 S: 558 S: 560 3.1.2.2. Table Info Form 562 The Table Info Form is used to retrieve information associated with 563 an IDN Table object. The information provided meta-data about the 564 IDN Table object. 566 In addition to the standard EPP command elements, the command 567 MUST contain an element that identifies the 568 idnTable namespace. The element in the Table Info 569 Form contains the following child elements: 571 Contains the IDN Table Identifier, as defined in 572 Section 2.1, of the IDN Table object to be queried. 574 Example Table Info Form command for the "CHI" IDN 575 Table Identifier, which represents a Language IDN Table: 577 C: 578 C: 579 C: 580 C: 581 C: 583 C: CHI 584 C: 585 C: 586 C: ABC-12345 587 C: 588 C: 590 Example Table Info Form command for the "THAI" IDN 591 Table Identifier, which represents a Script IDN Table: 593 C: 594 C: 595 C: 596 C: 597 C: 599 C: THAI 600 C: 601 C: 602 C: ABC-12345 603 C: 604 C: 606 When an command has been processed successfully, the EPP 607 element MUST contain a child element 608 that identifies the idnTable namespace. The 609 element in the Table Info Form contains the element 610 that contains the following child elements: 612 Server defined IDN Table Identifier, as defined in 613 Section 2.1. 615 The type of the IDN Table with the possible values 616 of "language", to reflect a Language IDN Table, and "script", to 617 reflect a Script IDN Table. 618 Server defined description of the IDN Table. 619 This text MUST be represented in the response language previously 620 negotiated with the client; an OPTIONAL "lang" attribute MAY be 621 present to identify the language if the negotiated value is 622 something other than the default value of "en" (English). 623 Contains the date and time that the IDN Table was 624 created or last updated. 625 OPTIONAL server defined version number of the IDN 626 Table. 627 OPTIONAL effective date for the IDN Table. 628 OPTIONAL boolean flag indicating that domains 629 created using the IDN Table will have IDN variants generated. 630 The management of variants is up to server policy. 631 OPTIONAL URL for downloading the IDN Table with the 632 applicable set of code points and rules. 634 Example Table Info Form response for the "CHI" IDN 635 Table Identifier, which represents a Language IDN Table: 637 S: 638 S: 639 S: 640 S: 641 S: Command completed successfully 642 S: 643 S: 644 S: 646 S: 647 S: CHI 648 S: language 649 S: Chinese (CHI) 650 S: 651 S: 2015-02-04T09:30:00.0Z 652 S: 653 S: 1.0 654 S: 2014-11-24 655 S: 656 S: true 657 S: 658 S: https://www.iana.org/domains/idn-tables/tables/tld_chi_1.0.txt 659 S: 660 S: 661 S: 662 S: 663 S: 664 S: ABC-12345 665 S: 54321-XYZ 666 S: 667 S: 668 S: 669 Example Table Info Form response for the "THAI" IDN 670 Table Identifier, which represents a Script IDN Table: 672 S: 673 S: 674 S: 675 S: 676 S: Command completed successfully 677 S: 678 S: 679 S: 681 S: 682 S: THAI 683 S: script 684 S: Thai 685 S: 2014-08-16T09:20:00.0Z 686 S: 687 S: 1.0 688 S: 2014-11-24 689 S: 690 S: false 691 S: 692 S: https://www.iana.org/domains/idn-tables/tables/tld_thai_1.0.txt 693 S: 694 S: 695 S: 696 S: 697 S: 698 S: ABC-12345 699 S: 54321-XYZ 700 S: 701 S: 702 S: 704 3.1.2.3. List Info Form 706 The List Info Form is used to retrieve the list of IDN Tables 707 supported by the server. The list of IDN Table Identifiers MAY be 708 used to query for the IDN Table information using the Table Info Form 709 (Section 3.1.2.2). 711 In addition to the standard EPP command elements, the command 712 MUST contain an element that identifies the 713 idnTable namespace. The element in the List Info 714 Form contains the following child elements: 716 Empty element used as a marker to the server of the 717 List Info Form to retrieve the list of IDN Tables. 719 Example List Info Form command: 721 C: 722 C: 723 C: 724 C: 725 C: 727 C: 728 C: 729 C: 730 C: ABC-12345 731 C: 732 C: 734 When an command has been processed successfully, the EPP 735 element MUST contain a child element 736 that identifies the idnTable namespace. The 737 element in the List Info Form contains the element 738 that contains the following child elements: 740 Zero or more elements that contain 741 the following child elements: 743 Server defined IDN Table Identifier, as defined 744 in Section 2.1, that is supported by the server. The 745 element value MAY be used as the value of 746 the element value in the Table Info Form 747 (Section 3.1.2.2) command to retrieve the information 748 on the IDN Table. 749 Contains the date and time that the IDN 750 Table was created or last updated. This element can be used 751 to determine whether a client-side cache needs to be 752 refreshed for the IDN Table using the Table Info Form 753 (Section 3.1.2.2). 755 Example List Info Form response that contains three IDN 756 Table Identifiers: 758 S: 759 S: 760 S: 761 S: 762 S: Command completed successfully 763 S: 764 S: 765 S: 767 S: 768 S: 769 S: CHI 770 S: 2015-02-04T09:30:00.0Z 771 S: 772 S: 773 S: 774 S: JPN 775 S: 2015-01-01T09:40:00.0Z 776 S: 777 S: 778 S: 779 S: THAI 780 S: 2014-08-16T09:20:00.0Z 781 S: 782 S: 783 S: 784 S: 785 S: 786 S: 787 S: ABC-12345 788 S: 54321-XYZ 789 S: 790 S: 791 S: 793 3.1.3. EPP Command 795 Transfer semantics do not apply to IDN table objects, so there is no 796 mapping defined for the EPP command. 798 3.2. EPP Transform Commands 800 EPP provides five commands to transform objects: to create 801 an instance of an object, to delete an instance of an 802 object, to extend the validity period of an object, 803 to manage object sponsorship changes, and to 804 change information associated with an object. 806 3.2.1. EPP Command 808 Create semantics do not apply to IDN table objects, so there is no 809 mapping defined for the EPP command. 811 3.2.2. EPP Command 813 Delete semantics do not apply to IDN table objects, so there is no 814 mapping defined for the EPP command. 816 3.2.3. EPP Command 818 Renewal semantics do not apply to IDN table objects, so there is no 819 mapping defined for the EPP command. 821 3.2.4. EPP Command 823 Transfer semantics do not apply to IDN table objects, so there is no 824 mapping defined for the EPP command. 826 3.2.5. EPP Command 828 Update semantics do not apply to IDN table objects, so there is no 829 mapping defined for the EPP command. 831 4. Formal Syntax 833 One schema is presented here that is the EPP IDN Table Mapping 834 schema. 836 The formal syntax presented here is a complete schema representation 837 of the object mapping suitable for automated validation of EPP XML 838 instances. The BEGIN and END tags are not part of the schema; they 839 are used to note the beginning and ending of the schema for URI 840 registration purposes. 842 4.1. IDN Table Mapping Schema 844 BEGIN 845 846 852 853 854 Extensible Provisioning Protocol v1.0 855 IDN Table Mapping. 856 857 859 860 863 866 867 869 872 873 874 875 876 877 879 882 883 884 885 887 888 889 890 893 894 895 896 898 900 901 902 904 907 908 909 910 911 912 913 914 915 917 920 921 923 926 927 928 929 931 933 934 935 936 939 940 941 942 943 944 945 947 950 951 952 953 954 955 956 957 959 962 963 964 965 966 967 969 970 971 973 976 977 978 979 980 981 983 984 985 987 990 991 992 993 994 995 997 998 999 1000 1001 1002 1003 1005 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1021 1024 1025 1026 1027 1028 1029 1031 1032 1034 1035 1037 1040 1041 1042 1043 1044 1045 1046 1047 1049 1052 1053 1054 1056 1057 1059 1062 1063 1064 1065 1066 1067 1069 1070 1071 END 1073 5. IANA Considerations 1074 5.1. XML Namespace 1076 This document uses URNs to describe XML namespaces and XML schemas 1077 conforming to a registry mechanism described in [RFC3688]. The 1078 following URI assignment is requested of IANA: 1080 URI: urn:ietf:params:xml:ns:idnTable-1.0 1082 Registrant Contact: See the "Author's Address" section of this 1083 document. 1085 XML: See the "Formal Syntax" section of this document. 1087 5.2. EPP Extension Registry 1089 The EPP extension described in this document should be registered by 1090 the IANA in the EPP Extension Registry described in [RFC7451]. The 1091 details of the registration are as follows: 1093 Name of Extension: "Extensible Provisioning Protocol (EPP) 1094 Internationalized Domain Name (IDN) Table Mapping" 1096 Document status: Standards Track 1098 Reference: (insert reference to RFC version of this document) 1100 Registrant Name and Email Address: IESG, 1102 TLDs: Any 1104 IPR Disclosure: None 1106 Status: Active 1108 Notes: None 1110 6. Implementation Status 1112 Note to RFC Editor: Please remove this section and the reference to 1113 RFC 7942 [RFC7942] before publication. 1115 This section records the status of known implementations of the 1116 protocol defined by this specification at the time of posting of this 1117 Internet-Draft, and is based on a proposal described in RFC 7942 1118 [RFC7942]. The description of implementations in this section is 1119 intended to assist the IETF in its decision processes in progressing 1120 drafts to RFCs. Please note that the listing of any individual 1121 implementation here does not imply endorsement by the IETF. 1123 Furthermore, no effort has been spent to verify the information 1124 presented here that was supplied by IETF contributors. This is not 1125 intended as, and must not be construed to be, a catalog of available 1126 implementations or their features. Readers are advised to note that 1127 other implementations may exist. 1129 According to RFC 7942 [RFC7942], "this will allow reviewers and 1130 working groups to assign due consideration to documents that have the 1131 benefit of running code, which may serve as evidence of valuable 1132 experimentation and feedback that have made the implemented protocols 1133 more mature. It is up to the individual working groups to use this 1134 information as they see fit". 1136 6.1. Verisign EPP SDK 1138 Organization: Verisign Inc. 1140 Name: Verisign EPP SDK 1142 Description: The Verisign EPP SDK includes both a full client 1143 implementation and a full server stub implementation of draft-gould- 1144 idn-table. 1146 Level of maturity: Production 1148 Coverage: All aspects of the protocol are implemented. 1150 Licensing: GNU Lesser General Public License 1152 Contact: jgould@verisign.com 1154 URL: https://www.verisign.com/en_US/channel-resources/domain- 1155 registry-products/epp-sdks 1157 7. Security Considerations 1159 The mapping extensions described in this document do not provide any 1160 security services beyond those described by EPP [RFC5730] and 1161 protocol layers used by EPP. The security considerations described 1162 in these other specifications apply to this specification as well. 1164 8. References 1166 8.1. Normative References 1168 [I-D.ietf-eppext-idnmap] 1169 Obispo, F., "Internationalized Domain Name Mapping 1170 Extension for the Extensible Provisioning Protocol (EPP)", 1171 draft-ietf-eppext-idnmap-02 (work in progress), January 1172 2015. 1174 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1175 Requirement Levels", BCP 14, RFC 2119, 1176 DOI 10.17487/RFC2119, March 1997, . 1179 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1180 DOI 10.17487/RFC3688, January 2004, . 1183 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1184 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1185 . 1187 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1188 Domain Name Mapping", STD 69, RFC 5731, 1189 DOI 10.17487/RFC5731, August 2009, . 1192 [RFC5890] Klensin, J., "Internationalized Domain Names for 1193 Applications (IDNA): Definitions and Document Framework", 1194 RFC 5890, DOI 10.17487/RFC5890, August 2010, 1195 . 1197 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1198 Code: The Implementation Status Section", BCP 205, 1199 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1200 . 1202 8.2. Informative References 1204 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1205 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1206 February 2015, . 1208 Appendix A. Change History 1210 A.1. Change from 00 to 01 1212 1. Amended XML Namespace section of IANA Considerations, added EPP 1213 Extension Registry section. 1215 A.2. Change from 01 to 02 1217 1. Removed support for returning the idnTable:codePoint and 1218 idnTable:codeRange elements in the table info response based on 1219 the feedback at the Registration Operations Workshop (ROW), held 1220 on March 22, 2015, prior to IETF-92. 1221 2. Fixed info command samples that referenced the element 1222 instead of the element. 1224 A.3. Change from 02 to 03 1226 1. Ping update. 1228 A.4. Change from 03 to 04 1230 1. Ping update. 1232 A.5. Change from 04 to 05 1234 1. Ping update. 1236 A.6. Change from 05 to 06 1238 1. Moved RFC 7451 to an informational reference based on a check 1239 done by the Idnits Tool. 1241 A.7. Change from 06 to 07 1243 1. Added the Implementation Status section. 1245 Authors' Addresses 1247 James Gould 1248 VeriSign, Inc. 1249 12061 Bluemont Way 1250 Reston, VA 20190 1251 US 1253 Email: jgould@verisign.com 1254 URI: http://www.verisigninc.com 1255 Francisco Obispo 1256 Uniregistry Corp. 1257 3-110 Governors Square 1258 Grand Cayman, Grand Cayman KY1-1108 1259 KY 1261 Email: fobispo@uniregistry.com 1262 URI: http://www.uniregistry.com/ 1264 Luis Enrique Munoz 1265 Uniregistry Corp. 1266 3-110 Governors Square 1267 Grand Cayman, Grand Cayman KY1-1108 1268 KY 1270 Email: fobispo@uniregistry.com 1271 URI: http://www.uniregistry.com/