idnits 2.17.1 draft-hollenbeck-rfc4932bis-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 : ---------------------------------------------------------------------------- == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. -- The draft header indicates that this document obsoletes RFC4932, but the abstract doesn't seem to directly say this. It does mention RFC4932 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 14, 2009) is 5453 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) == Outdated reference: A later version (-02) exists of draft-hollenbeck-rfc4930bis-01 -- Possible downref: Normative reference to a draft: ref. 'I-D.hollenbeck-rfc4930bis' ** Downref: Normative reference to an Unknown state RFC: RFC 952 -- Obsolete informational reference (is this intentional?): RFC 3490 (Obsoleted by RFC 5890, RFC 5891) -- Obsolete informational reference (is this intentional?): RFC 4932 (Obsoleted by RFC 5732) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Hollenbeck 3 Internet-Draft VeriSign, Inc. 4 Obsoletes: 4932 (if approved) May 14, 2009 5 Intended status: Standards Track 6 Expires: November 15, 2009 8 Extensible Provisioning Protocol (EPP) Host Mapping 9 draft-hollenbeck-rfc4932bis-01 11 Status of This Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on November 15, 2009. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license-info). 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 This document describes an Extensible Provisioning Protocol (EPP) 48 mapping for the provisioning and management of Internet host names 49 stored in a shared central repository. Specified in XML, the mapping 50 defines EPP command syntax and semantics as applied to host names. 51 This document is intended to obsolete RFC 4932. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Relationship of Host Objects and Domain Objects . . . . . 3 57 1.2. Conventions Used in This Document . . . . . . . . . . . . 3 58 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 59 2.1. Host Names . . . . . . . . . . . . . . . . . . . . . . . . 4 60 2.2. Client Identifiers . . . . . . . . . . . . . . . . . . . . 4 61 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 4 62 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 63 2.5. IP Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 64 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 65 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 6 66 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 6 67 3.1.2. EPP Command . . . . . . . . . . . . . . . . . . 8 68 3.1.3. EPP Query Command . . . . . . . . . . . . . 11 69 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 11 70 3.2.1. EPP Command . . . . . . . . . . . . . . . . . 12 71 3.2.2. EPP Command . . . . . . . . . . . . . . . . . 14 72 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 15 73 3.2.4. EPP Command . . . . . . . . . . . . . . . . 15 74 3.2.5. EPP Command . . . . . . . . . . . . . . . . . 16 75 3.3. Offline Review of Requested Actions . . . . . . . . . . . 18 76 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20 77 5. Internationalization Considerations . . . . . . . . . . . . . 25 78 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 79 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 80 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 81 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 82 9.1. Normative References . . . . . . . . . . . . . . . . . . . 28 83 9.2. Informative References . . . . . . . . . . . . . . . . . . 29 84 Appendix A. Changes from RFC 4932 . . . . . . . . . . . . . . . . 29 86 1. Introduction 88 This document describes an Internet host name mapping for version 1.0 89 of the Extensible Provisioning Protocol (EPP). This mapping is 90 specified using the Extensible Markup Language (XML) 1.0 as described 91 in [W3C.REC-xml-20040204] and XML Schema notation as described in 92 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. 93 This document is intended to obsolete RFC 4932 [RFC4932]. 95 [I-D.hollenbeck-rfc4930bis] provides a complete description of EPP 96 command and response structures. A thorough understanding of the 97 base protocol specification is necessary to understand the mapping 98 described in this document. 100 XML is case sensitive. Unless stated otherwise, XML specifications 101 and examples provided in this document MUST be interpreted in the 102 character case presented to develop a conforming implementation. 104 1.1. Relationship of Host Objects and Domain Objects 106 This document assumes that host name objects have a subordinate 107 relationship to a superordinate domain name object. For example, 108 host name "ns1.example.com" has a subordinate relationship to domain 109 name "example.com". EPP actions (such as object transfers) that do 110 not preserve this relationship MUST be explicitly disallowed. 112 A host name object can be created in a repository for which no 113 superordinate domain name object exists. For example, host name 114 "ns1.example.com" can be created in the ".example" repository so that 115 DNS domains in ".example" can be delegated to the host. Such hosts 116 are described as "external" hosts in this specification since the 117 name of the host does not belong to the name space of the repository 118 in which the host is being used for delegation purposes. 120 Whether a host is external or internal relates to the repository in 121 which the host is being used for delegation purposes. Whether or not 122 an internal host is subordinate relates to a domain within the 123 repository. For example, host ns1.example1.com is a subordinate host 124 of domain example1.com, but it is not a subordinate host of domain 125 example2.com. ns1.example1.com can be used as a name server for 126 example2.com. In this case, ns1.example1.com MUST be treated as an 127 internal host, subject to the rules governing operations on 128 subordinate hosts within the same repository. 130 1.2. Conventions Used in This Document 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 134 document are to be interpreted as described in [RFC2119]. 136 In examples, "C:" represents lines sent by a protocol client and "S:" 137 represents lines returned by a protocol server. Indentation and 138 white space in examples are provided only to illustrate element 139 relationships and are not a REQUIRED feature of this protocol. 141 2. Object Attributes 143 An EPP host object has attributes and associated values that can be 144 viewed and modified by the sponsoring client or the server. This 145 section describes each attribute type in detail. The formal syntax 146 for the attribute values described here can be found in the "Formal 147 Syntax" section of this document and in the appropriate normative 148 references. 150 2.1. Host Names 152 The syntax for host names described in this document MUST conform to 153 [RFC0952] as updated by [RFC1123]. At the time of this writing, RFC 154 3490 [RFC3490] describes a standard to use certain ASCII name labels 155 to represent non-ASCII name labels. These conformance requirements 156 might change in the future as a result of progressing work in 157 developing standards for internationalized host names. 159 2.2. Client Identifiers 161 All EPP clients are identified by a server-unique identifier. Client 162 identifiers conform to the "clIDType" syntax described in 163 [I-D.hollenbeck-rfc4930bis]. 165 2.3. Status Values 167 A host object MUST always have at least one associated status value. 168 Status values MAY be set only by the client that sponsors a host 169 object and by the server on which the object resides. A client can 170 change the status of a host object using the EPP command. 171 Each status value MAY be accompanied by a string of human-readable 172 text that describes the rationale for the status applied to the 173 object. 175 A client MUST NOT alter status values set by the server. A server 176 MAY alter or override status values set by a client subject to local 177 server policies. The status of an object MAY change as a result of 178 either a client-initiated transform command or an action performed by 179 a server operator. 181 Status values that can be added or removed by a client are prefixed 182 with "client". Corresponding status values that can be added or 183 removed by a server are prefixed with "server". Status values that 184 do not begin with either "client" or "server" are server-managed. 186 Status Value Descriptions: 188 - clientDeleteProhibited, serverDeleteProhibited 190 Requests to delete the object MUST be rejected. 192 - clientUpdateProhibited, serverUpdateProhibited 194 Requests to update the object (other than to remove this status) 195 MUST be rejected. 197 - linked 199 The host object has at least one active association with another 200 object, such as a domain object. Servers SHOULD provide services 201 to determine existing object associations. 203 - ok 205 This is the normal status value for an object that has no pending 206 operations or prohibitions. This value is set and removed by the 207 server as other status values are added or removed. 209 - pendingCreate, pendingDelete, pendingTransfer, pendingUpdate 211 A transform command has been processed for the object (or in the 212 case of a command, for the host object's superordinate 213 domain object), but the action has not been completed by the 214 server. Server operators can delay action completion for a 215 variety of reasons, such as to allow for human review or third- 216 party action. A transform command that is processed, but whose 217 requested action is pending, is noted with response code 1001. 219 When the requested action has been completed, the pendingCreate, 220 pendingDelete, pendingTransfer, or pendingUpdate status value MUST be 221 removed. All clients involved in the transaction MUST be notified 222 using a service message that the action has been completed and that 223 the status of the object has changed. 225 "ok" status MAY only be combined with "linked" status. 227 "linked" status MAY be combined with any status. 229 "pendingDelete" status MUST NOT be combined with either 230 "clientDeleteProhibited" or "serverDeleteProhibited" status. 232 "pendingUpdate" status MUST NOT be combined with either 233 "clientUpdateProhibited" or "serverUpdateProhibited" status. 235 The pendingCreate, pendingDelete, pendingTransfer, and pendingUpdate 236 status values MUST NOT be combined with each other. 238 Other status combinations not expressly prohibited MAY be used. 240 2.4. Dates and Times 242 Date and time attribute values MUST be represented in Universal 243 Coordinated Time (UTC) using the Gregorian calendar. The extended 244 date-time form using upper case "T" and "Z" characters defined in 245 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 246 values as XML Schema does not support truncated date-time forms or 247 lower case "T" and "Z" characters. 249 2.5. IP Addresses 251 The syntax for IPv4 addresses described in this document MUST conform 252 to [RFC0791]. The syntax for IPv6 addresses described in this 253 document MUST conform to [RFC4291]. Practical considerations for 254 publishing IPv6 address information in zone files are documented in 255 [RFC2874] and [RFC3596]. A server MAY reject IP addresses that have 256 not been allocated for public use by IANA. When a host object is 257 provisioned for use as a DNS name server, IP addresses SHOULD be 258 required only as needed to generate DNS glue records. 260 3. EPP Command Mapping 262 A detailed description of the EPP syntax and semantics can be found 263 in [I-D.hollenbeck-rfc4930bis]. The command mappings described here 264 are specifically for use in provisioning and managing Internet host 265 names via EPP. 267 3.1. EPP Query Commands 269 EPP provides two commands to retrieve host information: to 270 determine if a host object can be provisioned within a repository, 271 and to retrieve detailed information associated with a host 272 object. 274 3.1.1. EPP Command 276 The EPP command is used to determine if an object can be 277 provisioned within a repository. It provides a hint that allows a 278 client to anticipate the success or failure of provisioning an object 279 using the command as object provisioning requirements are 280 ultimately a matter of server policy. 282 In addition to the standard EPP command elements, the command 283 MUST contain a element that identifies the host 284 namespace. The element contains the following child 285 elements: 287 - One or more elements that contain the fully qualified 288 names of the host objects to be queried. 290 Example command: 292 C: 293 C: 294 C: 295 C: 296 C: 298 C: ns1.example.com 299 C: ns2.example.com 300 C: ns3.example.com 301 C: 302 C: 303 C: ABC-12345 304 C: 305 C: 307 When a command has been processed successfully, the EPP 308 element MUST contain a child element that 309 identifies the host namespace. The element contains 310 one or more elements that contain the following child 311 elements: 313 - A element that contains the fully qualified name of 314 the queried host object. This element MUST contain an "avail" 315 attribute whose value indicates object availability (can it be 316 provisioned or not) at the moment the command was 317 completed. A value of "1" or "true" means that the object can be 318 provisioned. A value of "0" or "false" means that the object 319 cannot be provisioned. 321 - An OPTIONAL element that MAY be provided when an 322 object cannot be provisioned. If present, this element contains 323 server-specific text to help explain why the object cannot be 324 provisioned. This text MUST be represented in the response 325 language previously negotiated with the client; an OPTIONAL "lang" 326 attribute MAY be present to identify the language if the 327 negotiated value is something other than the default value of "en" 328 (English). 330 Example response: 332 S: 333 S: 334 S: 335 S: 336 S: Command completed successfully 337 S: 338 S: 339 S: 341 S: 342 S: ns1.example.com 343 S: 344 S: 345 S: ns2.example2.com 346 S: In use 347 S: 348 S: 349 S: ns3.example3.com 350 S: 351 S: 352 S: 353 S: 354 S: ABC-12345 355 S: 54322-XYZ 356 S: 357 S: 358 S: 360 An EPP error response MUST be returned if a command cannot be 361 processed for any reason. 363 3.1.2. EPP Command 365 The EPP command is used to retrieve information associated 366 with a host object. In addition to the standard EPP command 367 elements, the command MUST contain a element that 368 identifies the host namespace. The element contains the 369 following child elements: 371 - A element that contains the fully qualified name of 372 the host object for which information is requested. 374 Example command: 376 C: 377 C: 378 C: 379 C: 380 C: 382 C: ns1.example.com 383 C: 384 C: 385 C: ABC-12345 386 C: 387 C: 389 When an command has been processed successfully, the EPP 390 element MUST contain a child element that 391 identifies the host namespace. The element contains 392 the following child elements: 394 - A element that contains the fully qualified name of 395 the host object. 397 - A element that contains the Repository Object 398 IDentifier assigned to the host object when the object was 399 created. 401 - One or more elements that describe the status of the 402 host object. 404 - Zero or more elements that contain the IP addresses 405 associated with the host object. 407 - A element that contains the identifier of the 408 sponsoring client. 410 - A element that contains the identifier of the client 411 that created the host object. 413 - A element that contains the date and time of host 414 object creation. 416 - A element that contains the identifier of the client 417 that last updated the host object. This element MUST NOT be 418 present if the host object has never been modified. 420 - A element that contains the date and time of the 421 most recent host object modification. This element MUST NOT be 422 present if the host object has never been modified. 424 - A element that contains the date and time of the 425 most recent successful host object transfer. This element MUST 426 NOT be provided if the host object has never been transferred. 427 Note that host objects MUST NOT be transferred directly; host 428 objects MUST be transferred implicitly when the host object's 429 superordinate domain object is transferred. Host objects that are 430 subject to transfer when transferring a domain object are listed 431 in the response to an EPP command performed on the domain 432 object. 434 Example response: 436 S: 437 S: 438 S: 439 S: 440 S: Command completed successfully 441 S: 442 S: 443 S: 445 S: ns1.example.com 446 S: NS1_EXAMPLE1-REP 447 S: 448 S: 449 S: 192.0.2.2 450 S: 192.0.2.29 451 S: 1080:0:0:0:8:800:200C:417A 452 S: ClientY 453 S: ClientX 454 S: 1999-04-03T22:00:00.0Z 455 S: ClientX 456 S: 1999-12-03T09:00:00.0Z 457 S: 2000-04-08T09:00:00.0Z 458 S: 459 S: 460 S: 461 S: ABC-12345 462 S: 54322-XYZ 463 S: 464 S: 465 S: 467 An EPP error response MUST be returned if an command cannot be 468 processed for any reason. 470 3.1.3. EPP Query Command 472 Transfer semantics do not directly apply to host objects, so there is 473 no mapping defined for the EPP query command. 475 3.2. EPP Transform Commands 477 EPP provides three commands to transform host objects: to 478 create an instance of a host object, to delete an instance 479 of a host object, and to change information associated with 480 a host object. This document does not define host object mappings 481 for the EPP and commands. 483 Transform commands are typically processed and completed in real 484 time. Server operators MAY receive and process transform commands, 485 but defer completing the requested action if human or third-party 486 review is required before the requested action can be completed. In 487 such situations, the server MUST return a 1001 response code to the 488 client to note that the command has been received and processed, but 489 the requested action is pending. The server MUST also manage the 490 status of the object that is the subject of the command to reflect 491 the initiation and completion of the requested action. Once the 492 action has been completed, all clients involved in the transaction 493 MUST be notified using a service message that the action has been 494 completed and that the status of the object has changed. Other 495 notification methods MAY be used in addition to the required service 496 message. 498 Server operators SHOULD confirm that a client is authorized to 499 perform a transform command on a given object. Any attempt to 500 transform an object by an unauthorized client MUST be rejected, and 501 the server MUST return a 2201 response code to the client to note 502 that the client lacks privileges to execute the requested command. 504 3.2.1. EPP Command 506 The EPP command provides a transform operation that allows a 507 client to create a host object. In addition to the standard EPP 508 command elements, the command MUST contain a 509 element that identifies the host namespace. The 510 element contains the following child elements: 512 - A element that contains the fully qualified name of 513 the host object to be created. 515 - Zero or more elements that contain the IP addresses to 516 be associated with the host. Each element MAY contain an "ip" 517 attribute to identify the IP address format. Attribute value "v4" 518 is used to note IPv4 address format. Attribute value "v6" is used 519 to note IPv6 address format. If the "ip" attribute is not 520 specified, "v4" is the default attribute value. 522 Hosts can be provisioned for use as name servers in the Domain Name 523 System (DNS), described in [RFC1034] and [RFC1035]. Hosts 524 provisioned as name servers might be subject to server operator 525 policies that require or prohibit specification of IP addresses 526 depending on the name of the host and the name space in which the 527 server will be used as a name server. When provisioned for use as a 528 name server, IP addresses are REQUIRED only as needed to produce DNS 529 glue records. For example, if the server is authoritative for the 530 "com" name space and the name of the server is "ns1.example.net", the 531 server is not required to produce DNS glue records for the name 532 server and IP addresses for the server are not required by the DNS. 534 If the host name exists in a name space for which the server is 535 authoritative, then the superordinate domain of the host MUST be 536 known to the server before the host object can be created. 538 Example command: 540 C: 541 C: 542 C: 543 C: 544 C: 546 C: ns1.example.com 547 C: 192.0.2.2 548 C: 192.0.2.29 549 C: 1080:0:0:0:8:800:200C:417A 550 C: 551 C: 552 C: ABC-12345 553 C: 554 C: 556 When a command has been processed successfully, the EPP 557 element MUST contain a child element that 558 identifies the host namespace. The element contains 559 the following child elements: 561 - A element that contains the fully qualified name of 562 the host object. 564 - A element that contains the date and time of host 565 object creation. 567 Example response: 569 S: 570 S: 571 S: 572 S: 573 S: Command completed successfully 574 S: 575 S: 576 S: 578 S: ns1.example.com 579 S: 1999-04-03T22:00:00.0Z 580 S: 581 S: 582 S: 583 S: ABC-12345 584 S: 54322-XYZ 585 S: 586 S: 587 S: 589 An EPP error response MUST be returned if a command cannot 590 be processed for any reason. 592 3.2.2. EPP Command 594 The EPP command provides a transform operation that allows a 595 client to delete a host object. In addition to the standard EPP 596 command elements, the command MUST contain a 597 element that identifies the host namespace. The 598 element contains the following child elements: 600 - A element that contains the fully qualified name of 601 the host object to be deleted. 603 A host name object SHOULD NOT be deleted if the host object is 604 associated with any other object. For example, if the host object is 605 associated with a domain object, the host object SHOULD NOT be 606 deleted until the existing association has been broken. Deleting a 607 host object without first breaking existing associations can cause 608 DNS resolution failure for domain objects that refer to the deleted 609 host object. 611 Example command: 613 C: 614 C: 615 C: 616 C: 617 C: 619 C: ns1.example.com 620 C: 621 C: 622 C: ABC-12345 623 C: 624 C: 626 When a command has been processed successfully, a server 627 MUST respond with an EPP response with no element. 629 Example response: 631 S: 632 S: 633 S: 634 S: 635 S: Command completed successfully 636 S: 637 S: 638 S: ABC-12345 639 S: 54321-XYZ 640 S: 641 S: 642 S: 644 An EPP error response MUST be returned if a command cannot 645 be processed for any reason. 647 3.2.3. EPP Command 649 Renewal semantics do not apply to host objects, so there is no 650 mapping defined for the EPP command. 652 3.2.4. EPP Command 654 Transfer semantics do not directly apply to host objects, so there is 655 no mapping defined for the EPP command. Host objects are 656 subordinate to an existing superordinate domain object, and as such 657 they are subject to transfer when a domain object is transferred. 659 3.2.5. EPP Command 661 The EPP command provides a transform operation that allows a 662 client to modify the attributes of a host object. In addition to the 663 standard EPP command elements, the command MUST contain a 664 element that identifies the host namespace. The element contains the following child elements: 667 - A element that contains the fully qualified name of 668 the host object to be updated. 670 - An OPTIONAL element that contains attribute values to 671 be added to the object. 673 - An OPTIONAL element that contains attribute values to 674 be removed from the object. 676 - An OPTIONAL element that contains object attribute 677 values to be changed. 679 At least one , , or element MUST be 680 provided if the command is not being extended. All of these elements 681 MAY be omitted if an extension is present. The 682 and elements contain the following child elements: 684 - One or more elements that contain IP addresses to be 685 associated with or removed from the host object. IP address 686 restrictions described in the command mapping apply here 687 as well. 689 - One or more elements that contain status values to 690 be associated with or removed from the object. When specifying a 691 value to be removed, only the attribute value is significant; 692 element text is not required to match a value for removal. 694 A element contains the following child elements: 696 - A element that contains a new fully qualified host 697 name by which the host object will be known. 699 Host name changes MAY require the addition or removal of IP addresses 700 to be accepted by the server. IP address association MAY be subject 701 to server policies for provisioning hosts as name servers. 703 Host name changes can have an impact on associated objects that refer 704 to the host object. A host name change SHOULD NOT require additional 705 updates of associated objects to preserve existing associations, with 706 one exception: changing an external host object that has associations 707 with objects that are sponsored by a different client. Attempts to 708 update such hosts directly MUST fail with EPP error code 2305. The 709 change can be provisioned by creating a new external host with a new 710 name and needed new attributes and subsequently updating the other 711 objects sponsored by the client. 713 Example command: 715 C: 716 C: 717 C: 718 C: 719 C: 721 C: ns1.example.com 722 C: 723 C: 192.0.2.22 724 C: 725 C: 726 C: 727 C: 1080:0:0:0:8:800:200C:417A 728 C: 729 C: 730 C: ns2.example.com 731 C: 732 C: 733 C: 734 C: ABC-12345 735 C: 736 C: 738 When an command has been processed successfully, a server 739 MUST respond with an EPP response with no element. 741 Example response: 743 S: 744 S: 745 S: 746 S: 747 S: Command completed successfully 748 S: 749 S: 750 S: ABC-12345 751 S: 54321-XYZ 752 S: 753 S: 754 S: 755 An EPP error response MUST be returned if an command could 756 not be processed for any reason. 758 3.3. Offline Review of Requested Actions 760 Commands are processed by a server in the order they are received 761 from a client. Though an immediate response confirming receipt and 762 processing of the command is produced by the server, a server 763 operator MAY perform an offline review of requested transform 764 commands before completing the requested action. In such situations, 765 the response from the server MUST clearly note that the transform 766 command has been received and processed, but the requested action is 767 pending. The status of the corresponding object MUST clearly reflect 768 processing of the pending action. The server MUST notify the client 769 when offline processing of the action has been completed. 771 Examples describing a command that requires offline review 772 are included here. Note the result code and message returned in 773 response to the command. 775 S: 776 S: 777 S: 778 S: 779 S: Command completed successfully; action pending 780 S: 781 S: 782 S: 784 S: ns1.example.com 785 S: 1999-04-03T22:00:00.0Z 786 S: 787 S: 788 S: 789 S: ABC-12345 790 S: 54322-XYZ 791 S: 792 S: 793 S: 795 The status of the host object after returning this response MUST 796 include "pendingCreate". The server operator reviews the request 797 offline, and informs the client of the outcome of the review either 798 by queuing a service message for retrieval via the command or 799 by using an out-of-band mechanism to inform the client of the 800 request. 802 The service message MUST contain text in the , , 803 element that describes the notification. In addition, the EPP 804 element MUST contain a child element that 805 identifies the host namespace. The element contains 806 the following child elements: 808 - A element that contains the fully qualified name of 809 the host object. The element contains a REQUIRED 810 "paResult" attribute. A positive boolean value indicates that the 811 request has been approved and completed. A negative boolean value 812 indicates that the request has been denied and the requested 813 action has not been taken. 815 - A element that contains the client transaction 816 identifier and server transaction identifier returned with the 817 original response to process the command. The client transaction 818 identifier is OPTIONAL and will only be returned if the client 819 provided an identifier with the original command. 821 - A element that contains the date and time describing 822 when review of the requested action was completed. 824 Example "review completed" service message: 826 S: 827 S: 828 S: 829 S: 830 S: Command completed successfully; ack to dequeue 831 S: 832 S: 833 S: 1999-04-04T22:01:00.0Z 834 S: Pending action completed successfully. 835 S: 836 S: 837 S: 839 S: ns1.example.com 840 S: 841 S: ABC-12345 842 S: 54322-XYZ 843 S: 844 S: 1999-04-04T22:00:00.0Z 845 S: 846 S: 847 S: 848 S: BCD-23456 849 S: 65432-WXY 850 S: 851 S: 852 S: 854 4. Formal Syntax 856 An EPP object mapping is specified in XML Schema notation. The 857 formal syntax presented here is a complete schema representation of 858 the object mapping suitable for automated validation of EPP XML 859 instances. The BEGIN and END tags are not part of the schema; they 860 are used to note the beginning and ending of the schema for URI 861 registration purposes. 863 BEGIN 864 866 873 876 877 879 880 881 Extensible Provisioning Protocol v1.0 882 host provisioning schema. 883 884 886 889 890 891 892 893 895 898 899 900 901 903 904 906 907 908 909 911 912 913 915 916 917 918 919 920 921 922 923 924 925 926 928 931 932 933 934 935 937 940 941 942 944 945 946 949 950 951 952 954 956 958 959 961 964 965 966 968 970 971 973 976 977 978 979 980 982 985 986 987 988 990 993 994 995 997 998 1000 1001 1002 1003 1005 1006 1008 1009 1010 1011 1013 1014 1015 1017 1020 1021 1022 1023 1024 1025 1027 1030 1031 1032 1033 1034 1036 1038 1039 1040 1041 1043 1045 1047 1048 1050 1054 1055 1056 1057 1059 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1079 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1094 1095 1096 1098 1101 1102 END 1104 5. Internationalization Considerations 1106 EPP is represented in XML, which provides native support for encoding 1107 information using the Unicode character set and its more compact 1108 representations including UTF-8. Conformant XML processors recognize 1109 both UTF-8 and UTF-16 [RFC2781]. Though XML includes provisions to 1110 identify and use other character encodings through use of an 1111 "encoding" attribute in an declaration, use of UTF-8 is 1112 RECOMMENDED in environments where parser encoding support 1113 incompatibility exists. 1115 All date-time values presented via EPP MUST be expressed in Universal 1116 Coordinated Time using the Gregorian calendar. XML Schema allows use 1117 of time zone identifiers to indicate offsets from the zero meridian, 1118 but this option MUST NOT be used with EPP. The extended date-time 1119 form using upper case "T" and "Z" characters defined in 1120 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 1121 values as XML Schema does not support truncated date-time forms or 1122 lower case "T" and "Z" characters. 1124 This document requires host name syntax as specified in [RFC0952] as 1125 updated by [RFC1123]. At the time of this writing, RFC 3490 1126 [RFC3490] describes a standard to use certain ASCII name labels to 1127 represent non-ASCII name labels. These conformance requirements 1128 might change as a result of progressing work in developing standards 1129 for internationalized host names. 1131 6. IANA Considerations 1133 This document uses URNs to describe XML namespaces and XML schemas 1134 conforming to a registry mechanism described in [RFC3688]. Two URI 1135 assignments have been registered by the IANA. 1137 Registration request for the host namespace: 1139 URI: urn:ietf:params:xml:ns:host-1.0 1141 Registrant Contact: See the "Author's Address" section of this 1142 document. 1144 XML: None. Namespace URIs do not represent an XML specification. 1146 Registration request for the host XML schema: 1148 URI: urn:ietf:params:xml:schema:host-1.0 1150 Registrant Contact: See the "Author's Address" section of this 1151 document. 1153 XML: See the "Formal Syntax" section of this document. 1155 7. Security Considerations 1157 The object mapping described in this document does not provide any 1158 security services or introduce any additional considerations beyond 1159 those described by [I-D.hollenbeck-rfc4930bis] and protocol layers 1160 used by EPP. 1162 8. Acknowledgements 1164 This document was originally written as an individual submission 1165 Internet-Draft. The PROVREG working group later adopted it as a 1166 working group document and provided many invaluable comments and 1167 suggested improvements. The author wishes to acknowledge the efforts 1168 of WG chairs Edward Lewis and Jaap Akkerhuis for their process and 1169 editorial contributions. 1171 Specific suggestions that have been incorporated into this document 1172 were provided by Chris Bason, Jordyn Buchanan, Dave Crocker, Anthony 1173 Eden, Sheer El-Showk, Klaus Malorny, Dan Manley, Michael Mealling, 1174 Patrick Mevzek, and Rick Wesson. 1176 9. References 1178 9.1. Normative References 1180 [I-D.hollenbeck-rfc4930bis] 1181 Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1182 draft-hollenbeck-rfc4930bis-01 (work in progress), 1183 May 2009. 1185 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 1186 September 1981. 1188 [RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet 1189 host table specification", RFC 952, October 1985. 1191 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 1192 STD 13, RFC 1034, November 1987. 1194 [RFC1035] Mockapetris, P., "Domain names - implementation and 1195 specification", STD 13, RFC 1035, November 1987. 1197 [RFC1123] Braden, R., "Requirements for Internet Hosts - Application 1198 and Support", STD 3, RFC 1123, October 1989. 1200 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1201 Requirement Levels", BCP 14, RFC 2119, March 1997. 1203 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1204 January 2004. 1206 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 1207 Architecture", RFC 4291, February 2006. 1209 [W3C.REC-xml-20040204] 1210 Sperberg-McQueen, C., Maler, E., Yergeau, F., Paoli, J., 1211 and T. Bray, "Extensible Markup Language (XML) 1.0 (Third 1212 Edition)", World Wide Web Consortium FirstEdition REC-xml- 1213 20040204, February 2004, 1214 . 1216 [W3C.REC-xmlschema-1-20041028] 1217 Beech, D., Thompson, H., Mendelsohn, N., and M. Maloney, 1218 "XML Schema Part 1: Structures Second Edition", World Wide 1219 Web Consortium Recommendation REC-xmlschema-1-20041028, 1220 October 2004, 1221 . 1223 [W3C.REC-xmlschema-2-20041028] 1224 Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes 1225 Second Edition", World Wide Web Consortium 1226 Recommendation REC-xmlschema-2-20041028, October 2004, 1227 . 1229 9.2. Informative References 1231 [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 1232 10646", RFC 2781, February 2000. 1234 [RFC2874] Crawford, M. and C. Huitema, "DNS Extensions to Support 1235 IPv6 Address Aggregation and Renumbering", RFC 2874, 1236 July 2000. 1238 [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, 1239 "Internationalizing Domain Names in Applications (IDNA)", 1240 RFC 3490, March 2003. 1242 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, 1243 "DNS Extensions to Support IP Version 6", RFC 3596, 1244 October 2003. 1246 [RFC4932] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1247 Host Mapping", RFC 4932, May 2007. 1249 Appendix A. Changes from RFC 4932 1251 1. Changed "This document obsoletes RFC 3732" to "This document is 1252 intended to obsolete RFC 4932". 1253 2. Replaced references to RFC 1886 with references to 3596. 1254 3. Removed references to RFC 3152 since both it and 1886 have been 1255 obsoleted by 3596. 1256 4. Replaced references to RFC 3732 with references to 4932. 1257 5. Replaced references to RFC 4930 with references to 4930bis. 1258 6. Added "Other notification methods MAY be used in addition to the 1259 required service message" in Section 3.2. 1260 7. Added 2201 response code text in Section 3.2. 1262 Author's Address 1264 Scott Hollenbeck 1265 VeriSign, Inc. 1266 21345 Ridgetop Circle 1267 Dulles, VA 20166-6503 1268 US 1270 EMail: shollenbeck@verisign.com