idnits 2.17.1 draft-brown-epp-fees-01.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 (December 9, 2013) is 3789 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Brown 3 Internet-Draft CentralNic Group plc 4 Intended status: Experimental December 9, 2013 5 Expires: June 12, 2014 7 Registry Fee Extension for the Extensible Provisioning Protocol (EPP) 8 draft-brown-epp-fees-01 10 Abstract 12 This document describes an Extensible Provisioning Protocol (EPP) 13 extension mapping for registry fees. 15 Status of this Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on June 12, 2014. 32 Copyright Notice 34 Copyright (c) 2013 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 51 2. Client Actions . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Currency Codes . . . . . . . . . . . . . . . . . . . . . . . . 4 53 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 54 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 4 55 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 56 4.1.2. EPP Command . . . . . . . . . . . . . . . . . . 8 57 4.1.3. EPP Transfer Query Command . . . . . . . . . . . . . . 11 58 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 12 59 4.2.1. EPP Command . . . . . . . . . . . . . . . . . 12 60 4.2.2. EPP Command . . . . . . . . . . . . . . . . . 14 61 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 15 62 4.2.4. EPP Command . . . . . . . . . . . . . . . . 17 63 4.2.5. EPP Command . . . . . . . . . . . . . . . . . 19 64 4.3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 21 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 25 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25 68 8. Change History . . . . . . . . . . . . . . . . . . . . . . . . 26 69 8.1. Change from 0.1 to 0.2 . . . . . . . . . . . . . . . . . . 26 70 8.2. Change from 0.2 to 0.3 . . . . . . . . . . . . . . . . . . 26 71 8.3. Change from 0.3 to 0.4 . . . . . . . . . . . . . . . . . . 26 72 9. Normative References . . . . . . . . . . . . . . . . . . . . . 27 73 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 27 75 1. Introduction 77 Historically, domain name registries have applied a simple fee 78 structure for billable transactions, namely a basic unit price 79 applied to domain , , and RGP restore 80 commands. Given the relatively small number of EPP servers to which 81 EPP clients have been required to connect, it has generally been the 82 case that client operators have been able to obtain details of these 83 fees out-of-band by contacting the server operators. 85 Given the imminent expansion of the DNS namespace, and the 86 proliferation of novel business models, it is now desirable to 87 provide a method for EPP clients to query EPP servers for the fees 88 and credits associated with certain commands and specific objects. 90 This document describes an extension mapping for version 1.0 of the 91 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 92 provides a mechanism by which EPP clients may query the fees and 93 credits associated with various billable transactions. 95 1.1. Conventions Used in This Document 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119 [RFC2119]. 101 XML is case sensitive. Unless stated otherwise, XML specifications 102 and examples provided in this document MUST be interpreted in the 103 character case presented in order to develop a conforming 104 implementation. 106 "fee" is used as an abbreviation for 107 "urn:ietf:params:xml:ns:fee-0.4". The XML namespace prefix "fee" is 108 used, but implementations MUST NOT depend on it and instead employ a 109 proper namespace-aware XML parser and serializer to interpret and 110 output the XML documents. 112 The XML namespace prefix above contains a version number, 113 specifically "0.4". This version number will increment with 114 successive versions of this document, and will reach 1.0 if and when 115 this document is published as an RFC. This permits clients to 116 distinguish which version of the extension a server has implemented. 118 2. Client Actions 120 The element is used in EPP query commands to determine 121 the command to which a fee is applicable. 123 The element values permitted by the server is a matter of repository 124 policy, but MUST include as a minimum the following values: 126 o "create" indicating a command; 128 o "renew" indicating a command; 130 o "transfer" indicating a command; 132 If the server supports the Registry Grace Period Mapping [RFC3915], 133 then the server MUST also support the "restore" value. 135 The element MAY have an OPTIONAL "phase" attribute 136 specifying a launch phase as described in 137 [draft-tan-epp-launchphase]. It may also contain an OPTIONAL 138 "subphase" attribute identifying the custom or sub-phase as described 139 in [draft-tan-epp-launchphase]. 141 3. Currency Codes 143 The element is used to indicate which currency fees 144 are charged in. This value of this element MUST be a three-character 145 currency code from [ISO4217]. 147 Note that ISO 4217 provides the special "XXX" code, which may be used 148 if the server uses a non-currency based system for assessing fees, 149 such as a system of credits. 151 4. EPP Command Mapping 153 A detailed description of the EPP syntax and semantics can be found 154 in [RFC5730]. 156 4.1. EPP Query Commands 158 This extension does not add any elements to the EPP command or 159 response. 161 4.1.1. EPP Command 163 This extension defines additional elements for the EPP 164 command. 166 The command frame MAY contain an element which MAY 167 contain one or more child elements with the following 168 child elements: 170 o A element that contains a domain name. 172 o A element that contains the currency the fee is 173 charged in. 175 o A element identifying the command. 177 o A element that contains the number of units to be 178 added to the registration period of the domain object. 180 Example command: 182 C: 183 C: 184 C: 185 C: 186 C: 188 C: example.com 189 C: example.net 190 C: example.org 191 C: 192 C: 193 C: 194 C: 196 C: example.com 197 C: USD 198 C: create 199 C: 1 200 C: 201 C: 203 C: example.net 204 C: EUR 205 C: 206 C: create 207 C: 2 208 C: 209 C: 211 C: example.org 212 C: EUR 213 C: transfer 214 C: 2 215 C: 216 C: 217 C: ABC-12345 218 C: 219 C: 221 When the server receives a command that includes the 222 extension elements described above, its response MUST contain an 223 element, which MUST contain a child element 224 for each element contained in the command. The MUST contain the following child elements: 227 o A element that contains a domain name which matches 228 the name in the corresponding element. 230 o A element that contains same currency code that 231 appeared in the corresponding element. 233 o A element that contains same action that appeared in 234 the corresponding element. This element MAY have the 235 OPTIONAL "phase" and "subphase" elements, which MUST match the 236 same attributes in the corresponding element. 238 o A element that contains same unit that appeared in 239 the corresponding element. 241 o A element that contains the fee associated with the 242 specified transaction. 244 Example response: 246 S: 247 S: 248 S: 249 S: 250 S: Command completed successfully 251 S: 252 S: 253 S: 255 S: 256 S: example.com 257 S: 258 S: 259 S: example.net 260 S: In use 261 S: 262 S: 263 S: example.org 264 S: In use 265 S: 266 S: 267 S: 268 S: 269 S: 271 S: example.com 272 S: USD 273 S: create 274 S: 1 275 S: 10.00 276 S: 277 S: 279 S: example.net 280 S: EUR 281 S: 282 S: create 283 S: 2 284 S: 5.00 285 S: 286 S: 288 S: example.org 289 S: EUR 290 S: transfer 291 S: 2 292 S: 2.50 293 S: 294 S: 295 S: 296 S: ABC-12345 297 S: 54322-XYZ 298 S: 299 S: 300 S: 302 4.1.2. EPP Command 304 This extension defines additional elements for the EPP 305 command. 307 The command frame MAY contain an element which contains a 308 element with the following child elements: 310 o A element that contains the currency the fee is 311 charged in. 313 o A element identifying the command. 315 o A element that contains the number of units to be 316 added to the registration period of the domain object. 318 Example command: 320 C: 321 C: 322 C: 323 C: 324 C: 326 C: example.com 327 C: 328 C: 329 C: 330 C: 331 C: USD 332 C: create 333 C: 1 334 C: 335 C: 336 C: ABC-12345 337 C: 338 C: 340 When the server receives an command that includes the 341 extension element described above, its response MUST (subject to the 342 exceptions described below) contain an element, which 343 MUST contain a child element. The MUST 344 contain the following child elements: 346 o A element that contains same currency code that 347 appeared in the original element. 349 o A element that contains same action that appeared in 350 the original element. This element MAY have the 351 OPTIONAL "phase" and "subphase" elements, which MUST match the 352 same attributes in the original element. 354 o A element that contains same unit that appeared in 355 the original element. 357 o A element that contains the fee associated with the 358 specified transaction. 360 If the domain name requested in the command is invalid, sponsored by 361 another client, or otherwise ineligible for registration, the server 362 MAY choose to omit the element and return an error 363 instead. 365 Example response: 367 S: 368 S: 369 S: 370 S: 371 S: Command completed successfully 372 S: 373 S: 374 S: 376 S: example.com 377 S: EXAMPLE1-REP 378 S: 379 S: jd1234 380 S: sh8013 381 S: sh8013 382 S: 383 S: ns1.example.com 384 S: ns1.example.net 385 S: 386 S: ns1.example.com 387 S: ns2.example.com 388 S: ClientX 389 S: ClientY 390 S: 1999-04-03T22:00:00.0Z 391 S: ClientX 392 S: 1999-12-03T09:00:00.0Z 393 S: 2005-04-03T22:00:00.0Z 394 S: 2000-04-08T09:00:00.0Z 395 S: 396 S: 2fooBAR 397 S: 398 S: 399 S: 400 S: 401 S: 402 S: USD 403 S: create 404 S: 1 405 S: 10.00 406 S: 407 S: 408 S: 409 S: ABC-12345 410 S: 54322-XYZ 411 S: 412 S: 413 S: 414 Example response where the domain name is not registered: 416 S: 417 S: 418 S: 419 S: 420 S: Object does not exist. 421 S: 422 S: 423 S: 425 S: USD 426 S: create 427 S: 1 428 S: 10.00 429 S: 430 S: 431 S: 432 S: ABC-12345 433 S: 54322-XYZ 434 S: 435 S: 436 S: 438 4.1.3. EPP Transfer Query Command 440 This extension does not add any elements to the EPP query 441 command, but does include elements in the response, when the 442 extension has been selected during a command. 444 When the query command has been processed successfully, 445 the client selected the extension when it logged in, and the client 446 is authorised by the server to view information about the transfer, 447 the server MAY include in the section of the EPP response 448 a element that contains a element containing 449 the fee associated with this command. If no element is 450 included in the response, then no fee has been assessed by the server 451 for this transaction. 453 Example query response: 455 S: 456 S: 457 S: 458 S: 459 S: Command completed successfully; action pending 460 S: 461 S: 462 S: 464 S: example.com 465 S: pending 466 S: ClientX 467 S: 2000-06-08T22:00:00.0Z 468 S: ClientY 469 S: 2000-06-13T22:00:00.0Z 470 S: 2002-09-08T22:00:00.0Z 471 S: 472 S: 473 S: 474 S: 475 S: USD 476 S: 5.00 477 S: 478 S: 479 S: 480 S: ABC-12345 481 S: 54322-XYZ 482 S: 483 S: 484 S: 486 4.2. EPP Transform Commands 488 4.2.1. EPP Command 490 This extension adds elements to both the EPP command and 491 response, when the extension has been selected during a 492 command. 494 When submitting a command to the server, the client MAY 495 include in the element a element which 496 includes the following child elements: 498 o A element containing the currency of the fee that 499 the command will result in. 501 o A element that contains the fee associated with the 502 command. 504 Depending on server policy, the server MAY choose to accept or refuse 505 the command depending on whether the currency and fee provided by the 506 client agrees with the server's own calculation of the fee. If the 507 server chooses to refuse the command due to an incorrect fee, it MUST 508 respond with a 2004 "Parameter value range error". 510 When the command has been processed successfully, and the 511 client selected the extension when it logged in, the server MAY 512 include in the section of the EPP response a element that contains the following child elements: 515 o A element containing the currency of the fee. 517 o A element that contains the fee. 519 If no element is included in the response, then no fee 520 has been assessed by the server for this transaction. 522 Example command: 524 C: 525 C: 526 C: 527 C: 528 C: 530 C: example.com 531 C: 2 532 C: 533 C: ns1.example.net 534 C: ns2.example.net 535 C: 536 C: jd1234 537 C: sh8013 538 C: sh8013 539 C: 540 C: 2fooBAR 541 C: 542 C: 543 C: 544 C: 545 C: 546 C: USD 547 C: 5.00 548 C: 549 C: 550 C: ABC-12345 551 C: 552 C: 554 Example response: 556 S: 557 S: 558 S: 559 S: 560 S: Command completed successfully 561 S: 562 S: 563 S: 565 S: example.com 566 S: 1999-04-03T22:00:00.0Z 567 S: 2001-04-03T22:00:00.0Z 568 S: 569 S: 570 S: 571 S: 572 S: USD 573 S: 5.00 574 S: 575 S: 576 S: 577 S: ABC-12345 578 S: 54321-XYZ 579 S: 580 S: 581 S: 583 4.2.2. EPP Command 585 This extension does not add any elements to the EPP command, 586 but does include elements in the response, when the extension has 587 been selected during the command. 589 When the command has been processed successfully, and the 590 client selected the extension when it logged in, the server MAY 591 include in the section of the EPP response a element that contains the following child elements: 594 o A element containing the currency of the credit. 596 o A element that contains the credit associated with 597 the deletion of the domain. 599 If no element is included in the response, then no 600 credit has been assessed by the server for this transaction. 602 Example response: 604 S: 605 S: 606 S: 607 S: 608 S: Command completed successfully 609 S: 610 S: 611 S: 612 S: USD 613 S: 5.00 614 S: 615 S: 616 S: 617 S: ABC-12345 618 S: 54321-XYZ 619 S: 620 S: 621 S: 623 4.2.3. EPP Command 625 This extension adds elements to both the EPP command and 626 response, when the extension has been selected during a 627 command. 629 When submitting a command to the server, the client MAY 630 include in the element a element which 631 includes the following child elements: 633 o A element containing the currency of the fee that 634 the command will result in. 636 o A element that contains the fee associated with the 637 command. 639 Depending on server policy, the server MAY choose to accept or refuse 640 the command depending on whether the currency and fee provided by the 641 client agrees with the server's own calculation of the fee. If the 642 server chooses to refuse the command due to an incorrect fee, it MUST 643 respond with a 2004 "Parameter value range error". 645 When the command has been processed successfully, and the 646 client selected the extension when it logged in, the server MAY 647 include in the section of the EPP response a element that contains the following child elements: 651 o A element containing the currency of the fee. 653 o A element that contains the fee. 655 If no element is included in the response, then no fee 656 has been assessed by the server for this transaction. 658 Example command: 660 C: 661 C: 662 C: 663 C: 664 C: 666 C: example.com 667 C: 2000-04-03 668 C: 5 669 C: 670 C: 671 C: 672 C: 673 C: USD 674 C: 5.00 675 C: 676 C: 677 C: ABC-12345 678 C: 679 C: 681 Example response: 683 S: 684 S: 685 S: 686 S: 687 S: Command completed successfully 688 S: 689 S: 690 S: 692 S: example.com 693 S: 2005-04-03T22:00:00.0Z 694 S: 695 S: 696 S: 697 S: 698 S: USD 699 S: 5.00 700 S: 701 S: 702 S: 703 S: ABC-12345 704 S: 54322-XYZ 705 S: 706 S: 707 S: 709 4.2.4. EPP Command 711 This extension adds elements to both the EPP command and 712 response, when the value of the "op" attribute of the 713 command element is "request", and the extension has been selected 714 during the command. 716 When submitting a command to the server, the client MAY 717 include in the element a element which 718 includes the following child elements: 720 o A element containing the currency of the fee that 721 the command will result in. 723 o A element that contains the fee associated with the 724 command. 726 Depending on server policy, the server MAY choose to accept or refuse 727 the command depending on whether the currency and fee provided by the 728 client agrees with the server's own calculation of the fee. If the 729 server chooses to refuse the command due to an incorrect fee, it MUST 730 respond with a 2004 "Parameter value range error". 732 When the command has been processed successfully, and the 733 client selected the extension when it logged in, the server MAY 734 include in the section of the EPP response a element that contains the following child elements: 737 o A element containing the currency of the fee. 739 o A element that contains the fee. 741 If no element is included in the response, then no 742 fee has been assessed by the server for this transaction. 744 Example command: 746 C: 747 C: 748 C: 749 C: 750 C: 752 C: example.com 753 C: 1 754 C: 755 C: 2fooBAR 756 C: 757 C: 758 C: 759 C: 760 C: 761 C: USD 762 C: 5.00 763 C: 764 C: 765 C: ABC-12345 766 C: 767 C: 769 Example response: 771 S: 772 S: 773 S: 774 S: 775 S: Command completed successfully; action pending 776 S: 777 S: 778 S: 780 S: example.com 781 S: pending 782 S: ClientX 783 S: 2000-06-08T22:00:00.0Z 784 S: ClientY 785 S: 2000-06-13T22:00:00.0Z 786 S: 2002-09-08T22:00:00.0Z 787 S: 788 S: 789 S: 790 S: 791 S: USD 792 S: 5.00 793 S: 794 S: 795 S: 796 S: ABC-12345 797 S: 54322-XYZ 798 S: 799 S: 800 S: 802 4.2.5. EPP Command 804 This extension adds elements to both the EPP command and 805 response, when the extension has been selected during a has 806 been selected during the command. 808 When submitting a command to the server, the client MAY 809 include in the element a element which 810 includes the following child elements: 812 o A element containing the currency of the fee that 813 the command will result in. 815 o A element that contains the fee associated with the 816 command. 818 Depending on server policy, the server MAY choose to accept or refuse 819 the command depending on whether the currency and fee provided by the 820 client agrees with the server's own calculation of the fee. If the 821 server chooses to refuse the command due to an incorrect fee, it MUST 822 respond with a 2004 "Parameter value range error". 824 When the command has been processed successfully, and the 825 client selected the extension when it logged in, the server MAY 826 include in the section of the EPP response a 827 element that contains the following child elements: 829 o A element containing the currency of the fee. 831 o A element that contains the fee. 833 If no element is included in the response, then no fee 834 has been assessed by the server for this transaction. 836 Example command: 838 C: 839 C: 840 C: 841 C: 842 C: 844 C: example.com 845 C: 846 C: sh8013 847 C: 848 C: 849 C: 850 C: 851 C: 852 C: USD 853 C: 5.00 854 C: 855 C: 856 C: ABC-12345 857 C: 858 C: 860 Example response: 862 S: 863 S: 864 S: 865 S: 866 S: Command completed successfully 867 S: 868 S: 869 S: 870 S: USD 871 S: 5.00 872 S: 873 S: 874 S: 875 S: ABC-12345 876 S: 54321-XYZ 877 S: 878 S: 879 S: 881 4.3. Formal Syntax 883 An EPP object mapping is specified in XML Schema notation. The 884 formal syntax presented here is a complete schema representation of 885 the object mapping suitable for automated validation of EPP XML 886 instances. 888 Copyright (c) 2013 IETF Trust and the persons identified as authors 889 of the code. All rights reserved. 891 Redistribution and use in source and binary forms, with or without 892 modification, are permitted provided that the following conditions 893 are met: 895 o Redistributions of source code must retain the above copyright 896 notice, this list of conditions and the following disclaimer. 898 o Redistributions in binary form must reproduce the above copyright 899 notice, this list of conditions and the following disclaimer in 900 the documentation and/or other materials provided with the 901 distribution. 903 o Neither the name of Internet Society, IETF or IETF Trust, nor the 904 names of specific contributors, may be used to endorse or promote 905 products derived from this software without specific prior written 906 permission. 908 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 909 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 910 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 911 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 912 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 913 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 914 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 915 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 916 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 917 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 918 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 920 BEGIN 921 922 929 930 932 933 Extensible Provisioning Protocol 934 v1.0 domain name extension schema for 935 fee information. 936 938 941 942 943 944 945 946 947 948 949 950 951 952 953 955 958 959 960 961 962 963 964 965 967 970 971 972 973 974 975 976 977 978 980 983 984 985 986 987 988 989 991 994 995 996 997 998 999 1000 1001 1003 1006 1007 1008 1009 1010 1011 1013 1016 1017 1018 1019 1020 1021 1023 1026 1027 1028 1029 1030 1031 1033 1036 1037 1038 1039 1040 1042 1043 1044 1045 1046 1047 1048 1049 1051 1052 1053 1054 1055 1056 1058 1059 1060 1061 1062 END 1064 5. Security Considerations 1066 The mapping extensions described in this document do not provide any 1067 security services beyond those described by EPP [RFC5730], the EPP 1068 domain name mapping [RFC5731], and protocol layers used by EPP. The 1069 security considerations described in these other specifications apply 1070 to this specification as well. 1072 6. IANA Considerations 1074 This document uses URNs to describe XML namespaces and XML schemas 1075 conforming to a registry mechanism described in [RFC3688]. Two URI 1076 assignments were requested and have been registered by the IANA. 1078 Registration request for the digital signature namespace: 1080 URI: urn:ietf:params:xml:ns:fee-0.4 1082 Registrant Contact: See the "Author's Address" section of this 1083 document. 1085 XML: None. Namespace URIs do not represent an XML specification. 1087 Registration request for the EPP fee XML schema: 1089 URI: urn:ietf:params:xml:ns:fee-0.4 1091 Registrant Contact: See the "Author's Address" section of this 1092 document. 1094 XML: See the "Formal Syntax" section of this document. 1096 7. Acknowledgements 1098 The author wishes to thank the following persons for their feedback 1099 and suggestions: 1101 o James Gould of Verisign 1103 o Luis Munoz of ISC 1105 o Michael Young of Architelos 1107 o Ben Levac and Jeff Eckhaus of Demand Media 1109 8. Change History 1111 8.1. Change from 0.1 to 0.2 1113 1. Added note about the use of the "XXX" code for non-currency 1114 transactions. 1116 2. Added phase attribute to the element, and normative 1117 reference to [draft-tan-epp-launchphase]. 1119 3. Added description of extension to transform and transfer query 1120 commands. 1122 4. Added Acknowledgements and Change History sections. 1124 8.2. Change from 0.2 to 0.3 1126 1. Added the subphase attribute to the element. 1128 2. Removed the enumeration for the element so any token 1129 may be used. 1131 3. Moved the fee lookup command from to . 1133 4. Added an extension to the command to return credit 1134 information. 1136 5. Changed MUSTs to MAYs so that the response extension elements can 1137 be omitted where no fee is applicable. 1139 6. Update of introductory text. 1141 8.3. Change from 0.3 to 0.4 1143 1. Restore the command extension; either or 1144 can be used. 1146 2. added extension elements for , , and 1147 so that the server can reject the command if the fee is 1148 incorrect. 1150 9. Normative References 1152 [ISO4217] International Organization for Standardization, "ISO 4217: 1153 2008, Codes for the representation of currencies and 1154 funds", 2008. 1156 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1157 Requirement Levels", BCP 14, RFC 2119, March 1997. 1159 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1160 January 2004. 1162 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 1163 the Extensible Provisioning Protocol (EPP)", RFC 3915, 1164 September 2004. 1166 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1167 STD 69, RFC 5730, August 2009. 1169 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1170 Domain Name Mapping", STD 69, RFC 5731, August 2009. 1172 [draft-tan-epp-launchphase] 1173 Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping 1174 for the Extensible Provisioning Protocol (EPP)", 2013. 1176 Author's Address 1178 Gavin Brown 1179 CentralNic Group plc 1180 35-39 Moorgate 1181 London, England EC2R 6AR 1182 GB 1184 Phone: +44 20 33 88 0600 1185 Email: gavin.brown@centralnic.com 1186 URI: https://www.centralnic.com