Does this affect your integration?
Answer four questions about how your EPP client reads responses. The changes that matter to you are highlighted below.
What changes
Open a change to see the current response next to the new one. Removed lines are marked −, new lines +.
Error details (extValue) are now written with an epp: prefix
Same namespace and content, but <extValue>, <value> and <reason> become <epp:extValue>, <epp:value> and <epp:reason>.
Action may be neededContact CreateContact DeleteDomain CreateDomain DeleteDomain Transfer Request200122012302230323042306
extValue) are now written with an epp: prefix<extValue>, <value> and <reason> become <epp:extValue>, <epp:value> and <epp:reason>.What changes
RyCE responses keep their unprefixed root, <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">. Inside <result>, the error-detail block is now written as <epp:extValue xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> with <epp:value> and <epp:reason> children.
The namespace URI is the same EPP namespace, so a namespace-aware parser sees exactly the same elements. Result codes, <msg> and <reason> text do not change.
Code that searches for the literal text <reason> or <extValue>, or uses XPath such as //reason without namespace bindings, will stop finding them.
What to do
urn:ietf:params:xml:ns:epp-1.0, local name reason) rather than the literal tag text.<?xml version='1.0' encoding='utf-8'?><epp xmlns="urn:ietf:params:xml:ns:epp-1.0"><response><result code="2302"><msg>Object exists</msg><extValue><value><undef/></value><reason>Contact exists: testcontact</reason></extValue></result><trID><svTRID>TRID-000000-0000-0000-0000</svTRID></trID></response></epp>
<?xml version="1.0" encoding="UTF-8"?><epp xmlns="urn:ietf:params:xml:ns:epp-1.0"><response><result code="2302"><msg>Object exists</msg><epp:extValue xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"><epp:value><undef/></epp:value><epp:reason>Contact exists: testcontact</epp:reason></epp:extValue></result><trID><svTRID>TRID-000000-0000-0000-0000</svTRID></trID></response></epp>
Seen in 8 responses in our test run
- Contact Create — Contact already exists
2302 - Contact Create — Invalid email
2306 - Contact Delete — Contact does not exist
2303 - Domain Create — Contact does not exist
2303 - Domain Create — And shows the response with the charge extension
2001 - Domain Delete — Domain does not exist
2303 - Domain Delete — Not the Registrar on Record
2201 - Domain Transfer Request — Transfer already in progress
2304
Schema-validation errors (2001) no longer echo your request
Same result code. The <msg> text is shorter.
Check your parserContact CreateDomain Create2001
<msg> text is shorter.What changes
The result code stays 2001. Today the <msg> text ends with the line number and a truncated copy of the XML you sent (line 19 Message: b'<epp …[truncated]). After the change, <msg> holds only the schema validation error.
The standalone='yes' attribute is also dropped from the XML declaration of these responses. The root element stays unprefixed, as in every other RyCE response.
In our test run this applied to every schema-validation failure, including Contact Create with an invalid phone number and Domain Create with an invalid charge-extension agreement element.
What to do
<msg> text, or log it expecting the echoed request, update that code. Rely on the result code, not on the message wording.<?xml version='1.0' encoding='utf-8' standalone='yes'?><epp xmlns="urn:ietf:params:xml:ns:epp-1.0"><response><result code="2001"><msg>XML failed EPP schema check: Element '{urn:ietf:params:xml:ns:contact-1.0}voice': [facet 'pattern'] The value '19' is not accepted by the pattern '(\+[0-9]{1,3}\.[0-9]{1,14})?'., line 19 Message: b'<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">\n <command>\n <create>\n ...[truncated]</msg></result><trID><svTRID>TRID-000000-0000-0000-0000</svTRID></trID></response></epp>
<?xml version="1.0" encoding="UTF-8"?><epp xmlns="urn:ietf:params:xml:ns:epp-1.0"><response><result code="2001"><msg>XML failed EPP schema check: Element '{urn:ietf:params:xml:ns:contact-1.0}voice': [facet 'pattern'] The value '19' is not accepted by the pattern '(\+[0-9]{1,3}\.[0-9]{1,14})?'.</msg></result><trID><svTRID>TRID-000000-0000-0000-0000</svTRID></trID></response></epp>
XML declaration uses double quotes and upper-case UTF-8
Every response. Both forms are equivalent XML.
No action expectedAll responses
UTF-8What changes
The first line of every response changes from <?xml version='1.0' encoding='utf-8'?> to <?xml version="1.0" encoding="UTF-8"?>.
Any XML parser treats the two as identical.
What to do
<?xml version='1.0' encoding='utf-8'?><?xml version="1.0" encoding="UTF-8"?>Seen in 38 responses in our test run
- Contact Check — That shows the contact is available
1000 - Contact Check — Which shows that the contact is not available, therefore exists
1000 - Contact Check — Even with incorrect auth code
1000 - Contact Check — Even if not the owner
1000 - Contact Create — A successful response
1000 - Contact Create — Contact already exists
2302 - Contact Create — Invalid email
2306 - Contact Create — An invalid phone number
2001 - Contact Delete — A successful response
1000 - Contact Delete — Contact does not exist
2303 - Contact Info — A successful response
1000 - Contact Info — A failed response
2303 - Contact Update — A successful response
1000 - Domain Check — A successful response
1000 - Domain Create — Contact does not exist
2303 - Domain Create — Invalid domain name
1000 - Domain Create — A successful response
1000 - Domain Create — And shows the response with the charge extension
2001 - Domain Delete — A successful response
1000 - Domain Delete — Domain does not exist
2303 - Domain Delete — Not the Registrar on Record
2201 - Domain Info — A successful response
1000 - Domain Info — Domain does not exist
2303 - Domain Renew — Exceeds maximum years
2105 - Domain Renew — Renew for 1 year
1000 - Domain to create — A failure as the host does not exists when using hostObj
2303 - Domain Transfer Approve — A successful response
1000 - Domain Transfer Cancel — Domain not pending transfer
2301 - Domain Transfer Cancel — A successful response
1000 - Domain Transfer Query — (no description)
1000 - Domain Transfer Reject — Must be the loosing Rar
2201 - Domain Transfer Reject — A successful response
1000 - Domain Transfer Request — A successful response
1001 - Domain Transfer Request — Cannot request a transfer by the RoR
2106 - Domain Transfer Request — Transfer already in progress
2304 - Domain Update — A successful response
1000 - Domain Update — ClientUpdateProhibited not supported on ZARC
1000 - Logout — A successful response
1500
Indentation inside resData differs
Whitespace only. The data inside <resData> is unchanged.
No action expectedSuccessful responses with data
resData differs<resData> is unchanged.What changes
The *:chkData, *:infData, *:creData and *:trnData blocks are indented differently. Whitespace between elements has no meaning in EPP.
What to do
<resData><contact:chkData xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"><contact:cd><contact:id avail="1">testcontact</contact:id></contact:cd></contact:chkData></resData>
<resData><contact:chkData xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"><contact:cd><contact:id avail="1">testcontact</contact:id></contact:cd></contact:chkData></resData>
Seen in 18 responses in our test run
- Contact Check — That shows the contact is available
1000 - Contact Check — Which shows that the contact is not available, therefore exists
1000 - Contact Check — Even with incorrect auth code
1000 - Contact Check — Even if not the owner
1000 - Contact Create — A successful response
1000 - Contact Info — A successful response
1000 - Domain Check — A successful response
1000 - Domain Create — Invalid domain name
1000 - Domain Create — A successful response
1000 - Domain Info — A successful response
1000 - Domain Renew — Renew for 1 year
1000 - Domain Transfer Approve — A successful response
1000 - Domain Transfer Cancel — Domain not pending transfer
2301 - Domain Transfer Cancel — A successful response
1000 - Domain Transfer Query — (no description)
1000 - Domain Transfer Reject — Must be the loosing Rar
2201 - Domain Transfer Reject — A successful response
1000 - Domain Transfer Request — A successful response
1001
Readiness checklist
Work through these before the change date.