< draft-hollenbeck-epp-rfc3732bis-03.txt   draft-hollenbeck-epp-rfc3732bis-04.txt >
Network Working Group S. Hollenbeck Network Working Group S. Hollenbeck
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Obsoletes: 3732 (if approved) September 19, 2006 Obsoletes: 3732 (if approved) November 17, 2006
Intended status: Standards Track Intended status: Standards Track
Expires: March 23, 2007 Expires: May 21, 2007
Extensible Provisioning Protocol (EPP) Host Mapping Extensible Provisioning Protocol (EPP) Host Mapping
draft-hollenbeck-epp-rfc3732bis-03.txt draft-hollenbeck-epp-rfc3732bis-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 23, 2007. This Internet-Draft will expire on May 21, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2006).
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet host names mapping for the provisioning and management of Internet host names
stored in a shared central repository. Specified in XML, the mapping stored in a shared central repository. Specified in XML, the mapping
defines EPP command syntax and semantics as applied to host names. defines EPP command syntax and semantics as applied to host names.
This document obsoletes RFC 3732 if approved. This document obsoletes RFC 3732 if approved.
Table of Contents Table of Contents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1.2. Conventions Used In This Document . . . . . . . . . . . . 3 1.2. Conventions Used In This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Host Names . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Host Names . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Client Identifiers . . . . . . . . . . . . . . . . . . . . 4 2.2. Client Identifiers . . . . . . . . . . . . . . . . . . . . 4
2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 4 2.3. Status Values . . . . . . . . . . . . . . . . . . . . . . 4
2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 2.4. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6
2.5. IP Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 2.5. IP Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 6 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 6
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7 3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7
3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 9 3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 8
3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 12 3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 11
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 13 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 11
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 13 3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 12
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 15 3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 14
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 17 3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 15
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 17 3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 15
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 17 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 16
3.3. Offline Review of Requested Actions . . . . . . . . . . . 19 3.3. Offline Review of Requested Actions . . . . . . . . . . . 18
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 21 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20
5. Internationalization Considerations . . . . . . . . . . . . . 27 5. Internationalization Considerations . . . . . . . . . . . . . 25
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations . . . . . . . . . . . . . . . . . . . 27
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 28 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.1. Normative References . . . . . . . . . . . . . . . . . . . 28 9.1. Normative References . . . . . . . . . . . . . . . . . . . 27
9.2. Informative References . . . . . . . . . . . . . . . . . . 30 9.2. Informative References . . . . . . . . . . . . . . . . . . 28
Appendix A. Changes from RFC 3732 . . . . . . . . . . . . . . . . 30 Appendix A. Changes from RFC 3732 . . . . . . . . . . . . . . . . 29
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 31 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 30
Intellectual Property and Copyright Statements . . . . . . . . . . 32 Intellectual Property and Copyright Statements . . . . . . . . . . 31
1. Introduction 1. Introduction
This document describes an Internet host name mapping for version 1.0 This document describes an Internet host name mapping for version 1.0
of the Extensible Provisioning Protocol (EPP). This mapping is of the Extensible Provisioning Protocol (EPP). This mapping is
specified using the Extensible Markup Language (XML) 1.0 as described specified using the Extensible Markup Language (XML) 1.0 as described
in [W3C.REC-xml-20040204] and XML Schema notation as described in in [W3C.REC-xml-20040204] and XML Schema notation as described in
[W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028].
This document obsoletes RFC 3732 [RFC3732] if approved. This document obsoletes RFC 3732 [RFC3732] if approved.
skipping to change at page 6, line 21 skipping to change at page 6, line 21
The pendingCreate, pendingDelete, pendingTransfer, and pendingUpdate The pendingCreate, pendingDelete, pendingTransfer, and pendingUpdate
status values MUST NOT be combined with each other. status values MUST NOT be combined with each other.
Other status combinations not expressly prohibited MAY be used. Other status combinations not expressly prohibited MAY be used.
2.4. Dates and Times 2.4. Dates and Times
Date and time attribute values MUST be represented in Universal Date and time attribute values MUST be represented in Universal
Coordinated Time (UTC) using the Gregorian calendar. The extended Coordinated Time (UTC) using the Gregorian calendar. The extended
date-time form using upper case "T" and "Z" characters defined in date-time form using upper case "T" and "Z" characters defined in
[RFC3339] MUST be used to represent date-time values as XML Schema [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time
does not support truncated date-time forms or lower case "T" and "Z" values as XML Schema does not support truncated date-time forms or
characters. lower case "T" and "Z" characters.
2.5. IP Addresses 2.5. IP Addresses
The syntax for IPv4 addresses described in this document MUST conform The syntax for IPv4 addresses described in this document MUST conform
to [RFC0791]. The syntax for IPv6 addresses described in this to [RFC0791]. The syntax for IPv6 addresses described in this
document MUST conform to [RFC3513]. Practical considerations for document MUST conform to [RFC4291]. Practical considerations for
publishing IPv6 address information in zone files are documented in publishing IPv6 address information in zone files are documented in
[RFC1886], [RFC2874], and [RFC3152]. A server MAY reject IP [RFC1886], [RFC2874], and [RFC3152]. A server MAY reject IP
addresses that have not been allocated for public use by IANA. When addresses that have not been allocated for public use by IANA. When
a host object is provisioned for use as a DNS name server, IP a host object is provisioned for use as a DNS name server, IP
addresses SHOULD be required only as needed to generate DNS glue addresses SHOULD be required only as needed to generate DNS glue
records. records.
3. EPP Command Mapping 3. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
skipping to change at page 7, line 15 skipping to change at page 7, line 15
3.1.1. EPP <check> Command 3.1.1. EPP <check> Command
The EPP <check> command is used to determine if an object can be The EPP <check> command is used to determine if an object can be
provisioned within a repository. It provides a hint that allows a provisioned within a repository. It provides a hint that allows a
client to anticipate the success or failure of provisioning an object client to anticipate the success or failure of provisioning an object
using the <create> command as object provisioning requirements are using the <create> command as object provisioning requirements are
ultimately a matter of server policy. ultimately a matter of server policy.
In addition to the standard EPP command elements, the <check> command In addition to the standard EPP command elements, the <check> command
MUST contain a <host:check> element that identifies the host MUST contain a <host:check> element that identifies the host
namespace and the location of the host schema. The <host:check> namespace. The <host:check> element contains the following child
element contains the following child elements: elements:
- One or more <host:name> elements that contain the fully qualified - One or more <host:name> elements that contain the fully qualified
names of the host objects to be queried. names of the host objects to be queried.
Example <check> command: Example <check> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command> C: <command>
C: <check> C: <check>
C: <host:check C: <host:check
C: xmlns:host="urn:ietf:params:xml:ns:host-1.0" C: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
C: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
C: host-1.0.xsd">
C: <host:name>ns1.example.com</host:name> C: <host:name>ns1.example.com</host:name>
C: <host:name>ns2.example.com</host:name> C: <host:name>ns2.example.com</host:name>
C: <host:name>ns3.example.com</host:name> C: <host:name>ns3.example.com</host:name>
C: </host:check> C: </host:check>
C: </check> C: </check>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp&gt C:</epp&gt
When a <check> command has been processed successfully, the EPP When a <check> command has been processed successfully, the EPP
<resData> element MUST contain a child <host:chkData> element that <resData> element MUST contain a child <host:chkData> element that
identifies the host namespace and the location of the host schema. identifies the host namespace. The <host:chkData> element contains
The <host:chkData> element contains one or more <host:cd> elements one or more <host:cd> elements that contain the following child
that contain the following child elements: elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the queried host object. This element MUST contain an "avail" the queried host object. This element MUST contain an "avail"
attribute whose value indicates object availability (can it be attribute whose value indicates object availability (can it be
provisioned or not) at the moment the <check> command was provisioned or not) at the moment the <check> command was
completed. A value of "1" or "true" means that the object can be completed. A value of "1" or "true" means that the object can be
provisioned. A value of "0" or "false" means that the object can provisioned. A value of "0" or "false" means that the object can
not be provisioned. not be provisioned.
- An OPTIONAL <host:reason> element that MAY be provided when an - An OPTIONAL <host:reason> element that MAY be provided when an
skipping to change at page 9, line 8 skipping to change at page 8, line 17
server-specific text to help explain why the object can not be server-specific text to help explain why the object can not be
provisioned. This text MUST be represented in the response provisioned. This text MUST be represented in the response
language previously negotiated with the client; an OPTIONAL "lang" language previously negotiated with the client; an OPTIONAL "lang"
attribute MAY be present to identify the language if the attribute MAY be present to identify the language if the
negotiated value is something other than the default value of "en" negotiated value is something other than the default value of "en"
(English). (English).
Example <check> response: Example <check> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <host:chkData S: <host:chkData
S: xmlns:host="urn:ietf:params:xml:ns:host-1.0" S: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
S: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
S: host-1.0.xsd">
S: <host:cd> S: <host:cd>
S: <host:name avail="1">ns1.example.com</host:name> S: <host:name avail="1">ns1.example.com</host:name>
S: </host:cd> S: </host:cd>
S: <host:cd> S: <host:cd>
S: <host:name avail="0">ns2.example2.com</host:name> S: <host:name avail="0">ns2.example2.com</host:name>
S: <host:reason>In use</host:reason> S: <host:reason>In use</host:reason>
S: </host:cd> S: </host:cd>
S: <host:cd> S: <host:cd>
S: <host:name avail="1">ns3.example3.com</host:name> S: <host:name avail="1">ns3.example3.com</host:name>
S: </host:cd> S: </host:cd>
skipping to change at page 9, line 48 skipping to change at page 8, line 52
S:</epp&gt S:</epp&gt
An EPP error response MUST be returned if a <check> command can not An EPP error response MUST be returned if a <check> command can not
be processed for any reason. be processed for any reason.
3.1.2. EPP <info> Command 3.1.2. EPP <info> Command
The EPP <info> command is used to retrieve information associated The EPP <info> command is used to retrieve information associated
with a host object. In addition to the standard EPP command with a host object. In addition to the standard EPP command
elements, the <info> command MUST contain a <host:info> element that elements, the <info> command MUST contain a <host:info> element that
identifies the host namespace and the location of the host schema. identifies the host namespace. The <host:info> element contains the
The <host:info> element contains the following child elements: following child elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object for which information is requested. the host object for which information is requested.
Example <info> command: Example <info> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command> C: <command>
C: <info> C: <info>
C: <host:info C: <host:info
C: xmlns:host="urn:ietf:params:xml:ns:host-1.0" C: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
C: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
C: host-1.0.xsd">
C: <host:name>ns1.example.com</host:name> C: <host:name>ns1.example.com</host:name>
C: </host:info> C: </host:info>
C: </info> C: </info>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp&gt C:</epp&gt
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <host:infData> element that <resData> element MUST contain a child <host:infData> element that
identifies the host namespace and the location of the host schema. identifies the host namespace. The <host:infData> element contains
The <host:infData> element contains the following child elements: the following child elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object. the host object.
- A <host:roid> element that contains the Repository Object - A <host:roid> element that contains the Repository Object
IDentifier assigned to the host object when the object was IDentifier assigned to the host object when the object was
created. created.
- One or more <host:status> elements that describe the status of the - One or more <host:status> elements that describe the status of the
host object. host object.
skipping to change at page 12, line 8 skipping to change at page 11, line 8
Note that host objects MUST NOT be transferred directly; host Note that host objects MUST NOT be transferred directly; host
objects MUST be transferred implicitly when the host object's objects MUST be transferred implicitly when the host object's
superordinate domain object is transferred. Host objects that are superordinate domain object is transferred. Host objects that are
subject to transfer when transferring a domain object are listed subject to transfer when transferring a domain object are listed
in the response to an EPP <info> command performed on the domain in the response to an EPP <info> command performed on the domain
object. object.
Example <info> response: Example <info> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <host:infData S: <host:infData
S: xmlns:host="urn:ietf:params:xml:ns:host-1.0" S: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
S: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
S: host-1.0.xsd">
S: <host:name>ns1.example.com</host:name> S: <host:name>ns1.example.com</host:name>
S: <host:roid>NS1_EXAMPLE1-REP</host:roid> S: <host:roid>NS1_EXAMPLE1-REP</host:roid>
S: <host:status s="linked"/> S: <host:status s="linked"/>
S: <host:status s="clientUpdateProhibited"/> S: <host:status s="clientUpdateProhibited"/>
S: <host:addr ip="v4">192.0.2.2</host:addr> S: <host:addr ip="v4">192.0.2.2</host:addr>
S: <host:addr ip="v4">192.0.2.29</host:addr> S: <host:addr ip="v4">192.0.2.29</host:addr>
S: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr> S: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr>
S: <host:clID>ClientY</host:clID> S: <host:clID>ClientY</host:clID>
S: <host:crID>ClientX</host:crID> S: <host:crID>ClientX</host:crID>
S: <host:crDate>1999-04-03T22:00:00.0Z</host:crDate> S: <host:crDate>1999-04-03T22:00:00.0Z</host:crDate>
skipping to change at page 13, line 31 skipping to change at page 12, line 23
the initiation and completion of the requested action. Once the the initiation and completion of the requested action. Once the
action has been completed, all clients involved in the transaction action has been completed, all clients involved in the transaction
MUST be notified using a service message that the action has been MUST be notified using a service message that the action has been
completed and that the status of the object has changed. completed and that the status of the object has changed.
3.2.1. EPP <create> Command 3.2.1. EPP <create> Command
The EPP <create> command provides a transform operation that allows a The EPP <create> command provides a transform operation that allows a
client to create a host object. In addition to the standard EPP client to create a host object. In addition to the standard EPP
command elements, the <create> command MUST contain a <host:create> command elements, the <create> command MUST contain a <host:create>
element that identifies the host namespace and the location of the element that identifies the host namespace. The <host:create>
host schema. The <host:create> element contains the following child element contains the following child elements:
elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object to be created. the host object to be created.
- Zero or more <host:addr> elements that contain the IP addresses to - Zero or more <host:addr> elements that contain the IP addresses to
be associated with the host. Each element MAY contain an "ip" be associated with the host. Each element MAY contain an "ip"
attribute to identify the IP address format. Attribute value "v4" attribute to identify the IP address format. Attribute value "v4"
is used to note IPv4 address format. Attribute value "v6" is used is used to note IPv4 address format. Attribute value "v6" is used
to note IPv6 address format. If the "ip" attribute is not to note IPv6 address format. If the "ip" attribute is not
specified, "v4" is the default attribute value. specified, "v4" is the default attribute value.
skipping to change at page 14, line 15 skipping to change at page 13, line 8
server is not required to produce DNS glue records for the name server is not required to produce DNS glue records for the name
server and IP addresses for the server are not required by the DNS. server and IP addresses for the server are not required by the DNS.
If the host name exists in a name space for which the server is If the host name exists in a name space for which the server is
authoritative, then the superordinate domain of the host MUST be authoritative, then the superordinate domain of the host MUST be
known to the server before the host object can be created. known to the server before the host object can be created.
Example <create> command: Example <create> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command> C: <command>
C: <create> C: <create>
C: <host:create C: <host:create
C: xmlns:host="urn:ietf:params:xml:ns:host-1.0" C: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
C: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
C: host-1.0.xsd">
C: <host:name>ns1.example.com</host:name> C: <host:name>ns1.example.com</host:name>
C: <host:addr ip="v4">192.0.2.2</host:addr> C: <host:addr ip="v4">192.0.2.2</host:addr>
C: <host:addr ip="v4">192.0.2.29</host:addr> C: <host:addr ip="v4">192.0.2.29</host:addr>
C: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr> C: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr>
C: </host:create> C: </host:create>
C: </create> C: </create>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp&gt C:</epp&gt
When a <create> command has been processed successfully, the EPP When a <create> command has been processed successfully, the EPP
<resData> element MUST contain a child <host:creData> element that <resData> element MUST contain a child <host:creData> element that
identifies the host namespace and the location of the host schema. identifies the host namespace. The <host:creData> element contains
The <host:creData> element contains the following child elements: the following child elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object. the host object.
- A <host:crDate> element that contains the date and time of host - A <host:crDate> element that contains the date and time of host
object creation. object creation.
Example <create> response: Example <create> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <host:creData S: <host:creData
S: xmlns:host="urn:ietf:params:xml:ns:host-1.0" S: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
S: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
S: host-1.0.xsd">
S: <host:name>ns1.example.com</host:name> S: <host:name>ns1.example.com</host:name>
S: <host:crDate>1999-04-03T22:00:00.0Z</host:crDate> S: <host:crDate>1999-04-03T22:00:00.0Z</host:crDate>
S: </host:creData> S: </host:creData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp&gt S:</epp&gt
An EPP error response MUST be returned if a <create> command can not An EPP error response MUST be returned if a <create> command can not
be processed for any reason. be processed for any reason.
3.2.2. EPP <delete> Command 3.2.2. EPP <delete> Command
The EPP <delete> command provides a transform operation that allows a The EPP <delete> command provides a transform operation that allows a
client to delete a host object. In addition to the standard EPP client to delete a host object. In addition to the standard EPP
command elements, the <delete> command MUST contain a <host:delete> command elements, the <delete> command MUST contain a <host:delete>
element that identifies the host namespace and the location of the element that identifies the host namespace. The <host:delete>
host schema. The <host:delete> element contains the following child element contains the following child elements:
elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object to be deleted. the host object to be deleted.
A host name object SHOULD NOT be deleted if the host object is A host name object SHOULD NOT be deleted if the host object is
associated with any other object. For example, if the host object is associated with any other object. For example, if the host object is
associated with a domain object, the host object SHOULD NOT be associated with a domain object, the host object SHOULD NOT be
deleted until the existing association has been broken. Deleting a deleted until the existing association has been broken. Deleting a
host object without first breaking existing associations can cause host object without first breaking existing associations can cause
DNS resolution failure for domain objects that refer to the deleted DNS resolution failure for domain objects that refer to the deleted
host object. host object.
Example <delete> command: Example <delete> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command> C: <command>
C: <delete> C: <delete>
C: <host:delete C: <host:delete
C: xmlns:host="urn:ietf:params:xml:ns:host-1.0" C: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
C: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
C: host-1.0.xsd">
C: <host:name>ns1.example.com</host:name> C: <host:name>ns1.example.com</host:name>
C: </host:delete> C: </host:delete>
C: </delete> C: </delete>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp&gt C:</epp&gt
When a <delete> command has been processed successfully, a server When a <delete> command has been processed successfully, a server
MUST respond with an EPP response with no <resData> element. MUST respond with an EPP response with no <resData> element.
Example <delete> response: Example <delete> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp&gt S:</epp&gt
skipping to change at page 17, line 22 skipping to change at page 16, line 10
Transfer semantics do not directly apply to host objects, so there is Transfer semantics do not directly apply to host objects, so there is
no mapping defined for the EPP <transfer> command. Host objects are no mapping defined for the EPP <transfer> command. Host objects are
subordinate to an existing superordinate domain object, and as such subordinate to an existing superordinate domain object, and as such
they are subject to transfer when a domain object is transferred. they are subject to transfer when a domain object is transferred.
3.2.5. EPP <update> Command 3.2.5. EPP <update> Command
The EPP <update> command provides a transform operation that allows a The EPP <update> command provides a transform operation that allows a
client to modify the attributes of a host object. In addition to the client to modify the attributes of a host object. In addition to the
standard EPP command elements, the <update> command MUST contain a standard EPP command elements, the <update> command MUST contain a
<host:update> element that identifies the host namespace and the <host:update> element that identifies the host namespace. The <host:
location of the host schema. The <host:update> element contains the update> element contains the following child elements:
following child elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object to be updated. the host object to be updated.
- An OPTIONAL <host:add> element that contains attribute values to - An OPTIONAL <host:add> element that contains attribute values to
be added to the object. be added to the object.
- An OPTIONAL <host:rem> element that contains attribute values to - An OPTIONAL <host:rem> element that contains attribute values to
be removed from the object. be removed from the object.
skipping to change at page 18, line 27 skipping to change at page 17, line 13
one exception: changing an external host object that has associations one exception: changing an external host object that has associations
with objects that are sponsored by a different client. Attempts to with objects that are sponsored by a different client. Attempts to
update such hosts directly MUST fail with EPP error code 2305. The update such hosts directly MUST fail with EPP error code 2305. The
change can be provisioned by creating a new external host with a new change can be provisioned by creating a new external host with a new
name and needed new attributes and subsequently updating the other name and needed new attributes and subsequently updating the other
objects sponsored by the client. objects sponsored by the client.
Example <update> command: Example <update> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command> C: <command>
C: <update> C: <update>
C: <host:update C: <host:update
C: xmlns:host="urn:ietf:params:xml:ns:host-1.0" C: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
C: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
C: host-1.0.xsd">
C: <host:name>ns1.example.com</host:name> C: <host:name>ns1.example.com</host:name>
C: <host:add> C: <host:add>
C: <host:addr ip="v4">192.0.2.22</host:addr> C: <host:addr ip="v4">192.0.2.22</host:addr>
C: <host:status s="clientUpdateProhibited"/> C: <host:status s="clientUpdateProhibited"/>
C: </host:add> C: </host:add>
C: <host:rem> C: <host:rem>
C: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr> C: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr>
C: </host:rem> C: </host:rem>
C: <host:chg> C: <host:chg>
C: <host:name>ns2.example.com</host:name> C: <host:name>ns2.example.com</host:name>
skipping to change at page 19, line 4 skipping to change at page 17, line 34
C: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr> C: <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr>
C: </host:rem> C: </host:rem>
C: <host:chg> C: <host:chg>
C: <host:name>ns2.example.com</host:name> C: <host:name>ns2.example.com</host:name>
C: </host:chg> C: </host:chg>
C: </host:update> C: </host:update>
C: </update> C: </update>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp&gt C:</epp&gt
When an <update> command has been processed successfully, a server When an <update> command has been processed successfully, a server
MUST respond with an EPP response with no <resData> element. MUST respond with an EPP response with no <resData> element.
Example <update> response: Example <update> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp&gt S:</epp&gt
skipping to change at page 20, line 6 skipping to change at page 18, line 25
command has been received and processed, but the requested action is command has been received and processed, but the requested action is
pending. The status of the corresponding object MUST clearly reflect pending. The status of the corresponding object MUST clearly reflect
processing of the pending action. The server MUST notify the client processing of the pending action. The server MUST notify the client
when offline processing of the action has been completed. when offline processing of the action has been completed.
Examples describing a <create> command that requires offline review Examples describing a <create> command that requires offline review
are included here. Note the result code and message returned in are included here. Note the result code and message returned in
response to the <create> command. response to the <create> command.
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1001"> S: <result code="1001">
S: <msg>Command completed successfully; action pending</msg> S: <msg>Command completed successfully; action pending</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <host:creData S: <host:creData
S: xmlns:host="urn:ietf:params:xml:ns:host-1.0" S: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
S: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
S: host-1.0.xsd">
S: <host:name>ns1.example.com</host:name> S: <host:name>ns1.example.com</host:name>
S: <host:crDate>1999-04-03T22:00:00.0Z</host:crDate> S: <host:crDate>1999-04-03T22:00:00.0Z</host:crDate>
S: </host:creData> S: </host:creData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp&gt S:</epp&gt
skipping to change at page 20, line 40 skipping to change at page 19, line 6
The status of the host object after returning this response MUST The status of the host object after returning this response MUST
include "pendingCreate". The server operator reviews the request include "pendingCreate". The server operator reviews the request
offline, and informs the client of the outcome of the review by offline, and informs the client of the outcome of the review by
either queuing a service message for retrieval via the <poll> command either queuing a service message for retrieval via the <poll> command
or by using an out-of-band mechanism to inform the client of the or by using an out-of-band mechanism to inform the client of the
request. request.
The service message MUST contain text in the <response>, <msgQ>, The service message MUST contain text in the <response>, <msgQ>,
<msg> element that describes the notification. In addition, the EPP <msg> element that describes the notification. In addition, the EPP
<resData> element MUST contain a child <host:panData> element that <resData> element MUST contain a child <host:panData> element that
identifies the host namespace and the location of the host schema. identifies the host namespace. The <host:panData> element contains
The <host:panData> element contains the following child elements: the following child elements:
- A <host:name> element that contains the fully qualified name of - A <host:name> element that contains the fully qualified name of
the host object. The <host:name> element contains a REQUIRED the host object. The <host:name> element contains a REQUIRED
"paResult" attribute. A positive boolean value indicates that the "paResult" attribute. A positive boolean value indicates that the
request has been approved and completed. A negative boolean value request has been approved and completed. A negative boolean value
indicates that the request has been denied and the requested indicates that the request has been denied and the requested
action has not been taken. action has not been taken.
- A <host:paTRID> element that contains the client transaction - A <host:paTRID> element that contains the client transaction
identifier and server transaction identifier returned with the identifier and server transaction identifier returned with the
original response to process the command. The client transaction original response to process the command. The client transaction
identifier is OPTIONAL and will only be returned if the client identifier is OPTIONAL and will only be returned if the client
provided an identifier with the original <create> command. provided an identifier with the original <create> command.
- A <host:paDate> element that contains the date and time describing - A <host:paDate> element that contains the date and time describing
when review of the requested action was completed. when review of the requested action was completed.
Example "review completed" service message: Example "review completed" service message:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ count="5" id="12345"> S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate> S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg> S: <msg>Pending action completed successfully.</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <host:panData S: <host:panData
S: xmlns:host="urn:ietf:params:xml:ns:host-1.0" S: xmlns:host="urn:ietf:params:xml:ns:host-1.0">
S: xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0
S: host-1.0.xsd">
S: <host:name paResult="1">ns1.example.com</host:name> S: <host:name paResult="1">ns1.example.com</host:name>
S: <host:paTRID> S: <host:paTRID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </host:paTRID> S: </host:paTRID>
S: <host:paDate>1999-04-04T22:00:00.0Z</host:paDate> S: <host:paDate>1999-04-04T22:00:00.0Z</host:paDate>
S: </host:panData> S: </host:panData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>BCD-23456</clTRID> S: <clTRID>BCD-23456</clTRID>
skipping to change at page 22, line 23 skipping to change at page 21, line 9
<schema targetNamespace="urn:ietf:params:xml:ns:host-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:host-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Extensible Provisioning Protocol v1.0 Extensible Provisioning Protocol v1.0
host provisioning schema. host provisioning schema.
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements found in EPP commands. Child elements found in EPP commands.
skipping to change at page 27, line 30 skipping to change at page 26, line 15
both UTF-8 and UTF-16 [RFC2781]. Though XML includes provisions to both UTF-8 and UTF-16 [RFC2781]. Though XML includes provisions to
identify and use other character encodings through use of an identify and use other character encodings through use of an
"encoding" attribute in an <?xml?> declaration, use of UTF-8 is "encoding" attribute in an <?xml?> declaration, use of UTF-8 is
RECOMMENDED in environments where parser encoding support RECOMMENDED in environments where parser encoding support
incompatibility exists. incompatibility exists.
All date-time values presented via EPP MUST be expressed in Universal All date-time values presented via EPP MUST be expressed in Universal
Coordinated Time using the Gregorian calendar. XML Schema allows use Coordinated Time using the Gregorian calendar. XML Schema allows use
of time zone identifiers to indicate offsets from the zero meridian, of time zone identifiers to indicate offsets from the zero meridian,
but this option MUST NOT be used with EPP. The extended date-time but this option MUST NOT be used with EPP. The extended date-time
form using upper case "T" and "Z" characters defined in <xref form using upper case "T" and "Z" characters defined in
target="RFC3339"/> MUST be used to represent date-time values as XML [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time
Schema does not support truncated date-time forms or lower case "T" values as XML Schema does not support truncated date-time forms or
and "Z" characters. lower case "T" and "Z" characters.
This document requires host name syntax as specified in <xref This document requires host name syntax as specified in [RFC0952] as
target="RFC0952"/> as updated by <xref target="RFC1123"/>. At the updated by [RFC1123]. At the time of this writing, RFC 3490
time of this writing, RFC 3490 <xref target="RFC3490"/> describes a [RFC3490] describes a standard to use certain ASCII name labels to
standard to use certain ASCII name labels to represent non-ASCII name represent non-ASCII name labels. These conformance requirements
labels. These conformance requirements might change as a result of might change as a result of progressing work in developing standards
progressing work in developing standards for internationalized host for internationalized host names.
names.
6. IANA Considerations 6. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. Two URI conforming to a registry mechanism described in [RFC3688]. Two URI
assignments have been registered by the IANA. assignments have been registered by the IANA.
Registration request for the host namespace: Registration request for the host namespace:
URI: urn:ietf:params:xml:ns:host-1.0 URI: urn:ietf:params:xml:ns:host-1.0
skipping to change at page 28, line 48 skipping to change at page 27, line 32
were provided by Chris Bason, Jordyn Buchanan, Dave Crocker, Anthony were provided by Chris Bason, Jordyn Buchanan, Dave Crocker, Anthony
Eden, Sheer El-Showk, Klaus Malorny, Dan Manley, Michael Mealling, Eden, Sheer El-Showk, Klaus Malorny, Dan Manley, Michael Mealling,
Patrick Mevzek, and Rick Wesson. Patrick Mevzek, and Rick Wesson.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.hollenbeck-epp-rfc3730bis] [I-D.hollenbeck-epp-rfc3730bis]
Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
draft-hollenbeck-epp-rfc3730bis-03 (work in progress), draft-hollenbeck-epp-rfc3730bis-04 (work in progress),
September 2006. November 2006.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet [RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet
host table specification", RFC 952, October 1985. host table specification", RFC 952, October 1985.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987. STD 13, RFC 1034, November 1987.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application [RFC1123] Braden, R., "Requirements for Internet Hosts - Application
and Support", STD 3, RFC 1123, October 1989. and Support", STD 3, RFC 1123, October 1989.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002.
[RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6
(IPv6) Addressing Architecture", RFC 3513, April 2003.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[W3C.REC-xml-20040204] [W3C.REC-xml-20040204]
Maler, E., Bray, T., Yergeau, F., Sperberg-McQueen, C., Paoli, J., Maler, E., Sperberg-McQueen, C., Bray, T., and
and J. Paoli, "Extensible Markup Language (XML) 1.0 (Third F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20040204, February 2004, xml-20040204, February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
[W3C.REC-xmlschema-1-20041028] [W3C.REC-xmlschema-1-20041028]
Thompson, H., Beech, D., Mendelsohn, N., and M. Maloney, Beech, D., Thompson, H., Maloney, M., and N. Mendelsohn,
"XML Schema Part 1: Structures Second Edition", World Wide "XML Schema Part 1: Structures Second Edition", World Wide
Web Consortium Recommendation REC-xmlschema-1-20041028, Web Consortium Recommendation REC-xmlschema-1-20041028,
October 2004, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition", World Wide Web Consortium Second Edition", World Wide Web Consortium
Recommendation REC-xmlschema-2-20041028, October 2004, Recommendation REC-xmlschema-2-20041028, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
skipping to change at page 31, line 25 skipping to change at page 30, line 5
client of the outcome of the review by queuing a service message client of the outcome of the review by queuing a service message
for retrieval via the <poll> command." for retrieval via the <poll> command."
to this: to this:
"The server operator reviews the request offline, and informs the "The server operator reviews the request offline, and informs the
client of the outcome of the review by either queuing a service client of the outcome of the review by either queuing a service
message for retrieval via the <poll> command or by using an out- message for retrieval via the <poll> command or by using an out-
of-band mechanism to inform the client of the request." of-band mechanism to inform the client of the request."
6. Updated EPP and XML references. 6. Removed text describing use of the XML Schema schemaLocation
attribute. This is an optional attribute that doesn't need to be
mandated for use in EPP.
7. Removed references to RFC 3339 and replaced them with references
to the W3C XML Schema specification.
8. Updated EPP and XML references.
Author's Address Author's Address
Scott Hollenbeck Scott Hollenbeck
VeriSign, Inc. VeriSign, Inc.
21345 Ridgetop Circle 21345 Ridgetop Circle
Dulles, VA 20166-6503 Dulles, VA 20166-6503
US US
Email: shollenbeck@verisign.com Email: shollenbeck@verisign.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 51 change blocks. 
161 lines changed or deleted 104 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/