From cbe3a8c4582f2f565e3e868775b992be5d155736 Mon Sep 17 00:00:00 2001 From: Gavin Brown Date: Wed, 24 Jan 2024 17:18:20 +0000 Subject: [PATCH] fix bug which hid a test case. add a consistency case. lint check for cross-suite dependencies. update integration test so it does its own EPP stuff --- inc/epp/cases.yaml | 56 +- inc/epp/errors.yaml | 45 + inc/integration/cases.yaml | 43 +- inc/suites.yaml.in | 2 + rst-test-specs.html | 5604 ++++++++++++++++++------------------ rst-test-specs.json | 160 +- rst-test-specs.yaml | 182 +- 7 files changed, 3239 insertions(+), 2853 deletions(-) diff --git a/inc/epp/cases.yaml b/inc/epp/cases.yaml index 23b531c..cf14b61 100644 --- a/inc/epp/cases.yaml +++ b/inc/epp/cases.yaml @@ -40,6 +40,7 @@ epp-01: - EPP_TLS_CERTIFICATE_CHAIN_MISSING - EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH - EPP_TLS_BAD_CIPHER + epp-02: Summary: Protocol conformance test Description: | @@ -86,6 +87,7 @@ epp-02: - EPP_GREETING_DOES_NOT_MATCH Input-Parameters: Dependencies: + epp-03: Summary: Authentication test Description: | @@ -110,6 +112,7 @@ epp-03: Input-Parameters: Resources: Errors: + epp-04: Summary: Domain command test Description: | @@ -135,6 +138,7 @@ epp-04: - EPP_DOMAIN_CHECK_VALID_DOMAIN_INCORRECT_AVAIL - EPP_DOMAIN_CHECK_INVALID_DOMAIN_INCORRECT_AVAIL - EPP_DOMAIN_CHECK_REGISTERED_DOMAIN_INCORRECT_AVAIL + epp-05: Summary: Host command test (if applicable) Description: | @@ -160,6 +164,7 @@ epp-05: - EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL - EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL - EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL + epp-06: Summary: Contact command test (if applicable for the registry type) Description: | @@ -181,6 +186,7 @@ epp-06: - EPP_CONTACT_CHECK_VALID_CONTACT_ID_INCORRECT_AVAIL - EPP_CONTACT_CHECK_INVALID_CONTACT_ID_INCORRECT_AVAIL - EPP_CONTACT_CHECK_REGISTERED_CONTACT_ID_INCORRECT_AVAIL + epp-07: Summary: Contact command test (if applicable for the registry type) Description: | @@ -245,6 +251,7 @@ epp-07: - EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC - EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE - EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL + epp-08: Summary: Contact object access control (if applicable) Description: | @@ -263,6 +270,7 @@ epp-08: Errors: - EPP_CONTACT_INFO_RESPONSE_NOT_2201 - EPP_CONTACT_UPDATE_RESPONSE_NOT_2201 + epp-09: Summary: Contact command test (if applicable for the registry type) Description: | @@ -319,11 +327,12 @@ epp-09: - EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC - EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE - EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL + epp-10: Summary: Contact command test (if applicable for the registry type) Description: | This test will perform `` commands on the objects created during - `epp-22` and will confirm that the server accepts the `` command + `epp-24` and will confirm that the server accepts the `` command with a `1xxx` response code. If the `general.minimalPublicDataSet` input parameter is `true`, this @@ -339,6 +348,7 @@ epp-10: Errors: - EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001 - EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS + epp-11: Summary: host command test (if applicable) Description: | @@ -374,6 +384,7 @@ epp-11: - EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE - EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST - EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES + epp-12: Summary: Host object access control (if applicable) Description: | @@ -390,6 +401,7 @@ epp-12: - epp-11 Errors: - EPP_HOST_UPDATE_AUTHZ_ERROR + epp-13: Summary: Host command test (if applicable) Description: | @@ -422,6 +434,7 @@ epp-13: - EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE - EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST - EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES + epp-14: Summary: Domain command test Description: | @@ -496,6 +509,7 @@ epp-14: - EPP_DOMAIN_CREATE_SERVER_ACCEPTS_AUTHINFO - EPP_DOMAIN_CREATE_INFO_RESPONSE_INVALID_ROID - EPP_DOMAIN_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES + epp-15: Summary: Registry object integrity test Description: | @@ -514,6 +528,7 @@ epp-15: Errors: - EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT - EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT + epp-16: Summary: Domain command test Description: | @@ -546,7 +561,24 @@ epp-16: - EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT - EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA - EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA -epp-16: + +epp-17: + Summary: Service Port consistency test + Description: | + This test confirms that all EPP service ports respond with consistent object + information. + + The client will establish seperate connections to each EPP service port + (defined as an IP address and TCP port) and perform `` commands on the + objects created in `epp-14`. In all cases, the server **MUST** respond with + a `1000` response and the content of the `` element **MUST** be + identical on all service ports. + Dependencies: + - epp-14 + Errors: + - EPP_SERVICE_PORT_NOT_CONSISTENT + +epp-18: Summary: Domain command test Description: | This test will confirm that the client is able to renew domain names. The @@ -570,7 +602,7 @@ epp-16: - EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE - EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS -epp-17: +epp-19: Summary: Domain command test Description: | This test will confirm that the client is able to initiate a domain @@ -625,13 +657,13 @@ epp-17: - EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS - EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET -epp-18: +epp-20: Summary: Domain rejection test Description: This test confirms that the server behaves correctly if the sponsoring registrar of a domain rejects a transfer request. - The test procedure matches that of `epp-17`, but the transfer request will + The test procedure matches that of `epp-19`, but the transfer request will be rejected rather than approved. An `` command will be used to confirm that the domain name remains under the sponsorship of the original registrar. @@ -640,7 +672,7 @@ epp-18: Errors: - EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER -epp-19: +epp-21: Summary: Domain command test Description: | This test will perform `` commands on the objects created during @@ -662,11 +694,11 @@ epp-19: - EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE - EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE -epp-20: +epp-22: Summary: Domain restore test Description: | This test will perform RGP restore operations on the objects deleted - during `epp-19`, in order to confirm the correct operation of the server's + during `epp-21`, in order to confirm the correct operation of the server's implementation of RFC 3915. Once the restore request has been procssed, the client will perform @@ -675,11 +707,11 @@ epp-20: Input-Parameters: - epp.restoreReportRequired Dependencies: - - epp-19 + - epp-21 Errors: - EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE -epp-21: +epp-23: Summary: Host rename test (if applicable) Description: | This tests verifies the server's support for host rename operations. @@ -717,7 +749,7 @@ epp-21: - EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN - EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME -epp-22: +epp-24: Summary: Host command test (if applicable) Description: | This test will perform `` commands on the objects created during @@ -731,6 +763,6 @@ epp-22: received from the server, the client will perform `` and `` commands to confirm that the objects have been deleted. Dependencies: - - epp-21 + - epp-23 Errors: - EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS diff --git a/inc/epp/errors.yaml b/inc/epp/errors.yaml index 4078ab9..21fcccc 100644 --- a/inc/epp/errors.yaml +++ b/inc/epp/errors.yaml @@ -1478,3 +1478,48 @@ EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS: EPP_GREETING_DOES_NOT_MATCH: Severity: ERROR Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_OBJECT: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_OBJECT: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_ATTRIBUTE: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_ATTRIBUTE: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_REGISTRANT: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA: + Severity: ERROR + Description: TBA + +EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA: + Severity: ERROR + Description: TBA + +EPP_SERVICE_PORT_NOT_CONSISTENT: + Severity: ERROR + Description: TBA + diff --git a/inc/integration/cases.yaml b/inc/integration/cases.yaml index d2251fc..be06af0 100644 --- a/inc/integration/cases.yaml +++ b/inc/integration/cases.yaml @@ -7,17 +7,28 @@ integration-01: are reflected in the RDAP system within the Service Level Requirement of the SLA. - The test system will perform RDAP queries to confirm that the RDAP server - provides responses for the domains created in `epp-14`, and host objects - created in `epp-11` (if applicable). The RDAP server **MUST** provide a 200 - response within 1 hour of the object's `` element. + The test system will connect to the EPP server and create domain and (if + applicable) host and contact objects using the same methodology as `epp-14` + `epp-11`. It will then perform RDAP queries for those objects. + + The RDAP server **MUST** provide a 200 response for every object created + within 1 hour of the object's `` element. Input-Parameters: + - epp.hostName + - epp.serverIssuedClientCertificate01 + - epp.clid01 + - epp.pwd01 - epp.hostModel - rdap.baseURLs - Dependencies: - - epp-14 - - epp-11 Errors: + - EPP_DNS_RESOLUTION_ERROR + - EPP_SERVICE_PORT_UNREACHABLE + - EPP_TLS_CONNECTION_ERROR + - EPP_LOGIN_ERROR + - EPP_XML_PARSE_ERROR + - EPP_GENERIC_COMMAND_ERROR + - EPP_UNEXPECTED_COMMAND_FAILURE + - EPP_SCHEMA_VALIDATION_ERROR - INTEGRATION_RDAP_REQUEST_FAILED - INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP integration-02: @@ -30,13 +41,13 @@ integration-02: the SLA. The test system will perform DNS queries to confirm that the DNS servers - provides responses for the domain names created in `epp-14`. All DNS - servers **MUST** provide the correct DNS response within 1 hour of the - object's `` element. + provide responses for the domain names created in `integration-01`. All DNS + servers **MUST** provide the correct DNS response for all domains within 1 + hour of the domains's `` element. Input-Parameters: - dns.nameservers Dependencies: - - epp-14 + - integration-01 Errors: - INTEGRATION_DNS_QUERY_FAILED - INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS @@ -58,10 +69,9 @@ integration-03: listed in the `integration.rdeSFTPACL` resource have been added to the Access Control List for the SFTP server (if any). - All objects created in the `epp-14` and `epp-11` (if applicable) tests - **MUST** be found within a valid RDE deposit file (that is, the deposit - passes all the tests in the RDE test suite) within 24 hours of each - object's `` element. + All objects created in the `integration-01` test case **MUST** be found + within a valid RDE deposit file (that is, the deposit passes all the tests + in the RDE test suite) within 24 hours of each object's `` element. Furthermore, for each deposit found in the directory, the corresponding RDE report (as described in [Section 2.1 of @@ -82,8 +92,7 @@ integration-03: - integration.rdeSFTPUsername - integration.rriACL Dependencies: - - epp-14 - - epp-11 + - integration-01 Errors: - INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE - INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR diff --git a/inc/suites.yaml.in b/inc/suites.yaml.in index 3aa94c0..4b9803c 100644 --- a/inc/suites.yaml.in +++ b/inc/suites.yaml.in @@ -282,3 +282,5 @@ StandardIntegrationTest: TS_PASSFAIL Test-Cases: ^integration- + Input-Parameters: + - general.minimalPublicDataSet diff --git a/rst-test-specs.html b/rst-test-specs.html index 365630e..68307b0 100644 --- a/rst-test-specs.html +++ b/rst-test-specs.html @@ -168,7 +168,7 @@ -

Registry System Testing - Test Specifications

Version 3.0.263

+

Registry System Testing - Test Specifications

Version 3.0.266

Last Updated: 2024-01-24

GDS Technical Services, Internet Corporation for Assigned Names and Numbers (ICANN)

2. Preamble

+
  • Test Plans
    1. Pre-Delegation Test
    2. RSP Change Test
    3. DNS RSP Change Test
    4. Standard IDN Test
    5. IDN Test (RSP Evaluation)
    6. SRS Gateway Test
    7. Main RSP Evaluation Test
    8. DNS RSP Evaluation Test
    9. DNSSEC RSP Evaluation Test
    10. SRS Gateway RSP Evaluation Test
  • Test Suites
    1. Authoritative DNS Service
    2. DNS Security Extensions (DNSSEC)
    3. Registration Data Access Protocol (RDAP)
    4. Extensible Provisioning Protocol (EPP)
    5. Registry Data Escrow (RDE)
    6. Internationalized Domain Names (IDN)
    7. SRS Gateway
    8. DNSSEC Operations
    9. Minimum Rights Protection Mechanisms (RPMs)
    10. Standard Integration Test
  • Resources
    1. dnssecOps.xfrACL
    2. epp.clientACL
    3. epp.clientCSR
    4. epp.clientCertificate
    5. epp.tlsCertificateStore
    6. integration.rdeSFTPACL
    7. integration.rdeSFTPPublicKey
    8. rde.encryptionKey
  • Test Cases
    1. dns-address01 - Name server address must be globally routable
    2. dns-address02 - Reverse DNS entry exists for name server IP address
    3. dns-address03 - Reverse DNS entry matches name server name
    4. dns-connectivity01 - UDP connectivity to name servers
    5. dns-connectivity02 - TCP connectivity to name servers
    6. dns-connectivity03 - AS Diversity
    7. dns-consistency02 - SOA RNAME consistency
    8. dns-consistency03 - SOA timers consistency
    9. dns-consistency04 - Name server NS consistency
    10. dns-consistency05 - Consistency between glue and authoritative data
    11. dns-consistency06 - SOA MNAME consistency
    12. dns-delegation01 - Minimum number of name servers
    13. dns-delegation02 - Name servers must have distinct IP addresses
    14. dns-delegation03 - No truncation of referrals
    15. dns-delegation04 - Name server is authoritative
    16. dns-delegation05 - Name server must not point at CNAME alias
    17. dns-delegation07 - Parent glue name records present in child
    18. dns-nameserver01 - A name server should not be a recursor
    19. dns-nameserver02 - Test of EDNS0 support
    20. dns-nameserver04 - Same source address
    21. dns-nameserver05 - Behaviour against AAAA query
    22. dns-nameserver06 - NS can be resolved
    23. dns-nameserver08 - Testing QNAME case insensitivity
    24. dns-nameserver09 - Testing QNAME case sensitivity
    25. dns-nameserver10 - Test for undefined EDNS version
    26. dns-nameserver11 - Test for unknown EDNS OPTION-CODE
    27. dns-nameserver12 - Test for unknown EDNS flags
    28. dns-nameserver13 - Test for truncated response on EDNS query
    29. dns-nameserver14 - Test for unknown version with unknown OPTION-CODE
    30. dns-syntax05 - Misuse of '@' character in the SOA RNAME field
    31. dns-syntax06 - No illegal characters in the SOA RNAME field
    32. dns-syntax07 - No illegal characters in the SOA MNAME field
    33. dns-zone07 - SOA master is not an alias
    34. dns-zone10 - No multiple SOA records
    35. dns-zz-idna2008-compliance - IDNA2008 compliance check
    36. dnssec-01 - Legal values for the DS hash digest algorithm
    37. dnssec-02 - DS must match a valid DNSKEY in the child zone
    38. dnssec-03 - Check for too many NSEC3 iterations
    39. dnssec-04 - Check for too short or too long RRSIG lifetimes
    40. dnssec-05 - Check for invalid DNSKEY algorithms
    41. dnssec-06 - Verify DNSSEC additional processing
    42. dnssec-08 - Valid RRSIG for DNSKEY
    43. dnssec-09 - RRSIG(SOA) must be valid and created by a valid DNSKEY
    44. dnssec-10 - Zone contains NSEC or NSEC3 records
    45. dnssec-12 - Test for DNSSEC Algorithm Completeness
    46. dnssec-13 - All DNSKEY algorithms used to sign the zone
    47. dnssec-14 - Check for valid RSA DNSKEY key size
    48. dnssec-15 - Existence of CDS and CDNSKEY
    49. dnssec-16 - Validate CDS
    50. dnssec-17 - Validate CDNSKEY
    51. dnssec-18 - Validate trust from DS to CDS and CDNSKEY
    52. dnssec-91 - Permitted signing algorithms
    53. dnssec-92 - Permitted DS record hash algorithm(s)
    54. dnssecOps01-ZSKRollover - ZSK rollover
    55. dnssecOps02-KSKRollover - KSK rollover
    56. dnssecOps03-AlgorithmRollover - algorithm rollover
    57. epp-01 - Service connectivity test
    58. epp-02 - Protocol conformance test
    59. epp-03 - Authentication test
    60. epp-04 - Domain <check> command test
    61. epp-05 - Host <check> command test (if applicable)
    62. epp-06 - Contact <check> command test (if applicable for the registry type)
    63. epp-07 - Contact <create> command test (if applicable for the registry type)
    64. epp-08 - Contact object access control (if applicable)
    65. epp-09 - Contact <update> command test (if applicable for the registry type)
    66. epp-10 - Contact <delete> command test (if applicable for the registry type)
    67. epp-11 - host <create> command test (if applicable)
    68. epp-12 - Host object access control (if applicable)
    69. epp-13 - Host <update> command test (if applicable)
    70. epp-14 - Domain <create> command test
    71. epp-15 - Registry object integrity test
    72. epp-16 - Domain <update> command test
    73. epp-17 - Service Port consistency test
    74. epp-18 - Domain <renew> command test
    75. epp-19 - Domain <transfer> command test
    76. epp-20 - Domain <transfer> rejection test
    77. epp-21 - Domain <delete> command test
    78. epp-22 - Domain restore test
    79. epp-23 - Host rename test (if applicable)
    80. epp-24 - Host <delete> command test (if applicable)
    81. idn-01 - Label validation test
    82. idn-02 - Level 1 variant handling test
    83. idn-03 - Level 2 variant handling test
    84. idn-04 - Level 3 variant handling test
    85. integration-01 - EPP -> RDAP Integration Test
    86. integration-02 - EPP -> DNS Integration Test
    87. integration-03 - EPP -> RDE Integration Test
    88. minimumRPMs-01 - Claims <check> command test
    89. minimumRPMs-02 - Sunrise domain/launch application <create> command test +
    90. minimumRPMs-03 - Trademark claims domain <create> command test
    91. rdap-01-domainCaseFoldingValidation - Domain label case folding validation
    92. rdap-02-domainNameValidation - Domain Name validation
    93. rdap-03-ipv4Validation - IPv4 address validation
    94. rdap-04-ipv6Validation - IPv6 address validation
    95. rdap-05-stdRdapAsEventActorValidation - asEventActor Validation
    96. rdap-06-stdRdapConformanceValidation - RDAP Conformance validation
    97. rdap-07-stdRdapDomainLookupValidation - Domain Lookup Validation
    98. rdap-08-stdRdapEntitiesValidation - Entities validation
    99. rdap-09-stdRdapEntityLookupValidation - Entity lookup validation
    100. rdap-10-stdRdapErrorResponseBodyValidation - Error Response Body
    101. rdap-11-stdRdapEventsValidation - Events Validation
    102. rdap-12-stdRdapHelpValidation - Help validation
    103. rdap-13-stdRdapIpAddressesValidation - IP Addresses Validation
    104. rdap-14-stdRdapLanguageIdentifierValidation - Language Identifier Validation
    105. rdap-15-stdRdapLdhNameValidation - LDH name
    106. rdap-16-stdRdapLinksValidation - Links validation
    107. rdap-17-stdRdapNameserverLookupValidation - Nameserver lookup validation
    108. rdap-18-stdRdapNameserversSearchValidation - Nameservers search validation
    109. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks Validation
    110. rdap-20-stdRdapPort43WhoisServerValidation - Port 43 WHOIS Server
    111. rdap-21-stdRdapPublicIdsValidation - Public IDs validation
    112. rdap-22-stdRdapRolesValidation - Roles validation
    113. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation
    114. rdap-24-stdRdapStatusValidation - Status validation
    115. rdap-25-stdRdapUnicodeNameValidation - Unicode name
    116. rdap-26-stdRdapVariantsValidation - Variants validation
    117. rdap-27-webUriValidation - Web URI validation
    118. rde-01 - validate deposit filename format
    119. rde-02 - validate signature over deposit file
    120. rde-03 - decrypt deposit file(s)
    121. rde-04 - validate XML/CSV
    122. rde-05 - validate object types
    123. rde-06 - validate object counts
    124. rde-07 - validate domain objects
    125. rde-08 - validate host objects (if applicable)
    126. rde-09 - validate contact objects (if applicable)
    127. rde-10 - validate registrar objects
    128. rde-11 - validate IDN table objects (if applicable)
    129. rde-12 - validate NNDN objects
    130. rde-13 - validate EPP parameters object
    131. rde-14 - validate policy object (if applicable)
    132. srsgw-01 - IPv4 and IPv6 connectivity
    133. srsgw-02 - Host <create> synchronization (if applicable)
    134. srsgw-03 - Contact <create> synchronization (if applicable)
    135. srsgw-04 - Domain <create> synchronization
    136. srsgw-05 - Domain <renew> synchronisation
    137. srsgw-06 - Domain <transfer> synchronisation
    138. srsgw-07 - Domain <transfer> approval synchronisation
    139. srsgw-08 - Domain <delete> synchronisation
    140. srsgw-09 - Host <update> synchronization (if applicable)
    141. srsgw-10 - Host <delete> synchronization (if applicable)
    142. srsgw-11 - Contact <update> synchronization (if applicable)
    143. srsgw-12 - Contact <delete> synchronization (if applicable)
    144. srsgw-13 - Domain RDAP synchronization
    145. srsgw-14 - Nameserver RDAP synchronization
    146. srsgw-15 - Registrar RDAP synchronization
  • Input Parameters
    1. dns.nameservers (object)
    2. dnssec.dsRecords (object)
    3. dnssecOps.algorithmRolloverZone (string)
    4. dnssecOps.csk (boolean)
    5. dnssecOps.kskRolloverZone (string)
    6. dnssecOps.nameservers (object)
    7. dnssecOps.primaryServer (string)
    8. dnssecOps.tsigKey (object)
    9. dnssecOps.zskRolloverZone (string)
    10. epp.clid01 (string)
    11. epp.clid02 (string)
    12. epp.greeting (string)
    13. epp.hostModel (string)
    14. epp.hostName (string)
    15. epp.pwd01 (string)
    16. epp.pwd02 (string)
    17. epp.registeredContacts (array)
    18. epp.registeredNames (array)
    19. epp.registeredNameservers (array)
    20. epp.restoreReportRequired (boolean)
    21. epp.secDNSInterfaces (string)
    22. epp.serverIssuedClientCertificate01 (string)
    23. epp.serverIssuedClientCertificate02 (string)
    24. general.minimalPublicDataSet (boolean)
    25. integration.rdeSFTPDirectory (string)
    26. integration.rdeSFTPHostname (string)
    27. integration.rdeSFTPUsername (string)
    28. integration.rriACL (array)
    29. minimumRPMS.claimsTLD (string)
    30. minimumRPMS.sunriseModels (string)
    31. minimumRPMS.sunriseTLD (string)
    32. rdap.baseURLs (object)
    33. rdap.testDomains (object)
    34. rdap.testEntities (object)
    35. rdap.testNameservers (object)
    36. rde.depositFile (file)
    37. rde.publicKey (file)
    38. rde.signatureFile (file)
    39. srsgw.eppClid01 (string)
    40. srsgw.eppClid02 (string)
    41. srsgw.eppHostName (string)
    42. srsgw.eppPwd01 (string)
    43. srsgw.eppPwd02 (string)
    44. srsgw.rdapBaseURLs (object)
    45. srsgw.serverIssuedClientCertificate01 (string)
    46. srsgw.serverIssuedClientCertificate02 (string)
  • Errors
    1. DNSSEC_DNS_QUERY_ERROR (ERROR)
    2. DNSSEC_INVALID_DIGEST_ALGORITHM (ERROR)
    3. DNSSEC_INVALID_SIGNING_ALGORITHM (ERROR)
    4. DNSSEC_OPS_ALGORITHM_ROLLOVER_CHAIN_OF_TRUST_BROKEN (ERROR)
    5. DNSSEC_OPS_ALGORITHM_ROLLOVER_NOT_COMPLETED (ERROR)
    6. DNSSEC_OPS_INVALID_ALGORITHM (ERROR)
    7. DNSSEC_OPS_KSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN (ERROR)
    8. DNSSEC_OPS_KSK_ROLLOVER_NOT_COMPLETED (ERROR)
    9. DNSSEC_OPS_XFR_FAILED (ERROR)
    10. DNSSEC_OPS_ZSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN (ERROR)
    11. DNSSEC_OPS_ZSK_ROLLOVER_NOT_COMPLETED (ERROR)
    12. DNS_IDNA2008_INVALID_MNAME (ERROR)
    13. DNS_IDNA2008_INVALID_RNAME (ERROR)
    14. EPP_CONTACT_CHECK_INVALID_CONTACT_ID_INCORRECT_AVAIL (ERROR)
    15. EPP_CONTACT_CHECK_REGISTERED_CONTACT_ID_INCORRECT_AVAIL (ERROR)
    16. EPP_CONTACT_CHECK_VALID_CONTACT_ID_INCORRECT_AVAIL (ERROR)
    17. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC (ERROR)
    18. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CITY (ERROR)
    19. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL (ERROR)
    20. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ID (ERROR)
    21. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_NAME (ERROR)
    22. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ORG (ERROR)
    23. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_PC (ERROR)
    24. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_POSTALINFO_TYPE (ERROR)
    25. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_SP (ERROR)
    26. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STATUS (ERROR)
    27. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STREET (ERROR)
    28. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE (ERROR)
    29. EPP_CONTACT_CREATE_INFO_RESPONSE_NOT_1000 (ERROR)
    30. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_CC (ERROR)
    31. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_EMAIL (ERROR)
    32. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_ID (ERROR)
    33. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_POSTALINFO_TYPE (ERROR)
    34. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_STATUS (ERROR)
    35. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_VOICE (ERROR)
    36. EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS (ERROR)
    37. EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001 (ERROR)
    38. EPP_CONTACT_INFO_RESPONSE_NOT_2201 (ERROR)
    39. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC (ERROR)
    40. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CITY (ERROR)
    41. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL (ERROR)
    42. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ID (ERROR)
    43. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_NAME (ERROR)
    44. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ORG (ERROR)
    45. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_PC (ERROR)
    46. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_POSTALINFO_TYPE (ERROR)
    47. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_SP (ERROR)
    48. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STATUS (ERROR)
    49. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STREET (ERROR)
    50. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE (ERROR)
    51. EPP_CONTACT_UPDATE_INFO_RESPONSE_NOT_1000 (ERROR)
    52. EPP_CONTACT_UPDATE_RESPONSE_NOT_2201 (ERROR)
    53. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_CC (ERROR)
    54. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_CITY (ERROR)
    55. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_EMAIL (ERROR)
    56. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_ORG (ERROR)
    57. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_PC (ERROR)
    58. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_POSTALINFO_TYPE (ERROR)
    59. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_SP (ERROR)
    60. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_STATUS (ERROR)
    61. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_STREET (ERROR)
    62. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_VOICE (ERROR)
    63. EPP_DNS_RESOLUTION_ERROR (ERROR)
    64. EPP_DOMAIN_CHECK_INVALID_DOMAIN_INCORRECT_AVAIL (ERROR)
    65. EPP_DOMAIN_CHECK_REGISTERED_DOMAIN_INCORRECT_AVAIL (ERROR)
    66. EPP_DOMAIN_CHECK_VALID_DOMAIN_INCORRECT_AVAIL (ERROR)
    67. EPP_DOMAIN_CREATE_INFO_RESPONSE_INVALID_ROID (ERROR)
    68. EPP_DOMAIN_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES (ERROR)
    69. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_AUTHINFO (ERROR)
    70. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_ATTRIBUTES (ERROR)
    71. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_ATTRIBUTES_WITHOUT_GLUE (ERROR)
    72. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_OBJECTS (ERROR)
    73. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_DNSSEC_DATA (ERROR)
    74. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_DOMAIN_NAME (ERROR)
    75. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_HOST_ATTRIBUTE (ERROR)
    76. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_HOST_ATTRIBUTES (ERROR)
    77. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_PERIOD (ERROR)
    78. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NON_EXISTENT_CONTACT_OBJECT (ERROR)
    79. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NON_EXISTENT_HOST_OBJECT (ERROR)
    80. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NO_REGISTRANT_FOR_THICK_REGISTRY (ERROR)
    81. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_REGISTRANT_FOR_THIN_REGISTRY (ERROR)
    82. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE (ERROR)
    83. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS (ERROR)
    84. EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE (ERROR)
    85. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA (ERROR)
    86. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_ATTRIBUTE (ERROR)
    87. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_OBJECT (ERROR)
    88. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT (ERROR)
    89. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE (ERROR)
    90. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA (ERROR)
    91. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_ATTRIBUTE (ERROR)
    92. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_OBJECT (ERROR)
    93. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_REGISTRANT (ERROR)
    94. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE (ERROR)
    95. EPP_GENERIC_COMMAND_ERROR (ERROR)
    96. EPP_GREETING_DOES_NOT_MATCH (ERROR)
    97. EPP_GREETING_INVALID_LANG (ERROR)
    98. EPP_GREETING_MISSING_EXTURI (ERROR)
    99. EPP_GREETING_MISSING_OBJURI (ERROR)
    100. EPP_GREETING_RECOMMENDED_EXTENSION_MISSING (WARNING)
    101. EPP_GREETING_SVDATE_INVALID (ERROR)
    102. EPP_GREETING_SVID_INVALID (ERROR)
    103. EPP_GREETING_UNEXPECTED_EXTURI (ERROR)
    104. EPP_GREETING_UNEXPECTED_OBJURI (ERROR)
    105. EPP_GREETING_VERSION_INVALID (ERROR)
    106. EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL (ERROR)
    107. EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL (ERROR)
    108. EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL (ERROR)
    109. EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES (ERROR)
    110. EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST (ERROR)
    111. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_HOSTNAME (ERROR)
    112. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS (ERROR)
    113. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS (ERROR)
    114. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE (ERROR)
    115. EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS (ERROR)
    116. EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME (ERROR)
    117. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN (ERROR)
    118. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_NONEXISTENT_DOMAIN (ERROR)
    119. EPP_HOST_RENAME_SERVER_REJECTS_OUT_OF_BAILIWICK_NAME (ERROR)
    120. EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME (ERROR)
    121. EPP_HOST_UPDATE_AUTHZ_ERROR (ERROR)
    122. EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES (ERROR)
    123. EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST (ERROR)
    124. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_HOSTNAME (ERROR)
    125. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS (ERROR)
    126. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS (ERROR)
    127. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE (ERROR)
    128. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT (ERROR)
    129. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT (ERROR)
    130. EPP_LOGIN_ERROR (ERROR)
    131. EPP_MISSING_AAAA_RECORDS (WARNING)
    132. EPP_MISSING_A_RECORDS (ERROR)
    133. EPP_NO_GREETING_RECEIVED (ERROR)
    134. EPP_OBJECT_SHOULD_EXIST (ERROR)
    135. EPP_OBJECT_SHOULD_NOT_EXIST (ERROR)
    136. EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS (ERROR)
    137. EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE (ERROR)
    138. EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE (ERROR)
    139. EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD (ERROR)
    140. EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE (ERROR)
    141. EPP_SCHEMA_VALIDATION_ERROR (ERROR)
    142. EPP_SERVICE_PORT_NOT_CONSISTENT (ERROR)
    143. EPP_SERVICE_PORT_UNREACHABLE (ERROR)
    144. EPP_TLS_BAD_CIPHER (ERROR)
    145. EPP_TLS_CERTIFICATE_CHAIN_MISSING (ERROR)
    146. EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH (ERROR)
    147. EPP_TLS_CONNECTION_ERROR (ERROR)
    148. EPP_TLS_EXPIRED_CERTIFICATE (ERROR)
    149. EPP_TLS_FORBIDDEN_PROTOCOL_SUPPORTED (ERROR)
    150. EPP_TLS_REQUIRED_PROTOCOL_NOT_SUPPORTED (ERROR)
    151. EPP_TLS_UNTRUSTED_CERTIFICATE (ERROR)
    152. EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED (ERROR)
    153. EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET (ERROR)
    154. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS (ERROR)
    155. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_STATUS_CODE (ERROR)
    156. EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE (ERROR)
    157. EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED (ERROR)
    158. EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO (ERROR)
    159. EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO (ERROR)
    160. EPP_TRANSFER_SERVER_ACCEPTS_INVALID_PERIOD (ERROR)
    161. EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER (ERROR)
    162. EPP_UNEXPECTED_COMMAND_FAILURE (ERROR)
    163. EPP_UNEXPECTED_COMMAND_SUCCESS (ERROR)
    164. EPP_XML_PARSE_ERROR (ERROR)
    165. IDN_SERVER_ACCEPTS_INVALID_LABEL (ERROR)
    166. IDN_SERVER_REJECTS_VALID_LABEL (ERROR)
    167. IDN_VARIANT_LABEL_NOT_BLOCKED (ERROR)
    168. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_FROM_INCORRECT_REGISTRAR (ERROR)
    169. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_WITH_INCORRECT_REGISTRANT (ERROR)
    170. INTEGRATION_DNS_ANSWER_IS_INCORRECT (ERROR)
    171. INTEGRATION_DNS_QUERY_FAILED (ERROR)
    172. INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS (ERROR)
    173. INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP (ERROR)
    174. INTEGRATION_RDAP_REQUEST_FAILED (ERROR)
    175. INTEGRATION_RDE_DEADLINE_MISSED (ERROR)
    176. INTEGRATION_RDE_MISSING_OBJECTS (ERROR)
    177. INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR (ERROR)
    178. INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE (ERROR)
    179. RDE_CONTACT_HAS_INVALID_CC (ERROR)
    180. RDE_CONTACT_HAS_INVALID_EMAIL (ERROR)
    181. RDE_CONTACT_HAS_INVALID_ROID (ERROR)
    182. RDE_CONTACT_HAS_MULTIPLE_POSTALINFO_TYPES (ERROR)
    183. RDE_CONTACT_HAS_NON_UNIQUE_ID (ERROR)
    184. RDE_CONTACT_HAS_UNKNOWN_ACRR (ERROR)
    185. RDE_CONTACT_HAS_UNKNOWN_CLID (ERROR)
    186. RDE_CONTACT_HAS_UNKNOWN_CRRR (ERROR)
    187. RDE_CONTACT_HAS_UNKNOWN_RERR (ERROR)
    188. RDE_CONTACT_HAS_UNKNOWN_UPRR (ERROR)
    189. RDE_DECRYPTION_FAILED (ERROR)
    190. RDE_DOMAIN_HAS_INVALID_CLID (ERROR)
    191. RDE_DOMAIN_HAS_INVALID_CRDATE (ERROR)
    192. RDE_DOMAIN_HAS_INVALID_EXDATE (ERROR)
    193. RDE_DOMAIN_HAS_INVALID_NAME (ERROR)
    194. RDE_DOMAIN_HAS_INVALID_REGISTRANT (ERROR)
    195. RDE_DOMAIN_HAS_INVALID_ROID (ERROR)
    196. RDE_DOMAIN_HAS_INVALID_STATUS (ERROR)
    197. RDE_DOMAIN_HAS_MISSING_CLID (ERROR)
    198. RDE_DOMAIN_HAS_MISSING_CRDATE (ERROR)
    199. RDE_DOMAIN_HAS_MISSING_EXDATE (ERROR)
    200. RDE_DOMAIN_HAS_MISSING_NAME (ERROR)
    201. RDE_DOMAIN_HAS_MISSING_REGISTRANT (ERROR)
    202. RDE_DOMAIN_HAS_MISSING_ROID (ERROR)
    203. RDE_DOMAIN_HAS_MISSING_STATUS (ERROR)
    204. RDE_GREETING_DOES_NOT_MATCH (ERROR)
    205. RDE_HOST_HAS_INVALID_CLID (ERROR)
    206. RDE_HOST_HAS_INVALID_IP_ADDRESS (ERROR)
    207. RDE_HOST_HAS_INVALID_NAME (ERROR)
    208. RDE_HOST_HAS_INVALID_ROID (ERROR)
    209. RDE_HOST_HAS_INVALID_STATUS (ERROR)
    210. RDE_HOST_HAS_MISSING_CLID (ERROR)
    211. RDE_HOST_HAS_MISSING_IP_ADDRESS (ERROR)
    212. RDE_HOST_HAS_MISSING_NAME (ERROR)
    213. RDE_HOST_HAS_MISSING_ROID (ERROR)
    214. RDE_HOST_HAS_MISSING_STATUS (ERROR)
    215. RDE_IDN_OBJECT_INVALID (ERROR)
    216. RDE_IDN_OBJECT_MISSING (ERROR)
    217. RDE_IDN_OBJECT_UNEXPECTED (ERROR)
    218. RDE_INVALID_CSV (ERROR)
    219. RDE_INVALID_FILENAME (ERROR)
    220. RDE_INVALID_SIGNATURE (ERROR)
    221. RDE_INVALID_XML (ERROR)
    222. RDE_MISSING_OBJECT_URI (ERROR)
    223. RDE_MIXED_TYPES (ERROR)
    224. RDE_NNDN_CONFLICTS_WITH_DOMAIN (ERROR)
    225. RDE_OBJECT_COUNT_MISMATCH (ERROR)
    226. RDE_POLICY_OBJECT_INVALID (ERROR)
    227. RDE_POLICY_OBJECT_MISSING (ERROR)
    228. RDE_POLICY_OBJECT_MISSING_OBJECTS (ERROR)
    229. RDE_POLICY_OBJECT_UNEXPECTED_OBJECTS (ERROR)
    230. RDE_REGISTRAR_HAS_INVALID_GURID (ERROR)
    231. RDE_REGISTRAR_HAS_INVALID_ID (ERROR)
    232. RDE_REGISTRAR_HAS_INVALID_NAME (ERROR)
    233. RDE_REGISTRAR_HAS_MISSING_GURID (ERROR)
    234. RDE_REGISTRAR_HAS_MISSING_ID (ERROR)
    235. RDE_REGISTRAR_HAS_MISSING_NAME (ERROR)
    236. RDE_SCHEMA_VALIDATION_ERROR (ERROR)
    237. RDE_UNEXPECTED_OBJECT_URI (ERROR)
    238. RDE_XML_PARSE_ERROR (ERROR)
    239. RPMS_MISSING_CLAIMS_KEY (ERROR)
    240. RPMS_SUNRISE_CREATE_INFO_OBJECT_DOES_NOT_EXIST (ERROR)
    241. RPMS_SUNRISE_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES (ERROR)
    242. RPMS_SUNRISE_CREATE_UNEXPECTED_FAILURE_USING_VALID_SMD (ERROR)
    243. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_SMD (ERROR)
    244. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_REVOKED_SMD (ERROR)
    245. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_SMD_WITH_REVOKED_SIGNATURE (ERROR)
    246. RPMS_TRADEMARK_CREATE_INFO_OBJECT_DOES_NOT_EXIST (ERROR)
    247. RPMS_TRADEMARK_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES (ERROR)
    248. RPMS_TRADEMARK_CREATE_UNEXPECTED_FAILURE_USING_VALID_CLAIM_KEY (ERROR)
    249. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_ACCEPTANCE_DATE (ERROR)
    250. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_CLAIM_KEY (ERROR)
    251. RPMS_UNEXPECTED_CLAIMS_KEY (ERROR)
    252. SRSGW_CONTACT_CREATE_FAILED (ERROR)
    253. SRSGW_CONTACT_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES (ERROR)
    254. SRSGW_CONTACT_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE (ERROR)
    255. SRSGW_DOMAIN_CREATE_FAILED (ERROR)
    256. SRSGW_DOMAIN_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES (ERROR)
    257. SRSGW_DOMAIN_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE (ERROR)
    258. SRSGW_DOMAIN_DELETE_DOMAIN_NOT_PENDINGDELETE (ERROR)
    259. SRSGW_DOMAIN_DELETE_FAILED (ERROR)
    260. SRSGW_DOMAIN_DELETE_RGP_STATUS_NOT_PENDINGDELETERESTORABLE (ERROR)
    261. SRSGW_DOMAIN_RENEW_FAILED (ERROR)
    262. SRSGW_DOMAIN_RENEW_OBJECT_HAS_INVALID_EXDATE (ERROR)
    263. SRSGW_DOMAIN_RENEW_OBJECT_NOT_UPDATED_WITHIN_DEADLINE (ERROR)
    264. SRSGW_DOMAIN_TRANSFER_APPROVAL_FAILED (ERROR)
    265. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_HAS_INCORRECT_CLID (ERROR)
    266. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_NOT_UPDATED_WITHIN_DEADLINE (ERROR)
    267. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_STILL_PENDING_TRANSFER (ERROR)
    268. SRSGW_DOMAIN_TRANSFER_REQUEST_FAILED (ERROR)
    269. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_HAS_INCORRECT_CLID (ERROR)
    270. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_PENDING_TRANSFER (ERROR)
    271. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_UPDATED_WITHIN_DEADLINE (ERROR)
    272. SRSGW_EPP_DNS_RESOLUTION_ERROR (ERROR)
    273. SRSGW_EPP_GENERIC_COMMAND_ERROR (ERROR)
    274. SRSGW_EPP_LOGIN_ERROR (ERROR)
    275. SRSGW_EPP_OBJECT_SHOULD_EXIST (ERROR)
    276. SRSGW_EPP_OBJECT_SHOULD_NOT_EXIST (ERROR)
    277. SRSGW_EPP_SCHEMA_VALIDATION_ERROR (ERROR)
    278. SRSGW_EPP_SERVICE_PORT_UNREACHABLE (ERROR)
    279. SRSGW_EPP_TLS_CONNECTION_ERROR (ERROR)
    280. SRSGW_EPP_UNEXPECTED_COMMAND_FAILURE (ERROR)
    281. SRSGW_EPP_UNEXPECTED_COMMAND_SUCCESS (ERROR)
    282. SRSGW_EPP_XML_PARSE_ERROR (ERROR)
    283. SRSGW_HOST_CREATE_FAILED (ERROR)
    284. SRSGW_HOST_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES (ERROR)
    285. SRSGW_HOST_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE (ERROR)
    286. ZM_AAAA_BAD_RDATA (ERROR)
    287. ZM_AAAA_QUERY_DROPPED (ERROR)
    288. ZM_AAAA_UNEXPECTED_RCODE (ERROR)
    289. ZM_ALGORITHM_DEPRECATED (ERROR)
    290. ZM_ALGORITHM_NOT_RECOMMENDED (WARNING)
    291. ZM_ALGORITHM_NOT_ZONE_SIGN (ERROR)
    292. ZM_ALGORITHM_PRIVATE (ERROR)
    293. ZM_ALGORITHM_RESERVED (ERROR)
    294. ZM_ALGORITHM_UNASSIGNED (ERROR)
    295. ZM_A_UNEXPECTED_RCODE (ERROR)
    296. ZM_BREAKS_ON_EDNS (ERROR)
    297. ZM_CHILD_NS_FAILED (ERROR)
    298. ZM_CHILD_NS_SAME_IP (ERROR)
    299. ZM_CHILD_ZONE_LAME (ERROR)
    300. ZM_CN01_MISSING_NS_RECORD_UDP (ERROR)
    301. ZM_CN01_MISSING_SOA_RECORD_UDP (ERROR)
    302. ZM_CN01_NO_RESPONSE_NS_QUERY_UDP (ERROR)
    303. ZM_CN01_NO_RESPONSE_SOA_QUERY_UDP (ERROR)
    304. ZM_CN01_NO_RESPONSE_UDP (ERROR)
    305. ZM_CN01_NS_RECORD_NOT_AA_UDP (ERROR)
    306. ZM_CN01_SOA_RECORD_NOT_AA_UDP (ERROR)
    307. ZM_CN01_UNEXPECTED_RCODE_NS_QUERY_UDP (ERROR)
    308. ZM_CN01_UNEXPECTED_RCODE_SOA_QUERY_UDP (ERROR)
    309. ZM_CN01_WRONG_NS_RECORD_UDP (ERROR)
    310. ZM_CN01_WRONG_SOA_RECORD_UDP (ERROR)
    311. ZM_CN02_MISSING_NS_RECORD_TCP (ERROR)
    312. ZM_CN02_MISSING_SOA_RECORD_TCP (ERROR)
    313. ZM_CN02_NO_RESPONSE_NS_QUERY_TCP (ERROR)
    314. ZM_CN02_NO_RESPONSE_SOA_QUERY_TCP (ERROR)
    315. ZM_CN02_NO_RESPONSE_TCP (ERROR)
    316. ZM_CN02_NS_RECORD_NOT_AA_TCP (ERROR)
    317. ZM_CN02_SOA_RECORD_NOT_AA_TCP (ERROR)
    318. ZM_CN02_UNEXPECTED_RCODE_NS_QUERY_TCP (ERROR)
    319. ZM_CN02_UNEXPECTED_RCODE_SOA_QUERY_TCP (ERROR)
    320. ZM_CN02_WRONG_NS_RECORD_TCP (ERROR)
    321. ZM_CN02_WRONG_SOA_RECORD_TCP (ERROR)
    322. ZM_DEL_NS_SAME_IP (ERROR)
    323. ZM_DNSKEY_SMALLER_THAN_REC (WARNING)
    324. ZM_DNSKEY_TOO_LARGE_FOR_ALGO (ERROR)
    325. ZM_DNSKEY_TOO_SMALL_FOR_ALGO (ERROR)
    326. ZM_DNSSEC_03_FAILED (ERROR)
    327. ZM_DNSSEC_04_FAILED (ERROR)
    328. ZM_DNSSEC_06_FAILED (ERROR)
    329. ZM_DNSSEC_12_FAILED (ERROR)
    330. ZM_DNS_ADDRESS01_FAILED (ERROR)
    331. ZM_DNS_ADDRESS02_FAILED (ERROR)
    332. ZM_DNS_ADDRESS03_FAILED (ERROR)
    333. ZM_DNS_DELEGATION04_FAILED (ERROR)
    334. ZM_DNS_DELEGATION07_FAILED (ERROR)
    335. ZM_DNS_NAMESERVER04_FAILED (ERROR)
    336. ZM_DNS_NAMESERVER06_FAILED (ERROR)
    337. ZM_DNS_NAMESERVER08_FAILED (ERROR)
    338. ZM_DNS_NAMESERVER09_FAILED (ERROR)
    339. ZM_DNS_SYNTAX05_FAILED (ERROR)
    340. ZM_DNS_SYNTAX07_FAILED (ERROR)
    341. ZM_DNS_ZONE07_FAILED (ERROR)
    342. ZM_DS01_DS_ALGO_2_MISSING (ERROR)
    343. ZM_DS01_DS_ALGO_DEPRECATED (ERROR)
    344. ZM_DS01_DS_ALGO_NOT_DS (ERROR)
    345. ZM_DS01_DS_ALGO_RESERVED (ERROR)
    346. ZM_DS02_DNSKEY_NOT_FOR_ZONE_SIGNING (ERROR)
    347. ZM_DS02_DNSKEY_NOT_SEP (ERROR)
    348. ZM_DS02_DNSKEY_NOT_SIGNED_BY_ANY_DS (ERROR)
    349. ZM_DS02_NO_DNSKEY_FOR_DS (ERROR)
    350. ZM_DS02_NO_MATCHING_DNSKEY_RRSIG (ERROR)
    351. ZM_DS02_NO_MATCH_DS_DNSKEY (ERROR)
    352. ZM_DS02_NO_VALID_DNSKEY_FOR_ANY_DS (ERROR)
    353. ZM_DS02_RRSIG_NOT_VALID_BY_DNSKEY (ERROR)
    354. ZM_DS08_DNSKEY_RRSIG_EXPIRED (ERROR)
    355. ZM_DS08_DNSKEY_RRSIG_NOT_YET_VALID (ERROR)
    356. ZM_DS08_MISSING_RRSIG_IN_RESPONSE (ERROR)
    357. ZM_DS08_NO_MATCHING_DNSKEY (ERROR)
    358. ZM_DS08_RRSIG_NOT_VALID_BY_DNSKEY (ERROR)
    359. ZM_DS09_MISSING_RRSIG_IN_RESPONSE (ERROR)
    360. ZM_DS09_NO_MATCHING_DNSKEY (ERROR)
    361. ZM_DS09_RRSIG_NOT_VALID_BY_DNSKEY (ERROR)
    362. ZM_DS09_SOA_RRSIG_EXPIRED (ERROR)
    363. ZM_DS09_SOA_RRSIG_NOT_YET_VALID (ERROR)
    364. ZM_DS10_ANSWER_VERIFY_ERROR (ERROR)
    365. ZM_DS10_INCONSISTENT_NSEC_NSEC3 (ERROR)
    366. ZM_DS10_MISSING_NSEC_NSEC3 (ERROR)
    367. ZM_DS10_MIXED_NSEC_NSEC3 (ERROR)
    368. ZM_DS10_NAME_NOT_COVERED_BY_NSEC (ERROR)
    369. ZM_DS10_NAME_NOT_COVERED_BY_NSEC3 (ERROR)
    370. ZM_DS10_NON_EXISTENT_RESPONSE_ERROR (ERROR)
    371. ZM_DS10_NSEC3_MISSING_SIGNATURE (ERROR)
    372. ZM_DS10_NSEC3_RRSIG_VERIFY_ERROR (ERROR)
    373. ZM_DS10_NSEC_MISSING_SIGNATURE (ERROR)
    374. ZM_DS10_NSEC_RRSIG_VERIFY_ERROR (ERROR)
    375. ZM_DS10_UNSIGNED_ANSWER (ERROR)
    376. ZM_DS13_ALGO_NOT_SIGNED_DNSKEY (ERROR)
    377. ZM_DS13_ALGO_NOT_SIGNED_NS (ERROR)
    378. ZM_DS13_ALGO_NOT_SIGNED_SOA (ERROR)
    379. ZM_DS15_INCONSISTENT_CDNSKEY (ERROR)
    380. ZM_DS15_INCONSISTENT_CDS (ERROR)
    381. ZM_DS15_MISMATCH_CDS_CDNSKEY (ERROR)
    382. ZM_DS16_CDS_INVALID_RRSIG (ERROR)
    383. ZM_DS16_CDS_MATCHES_NON_SEP_DNSKEY (ERROR)
    384. ZM_DS16_CDS_MATCHES_NON_ZONE_DNSKEY (ERROR)
    385. ZM_DS16_CDS_MATCHES_NO_DNSKEY (ERROR)
    386. ZM_DS16_CDS_NOT_SIGNED_BY_CDS (ERROR)
    387. ZM_DS16_CDS_SIGNED_BY_UNKNOWN_DNSKEY (ERROR)
    388. ZM_DS16_CDS_UNSIGNED (ERROR)
    389. ZM_DS16_CDS_WITHOUT_DNSKEY (ERROR)
    390. ZM_DS16_DNSKEY_NOT_SIGNED_BY_CDS (ERROR)
    391. ZM_DS16_MIXED_DELETE_CDS (ERROR)
    392. ZM_DS17_CDNSKEY_INVALID_RRSIG (ERROR)
    393. ZM_DS17_CDNSKEY_IS_NON_SEP (ERROR)
    394. ZM_DS17_CDNSKEY_IS_NON_ZONE (ERROR)
    395. ZM_DS17_CDNSKEY_MATCHES_NO_DNSKEY (ERROR)
    396. ZM_DS17_CDNSKEY_NOT_SIGNED_BY_CDNSKEY (ERROR)
    397. ZM_DS17_CDNSKEY_SIGNED_BY_UNKNOWN_DNSKEY (ERROR)
    398. ZM_DS17_CDNSKEY_UNSIGNED (ERROR)
    399. ZM_DS17_CDNSKEY_WITHOUT_DNSKEY (ERROR)
    400. ZM_DS17_DNSKEY_NOT_SIGNED_BY_CDNSKEY (ERROR)
    401. ZM_DS17_MIXED_DELETE_CDNSKEY (ERROR)
    402. ZM_DS18_NO_MATCH_CDNSKEY_RRSIG_DS (ERROR)
    403. ZM_DS18_NO_MATCH_CDS_RRSIG_DS (ERROR)
    404. ZM_EDNS_RESPONSE_WITHOUT_EDNS (ERROR)
    405. ZM_EDNS_VERSION_ERROR (ERROR)
    406. ZM_EMPTY_ASN_SET (ERROR)
    407. ZM_ERROR_ASN_DATABASE (ERROR)
    408. ZM_EXTRA_ADDRESS_CHILD (ERROR)
    409. ZM_IN_BAILIWICK_ADDR_MISMATCH (ERROR)
    410. ZM_IPV4_ONE_ASN (ERROR)
    411. ZM_IPV6_ONE_ASN (ERROR)
    412. ZM_IS_A_RECURSOR (ERROR)
    413. ZM_MISSING_OPT_IN_TRUNCATED (ERROR)
    414. ZM_MULTIPLE_NS_SET (ERROR)
    415. ZM_MULTIPLE_SOA (ERROR)
    416. ZM_MULTIPLE_SOA_MNAMES (ERROR)
    417. ZM_MULTIPLE_SOA_RNAMES (ERROR)
    418. ZM_MULTIPLE_SOA_TIME_PARAMETER_SET (ERROR)
    419. ZM_N10_EDNS_RESPONSE_ERROR (ERROR)
    420. ZM_N10_NO_RESPONSE_EDNS1_QUERY (ERROR)
    421. ZM_N10_UNEXPECTED_RCODE (ERROR)
    422. ZM_N11_NO_EDNS (ERROR)
    423. ZM_N11_NO_RESPONSE (ERROR)
    424. ZM_N11_RETURNS_UNKNOWN_OPTION_CODE (ERROR)
    425. ZM_N11_UNEXPECTED_ANSWER_SECTION (ERROR)
    426. ZM_N11_UNEXPECTED_RCODE (ERROR)
    427. ZM_N11_UNSET_AA (ERROR)
    428. ZM_NOT_ENOUGH_IPV4_NS_CHILD (ERROR)
    429. ZM_NOT_ENOUGH_IPV4_NS_DEL (ERROR)
    430. ZM_NOT_ENOUGH_IPV6_NS_CHILD (ERROR)
    431. ZM_NOT_ENOUGH_IPV6_NS_DEL (ERROR)
    432. ZM_NOT_ENOUGH_NS_CHILD (ERROR)
    433. ZM_NOT_ENOUGH_NS_DEL (ERROR)
    434. ZM_NO_EDNS_SUPPORT (ERROR)
    435. ZM_NO_IPV4_NS_CHILD (ERROR)
    436. ZM_NO_IPV4_NS_DEL (ERROR)
    437. ZM_NO_IPV6_NS_CHILD (ERROR)
    438. ZM_NO_IPV6_NS_DEL (ERROR)
    439. ZM_NO_RESPONSE (ERROR)
    440. ZM_NO_RESPONSE_DNSKEY (ERROR)
    441. ZM_NO_RESPONSE_NS_QUERY (ERROR)
    442. ZM_NO_RESPONSE_SOA_QUERY (ERROR)
    443. ZM_NO_SOA_IN_RESPONSE (ERROR)
    444. ZM_NS_ERROR (ERROR)
    445. ZM_NS_IS_CNAME (ERROR)
    446. ZM_OUT_OF_BAILIWICK_ADDR_MISMATCH (ERROR)
    447. ZM_REFERRAL_SIZE_TOO_LARGE (ERROR)
    448. ZM_RNAME_MAIL_DOMAIN_INVALID (ERROR)
    449. ZM_RNAME_MAIL_DOMAIN_LOCALHOST (ERROR)
    450. ZM_RNAME_MAIL_ILLEGAL_CNAME (ERROR)
    451. ZM_RNAME_RFC822_INVALID (ERROR)
    452. ZM_UNEXPECTED_RCODE (WARNING)
    453. ZM_UNKNOWN_OPTION_CODE (ERROR)
    454. ZM_UNSUPPORTED_EDNS_VER (ERROR)
    455. ZM_WRONG_SOA (ERROR)
    456. ZM_Z_FLAGS_NOTCLEAR (ERROR)
  • About this document
  • ● ━━
    ● ━━
    ● ━━

    2. Preamble

    This file describes each test plan, suite and case in the RST system, as well as the input @@ -451,7 +451,7 @@

    Pass/fail criteria

    1. Authoritative DNS Service
    2. DNS Security Extensions (DNSSEC)
    3. Registration Data Access Protocol (RDAP)
    4. Extensible Provisioning Protocol (EPP)
    5. Registry Data Escrow (RDE)
    6. Internationalized Domain Names (IDN)
    7. Standard Integration Test

    3.1.4. Resources

    The following resources may be required to prepare for this test plan:

    3.1.5. Errors

    This test plan may produce the following errors:

    -

    3.1.6. Input parameters

    This plan requires the following input parameters:

    +

    3.1.6. Input parameters

    This plan requires the following input parameters:

    3.1.7. Required files

    3.1.8. RST-API example

    POST /test/987654/inputs HTTP/1.1
     Content-Type: application/json
     Content-Length: 2666
    @@ -532,17 +532,17 @@ 

    Pass/fail criteria

    - - + + Perl - + dns-address01 - -dns-address01 + +dns-address01 @@ -550,1849 +550,1867 @@

    Pass/fail criteria

    dns-address02 - -dns-address02 + +dns-address02 dns-address01->dns-address02 - - + + dns-address03 - -dns-address03 + +dns-address03 dns-address02->dns-address03 - - + + dns-connectivity01 - -dns-connectivity01 + +dns-connectivity01 dns-address03->dns-connectivity01 - - + + dns-connectivity02 - -dns-connectivity02 + +dns-connectivity02 dns-connectivity01->dns-connectivity02 - - + + dns-connectivity03 - -dns-connectivity03 + +dns-connectivity03 dns-connectivity02->dns-connectivity03 - - + + dns-consistency02 - -dns-consistency02 + +dns-consistency02 dns-connectivity03->dns-consistency02 - - + + dns-consistency03 - -dns-consistency03 + +dns-consistency03 dns-consistency02->dns-consistency03 - - + + dns-consistency04 - -dns-consistency04 + +dns-consistency04 dns-consistency03->dns-consistency04 - - + + dns-consistency05 - -dns-consistency05 + +dns-consistency05 dns-consistency04->dns-consistency05 - - + + dns-consistency06 - -dns-consistency06 + +dns-consistency06 dns-consistency05->dns-consistency06 - - + + dns-delegation01 - -dns-delegation01 + +dns-delegation01 dns-consistency06->dns-delegation01 - - + + dns-delegation02 - -dns-delegation02 + +dns-delegation02 dns-delegation01->dns-delegation02 - - + + dns-delegation03 - -dns-delegation03 + +dns-delegation03 dns-delegation02->dns-delegation03 - - + + dns-delegation04 - -dns-delegation04 + +dns-delegation04 dns-delegation03->dns-delegation04 - - + + dns-delegation05 - -dns-delegation05 + +dns-delegation05 dns-delegation04->dns-delegation05 - - + + dns-delegation07 - -dns-delegation07 + +dns-delegation07 dns-delegation05->dns-delegation07 - - + + dns-nameserver01 - -dns-nameserver01 + +dns-nameserver01 dns-delegation07->dns-nameserver01 - - + + dns-nameserver02 - -dns-nameserver02 + +dns-nameserver02 dns-nameserver01->dns-nameserver02 - - + + dns-nameserver04 - -dns-nameserver04 + +dns-nameserver04 dns-nameserver02->dns-nameserver04 - - + + dns-nameserver05 - -dns-nameserver05 + +dns-nameserver05 dns-nameserver04->dns-nameserver05 - - + + dns-nameserver06 - -dns-nameserver06 + +dns-nameserver06 dns-nameserver05->dns-nameserver06 - - + + dns-nameserver08 - -dns-nameserver08 + +dns-nameserver08 dns-nameserver06->dns-nameserver08 - - + + dns-nameserver09 - -dns-nameserver09 + +dns-nameserver09 dns-nameserver08->dns-nameserver09 - - + + dns-nameserver10 - -dns-nameserver10 + +dns-nameserver10 dns-nameserver09->dns-nameserver10 - - + + dns-nameserver11 - -dns-nameserver11 + +dns-nameserver11 dns-nameserver10->dns-nameserver11 - - + + dns-nameserver12 - -dns-nameserver12 + +dns-nameserver12 dns-nameserver11->dns-nameserver12 - - + + dns-nameserver13 - -dns-nameserver13 + +dns-nameserver13 dns-nameserver12->dns-nameserver13 - - + + dns-nameserver14 - -dns-nameserver14 + +dns-nameserver14 dns-nameserver13->dns-nameserver14 - - + + dns-syntax05 - -dns-syntax05 + +dns-syntax05 dns-nameserver14->dns-syntax05 - - + + dns-syntax06 - -dns-syntax06 + +dns-syntax06 dns-syntax05->dns-syntax06 - - + + dns-syntax07 - -dns-syntax07 + +dns-syntax07 dns-syntax06->dns-syntax07 - - + + dns-zone07 - -dns-zone07 + +dns-zone07 dns-syntax07->dns-zone07 - - + + dns-zone10 - -dns-zone10 + +dns-zone10 dns-zone07->dns-zone10 - - + + dns-zz-idna2008-compliance - -dns-zz-idna2008-compliance + +dns-zz-idna2008-compliance dns-zone10->dns-zz-idna2008-compliance - - + + dnssec-01 - -dnssec-01 + +dnssec-01 dns-zz-idna2008-compliance->dnssec-01 - - + + dnssec-02 - -dnssec-02 + +dnssec-02 dnssec-01->dnssec-02 - - + + dnssec-03 - -dnssec-03 + +dnssec-03 dnssec-02->dnssec-03 - - + + dnssec-04 - -dnssec-04 + +dnssec-04 dnssec-03->dnssec-04 - - + + dnssec-05 - -dnssec-05 + +dnssec-05 dnssec-04->dnssec-05 - - + + dnssec-06 - -dnssec-06 + +dnssec-06 dnssec-05->dnssec-06 - - + + dnssec-91 - -dnssec-91 + +dnssec-91 dnssec-05->dnssec-91 - - + + dnssec-08 - -dnssec-08 + +dnssec-08 dnssec-06->dnssec-08 - - + + dnssec-09 - -dnssec-09 + +dnssec-09 dnssec-08->dnssec-09 - - + + dnssec-10 - -dnssec-10 + +dnssec-10 dnssec-09->dnssec-10 - - + + dnssec-12 - -dnssec-12 + +dnssec-12 dnssec-10->dnssec-12 - - + + dnssec-13 - -dnssec-13 + +dnssec-13 dnssec-12->dnssec-13 - - + + dnssec-14 - -dnssec-14 + +dnssec-14 dnssec-13->dnssec-14 - - + + dnssec-15 - -dnssec-15 + +dnssec-15 dnssec-14->dnssec-15 - - + + dnssec-16 - -dnssec-16 + +dnssec-16 dnssec-15->dnssec-16 - - + + dnssec-17 - -dnssec-17 + +dnssec-17 dnssec-16->dnssec-17 - - + + dnssec-18 - -dnssec-18 + +dnssec-18 dnssec-17->dnssec-18 - - + + dnssec-92 - -dnssec-92 + +dnssec-92 dnssec-91->dnssec-92 - - + + epp-01 - -epp-01 + +epp-01 dnssec-92->epp-01 - - + + epp-02 - -epp-02 + +epp-02 epp-01->epp-02 - - + + epp-03 - -epp-03 + +epp-03 epp-02->epp-03 - - + + epp-04 - - -epp-04 + + +epp-04 epp-03->epp-04 - - + + epp-14 - - -epp-14 + + +epp-14 epp-03->epp-14 - - + + epp-05 - - -epp-05 + + +epp-05 epp-04->epp-05 - - + + epp-06 - - -epp-06 + + +epp-06 epp-05->epp-06 - - + + epp-07 - - -epp-07 + + +epp-07 epp-06->epp-07 - - + + epp-08 - -epp-08 + +epp-08 epp-07->epp-08 - - + + epp-09 - - -epp-09 + + +epp-09 epp-08->epp-09 - - + + epp-10 - - -epp-10 + + +epp-10 epp-09->epp-10 - - + + epp-11 - -epp-11 + +epp-11 epp-10->epp-11 - - + + epp-12 - - -epp-12 + + +epp-12 epp-11->epp-12 - - + + epp-13 - - -epp-13 + + +epp-13 epp-11->epp-13 - - + + - - -epp-21 - - -epp-21 - - - - - -epp-11->epp-21 - - - - - -integration-01 - - -integration-01 - - - - - -epp-11->integration-01 - - - - - -integration-03 - - -integration-03 + + +epp-23 + + +epp-23 - - -epp-11->integration-03 - - + + +epp-11->epp-23 + + epp-15 - -epp-15 + +epp-15 epp-14->epp-15 - - + + epp-16 - - -epp-16 + + +epp-16 epp-14->epp-16 - - + + epp-17 - - -epp-17 + + +epp-17 epp-14->epp-17 - - + + epp-18 - - -epp-18 + + +epp-18 epp-14->epp-18 - - + + epp-19 - - -epp-19 + + +epp-19 epp-14->epp-19 - - - - - -epp-14->epp-21 - - - - - -epp-14->integration-01 - - - - - -integration-02 - - -integration-02 - - - - - -epp-14->integration-02 - - - - - -epp-14->integration-03 - - + + epp-20 - - -epp-20 + + +epp-20 - + -epp-19->epp-20 - - +epp-14->epp-20 + + + + + +epp-21 + + +epp-21 + + + + + +epp-14->epp-21 + + + + + +epp-14->epp-23 + + epp-22 - - -epp-22 + + +epp-22 - + epp-21->epp-22 - - + + + + + +epp-24 + + +epp-24 + + + + + +epp-23->epp-24 + + - + idn-01 - - -idn-01 + + +idn-01 - - -epp-22->idn-01 - - + + +epp-24->idn-01 + + - + idn-02 - - -idn-02 + + +idn-02 - + idn-01->idn-02 - - + + - + idn-03 - - -idn-03 + + +idn-03 - + idn-02->idn-03 - - + + - + idn-04 - - -idn-04 + + +idn-04 - + idn-03->idn-04 - - + + - + + +integration-01 + + +integration-01 + + + + + +idn-04->integration-01 + + + + +integration-02 + + +integration-02 + + + + + +integration-01->integration-02 + + + + + +integration-03 + + +integration-03 + + + + + +integration-01->integration-03 + + + + + rdap-01-domainCaseFoldingValidation - - -rdap-01-domainCaseFoldingValidation + + +rdap-01-domainCaseFoldingValidation integration-03->rdap-01-domainCaseFoldingValidation - - + + - + rdap-02-domainNameValidation - - -rdap-02-domainNameValidation + + +rdap-02-domainNameValidation rdap-01-domainCaseFoldingValidation->rdap-02-domainNameValidation - - + + - + rdap-03-ipv4Validation - - -rdap-03-ipv4Validation + + +rdap-03-ipv4Validation rdap-02-domainNameValidation->rdap-03-ipv4Validation - - + + - + rdap-04-ipv6Validation - - -rdap-04-ipv6Validation + + +rdap-04-ipv6Validation rdap-03-ipv4Validation->rdap-04-ipv6Validation - - + + - + rdap-05-stdRdapAsEventActorValidation - - -rdap-05-stdRdapAsEventActorValidation + + +rdap-05-stdRdapAsEventActorValidation rdap-04-ipv6Validation->rdap-05-stdRdapAsEventActorValidation - - + + - + rdap-06-stdRdapConformanceValidation - - -rdap-06-stdRdapConformanceValidation + + +rdap-06-stdRdapConformanceValidation rdap-05-stdRdapAsEventActorValidation->rdap-06-stdRdapConformanceValidation - - + + - + rdap-07-stdRdapDomainLookupValidation - - -rdap-07-stdRdapDomainLookupValidation + + +rdap-07-stdRdapDomainLookupValidation rdap-06-stdRdapConformanceValidation->rdap-07-stdRdapDomainLookupValidation - - + + - + rdap-08-stdRdapEntitiesValidation - - -rdap-08-stdRdapEntitiesValidation + + +rdap-08-stdRdapEntitiesValidation rdap-07-stdRdapDomainLookupValidation->rdap-08-stdRdapEntitiesValidation - - + + - + rdap-09-stdRdapEntityLookupValidation - - -rdap-09-stdRdapEntityLookupValidation + + +rdap-09-stdRdapEntityLookupValidation rdap-08-stdRdapEntitiesValidation->rdap-09-stdRdapEntityLookupValidation - - + + - + rdap-10-stdRdapErrorResponseBodyValidation - - -rdap-10-stdRdapErrorResponseBodyValidation + + +rdap-10-stdRdapErrorResponseBodyValidation rdap-09-stdRdapEntityLookupValidation->rdap-10-stdRdapErrorResponseBodyValidation - - + + - + rdap-11-stdRdapEventsValidation - - -rdap-11-stdRdapEventsValidation + + +rdap-11-stdRdapEventsValidation rdap-10-stdRdapErrorResponseBodyValidation->rdap-11-stdRdapEventsValidation - - + + - + rdap-12-stdRdapHelpValidation - - -rdap-12-stdRdapHelpValidation + + +rdap-12-stdRdapHelpValidation rdap-11-stdRdapEventsValidation->rdap-12-stdRdapHelpValidation - - + + - + rdap-13-stdRdapIpAddressesValidation - - -rdap-13-stdRdapIpAddressesValidation + + +rdap-13-stdRdapIpAddressesValidation rdap-12-stdRdapHelpValidation->rdap-13-stdRdapIpAddressesValidation - - + + - + rdap-14-stdRdapLanguageIdentifierValidation - - -rdap-14-stdRdapLanguageIdentifierValidation + + +rdap-14-stdRdapLanguageIdentifierValidation rdap-13-stdRdapIpAddressesValidation->rdap-14-stdRdapLanguageIdentifierValidation - - + + - + rdap-15-stdRdapLdhNameValidation - - -rdap-15-stdRdapLdhNameValidation + + +rdap-15-stdRdapLdhNameValidation rdap-14-stdRdapLanguageIdentifierValidation->rdap-15-stdRdapLdhNameValidation - - + + - + rdap-16-stdRdapLinksValidation - - -rdap-16-stdRdapLinksValidation + + +rdap-16-stdRdapLinksValidation rdap-15-stdRdapLdhNameValidation->rdap-16-stdRdapLinksValidation - - + + - + rdap-17-stdRdapNameserverLookupValidation - - -rdap-17-stdRdapNameserverLookupValidation + + +rdap-17-stdRdapNameserverLookupValidation rdap-16-stdRdapLinksValidation->rdap-17-stdRdapNameserverLookupValidation - - + + - + rdap-18-stdRdapNameserversSearchValidation - - -rdap-18-stdRdapNameserversSearchValidation + + +rdap-18-stdRdapNameserversSearchValidation rdap-17-stdRdapNameserverLookupValidation->rdap-18-stdRdapNameserversSearchValidation - - + + - + rdap-19-stdRdapNoticesRemarksValidation - - -rdap-19-stdRdapNoticesRemarksValidation + + +rdap-19-stdRdapNoticesRemarksValidation rdap-18-stdRdapNameserversSearchValidation->rdap-19-stdRdapNoticesRemarksValidation - - + + - + rdap-20-stdRdapPort43WhoisServerValidation - - -rdap-20-stdRdapPort43WhoisServerValidation + + +rdap-20-stdRdapPort43WhoisServerValidation rdap-19-stdRdapNoticesRemarksValidation->rdap-20-stdRdapPort43WhoisServerValidation - - + + - + rdap-21-stdRdapPublicIdsValidation - - -rdap-21-stdRdapPublicIdsValidation + + +rdap-21-stdRdapPublicIdsValidation rdap-20-stdRdapPort43WhoisServerValidation->rdap-21-stdRdapPublicIdsValidation - - + + - + rdap-22-stdRdapRolesValidation - - -rdap-22-stdRdapRolesValidation + + +rdap-22-stdRdapRolesValidation rdap-21-stdRdapPublicIdsValidation->rdap-22-stdRdapRolesValidation - - + + - + rdap-23-stdRdapSecureDnsValidation - - -rdap-23-stdRdapSecureDnsValidation + + +rdap-23-stdRdapSecureDnsValidation rdap-22-stdRdapRolesValidation->rdap-23-stdRdapSecureDnsValidation - - + + - + rdap-24-stdRdapStatusValidation - - -rdap-24-stdRdapStatusValidation + + +rdap-24-stdRdapStatusValidation rdap-23-stdRdapSecureDnsValidation->rdap-24-stdRdapStatusValidation - - + + - + rdap-25-stdRdapUnicodeNameValidation - - -rdap-25-stdRdapUnicodeNameValidation + + +rdap-25-stdRdapUnicodeNameValidation rdap-24-stdRdapStatusValidation->rdap-25-stdRdapUnicodeNameValidation - - + + - + rdap-26-stdRdapVariantsValidation - - -rdap-26-stdRdapVariantsValidation + + +rdap-26-stdRdapVariantsValidation rdap-25-stdRdapUnicodeNameValidation->rdap-26-stdRdapVariantsValidation - - + + - + rdap-27-webUriValidation - - -rdap-27-webUriValidation + + +rdap-27-webUriValidation rdap-26-stdRdapVariantsValidation->rdap-27-webUriValidation - - + + - + rde-01 - - -rde-01 + + +rde-01 rdap-27-webUriValidation->rde-01 - - + + - + rde-02 - - -rde-02 + + +rde-02 rde-01->rde-02 - - + + - + rde-03 - - -rde-03 + + +rde-03 rde-02->rde-03 - - + + - + rde-04 - - -rde-04 + + +rde-04 rde-03->rde-04 - - + + - + rde-05 - - -rde-05 + + +rde-05 rde-04->rde-05 - - + + - + rde-06 - - -rde-06 + + +rde-06 rde-05->rde-06 - - + + - + rde-07 - - -rde-07 + + +rde-07 rde-06->rde-07 - - + + - + rde-08 - - -rde-08 + + +rde-08 rde-07->rde-08 - - + + - + rde-09 - - -rde-09 + + +rde-09 rde-08->rde-09 - - + + - + rde-10 - - -rde-10 + + +rde-10 rde-09->rde-10 - - + + - + rde-11 - - -rde-11 + + +rde-11 rde-10->rde-11 - - + + - + rde-12 - - -rde-12 + + +rde-12 rde-11->rde-12 - - + + - + rde-13 - - -rde-13 + + +rde-13 rde-12->rde-13 - - + + - + rde-14 - - -rde-14 + + +rde-14 rde-13->rde-14 - - + + @@ -2418,7 +2436,7 @@

    Pass/fail criteria

    1. Authoritative DNS Service
    2. DNS Security Extensions (DNSSEC)
    3. Registration Data Access Protocol (RDAP)
    4. Extensible Provisioning Protocol (EPP)
    5. Registry Data Escrow (RDE)
    6. Internationalized Domain Names (IDN)
    7. Standard Integration Test

    3.2.4. Resources

    The following resources may be required to prepare for this test plan:

    3.2.5. Errors

    This test plan may produce the following errors:

    -

    3.2.6. Input parameters

    This plan requires the following input parameters:

    +

    3.2.6. Input parameters

    This plan requires the following input parameters:

    3.2.7. Required files

    3.2.8. RST-API example

    POST /test/987654/inputs HTTP/1.1
     Content-Type: application/json
     Content-Length: 2666
    @@ -2499,17 +2517,17 @@ 

    Pass/fail criteria

    - - + + Perl - + dns-address01 - -dns-address01 + +dns-address01 @@ -2517,1849 +2535,1867 @@

    Pass/fail criteria

    dns-address02 - -dns-address02 + +dns-address02 dns-address01->dns-address02 - - + + dns-address03 - -dns-address03 + +dns-address03 dns-address02->dns-address03 - - + + dns-connectivity01 - -dns-connectivity01 + +dns-connectivity01 dns-address03->dns-connectivity01 - - + + dns-connectivity02 - -dns-connectivity02 + +dns-connectivity02 dns-connectivity01->dns-connectivity02 - - + + dns-connectivity03 - -dns-connectivity03 + +dns-connectivity03 dns-connectivity02->dns-connectivity03 - - + + dns-consistency02 - -dns-consistency02 + +dns-consistency02 dns-connectivity03->dns-consistency02 - - + + dns-consistency03 - -dns-consistency03 + +dns-consistency03 dns-consistency02->dns-consistency03 - - + + dns-consistency04 - -dns-consistency04 + +dns-consistency04 dns-consistency03->dns-consistency04 - - + + dns-consistency05 - -dns-consistency05 + +dns-consistency05 dns-consistency04->dns-consistency05 - - + + dns-consistency06 - -dns-consistency06 + +dns-consistency06 dns-consistency05->dns-consistency06 - - + + dns-delegation01 - -dns-delegation01 + +dns-delegation01 dns-consistency06->dns-delegation01 - - + + dns-delegation02 - -dns-delegation02 + +dns-delegation02 dns-delegation01->dns-delegation02 - - + + dns-delegation03 - -dns-delegation03 + +dns-delegation03 dns-delegation02->dns-delegation03 - - + + dns-delegation04 - -dns-delegation04 + +dns-delegation04 dns-delegation03->dns-delegation04 - - + + dns-delegation05 - -dns-delegation05 + +dns-delegation05 dns-delegation04->dns-delegation05 - - + + dns-delegation07 - -dns-delegation07 + +dns-delegation07 dns-delegation05->dns-delegation07 - - + + dns-nameserver01 - -dns-nameserver01 + +dns-nameserver01 dns-delegation07->dns-nameserver01 - - + + dns-nameserver02 - -dns-nameserver02 + +dns-nameserver02 dns-nameserver01->dns-nameserver02 - - + + dns-nameserver04 - -dns-nameserver04 + +dns-nameserver04 dns-nameserver02->dns-nameserver04 - - + + dns-nameserver05 - -dns-nameserver05 + +dns-nameserver05 dns-nameserver04->dns-nameserver05 - - + + dns-nameserver06 - -dns-nameserver06 + +dns-nameserver06 dns-nameserver05->dns-nameserver06 - - + + dns-nameserver08 - -dns-nameserver08 + +dns-nameserver08 dns-nameserver06->dns-nameserver08 - - + + dns-nameserver09 - -dns-nameserver09 + +dns-nameserver09 dns-nameserver08->dns-nameserver09 - - + + dns-nameserver10 - -dns-nameserver10 + +dns-nameserver10 dns-nameserver09->dns-nameserver10 - - + + dns-nameserver11 - -dns-nameserver11 + +dns-nameserver11 dns-nameserver10->dns-nameserver11 - - + + dns-nameserver12 - -dns-nameserver12 + +dns-nameserver12 dns-nameserver11->dns-nameserver12 - - + + dns-nameserver13 - -dns-nameserver13 + +dns-nameserver13 dns-nameserver12->dns-nameserver13 - - + + dns-nameserver14 - -dns-nameserver14 + +dns-nameserver14 dns-nameserver13->dns-nameserver14 - - + + dns-syntax05 - -dns-syntax05 + +dns-syntax05 dns-nameserver14->dns-syntax05 - - + + dns-syntax06 - -dns-syntax06 + +dns-syntax06 dns-syntax05->dns-syntax06 - - + + dns-syntax07 - -dns-syntax07 + +dns-syntax07 dns-syntax06->dns-syntax07 - - + + dns-zone07 - -dns-zone07 + +dns-zone07 dns-syntax07->dns-zone07 - - + + dns-zone10 - -dns-zone10 + +dns-zone10 dns-zone07->dns-zone10 - - + + dns-zz-idna2008-compliance - -dns-zz-idna2008-compliance + +dns-zz-idna2008-compliance dns-zone10->dns-zz-idna2008-compliance - - + + dnssec-01 - -dnssec-01 + +dnssec-01 dns-zz-idna2008-compliance->dnssec-01 - - + + dnssec-02 - -dnssec-02 + +dnssec-02 dnssec-01->dnssec-02 - - + + dnssec-03 - -dnssec-03 + +dnssec-03 dnssec-02->dnssec-03 - - + + dnssec-04 - -dnssec-04 + +dnssec-04 dnssec-03->dnssec-04 - - + + dnssec-05 - -dnssec-05 + +dnssec-05 dnssec-04->dnssec-05 - - + + dnssec-06 - -dnssec-06 + +dnssec-06 dnssec-05->dnssec-06 - - + + dnssec-91 - -dnssec-91 + +dnssec-91 dnssec-05->dnssec-91 - - + + dnssec-08 - -dnssec-08 + +dnssec-08 dnssec-06->dnssec-08 - - + + dnssec-09 - -dnssec-09 + +dnssec-09 dnssec-08->dnssec-09 - - + + dnssec-10 - -dnssec-10 + +dnssec-10 dnssec-09->dnssec-10 - - + + dnssec-12 - -dnssec-12 + +dnssec-12 dnssec-10->dnssec-12 - - + + dnssec-13 - -dnssec-13 + +dnssec-13 dnssec-12->dnssec-13 - - + + dnssec-14 - -dnssec-14 + +dnssec-14 dnssec-13->dnssec-14 - - + + dnssec-15 - -dnssec-15 + +dnssec-15 dnssec-14->dnssec-15 - - + + dnssec-16 - -dnssec-16 + +dnssec-16 dnssec-15->dnssec-16 - - + + dnssec-17 - -dnssec-17 + +dnssec-17 dnssec-16->dnssec-17 - - + + dnssec-18 - -dnssec-18 + +dnssec-18 dnssec-17->dnssec-18 - - + + dnssec-92 - -dnssec-92 + +dnssec-92 dnssec-91->dnssec-92 - - + + epp-01 - -epp-01 + +epp-01 dnssec-92->epp-01 - - + + epp-02 - -epp-02 + +epp-02 epp-01->epp-02 - - + + epp-03 - -epp-03 + +epp-03 epp-02->epp-03 - - + + epp-04 - - -epp-04 + + +epp-04 epp-03->epp-04 - - + + epp-14 - - -epp-14 + + +epp-14 epp-03->epp-14 - - + + epp-05 - - -epp-05 + + +epp-05 epp-04->epp-05 - - + + epp-06 - - -epp-06 + + +epp-06 epp-05->epp-06 - - + + epp-07 - - -epp-07 + + +epp-07 epp-06->epp-07 - - + + epp-08 - -epp-08 + +epp-08 epp-07->epp-08 - - + + epp-09 - - -epp-09 + + +epp-09 epp-08->epp-09 - - + + epp-10 - - -epp-10 + + +epp-10 epp-09->epp-10 - - + + epp-11 - -epp-11 + +epp-11 epp-10->epp-11 - - + + epp-12 - - -epp-12 + + +epp-12 epp-11->epp-12 - - + + epp-13 - - -epp-13 + + +epp-13 epp-11->epp-13 - - - - - -epp-21 - - -epp-21 - - - - - -epp-11->epp-21 - - - - - -integration-01 - - -integration-01 - - + + - - -epp-11->integration-01 - - - - - -integration-03 - - -integration-03 + + +epp-23 + + +epp-23 - - -epp-11->integration-03 - - + + +epp-11->epp-23 + + epp-15 - -epp-15 + +epp-15 epp-14->epp-15 - - + + epp-16 - - -epp-16 + + +epp-16 epp-14->epp-16 - - + + epp-17 - - -epp-17 + + +epp-17 epp-14->epp-17 - - + + epp-18 - - -epp-18 + + +epp-18 epp-14->epp-18 - - + + epp-19 - - -epp-19 + + +epp-19 epp-14->epp-19 - - - - - -epp-14->epp-21 - - - - - -epp-14->integration-01 - - - - - -integration-02 - - -integration-02 - - - - - -epp-14->integration-02 - - - - - -epp-14->integration-03 - - + + epp-20 - - -epp-20 + + +epp-20 - + -epp-19->epp-20 - - +epp-14->epp-20 + + + + + +epp-21 + + +epp-21 + + + + + +epp-14->epp-21 + + + + + +epp-14->epp-23 + + epp-22 - - -epp-22 + + +epp-22 - + epp-21->epp-22 - - + + + + + +epp-24 + + +epp-24 + + + + + +epp-23->epp-24 + + - + idn-01 - - -idn-01 + + +idn-01 - - -epp-22->idn-01 - - + + +epp-24->idn-01 + + - + idn-02 - - -idn-02 + + +idn-02 - + idn-01->idn-02 - - + + - + idn-03 - - -idn-03 + + +idn-03 - + idn-02->idn-03 - - + + - + idn-04 - - -idn-04 + + +idn-04 - + idn-03->idn-04 - - + + - - -rdap-01-domainCaseFoldingValidation - - -rdap-01-domainCaseFoldingValidation - + + +integration-01 + + +integration-01 + + + + + +idn-04->integration-01 + + + + + +integration-02 + + +integration-02 + + + + + +integration-01->integration-02 + + + + + +integration-03 + + +integration-03 + + + + + +integration-01->integration-03 + + + + + +rdap-01-domainCaseFoldingValidation + + +rdap-01-domainCaseFoldingValidation + integration-03->rdap-01-domainCaseFoldingValidation - - + + - + rdap-02-domainNameValidation - - -rdap-02-domainNameValidation + + +rdap-02-domainNameValidation rdap-01-domainCaseFoldingValidation->rdap-02-domainNameValidation - - + + - + rdap-03-ipv4Validation - - -rdap-03-ipv4Validation + + +rdap-03-ipv4Validation rdap-02-domainNameValidation->rdap-03-ipv4Validation - - + + - + rdap-04-ipv6Validation - - -rdap-04-ipv6Validation + + +rdap-04-ipv6Validation rdap-03-ipv4Validation->rdap-04-ipv6Validation - - + + - + rdap-05-stdRdapAsEventActorValidation - - -rdap-05-stdRdapAsEventActorValidation + + +rdap-05-stdRdapAsEventActorValidation rdap-04-ipv6Validation->rdap-05-stdRdapAsEventActorValidation - - + + - + rdap-06-stdRdapConformanceValidation - - -rdap-06-stdRdapConformanceValidation + + +rdap-06-stdRdapConformanceValidation rdap-05-stdRdapAsEventActorValidation->rdap-06-stdRdapConformanceValidation - - + + - + rdap-07-stdRdapDomainLookupValidation - - -rdap-07-stdRdapDomainLookupValidation + + +rdap-07-stdRdapDomainLookupValidation rdap-06-stdRdapConformanceValidation->rdap-07-stdRdapDomainLookupValidation - - + + - + rdap-08-stdRdapEntitiesValidation - - -rdap-08-stdRdapEntitiesValidation + + +rdap-08-stdRdapEntitiesValidation rdap-07-stdRdapDomainLookupValidation->rdap-08-stdRdapEntitiesValidation - - + + - + rdap-09-stdRdapEntityLookupValidation - - -rdap-09-stdRdapEntityLookupValidation + + +rdap-09-stdRdapEntityLookupValidation rdap-08-stdRdapEntitiesValidation->rdap-09-stdRdapEntityLookupValidation - - + + - + rdap-10-stdRdapErrorResponseBodyValidation - - -rdap-10-stdRdapErrorResponseBodyValidation + + +rdap-10-stdRdapErrorResponseBodyValidation rdap-09-stdRdapEntityLookupValidation->rdap-10-stdRdapErrorResponseBodyValidation - - + + - + rdap-11-stdRdapEventsValidation - - -rdap-11-stdRdapEventsValidation + + +rdap-11-stdRdapEventsValidation rdap-10-stdRdapErrorResponseBodyValidation->rdap-11-stdRdapEventsValidation - - + + - + rdap-12-stdRdapHelpValidation - - -rdap-12-stdRdapHelpValidation + + +rdap-12-stdRdapHelpValidation rdap-11-stdRdapEventsValidation->rdap-12-stdRdapHelpValidation - - + + - + rdap-13-stdRdapIpAddressesValidation - - -rdap-13-stdRdapIpAddressesValidation + + +rdap-13-stdRdapIpAddressesValidation rdap-12-stdRdapHelpValidation->rdap-13-stdRdapIpAddressesValidation - - + + - + rdap-14-stdRdapLanguageIdentifierValidation - - -rdap-14-stdRdapLanguageIdentifierValidation + + +rdap-14-stdRdapLanguageIdentifierValidation rdap-13-stdRdapIpAddressesValidation->rdap-14-stdRdapLanguageIdentifierValidation - - + + - + rdap-15-stdRdapLdhNameValidation - - -rdap-15-stdRdapLdhNameValidation + + +rdap-15-stdRdapLdhNameValidation rdap-14-stdRdapLanguageIdentifierValidation->rdap-15-stdRdapLdhNameValidation - - + + - + rdap-16-stdRdapLinksValidation - - -rdap-16-stdRdapLinksValidation + + +rdap-16-stdRdapLinksValidation rdap-15-stdRdapLdhNameValidation->rdap-16-stdRdapLinksValidation - - + + - + rdap-17-stdRdapNameserverLookupValidation - - -rdap-17-stdRdapNameserverLookupValidation + + +rdap-17-stdRdapNameserverLookupValidation rdap-16-stdRdapLinksValidation->rdap-17-stdRdapNameserverLookupValidation - - + + - + rdap-18-stdRdapNameserversSearchValidation - - -rdap-18-stdRdapNameserversSearchValidation + + +rdap-18-stdRdapNameserversSearchValidation rdap-17-stdRdapNameserverLookupValidation->rdap-18-stdRdapNameserversSearchValidation - - + + - + rdap-19-stdRdapNoticesRemarksValidation - - -rdap-19-stdRdapNoticesRemarksValidation + + +rdap-19-stdRdapNoticesRemarksValidation rdap-18-stdRdapNameserversSearchValidation->rdap-19-stdRdapNoticesRemarksValidation - - + + - + rdap-20-stdRdapPort43WhoisServerValidation - - -rdap-20-stdRdapPort43WhoisServerValidation + + +rdap-20-stdRdapPort43WhoisServerValidation rdap-19-stdRdapNoticesRemarksValidation->rdap-20-stdRdapPort43WhoisServerValidation - - + + - + rdap-21-stdRdapPublicIdsValidation - - -rdap-21-stdRdapPublicIdsValidation + + +rdap-21-stdRdapPublicIdsValidation rdap-20-stdRdapPort43WhoisServerValidation->rdap-21-stdRdapPublicIdsValidation - - + + - + rdap-22-stdRdapRolesValidation - - -rdap-22-stdRdapRolesValidation + + +rdap-22-stdRdapRolesValidation rdap-21-stdRdapPublicIdsValidation->rdap-22-stdRdapRolesValidation - - + + - + rdap-23-stdRdapSecureDnsValidation - - -rdap-23-stdRdapSecureDnsValidation + + +rdap-23-stdRdapSecureDnsValidation rdap-22-stdRdapRolesValidation->rdap-23-stdRdapSecureDnsValidation - - + + - + rdap-24-stdRdapStatusValidation - - -rdap-24-stdRdapStatusValidation + + +rdap-24-stdRdapStatusValidation rdap-23-stdRdapSecureDnsValidation->rdap-24-stdRdapStatusValidation - - + + - + rdap-25-stdRdapUnicodeNameValidation - - -rdap-25-stdRdapUnicodeNameValidation + + +rdap-25-stdRdapUnicodeNameValidation rdap-24-stdRdapStatusValidation->rdap-25-stdRdapUnicodeNameValidation - - + + - + rdap-26-stdRdapVariantsValidation - - -rdap-26-stdRdapVariantsValidation + + +rdap-26-stdRdapVariantsValidation rdap-25-stdRdapUnicodeNameValidation->rdap-26-stdRdapVariantsValidation - - + + - + rdap-27-webUriValidation - - -rdap-27-webUriValidation + + +rdap-27-webUriValidation rdap-26-stdRdapVariantsValidation->rdap-27-webUriValidation - - + + - + rde-01 - - -rde-01 + + +rde-01 rdap-27-webUriValidation->rde-01 - - + + - + rde-02 - - -rde-02 + + +rde-02 rde-01->rde-02 - - + + - + rde-03 - - -rde-03 + + +rde-03 rde-02->rde-03 - - + + - + rde-04 - - -rde-04 + + +rde-04 rde-03->rde-04 - - + + - + rde-05 - - -rde-05 + + +rde-05 rde-04->rde-05 - - + + - + rde-06 - - -rde-06 + + +rde-06 rde-05->rde-06 - - + + - + rde-07 - - -rde-07 + + +rde-07 rde-06->rde-07 - - + + - + rde-08 - - -rde-08 + + +rde-08 rde-07->rde-08 - - + + - + rde-09 - - -rde-09 + + +rde-09 rde-08->rde-09 - - + + - + rde-10 - - -rde-10 + + +rde-10 rde-09->rde-10 - - + + - + rde-11 - - -rde-11 + + +rde-11 rde-10->rde-11 - - + + - + rde-12 - - -rde-12 + + +rde-12 rde-11->rde-12 - - + + - + rde-13 - - -rde-13 + + +rde-13 rde-12->rde-13 - - + + - + rde-14 - - -rde-14 + + +rde-14 rde-13->rde-14 - - + + @@ -5729,7 +5765,7 @@

    Pass/fail criteria

    1. Registration Data Access Protocol (RDAP)
    2. Extensible Provisioning Protocol (EPP)
    3. Registry Data Escrow (RDE)
    4. Minimum Rights Protection Mechanisms (RPMs)

    3.7.4. Resources

    The following resources may be required to prepare for this test plan:

    3.7.5. Errors

    This test plan may produce the following errors:

    -

    3.7.6. Input parameters

    This plan requires the following input parameters:

    +

    3.7.6. Input parameters

    This plan requires the following input parameters:

    3.7.7. Required files

    3.7.8. RST-API example

    POST /test/987654/inputs HTTP/1.1
     Content-Type: application/json
     Content-Length: 2125
    @@ -5784,17 +5820,17 @@ 

    Pass/fail criteria

    - - + + Perl - + epp-01 - -epp-01 + +epp-01 @@ -5802,982 +5838,1012 @@

    Pass/fail criteria

    epp-02 - -epp-02 + +epp-02 epp-01->epp-02 - - + + epp-03 - -epp-03 + +epp-03 epp-02->epp-03 - - + + epp-04 - - -epp-04 + + +epp-04 epp-03->epp-04 - - + + epp-14 - - -epp-14 + + +epp-14 epp-03->epp-14 - - + + epp-05 - - -epp-05 + + +epp-05 epp-04->epp-05 - - + + epp-06 - - -epp-06 + + +epp-06 epp-05->epp-06 - - + + epp-07 - - -epp-07 + + +epp-07 epp-06->epp-07 - - + + epp-08 - -epp-08 + +epp-08 epp-07->epp-08 - - + + epp-09 - - -epp-09 + + +epp-09 epp-08->epp-09 - - + + epp-10 - - -epp-10 + + +epp-10 epp-09->epp-10 - - + + epp-11 - -epp-11 + +epp-11 epp-10->epp-11 - - + + epp-12 - - -epp-12 + + +epp-12 epp-11->epp-12 - - + + epp-13 - - -epp-13 + + +epp-13 epp-11->epp-13 - - + + - - -epp-21 - - -epp-21 + + +epp-23 + + +epp-23 - - -epp-11->epp-21 - - + + +epp-11->epp-23 + + epp-15 - -epp-15 + +epp-15 epp-14->epp-15 - - + + epp-16 - - -epp-16 + + +epp-16 epp-14->epp-16 - - + + epp-17 - - -epp-17 + + +epp-17 epp-14->epp-17 - - + + epp-18 - - -epp-18 + + +epp-18 epp-14->epp-18 - - + + epp-19 - - -epp-19 + + +epp-19 epp-14->epp-19 - - - - - -epp-14->epp-21 - - + + epp-20 - - -epp-20 + + +epp-20 - + -epp-19->epp-20 - - +epp-14->epp-20 + + + + + +epp-21 + + +epp-21 + + + + + +epp-14->epp-21 + + + + + +epp-14->epp-23 + + epp-22 - - -epp-22 + + +epp-22 - + epp-21->epp-22 - - + + + + + +epp-24 + + +epp-24 + + + + + +epp-23->epp-24 + + - + minimumRPMs-01 - - -minimumRPMs-01 + + +minimumRPMs-01 - - -epp-22->minimumRPMs-01 - - + + +epp-24->minimumRPMs-01 + + - + minimumRPMs-02 - - -minimumRPMs-02 + + +minimumRPMs-02 - + minimumRPMs-01->minimumRPMs-02 - - + + - + minimumRPMs-03 - - -minimumRPMs-03 + + +minimumRPMs-03 - + minimumRPMs-02->minimumRPMs-03 - - + + - + rdap-01-domainCaseFoldingValidation - - -rdap-01-domainCaseFoldingValidation + + +rdap-01-domainCaseFoldingValidation - + minimumRPMs-03->rdap-01-domainCaseFoldingValidation - - + + - + rdap-02-domainNameValidation - - -rdap-02-domainNameValidation + + +rdap-02-domainNameValidation - + rdap-01-domainCaseFoldingValidation->rdap-02-domainNameValidation - - + + - + rdap-03-ipv4Validation - - -rdap-03-ipv4Validation + + +rdap-03-ipv4Validation - + rdap-02-domainNameValidation->rdap-03-ipv4Validation - - + + - + rdap-04-ipv6Validation - - -rdap-04-ipv6Validation + + +rdap-04-ipv6Validation - + rdap-03-ipv4Validation->rdap-04-ipv6Validation - - + + - + rdap-05-stdRdapAsEventActorValidation - - -rdap-05-stdRdapAsEventActorValidation + + +rdap-05-stdRdapAsEventActorValidation - + rdap-04-ipv6Validation->rdap-05-stdRdapAsEventActorValidation - - + + - + rdap-06-stdRdapConformanceValidation - - -rdap-06-stdRdapConformanceValidation + + +rdap-06-stdRdapConformanceValidation - + rdap-05-stdRdapAsEventActorValidation->rdap-06-stdRdapConformanceValidation - - + + - + rdap-07-stdRdapDomainLookupValidation - - -rdap-07-stdRdapDomainLookupValidation + + +rdap-07-stdRdapDomainLookupValidation - + rdap-06-stdRdapConformanceValidation->rdap-07-stdRdapDomainLookupValidation - - + + - + rdap-08-stdRdapEntitiesValidation - - -rdap-08-stdRdapEntitiesValidation + + +rdap-08-stdRdapEntitiesValidation - + rdap-07-stdRdapDomainLookupValidation->rdap-08-stdRdapEntitiesValidation - - + + - + rdap-09-stdRdapEntityLookupValidation - - -rdap-09-stdRdapEntityLookupValidation + + +rdap-09-stdRdapEntityLookupValidation - + rdap-08-stdRdapEntitiesValidation->rdap-09-stdRdapEntityLookupValidation - - + + - + rdap-10-stdRdapErrorResponseBodyValidation - - -rdap-10-stdRdapErrorResponseBodyValidation + + +rdap-10-stdRdapErrorResponseBodyValidation - + rdap-09-stdRdapEntityLookupValidation->rdap-10-stdRdapErrorResponseBodyValidation - - + + - + rdap-11-stdRdapEventsValidation - - -rdap-11-stdRdapEventsValidation + + +rdap-11-stdRdapEventsValidation - + rdap-10-stdRdapErrorResponseBodyValidation->rdap-11-stdRdapEventsValidation - - + + - + rdap-12-stdRdapHelpValidation - - -rdap-12-stdRdapHelpValidation + + +rdap-12-stdRdapHelpValidation - + rdap-11-stdRdapEventsValidation->rdap-12-stdRdapHelpValidation - - + + - + rdap-13-stdRdapIpAddressesValidation - - -rdap-13-stdRdapIpAddressesValidation + + +rdap-13-stdRdapIpAddressesValidation - + rdap-12-stdRdapHelpValidation->rdap-13-stdRdapIpAddressesValidation - - + + - + rdap-14-stdRdapLanguageIdentifierValidation - - -rdap-14-stdRdapLanguageIdentifierValidation + + +rdap-14-stdRdapLanguageIdentifierValidation - + rdap-13-stdRdapIpAddressesValidation->rdap-14-stdRdapLanguageIdentifierValidation - - + + - + rdap-15-stdRdapLdhNameValidation - - -rdap-15-stdRdapLdhNameValidation + + +rdap-15-stdRdapLdhNameValidation - + rdap-14-stdRdapLanguageIdentifierValidation->rdap-15-stdRdapLdhNameValidation - - + + - + rdap-16-stdRdapLinksValidation - - -rdap-16-stdRdapLinksValidation + + +rdap-16-stdRdapLinksValidation - + rdap-15-stdRdapLdhNameValidation->rdap-16-stdRdapLinksValidation - - + + - + rdap-17-stdRdapNameserverLookupValidation - - -rdap-17-stdRdapNameserverLookupValidation + + +rdap-17-stdRdapNameserverLookupValidation - + rdap-16-stdRdapLinksValidation->rdap-17-stdRdapNameserverLookupValidation - - + + - + rdap-18-stdRdapNameserversSearchValidation - - -rdap-18-stdRdapNameserversSearchValidation + + +rdap-18-stdRdapNameserversSearchValidation - + rdap-17-stdRdapNameserverLookupValidation->rdap-18-stdRdapNameserversSearchValidation - - + + - + rdap-19-stdRdapNoticesRemarksValidation - - -rdap-19-stdRdapNoticesRemarksValidation + + +rdap-19-stdRdapNoticesRemarksValidation - + rdap-18-stdRdapNameserversSearchValidation->rdap-19-stdRdapNoticesRemarksValidation - - + + - + rdap-20-stdRdapPort43WhoisServerValidation - - -rdap-20-stdRdapPort43WhoisServerValidation + + +rdap-20-stdRdapPort43WhoisServerValidation - + rdap-19-stdRdapNoticesRemarksValidation->rdap-20-stdRdapPort43WhoisServerValidation - - + + - + rdap-21-stdRdapPublicIdsValidation - - -rdap-21-stdRdapPublicIdsValidation + + +rdap-21-stdRdapPublicIdsValidation - + rdap-20-stdRdapPort43WhoisServerValidation->rdap-21-stdRdapPublicIdsValidation - - + + - + rdap-22-stdRdapRolesValidation - - -rdap-22-stdRdapRolesValidation + + +rdap-22-stdRdapRolesValidation - + rdap-21-stdRdapPublicIdsValidation->rdap-22-stdRdapRolesValidation - - + + - + rdap-23-stdRdapSecureDnsValidation - - -rdap-23-stdRdapSecureDnsValidation + + +rdap-23-stdRdapSecureDnsValidation - + rdap-22-stdRdapRolesValidation->rdap-23-stdRdapSecureDnsValidation - - + + - + rdap-24-stdRdapStatusValidation - - -rdap-24-stdRdapStatusValidation + + +rdap-24-stdRdapStatusValidation - + rdap-23-stdRdapSecureDnsValidation->rdap-24-stdRdapStatusValidation - - + + - + rdap-25-stdRdapUnicodeNameValidation - - -rdap-25-stdRdapUnicodeNameValidation + + +rdap-25-stdRdapUnicodeNameValidation - + rdap-24-stdRdapStatusValidation->rdap-25-stdRdapUnicodeNameValidation - - + + - + rdap-26-stdRdapVariantsValidation - - -rdap-26-stdRdapVariantsValidation + + +rdap-26-stdRdapVariantsValidation - + rdap-25-stdRdapUnicodeNameValidation->rdap-26-stdRdapVariantsValidation - - + + - + rdap-27-webUriValidation - - -rdap-27-webUriValidation + + +rdap-27-webUriValidation - + rdap-26-stdRdapVariantsValidation->rdap-27-webUriValidation - - + + - + rde-01 - - -rde-01 + + +rde-01 - + rdap-27-webUriValidation->rde-01 - - + + - + rde-02 - - -rde-02 + + +rde-02 - + rde-01->rde-02 - - + + - + rde-03 - - -rde-03 + + +rde-03 - + rde-02->rde-03 - - + + - + rde-04 - - -rde-04 + + +rde-04 - + rde-03->rde-04 - - + + - + rde-05 - - -rde-05 + + +rde-05 - + rde-04->rde-05 - - + + - + rde-06 - - -rde-06 + + +rde-06 - + rde-05->rde-06 - - + + - + rde-07 - - -rde-07 + + +rde-07 - + rde-06->rde-07 - - + + - + rde-08 - - -rde-08 + + +rde-08 - + rde-07->rde-08 - - + + - + rde-09 - - -rde-09 + + +rde-09 - + rde-08->rde-09 - - + + - + rde-10 - - -rde-10 + + +rde-10 - + rde-09->rde-10 - - + + - + rde-11 - - -rde-11 + + +rde-11 - + rde-10->rde-11 - - + + - + rde-12 - - -rde-12 + + +rde-12 - + rde-11->rde-12 - - + + - + rde-13 - - -rde-13 + + +rde-13 - + rde-12->rde-13 - - + + - + rde-14 - - -rde-14 + + +rde-14 - + rde-13->rde-14 - - + + @@ -9351,11 +9417,11 @@

    Pass/fail criteria

    MUST pass: if any fail, then the suite as a whole will fail.

    4.4.2. Test cases

    This suite uses the following test cases:

    -
    1. epp-01 - Service connectivity test
    2. epp-02 - Protocol conformance test
    3. epp-03 - Authentication test
    4. epp-04 - domain <check> command test
    5. epp-05 - host <check> command test (if applicable)
    6. epp-06 - contact <check> command test (if applicable for the registry type)
    7. epp-07 - contact <create> command test (if applicable for the registry type)
    8. epp-08 - Contact object access control (if applicable)
    9. epp-09 - contact <update> command test (if applicable for the registry type)
    10. epp-10 - contact <delete> command test (if applicable for the registry type)
    11. epp-11 - host <create> command test (if applicable)
    12. epp-12 - host object access control (if applicable)
    13. epp-13 - host <update> command test (if applicable)
    14. epp-14 - domain <create> command test
    15. epp-15 - Registry object integrity test
    16. epp-16 - domain <renew> command test
    17. epp-17 - domain <transfer> command test
    18. epp-18 - domain <transfer> rejection test
    19. epp-19 - domain <delete> command test
    20. epp-20 - domain restore test
    21. epp-21 - host rename test (if applicable)
    22. epp-22 - host <delete> command test (if applicable)

    4.4.3. Test plans

    This suite is used by the following test plans:

    +
    1. epp-01 - Service connectivity test
    2. epp-02 - Protocol conformance test
    3. epp-03 - Authentication test
    4. epp-04 - Domain <check> command test
    5. epp-05 - Host <check> command test (if applicable)
    6. epp-06 - Contact <check> command test (if applicable for the registry type)
    7. epp-07 - Contact <create> command test (if applicable for the registry type)
    8. epp-08 - Contact object access control (if applicable)
    9. epp-09 - Contact <update> command test (if applicable for the registry type)
    10. epp-10 - Contact <delete> command test (if applicable for the registry type)
    11. epp-11 - host <create> command test (if applicable)
    12. epp-12 - Host object access control (if applicable)
    13. epp-13 - Host <update> command test (if applicable)
    14. epp-14 - Domain <create> command test
    15. epp-15 - Registry object integrity test
    16. epp-16 - Domain <update> command test
    17. epp-17 - Service Port consistency test
    18. epp-18 - Domain <renew> command test
    19. epp-19 - Domain <transfer> command test
    20. epp-20 - Domain <transfer> rejection test
    21. epp-21 - Domain <delete> command test
    22. epp-22 - Domain restore test
    23. epp-23 - Host rename test (if applicable)
    24. epp-24 - Host <delete> command test (if applicable)

    4.4.3. Test plans

    This suite is used by the following test plans:

    1. Pre-Delegation Test
    2. RSP Change Test
    3. Main RSP Evaluation Test

    4.4.4. Resources

    The following resources may be required to prepare for this test plan:

    4.4.5. Errors

    This test suite may produce the following errors:

    -

    4.4.6. Input parameters

    The test cases used by this suite require the following input +

    4.4.6. Input parameters

    The test cases used by this suite require the following input parameters:

    1. epp.clid01 (string)
    2. epp.clid02 (string)
    3. epp.hostModel (string)
    4. epp.hostName (string)
    5. epp.pwd01 (string)
    6. epp.pwd02 (string)
    7. epp.registeredContacts (array)
    8. epp.registeredNames (array)
    9. epp.registeredNameservers (array)
    10. epp.restoreReportRequired (boolean)
    11. epp.secDNSInterfaces (string)
    12. epp.serverIssuedClientCertificate01 (string)
    13. epp.serverIssuedClientCertificate02 (string)
    14. general.minimalPublicDataSet (boolean)

    4.4.7. Sequence diagram

    Pass/fail criteria - - + + Perl - + epp-01 - -epp-01 + +epp-01 @@ -9381,322 +9447,352 @@

    Pass/fail criteria

    epp-02 - -epp-02 + +epp-02 epp-01->epp-02 - - + + epp-03 - -epp-03 + +epp-03 epp-02->epp-03 - - + + epp-04 - - -epp-04 + + +epp-04 epp-03->epp-04 - - + + epp-14 - - -epp-14 + + +epp-14 epp-03->epp-14 - - + + epp-05 - - -epp-05 + + +epp-05 epp-04->epp-05 - - + + epp-06 - - -epp-06 + + +epp-06 epp-05->epp-06 - - + + epp-07 - - -epp-07 + + +epp-07 epp-06->epp-07 - - + + epp-08 - -epp-08 + +epp-08 epp-07->epp-08 - - + + epp-09 - - -epp-09 + + +epp-09 epp-08->epp-09 - - + + epp-10 - - -epp-10 + + +epp-10 epp-09->epp-10 - - + + epp-11 - -epp-11 + +epp-11 epp-10->epp-11 - - + + epp-12 - - -epp-12 + + +epp-12 epp-11->epp-12 - - + + epp-13 - - -epp-13 + + +epp-13 epp-11->epp-13 - - + + - - -epp-21 - - -epp-21 + + +epp-23 + + +epp-23 - - -epp-11->epp-21 - - + + +epp-11->epp-23 + + epp-15 - -epp-15 + +epp-15 epp-14->epp-15 - - + + epp-16 - - -epp-16 + + +epp-16 epp-14->epp-16 - - + + epp-17 - - -epp-17 + + +epp-17 epp-14->epp-17 - - + + epp-18 - - -epp-18 + + +epp-18 epp-14->epp-18 - - + + epp-19 - - -epp-19 + + +epp-19 epp-14->epp-19 - - - - - -epp-14->epp-21 - - + + epp-20 - - -epp-20 + + +epp-20 - + -epp-19->epp-20 - - +epp-14->epp-20 + + + + + +epp-21 + + +epp-21 + + + + + +epp-14->epp-21 + + + + + +epp-14->epp-23 + + epp-22 - - -epp-22 + + +epp-22 - + epp-21->epp-22 - - + + + + + +epp-24 + + +epp-24 + + + + + +epp-23->epp-24 + + @@ -10415,25 +10511,25 @@

    Pass/fail criteria

    1. Pre-Delegation Test
    2. RSP Change Test

    4.10.4. Resources

    The following resources may be required to prepare for this test plan:

    4.10.5. Errors

    This test suite may produce the following errors:

    -

    4.10.6. Input parameters

    The test cases used by this suite require the following input +

    4.10.6. Input parameters

    The test cases used by this suite require the following input parameters:

    -
    1. dns.nameservers (object)
    2. epp.hostModel (string)
    3. integration.rdeSFTPDirectory (string)
    4. integration.rdeSFTPHostname (string)
    5. integration.rdeSFTPUsername (string)
    6. integration.rriACL (array)
    7. rdap.baseURLs (object)

    4.10.7. Sequence diagram

    +
    1. dns.nameservers (object)
    2. epp.clid01 (string)
    3. epp.hostModel (string)
    4. epp.hostName (string)
    5. epp.pwd01 (string)
    6. epp.serverIssuedClientCertificate01 (string)
    7. general.minimalPublicDataSet (boolean)
    8. integration.rdeSFTPDirectory (string)
    9. integration.rdeSFTPHostname (string)
    10. integration.rdeSFTPUsername (string)
    11. integration.rriACL (array)
    12. rdap.baseURLs (object)

    4.10.7. Sequence diagram

    - - + + Perl - + integration-01 - -integration-01 + +integration-01 @@ -10441,61 +10537,31 @@

    Pass/fail criteria

    integration-02 - -integration-02 + +integration-02 + + +integration-01->integration-02 + + + integration-03 - -integration-03 + +integration-03 - - -epp-11 - -epp-11 - - - -epp-11->integration-01 - - - - - -epp-11->integration-03 - - - - - -epp-14 - -epp-14 - - + -epp-14->integration-01 - - - - - -epp-14->integration-02 - - - - - -epp-14->integration-03 - - +integration-01->integration-03 + + @@ -12600,8 +12666,8 @@
    Objective
    successfully passed:

    • None specified.

    6.59.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.59.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.60. epp-04 - domain <check> command test

    6.60.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.60.2. Description

    The client will perform a series of <check> +

    6.59.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.60. epp-04 - Domain <check> command test

    6.60.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.60.2. Description

    The client will perform a series of <check> commands and will validate the avail attribute of the <domain:name> elements in the server response, as follows:

    @@ -12629,8 +12695,8 @@
    Objective
    successfully passed:

    6.60.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.60.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.61. epp-05 - host <check> command test (if applicable)

    6.61.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.61.2. Description

    If the EPP server supports host objects, this test will perform a +

    6.60.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.61. epp-05 - Host <check> command test (if applicable)

    6.61.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.61.2. Description

    If the EPP server supports host objects, this test will perform a series of <check> commands and will validate the avail attribute of the <host:name> elements in the server response, as follows:

    @@ -12654,10 +12720,10 @@
    Objective
    suite:

    • None specified.

    6.61.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.61.7. Dependants

    The following test cases require this test case to have +

    6.61.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.61.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.62. epp-06 - contact <check> command test (if applicable for the registry type)

    6.62.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.62.2. Description

    If the EPP server supports contact objects, this test will perform a +

    6.61.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.62. epp-06 - Contact <check> command test (if applicable for the registry type)

    6.62.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.62.2. Description

    If the EPP server supports contact objects, this test will perform a series of <check> commands and will validate the avail attribute of the <contact:id> elements in the server response, as follows:

    @@ -12679,10 +12745,10 @@
    Objective
    suite:

    • None specified.

    6.62.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.62.7. Dependants

    The following test cases require this test case to have +

    6.62.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.62.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.63. epp-07 - contact <create> command test (if applicable for the registry type)

    6.63.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.63.2. Description

    This test attempts to create a number of contact objects, and +

    6.62.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.63. epp-07 - Contact <create> command test (if applicable for the registry type)

    6.63.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.63.2. Description

    This test attempts to create a number of contact objects, and validates the server’s response. For example, the test will expect that the server will reject a command that creates an object with missing or invalid properties, but will accept a command to create an object with @@ -12734,7 +12800,7 @@

    Objective
    suite:

    • None specified.

    6.63.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.63.7. Dependants

    The following test cases require this test case to have +

    6.63.7. Dependants

    The following test cases require this test case to have successfully passed:

    6.63.8. Test suites

    This test case is used in the following test suite(s):

    6.64. epp-08 - Contact object access control (if applicable)

    6.64.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.64.2. Description

    This test will confirm that EPP clients are unable to perform @@ -12756,10 +12822,10 @@

    Objective
    suite:

    • None specified.

    6.64.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.64.7. Dependants

    The following test cases require this test case to have +

    6.64.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.64.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.65. epp-09 - contact <update> command test (if applicable for the registry type)

    6.65.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.65.2. Description

    This test will perform <update> commands on the +

    6.64.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.65. epp-09 - Contact <update> command test (if applicable for the registry type)

    6.65.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.65.2. Description

    This test will perform <update> commands on the objects created during epp-07 and will confirm that the server correctly rejects invalid commands (which would specify invalid property values) and accepts valid commands.

    @@ -12801,9 +12867,9 @@
    Objective
    successfully passed:

    6.65.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.65.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.66. epp-10 - contact <delete> command test (if applicable for the registry type)

    6.66.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.66.2. Description

    This test will perform <delete> commands on the -objects created during epp-22 and will confirm that the +

    6.65.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.66. epp-10 - Contact <delete> command test (if applicable for the registry type)

    6.66.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.66.2. Description

    This test will perform <delete> commands on the +objects created during epp-24 and will confirm that the server accepts the <delete> command with a 1xxx response code.

    If the general.minimalPublicDataSet input parameter is @@ -12822,7 +12888,7 @@

    Objective
    suite:

    • None specified.

    6.66.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.66.7. Dependants

    The following test cases require this test case to have +

    6.66.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.66.8. Test suites

    This test case is used in the following test suite(s):

    6.67. epp-11 - host <create> command test (if applicable)

    6.67.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.67.2. Description

    This test attempts to create a number of host objects, and validates @@ -12858,8 +12924,8 @@

    Objective
    successfully passed:

    • None specified.

    6.67.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.67.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.68. epp-12 - host object access control (if applicable)

    6.68.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.68.2. Description

    This test will confirm that EPP clients are unable to perform +

    6.67.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.68. epp-12 - Host object access control (if applicable)

    6.68.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.68.2. Description

    This test will confirm that EPP clients are unable to perform <info> commands on objects that they do not sponsor.

    If the epp.hostModel input parameter is @@ -12880,7 +12946,7 @@

    Objective

    6.68.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.68.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.69. epp-13 - host <update> command test (if applicable)

    6.69.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.69.2. Description

    This test will perform <update> commands on the +

    6.69. epp-13 - Host <update> command test (if applicable)

    6.69.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.69.2. Description

    This test will perform <update> commands on the objects created during epp-11 and will confirm that the server correctly rejects invalid commands (which would specify invalid property values) and accepts valid commands.

    @@ -12910,7 +12976,7 @@
    Objective

    6.69.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.69.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.70. epp-14 - domain <create> command test

    6.70.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.70.2. Description

    This test performs a series domain <create> +

    6.70. epp-14 - Domain <create> command test

    6.70.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.70.2. Description

    This test performs a series domain <create> commands, using pseudo- random ASCII domain names under each TLD in the TLD set. If the general.minimalPublicDataSet input parameter is false, then a contact object (containing @@ -12981,7 +13047,7 @@

    Objective
    successfully passed:

    6.70.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.70.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.70.8. Test suites

    This test case is used in the following test suite(s):

    6.71. epp-15 - Registry object integrity test

    6.71.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.71.2. Description

    This test confirms that the EPP server will refuse a request to delete a linked object.

    If the epp.hostModel input parameter is @@ -13001,10 +13067,59 @@

    Objective
    suite:

    • None specified.

    6.71.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.71.7. Dependants

    The following test cases require this test case to have +

    6.71.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.71.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.72. epp-16 - domain <renew> command test

    6.72.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.72.2. Description

    This test will confirm that the client is able to renew domain names. +

    6.72. epp-16 - Domain <update> command test

    6.72.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.72.2. Description

    This test will confirm that the client is able to perform an +<update> command on the domain names created in +epp-14, including:

    +
      +
    • adding and removing client-assigned status codes
    • +
    • adding and removing nameservers (whether objects or attributes)
    • +
    • changing registrant object (if applicable)
    • +
    • adding and remove DNSSEC information
    • +
    +

    The client will also confirm that it cannot perform an +<update> command on a domain sponsored by another +registrar, and that the server responds with a 2201 +authorization error.

    +

    Once the <update> commands have been processed, +the client will then perform <info> commands to +confirm that the changes have been correctly stored by the server.

    +

    6.72.3. Errors

    This test case may produce the following errors, in addition to + those defined in test suite:

    +

    6.72.4. Input parameters

    This test case requires the following input parameters, in + addition to those defined in the test suite:

    +
    • None specified.

    6.72.5. Resources

    The following resources may be required to prepare for this + test case, in addition to those defined in the test + suite:

    +
    • None specified.

    6.72.6. Dependencies

    This test case requires the following test cases to have + successfully passed:

    +

    6.72.7. Dependants

    The following test cases require this test case to have + successfully passed:

    +
    • None specified.

    6.72.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.73. epp-17 - Service Port consistency test

    6.73.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.73.2. Description

    This test confirms that all EPP service ports respond with consistent +object information.

    +

    The client will establish seperate connections to each EPP service +port (defined as an IP address and TCP port) and perform +<info> commands on the objects created in +epp-14. In all cases, the server MUST +respond with a 1000 response and the content of the +<infData> element MUST be identical +on all service ports.

    +

    6.73.3. Errors

    This test case may produce the following errors, in addition to + those defined in test suite:

    +

    6.73.4. Input parameters

    This test case requires the following input parameters, in + addition to those defined in the test suite:

    +
    • None specified.

    6.73.5. Resources

    The following resources may be required to prepare for this + test case, in addition to those defined in the test + suite:

    +
    • None specified.

    6.73.6. Dependencies

    This test case requires the following test cases to have + successfully passed:

    +

    6.73.7. Dependants

    The following test cases require this test case to have + successfully passed:

    +
    • None specified.

    6.73.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.74. epp-18 - Domain <renew> command test

    6.74.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.74.2. Description

    This test will confirm that the client is able to renew domain names. The client will submit a number of <renew> commands for the domains created in epp-14.

      @@ -13020,19 +13135,19 @@
      Objective

      The client will issue the <renew> commands and then perform <info> commands to ensure that the expiry date and RGP status of the domain are set correctly.

      -

    6.72.3. Errors

    This test case may produce the following errors, in addition to +

    6.74.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.72.4. Input parameters

    This test case requires the following input parameters, in +

    6.74.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.72.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.74.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.72.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.74.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.72.7. Dependants

    The following test cases require this test case to have +

    6.74.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.72.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.73. epp-17 - domain <transfer> command test

    6.73.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.73.2. Description

    This test will confirm that the client is able to initiate a domain +

    • None specified.

    6.74.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.75. epp-19 - Domain <transfer> command test

    6.75.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.75.2. Description

    This test will confirm that the client is able to initiate a domain transfer.

    The client will perform an <update> command to set the authInfo code for the test domain (taken from the set created in @@ -13070,37 +13185,37 @@

    Objective

    This message MUST be received within 120 seconds of the transfer approval.

    -

    6.73.3. Errors

    This test case may produce the following errors, in addition to +

    6.75.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.73.4. Input parameters

    This test case requires the following input parameters, in +

    6.75.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.73.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.75.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.73.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.75.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.73.7. Dependants

    The following test cases require this test case to have +

    6.75.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.73.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.74. epp-18 - domain <transfer> rejection test

    6.74.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.74.2. Description

    This test confirms that the server behaves correctly if the +

    • None specified.

    6.75.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.76. epp-20 - Domain <transfer> rejection test

    6.76.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.76.2. Description

    This test confirms that the server behaves correctly if the sponsoring registrar of a domain rejects a transfer request. The test -procedure matches that of epp-17, but the transfer request +procedure matches that of epp-19, but the transfer request will be rejected rather than approved. An <info> command will be used to confirm that the domain name remains under the sponsorship of the original registrar.

    -

    6.74.3. Errors

    This test case may produce the following errors, in addition to +

    6.76.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.74.4. Input parameters

    This test case requires the following input parameters, in +

    6.76.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.74.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.76.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.74.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.76.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.74.7. Dependants

    The following test cases require this test case to have +

    6.76.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.74.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.75. epp-19 - domain <delete> command test

    6.75.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.75.2. Description

    This test will perform <delete> commands on the +

    • None specified.

    6.76.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.77. epp-21 - Domain <delete> command test

    6.77.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.77.2. Description

    This test will perform <delete> commands on the objects created during epp-14 and will confirm that the server accepts the <delete> command with a 1xxx response code.

    @@ -13115,38 +13230,38 @@
    Objective
    pendingDelete status and the redemptionPeriod RGP status. -

    6.75.3. Errors

    This test case may produce the following errors, in addition to +

    6.77.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.75.4. Input parameters

    This test case requires the following input parameters, in +

    6.77.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.75.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.77.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.75.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.77.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.75.7. Dependants

    The following test cases require this test case to have +

    6.77.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.75.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.76. epp-20 - domain restore test

    6.76.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.76.2. Description

    This test will perform RGP restore operations on the objects deleted -during epp-19, in order to confirm the correct operation of +

    6.77.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.78. epp-22 - Domain restore test

    6.78.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.78.2. Description

    This test will perform RGP restore operations on the objects deleted +during epp-21, in order to confirm the correct operation of the server’s implementation of RFC 3915.

    Once the restore request has been procssed, the client will perform <info> commands on the deleted to object to confirm that the domain no longer has the pendingDelete status and RGP status.

    -

    6.76.3. Errors

    This test case may produce the following errors, in addition to +

    6.78.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.76.4. Input parameters

    This test case requires the following input parameters, in +

    6.78.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -

    6.76.5. Resources

    The following resources may be required to prepare for this +

    6.78.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.76.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.78.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.76.7. Dependants

    The following test cases require this test case to have +

    6.78.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.76.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.77. epp-21 - host rename test (if applicable)

    6.77.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.77.2. Description

    This tests verifies the server’s support for host rename +

    • None specified.

    6.78.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.79. epp-23 - Host rename test (if applicable)

    6.79.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.79.2. Description

    This tests verifies the server’s support for host rename operations.

    If the epp.hostModel input parameter is attributes, this test will be skipped.

    @@ -13172,19 +13287,19 @@
    Objective

    The client will then perform <info> commands on the objects successfully updated, to confirm that the server has correctly stored the updated values.

    -

    6.77.3. Errors

    This test case may produce the following errors, in addition to +

    6.79.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.77.4. Input parameters

    This test case requires the following input parameters, in +

    6.79.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.77.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.79.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.77.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.79.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.77.7. Dependants

    The following test cases require this test case to have +

    6.79.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.77.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.78. epp-22 - host <delete> command test (if applicable)

    6.78.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.78.2. Description

    This test will perform <delete> commands on the +

    6.79.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.80. epp-24 - Host <delete> command test (if applicable)

    6.80.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.80.2. Description

    This test will perform <delete> commands on the objects created during epp-11 and will confirm that the server accepts the <delete> command with a 1xxx response code.

    @@ -13194,19 +13309,19 @@
    Objective
    a 1000 response was received from the server, the client will perform <check> and <info> commands to confirm that the objects have been deleted.

    -

    6.78.3. Errors

    This test case may produce the following errors, in addition to +

    6.80.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.78.4. Input parameters

    This test case requires the following input parameters, in +

    6.80.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.78.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.80.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.78.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.80.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.78.7. Dependants

    The following test cases require this test case to have +

    6.80.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.78.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.79. idn-01 - Label validation test

    6.79.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.79.2. Description

    This test confirms that the EPP server correctly accepts or rejects +

    • None specified.

    6.80.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.81. idn-01 - Label validation test

    6.81.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.81.2. Description

    This test confirms that the EPP server correctly accepts or rejects domain <create> commands for valid and invalid IDN labels, respectively.

    If there are no IDN tables supported under any of the TLDs associated @@ -13219,19 +13334,19 @@

    Objective
    <create> commands for invalid labels and MUST accept all <create> commands for valid labels.

    -

    6.79.3. Errors

    This test case may produce the following errors, in addition to +

    6.81.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.79.4. Input parameters

    This test case requires the following input parameters, in +

    6.81.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.79.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.81.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.79.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.81.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.79.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.81.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.79.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.80. idn-02 - Level 1 variant handling test

    6.80.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.80.2. Description

    This test confirms the EPP server’s conformance with the Level 1 +

    • None specified.

    6.81.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.82. idn-02 - Level 1 variant handling test

    6.82.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.82.2. Description

    This test confirms the EPP server’s conformance with the Level 1 variant support (no support for variant activation, all variants are blocked).

    If there are no IDN tables for which Level 1 support is claimed, this @@ -13243,19 +13358,19 @@

    Objective

    The client will then submit <create> commands for one or more labels that are variants of the names created in the first step. The server MUST reject these commands.

    -

    6.80.3. Errors

    This test case may produce the following errors, in addition to +

    6.82.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.80.4. Input parameters

    This test case requires the following input parameters, in +

    6.82.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.80.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.82.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.80.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.82.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.80.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.82.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.80.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.81. idn-03 - Level 2 variant handling test

    6.81.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.81.2. Description

    This test confirms the EPP server’s conformance with the Level 2 +

    • None specified.

    6.82.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.83. idn-03 - Level 2 variant handling test

    6.83.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.83.2. Description

    This test confirms the EPP server’s conformance with the Level 2 variant support (variants are supported within the same TLD).

    If there are no IDN tables for which Level 2 support is claimed, this test will be skipped.

    @@ -13274,19 +13389,19 @@
    Objective

    The server MUST reject <create> commands where the (a) registrar is different from that of the primary label or (b) the registrant (if applicable) is different.

    -

    6.81.3. Errors

    This test case may produce the following errors, in addition to +

    6.83.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.81.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.83.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.81.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.83.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.81.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.83.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.81.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.83.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.81.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.82. idn-04 - Level 3 variant handling test

    6.82.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.82.2. Description

    This test confirms the EPP server’s conformance with the Level 3 +

    • None specified.

    6.83.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.84. idn-04 - Level 3 variant handling test

    6.84.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.84.2. Description

    This test confirms the EPP server’s conformance with the Level 3 variant support (variants are supported within variant TLD(s)).

    If there are no IDN tables for which Level 3 support is claimed, this test will be skipped.

    @@ -13305,62 +13420,63 @@
    Objective

    The server MUST reject <create> commands where the (a) registrar is different from that of the primary label or (b) the registrant (if applicable) is different.

    -

    6.82.3. Errors

    This test case may produce the following errors, in addition to +

    6.84.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.82.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.84.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.82.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.84.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.82.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.84.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.82.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.84.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.82.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.83. integration-01 - EPP -> RDAP Integration Test

    6.83.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.83.2. Description

    This test confirms that the EPP and RDAP systems are properly +

    • None specified.

    6.84.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.85. integration-01 - EPP -> RDAP Integration Test

    6.85.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.85.2. Description

    This test confirms that the EPP and RDAP systems are properly integrated, that is, that transform commands performed on objects in the EPP system are reflected in the RDAP system within the Service Level Requirement of the SLA.

    -

    The test system will perform RDAP queries to confirm that the RDAP -server provides responses for the domains created in -epp-14, and host objects created in epp-11 (if -applicable). The RDAP server MUST provide a 200 -response within 1 hour of the object’s <crDate> -element.

    -

    6.83.3. Errors

    This test case may produce the following errors, in addition to +

    The test system will connect to the EPP server and create domain and +(if applicable) host and contact objects using the same methodology as +epp-14 epp-11. It will then perform RDAP +queries for those objects.

    +

    The RDAP server MUST provide a 200 response for +every object created within 1 hour of the object’s +<crDate> element.

    +

    6.85.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.83.4. Input parameters

    This test case requires the following input parameters, in +

    6.85.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -

    6.83.5. Resources

    The following resources may be required to prepare for this +

    6.85.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.83.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.85.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.83.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.85.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.83.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.84. integration-02 - EPP -> DNS Integration Test

    6.84.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.84.2. Description

    This test confirms that the EPP and DNS systems are properly +

    6.85.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.86. integration-02 - EPP -> DNS Integration Test

    6.86.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.86.2. Description

    This test confirms that the EPP and DNS systems are properly integrated, that is, that transform commands performed on objects in the EPP system are reflected in the RDAP system within the Service Level Requirement of the SLA.

    The test system will perform DNS queries to confirm that the DNS -servers provides responses for the domain names created in -epp-14. All DNS servers MUST provide the -correct DNS response within 1 hour of the object’s -<crDate> element.

    -

    6.84.3. Errors

    This test case may produce the following errors, in addition to +servers provide responses for the domain names created in +integration-01. All DNS servers MUST +provide the correct DNS response for all domains within 1 hour of the +domains’s <crDate> element.

    +

    6.86.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.84.4. Input parameters

    This test case requires the following input parameters, in +

    6.86.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -

    6.84.5. Resources

    The following resources may be required to prepare for this +

    6.86.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.84.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.86.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.84.7. Dependants

    The following test cases require this test case to have +

    6.86.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.84.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.85. integration-03 - EPP -> RDE Integration Test

    6.85.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.85.2. Description

    This test confirms that the EPP and RDE systems are properly +

    • None specified.

    6.86.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.87. integration-03 - EPP -> RDE Integration Test

    6.87.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.87.2. Description

    This test confirms that the EPP and RDE systems are properly integrated, that is, that objects created in the EPP system are reflected in a valid RDE deposit file within the Service Level Requirement of the SLA.

    @@ -13374,11 +13490,10 @@
    Objective
    operators MUST ensure that the IP addresses listed in the integration.rdeSFTPACL resource have been added to the Access Control List for the SFTP server (if any).

    -

    All objects created in the epp-14 and -epp-11 (if applicable) tests MUST be found -within a valid RDE deposit file (that is, the deposit passes all the -tests in the RDE test suite) within 24 hours of each object’s -<crDate> element.

    +

    All objects created in the integration-01 test case +MUST be found within a valid RDE deposit file (that is, +the deposit passes all the tests in the RDE test suite) within 24 hours +of each object’s <crDate> element.

    Furthermore, for each deposit found in the directory, the corresponding RDE report (as described in Section @@ -13389,19 +13504,19 @@

    Objective
    will be configured to accept submissions for the TLDs associated with the test from clients using the same TLSA DNS hostnames that are configured for the test.

    -

    6.85.3. Errors

    This test case may produce the following errors, in addition to +

    6.87.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.85.4. Input parameters

    This test case requires the following input parameters, in +

    6.87.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -

    6.85.5. Resources

    The following resources may be required to prepare for this +

    6.87.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -

    6.85.6. Dependencies

    This test case requires the following test cases to have +

    6.87.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.85.7. Dependants

    The following test cases require this test case to have +

    6.87.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.85.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.86. minimumRPMs-01 - Claims <check> command test

    6.86.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.86.2. Description

    This test is used to confirm the conformance of the EPP server’s +

    • None specified.

    6.87.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.88. minimumRPMs-01 - Claims <check> command test

    6.88.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.88.2. Description

    This test is used to confirm the conformance of the EPP server’s implementation of the Claims Check Form, as described in Section 3.1.1 of RFC 8334.

    For this test, it is assumed that the EPP server has been configured @@ -13422,20 +13537,20 @@

    Objective
    present on the DNL does not contain a <launch:claimKey> element. -

    6.86.3. Errors

    This test case may produce the following errors, in addition to +

    6.88.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.86.4. Input parameters

    This test case requires the following input parameters, in +

    6.88.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.86.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.88.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.86.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.88.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.86.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.88.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.86.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.87. minimumRPMs-02 - Sunrise domain/launch application <create> command test -

    6.87.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.87.2. Description

    This test is used to confirm the conformance of the EPP server’s +

    • None specified.

    6.88.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.89. minimumRPMs-02 - Sunrise domain/launch application <create> command test +

    6.89.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.89.2. Description

    This test is used to confirm the conformance of the EPP server’s implementation of the Sunrise Create Form, as described in Section 3.3.1 of RFC 8334.

    For this test, it is assumed that the EPP server has been configured @@ -13467,19 +13582,19 @@

    Objective
  • create a domain using a revoked SMD;
  • create a domain using an SMD signed by a revoked certificate.
  • -

    6.87.3. Errors

    This test case may produce the following errors, in addition to +

    6.89.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.87.4. Input parameters

    This test case requires the following input parameters, in +

    6.89.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.87.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.89.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.87.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.89.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.87.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.89.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.87.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.88. minimumRPMs-03 - Trademark claims domain <create> command test

    6.88.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.88.2. Description

    This test is used to confirm the conformance of the EPP server’s +

    • None specified.

    6.89.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.90. minimumRPMs-03 - Trademark claims domain <create> command test

    6.90.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.90.2. Description

    This test is used to confirm the conformance of the EPP server’s implementation of the Claims Create Form, as described in Section 3.3.2 of RFC 8334.

    For this test, it is assumed that the EPP server has been configured @@ -13505,67 +13620,35 @@

    Objective
  • create a domain using an acceptance datetime more than 48 hours in the past.
  • -

    6.88.3. Errors

    This test case may produce the following errors, in addition to +

    6.90.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.88.4. Input parameters

    This test case requires the following input parameters, in +

    6.90.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.88.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.90.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.88.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.90.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.88.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.90.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.88.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.89. rdap-01-domainCaseFoldingValidation - Domain label case folding validation

    6.89.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.89.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    • None specified.

    6.90.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.91. rdap-01-domainCaseFoldingValidation - Domain label case folding validation

    6.91.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.91.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    -

    6.89.3. Errors

    This test case may produce the following errors, in addition to +

    6.91.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.89.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.91.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.89.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.91.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.89.6. Dependencies

    This test case requires the following test cases to have - successfully passed:

    -
    • None specified.

    6.89.7. Dependants

    The following test cases require this test case to have - successfully passed:

    -
    • None specified.

    6.89.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.90. rdap-02-domainNameValidation - Domain Name validation

    6.90.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.90.2. Description

    This test case comes from the RDAP Conformance Tool. For more -information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    -

    6.90.3. Errors

    This test case may produce the following errors, in addition to - those defined in test suite:

    -
    • None specified.

    6.90.4. Input parameters

    This test case requires the following input parameters, in - addition to those defined in the test suite:

    -
    • None specified.

    6.90.5. Resources

    The following resources may be required to prepare for this - test case, in addition to those defined in the test - suite:

    -
    • None specified.

    6.90.6. Dependencies

    This test case requires the following test cases to have - successfully passed:

    -
    • None specified.

    6.90.7. Dependants

    The following test cases require this test case to have - successfully passed:

    -
    • None specified.

    6.90.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.91. rdap-03-ipv4Validation - IPv4 address validation

    6.91.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.91.2. Description

    This test case comes from the RDAP Conformance Tool. For more -information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    -

    6.91.3. Errors

    This test case may produce the following errors, in addition to - those defined in test suite:

    -
    • None specified.

    6.91.4. Input parameters

    This test case requires the following input parameters, in - addition to those defined in the test suite:

    -
    • None specified.

    6.91.5. Resources

    The following resources may be required to prepare for this - test case, in addition to those defined in the test - suite:

    -
    • None specified.

    6.91.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.91.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    • None specified.

    6.91.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.91.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.92. rdap-04-ipv6Validation - IPv6 address validation

    6.92.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.92.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.92. rdap-02-domainNameValidation - Domain Name validation

    6.92.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.92.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13581,7 +13664,7 @@
    Objective
    • None specified.

    6.92.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.92.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.93. rdap-05-stdRdapAsEventActorValidation - asEventActor Validation

    6.93.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.93.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.93. rdap-03-ipv4Validation - IPv4 address validation

    6.93.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.93.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13597,7 +13680,7 @@
    Objective
    • None specified.

    6.93.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.93.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.94. rdap-06-stdRdapConformanceValidation - RDAP Conformance validation

    6.94.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.94.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.94. rdap-04-ipv6Validation - IPv6 address validation

    6.94.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.94.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13613,7 +13696,7 @@
    Objective
    • None specified.

    6.94.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.94.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.95. rdap-07-stdRdapDomainLookupValidation - Domain Lookup Validation

    6.95.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.95.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.95. rdap-05-stdRdapAsEventActorValidation - asEventActor Validation

    6.95.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.95.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13629,7 +13712,7 @@
    Objective
    • None specified.

    6.95.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.95.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.96. rdap-08-stdRdapEntitiesValidation - Entities validation

    6.96.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.96.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.96. rdap-06-stdRdapConformanceValidation - RDAP Conformance validation

    6.96.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.96.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13645,7 +13728,7 @@
    Objective
    • None specified.

    6.96.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.96.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.97. rdap-09-stdRdapEntityLookupValidation - Entity lookup validation

    6.97.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.97.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.97. rdap-07-stdRdapDomainLookupValidation - Domain Lookup Validation

    6.97.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.97.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13661,7 +13744,7 @@
    Objective
    • None specified.

    6.97.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.97.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.98. rdap-10-stdRdapErrorResponseBodyValidation - Error Response Body

    6.98.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.98.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.98. rdap-08-stdRdapEntitiesValidation - Entities validation

    6.98.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.98.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13677,7 +13760,7 @@
    Objective
    • None specified.

    6.98.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.98.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.99. rdap-11-stdRdapEventsValidation - Events Validation

    6.99.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.99.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.99. rdap-09-stdRdapEntityLookupValidation - Entity lookup validation

    6.99.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.99.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13693,7 +13776,7 @@
    Objective
    • None specified.

    6.99.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.99.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.100. rdap-12-stdRdapHelpValidation - Help validation

    6.100.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.100.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.100. rdap-10-stdRdapErrorResponseBodyValidation - Error Response Body

    6.100.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.100.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13709,7 +13792,7 @@
    Objective
    • None specified.

    6.100.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.100.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.101. rdap-13-stdRdapIpAddressesValidation - IP Addresses Validation

    6.101.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.101.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.101. rdap-11-stdRdapEventsValidation - Events Validation

    6.101.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.101.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13725,7 +13808,7 @@
    Objective
    • None specified.

    6.101.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.101.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.102. rdap-14-stdRdapLanguageIdentifierValidation - Language Identifier Validation

    6.102.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.102.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.102. rdap-12-stdRdapHelpValidation - Help validation

    6.102.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.102.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13741,7 +13824,7 @@
    Objective
    • None specified.

    6.102.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.102.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.103. rdap-15-stdRdapLdhNameValidation - LDH name

    6.103.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.103.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.103. rdap-13-stdRdapIpAddressesValidation - IP Addresses Validation

    6.103.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.103.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13757,7 +13840,7 @@
    Objective
    • None specified.

    6.103.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.103.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.104. rdap-16-stdRdapLinksValidation - Links validation

    6.104.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.104.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.104. rdap-14-stdRdapLanguageIdentifierValidation - Language Identifier Validation

    6.104.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.104.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13773,7 +13856,7 @@
    Objective
    • None specified.

    6.104.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.104.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.105. rdap-17-stdRdapNameserverLookupValidation - Nameserver lookup validation

    6.105.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.105.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.105. rdap-15-stdRdapLdhNameValidation - LDH name

    6.105.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.105.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13789,7 +13872,7 @@
    Objective
    • None specified.

    6.105.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.105.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.106. rdap-18-stdRdapNameserversSearchValidation - Nameservers search validation

    6.106.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.106.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.106. rdap-16-stdRdapLinksValidation - Links validation

    6.106.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.106.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13805,7 +13888,7 @@
    Objective
    • None specified.

    6.106.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.106.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.107. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks Validation

    6.107.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.107.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.107. rdap-17-stdRdapNameserverLookupValidation - Nameserver lookup validation

    6.107.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.107.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13821,7 +13904,7 @@
    Objective
    • None specified.

    6.107.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.107.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.108. rdap-20-stdRdapPort43WhoisServerValidation - Port 43 WHOIS Server

    6.108.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.108.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.108. rdap-18-stdRdapNameserversSearchValidation - Nameservers search validation

    6.108.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.108.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13837,7 +13920,7 @@
    Objective
    • None specified.

    6.108.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.108.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.109. rdap-21-stdRdapPublicIdsValidation - Public IDs validation

    6.109.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.109.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.109. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks Validation

    6.109.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.109.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13853,7 +13936,7 @@
    Objective
    • None specified.

    6.109.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.109.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.110. rdap-22-stdRdapRolesValidation - Roles validation

    6.110.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.110.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.110. rdap-20-stdRdapPort43WhoisServerValidation - Port 43 WHOIS Server

    6.110.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.110.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13869,7 +13952,7 @@
    Objective
    • None specified.

    6.110.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.110.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.111. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation

    6.111.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.111.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.111. rdap-21-stdRdapPublicIdsValidation - Public IDs validation

    6.111.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.111.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13885,7 +13968,7 @@
    Objective
    • None specified.

    6.111.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.111.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.112. rdap-24-stdRdapStatusValidation - Status validation

    6.112.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.112.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.112. rdap-22-stdRdapRolesValidation - Roles validation

    6.112.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.112.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13901,7 +13984,7 @@
    Objective
    • None specified.

    6.112.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.112.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.113. rdap-25-stdRdapUnicodeNameValidation - Unicode name

    6.113.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.113.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.113. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation

    6.113.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.113.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13917,7 +14000,7 @@
    Objective
    • None specified.

    6.113.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.113.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.114. rdap-26-stdRdapVariantsValidation - Variants validation

    6.114.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.114.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.114. rdap-24-stdRdapStatusValidation - Status validation

    6.114.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.114.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13933,7 +14016,7 @@
    Objective
    • None specified.

    6.114.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.114.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.115. rdap-27-webUriValidation - Web URI validation

    6.115.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.115.2. Description

    This test case comes from the RDAP Conformance Tool. For more +

    6.115. rdap-25-stdRdapUnicodeNameValidation - Unicode name

    6.115.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.115.2. Description

    This test case comes from the RDAP Conformance Tool. For more information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -13949,17 +14032,13 @@
    Objective
    • None specified.

    6.115.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.115.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.116. rde-01 - validate deposit filename format

    6.116.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.116.2. Description

      -
    • The deposit filename MUST conform to the format -specified in the RA.
    • -
    • The type of the deposit MUST be -FULL.
    • -
    • The TLD in the filename MUST be present in the list -of TLDs associated with the test.
    • -
    +

    6.116. rdap-26-stdRdapVariantsValidation - Variants validation

    6.116.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.116.2. Description

    This test case comes from the RDAP Conformance Tool. For more +information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    6.116.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.116.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.116.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    • None specified.

    6.116.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test @@ -13969,13 +14048,15 @@

    Objective
    • None specified.

    6.116.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.116.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.117. rde-02 - validate signature over deposit file

    6.117.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.117.2. Description

    The PGP signature MUST be valid for the deposit file -and the RSP’s key.

    +

    6.117. rdap-27-webUriValidation - Web URI validation

    6.117.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.117.2. Description

    This test case comes from the RDAP Conformance Tool. For more +information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    6.117.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.117.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.117.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -

    6.117.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.117.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    • None specified.

    6.117.6. Dependencies

    This test case requires the following test cases to have @@ -13983,42 +14064,76 @@

    Objective
    • None specified.

    6.117.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.117.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.118. rde-03 - decrypt deposit file(s)

    6.118.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.118.2. Description

    It MUST be possible to decrypt the deposit file -using the RST key. The PGP public key for which the deposit -MUST be encrypted may be found in the URL specified by -the rde.encryptionKey resource.

    +

    6.118. rde-01 - validate deposit filename format

    6.118.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.118.2. Description

      +
    • The deposit filename MUST conform to the format +specified in the RA.
    • +
    • The type of the deposit MUST be +FULL.
    • +
    • The TLD in the filename MUST be present in the list +of TLDs associated with the test.
    • +

    6.118.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.118.4. Input parameters

    This test case requires the following input parameters, in +

    6.118.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    • None specified.

    6.118.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -

    6.118.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.118.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    • None specified.

    6.118.7. Dependants

    The following test cases require this test case to have successfully passed:

    • None specified.

    6.118.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.119. rde-04 - validate XML/CSV

    6.119.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.119.2. Description

    6.119. rde-02 - validate signature over deposit file

    6.119.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.119.2. Description

    The PGP signature MUST be valid for the deposit file +and the RSP’s key.

    +

    6.119.3. Errors

    This test case may produce the following errors, in addition to + those defined in test suite:

    +

    6.119.4. Input parameters

    This test case requires the following input parameters, in + addition to those defined in the test suite:

    +

    6.119.5. Resources

    The following resources may be required to prepare for this + test case, in addition to those defined in the test + suite:

    +
    • None specified.

    6.119.6. Dependencies

    This test case requires the following test cases to have + successfully passed:

    +
    • None specified.

    6.119.7. Dependants

    The following test cases require this test case to have + successfully passed:

    +
    • None specified.

    6.119.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.120. rde-03 - decrypt deposit file(s)

    6.120.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.120.2. Description

    It MUST be possible to decrypt the deposit file +using the RST key. The PGP public key for which the deposit +MUST be encrypted may be found in the URL specified by +the rde.encryptionKey resource.

    +

    6.120.3. Errors

    This test case may produce the following errors, in addition to + those defined in test suite:

    +

    6.120.4. Input parameters

    This test case requires the following input parameters, in + addition to those defined in the test suite:

    +
    • None specified.

    6.120.5. Resources

    The following resources may be required to prepare for this + test case, in addition to those defined in the test + suite:

    +

    6.120.6. Dependencies

    This test case requires the following test cases to have + successfully passed:

    +
    • None specified.

    6.120.7. Dependants

    The following test cases require this test case to have + successfully passed:

    +
    • None specified.

    6.120.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.121. rde-04 - validate XML/CSV

    6.121.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.121.2. Description

    • XML deposit files MUST be well-formed and validate against the XML schema.
    • CSV files MUST conform to RFC 4180.
    • Deposits MUST NOT contain a mix of XML and CSV files for the deposit contents.
    -

    6.119.3. Errors

    This test case may produce the following errors, in addition to +

    6.121.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.119.4. Input parameters

    This test case requires the following input parameters, in +

    6.121.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.119.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.121.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.119.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.121.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.119.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.121.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.119.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.120. rde-05 - validate object types

    6.120.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.120.2. Description

    The header object MUST reference the correct object +

    • None specified.

    6.121.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.122. rde-05 - validate object types

    6.122.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.122.2. Description

    The header object MUST reference the correct object XML namespace URIs.

    The correct URIs is determined by the general.minimalPublicDataSet and epp.hostModel @@ -14035,33 +14150,33 @@

    Objective

    All expected URIs MUST be present in the header, and the header MUST NOT contain any unexpected URIs.

    -

    6.120.3. Errors

    This test case may produce the following errors, in addition to +

    6.122.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.120.4. Input parameters

    This test case requires the following input parameters, in +

    6.122.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.120.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.122.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.120.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.122.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.120.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.122.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.120.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.121. rde-06 - validate object counts

    6.121.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.121.2. Description

    The number of each type of object MUST match the +

    • None specified.

    6.122.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.123. rde-06 - validate object counts

    6.123.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.123.2. Description

    The number of each type of object MUST match the number of objects actually present in the deposit file.

    -

    6.121.3. Errors

    This test case may produce the following errors, in addition to +

    6.123.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.121.4. Input parameters

    This test case requires the following input parameters, in +

    6.123.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.121.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.123.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.121.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.123.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.121.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.123.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.121.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.122. rde-07 - validate domain objects

    6.122.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.122.2. Description

    Domain objects (whether CSV or XML) MUST have the +

    • None specified.

    6.123.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.124. rde-07 - validate domain objects

    6.124.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.124.2. Description

    Domain objects (whether CSV or XML) MUST have the required object properties, and the values of those object properties MUST be well-formed.

    The required properties are:

    @@ -14079,19 +14194,19 @@
    Objective

    Contact, host and registrar objects (including optional objects such as admin and tech contacts) which are referenced in domain objects MUST be present in the deposit.

    -

    6.122.3. Errors

    This test case may produce the following errors, in addition to +

    6.124.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.122.4. Input parameters

    This test case requires the following input parameters, in +

    6.124.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.122.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.124.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.122.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.124.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.122.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.124.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.122.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.123. rde-08 - validate host objects (if applicable)

    6.123.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.123.2. Description

    Host objects (whether CSV or XML) MUST have the +

    • None specified.

    6.124.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.125. rde-08 - validate host objects (if applicable)

    6.125.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.125.2. Description

    Host objects (whether CSV or XML) MUST have the required object properties, and the values of those object properties MUST be well-formed.

    The required properties are:

    @@ -14108,19 +14223,19 @@
    Objective
    be skipped.

    Registrar objects which are referenced in host objects MUST be present in the deposit.

    -

    6.123.3. Errors

    This test case may produce the following errors, in addition to +

    6.125.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.123.4. Input parameters

    This test case requires the following input parameters, in +

    6.125.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.123.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.125.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.123.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.125.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.123.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.125.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.123.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.124. rde-09 - validate contact objects (if applicable)

    6.124.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.124.2. Description

    Contact objects (whether CSV or XML) MUST have the +

    • None specified.

    6.125.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.126. rde-09 - validate contact objects (if applicable)

    6.126.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.126.2. Description

    Contact objects (whether CSV or XML) MUST have the required object properties, and the values of those object properties MUST be well-formed.

    If the value of the general.minimalPublicDataSet input @@ -14140,19 +14255,19 @@

    Objective

    Registrar objects which are referenced in contact objects MUST be present in the deposit.

    -

    6.124.3. Errors

    This test case may produce the following errors, in addition to +

    6.126.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.124.4. Input parameters

    This test case requires the following input parameters, in +

    6.126.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.124.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.126.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.124.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.126.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.124.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.126.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.124.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.125. rde-10 - validate registrar objects

    6.125.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.125.2. Description

    Registrar objects (whether CSV or XML) MUST have the +

    • None specified.

    6.126.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.127. rde-10 - validate registrar objects

    6.127.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.127.2. Description

    Registrar objects (whether CSV or XML) MUST have the required object properties, and the values of those object properties MUST be well-formed.

    The required properties are:

    @@ -14161,72 +14276,72 @@
    Objective
  • <rdeRegistrar:name>
  • <rdeRegistrar:gurid> (IANA ID)
  • -

    6.125.3. Errors

    This test case may produce the following errors, in addition to +

    6.127.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.125.4. Input parameters

    This test case requires the following input parameters, in +

    6.127.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.125.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.127.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.125.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.127.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.125.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.127.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.125.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.126. rde-11 - validate IDN table objects (if applicable)

    6.126.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.126.2. Description

    IDN table objects (whether CSV or XML) MUST have the +

    • None specified.

    6.127.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.128. rde-11 - validate IDN table objects (if applicable)

    6.128.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.128.2. Description

    IDN table objects (whether CSV or XML) MUST have the required object properties, and the values of those object properties MUST be well-formed.

    All IDN table objects present in the deposit MUST correspond to IDN tables approved for the TLD, and all approved tables MUST have a corresponding object in the deposit.

    -

    6.126.3. Errors

    This test case may produce the following errors, in addition to +

    6.128.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.126.4. Input parameters

    This test case requires the following input parameters, in +

    6.128.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.126.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.128.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.126.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.128.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.126.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.128.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.126.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.127. rde-12 - validate NNDN objects

    6.127.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.127.2. Description

    NNDN table objects (whether CSV or XML) MUST have +

    • None specified.

    6.128.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.129. rde-12 - validate NNDN objects

    6.129.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.129.2. Description

    NNDN table objects (whether CSV or XML) MUST have the required object properties, and the values of those object properties MUST be well-formed.

    The aName property of NNDN objects MUST NOT match the name property of a domain object.

    -

    6.127.3. Errors

    This test case may produce the following errors, in addition to +

    6.129.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.127.4. Input parameters

    This test case requires the following input parameters, in +

    6.129.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.127.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.129.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.127.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.129.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.127.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.129.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.127.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.128. rde-13 - validate EPP parameters object

    6.128.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.128.2. Description

    The EPP Parameters object MUST match the +

    • None specified.

    6.129.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.130. rde-13 - validate EPP parameters object

    6.130.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.130.2. Description

    The EPP Parameters object MUST match the <greeting> element provided as an input parameter.

    A test case in the EPP Test Suite will confirm that this also matches what is returned when a client connects to the EPP server.

    -

    6.128.3. Errors

    This test case may produce the following errors, in addition to +

    6.130.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.128.4. Input parameters

    This test case requires the following input parameters, in +

    6.130.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -

    6.128.5. Resources

    The following resources may be required to prepare for this +

    6.130.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.128.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.130.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.128.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.130.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.128.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.129. rde-14 - validate policy object (if applicable)

    6.129.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.129.2. Description

    The object policies included in the +

    • None specified.

    6.130.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.131. rde-14 - validate policy object (if applicable)

    6.131.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.131.2. Description

    The object policies included in the <rdePolicy:policy> object MUST conform to the Registration Data Policy and the applicable data model.

    @@ -14238,37 +14353,37 @@
    Objective
    attributes, then host objects MUST NOT be present in the deposit. -

    6.129.3. Errors

    This test case may produce the following errors, in addition to +

    6.131.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.129.4. Input parameters

    This test case requires the following input parameters, in +

    6.131.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.129.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.131.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.129.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.131.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.129.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.131.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.129.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.130. srsgw-01 - IPv4 and IPv6 connectivity

    6.130.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.130.2. Description

    This test confirms that the SRS Gateway EPP system is reachable over +

    • None specified.

    6.131.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.132. srsgw-01 - IPv4 and IPv6 connectivity

    6.132.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.132.2. Description

    This test confirms that the SRS Gateway EPP system is reachable over IPv4 and IPv6.

    The SRS Gateway EPP server host name will be resolved to obtain its IPv4 and IPv6 addresses. The client will then attempt to connect to TCP port 700 on these addresses and log in using the provided credentials.

    -

    6.130.3. Errors

    This test case may produce the following errors, in addition to +

    6.132.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.130.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.132.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.130.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.132.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.130.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.132.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.130.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.132.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.130.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.131. srsgw-02 - Host <create> synchronization (if applicable)

    6.131.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.131.2. Description

    This test confirms that host objects created in the SRS Gateway EPP +

    • None specified.

    6.132.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.133. srsgw-02 - Host <create> synchronization (if applicable)

    6.133.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.133.2. Description

    This test confirms that host objects created in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the epp.hostModel input parameter is attributes, then this test will be skipped.

    @@ -14286,19 +14401,19 @@
    Objective
    response.

    The two <info> responses will then be compared and MUST be identical.

    -

    6.131.3. Errors

    This test case may produce the following errors, in addition to +

    6.133.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.131.4. Input parameters

    This test case requires the following input parameters, in +

    6.133.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.131.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.133.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.131.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.133.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.131.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.133.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.131.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.132. srsgw-03 - Contact <create> synchronization (if applicable)

    6.132.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.132.2. Description

    This test confirms that contact objects created in the SRS Gateway +

    6.133.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.134. srsgw-03 - Contact <create> synchronization (if applicable)

    6.134.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.134.2. Description

    This test confirms that contact objects created in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the general.minimalPublicDataSet input @@ -14315,19 +14430,19 @@

    Objective
    response.

    The two <info> responses will then be compared and MUST be identical.

    -

    6.132.3. Errors

    This test case may produce the following errors, in addition to +

    6.134.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.132.4. Input parameters

    This test case requires the following input parameters, in +

    6.134.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.132.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.134.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.132.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.134.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -
    • None specified.

    6.132.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.134.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.132.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.133. srsgw-04 - Domain <create> synchronization

    6.133.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.133.2. Description

    This test confirms that domain objects created in the SRS Gateway EPP +

    6.134.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.135. srsgw-04 - Domain <create> synchronization

    6.135.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.135.2. Description

    This test confirms that domain objects created in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    The client will connect to the SRS Gateway EPP system, authenticate, and submit <create> commands for a pseudo-randomly @@ -14344,19 +14459,19 @@

    Objective
    response.

    The pairs of <info> responses will then be compared and MUST be identical.

    -

    6.133.3. Errors

    This test case may produce the following errors, in addition to +

    6.135.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.133.4. Input parameters

    This test case requires the following input parameters, in +

    6.135.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.133.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.135.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.133.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.135.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.133.7. Dependants

    The following test cases require this test case to have +

    6.135.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.133.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.134. srsgw-05 - Domain <renew> synchronisation

    6.134.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.134.2. Description

    This test confirms that the expiry dates of domain objects renewed in +

    6.135.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.136. srsgw-05 - Domain <renew> synchronisation

    6.136.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.136.2. Description

    This test confirms that the expiry dates of domain objects renewed in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    The client will connect to the SRS Gateway EPP system, authenticate, @@ -14371,19 +14486,19 @@

    Objective

    The <exDate> element of the two <info> responses will then be compared and MUST be identical.

    -

    6.134.3. Errors

    This test case may produce the following errors, in addition to +

    6.136.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.134.4. Input parameters

    This test case requires the following input parameters, in +

    6.136.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.134.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.136.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.134.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.136.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.134.7. Dependants

    The following test cases require this test case to have +

    6.136.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.134.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.135. srsgw-06 - Domain <transfer> synchronisation

    6.135.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.135.2. Description

    This test confirms that transfer requests submitted in the SRS +

    6.136.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.137. srsgw-06 - Domain <transfer> synchronisation

    6.137.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.137.2. Description

    This test confirms that transfer requests submitted in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    The client will connect to the SRS Gateway EPP system, authenticate, @@ -14407,19 +14522,19 @@

    Objective
    command was 1001, then the domain MUST have the pendingTransfer status. -

    6.135.3. Errors

    This test case may produce the following errors, in addition to +

    6.137.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.135.4. Input parameters

    This test case requires the following input parameters, in +

    6.137.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.135.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.137.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.135.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.137.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.135.7. Dependants

    The following test cases require this test case to have +

    6.137.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.135.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.136. srsgw-07 - Domain <transfer> approval synchronisation

    6.136.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.136.2. Description

    This test confirms that transfer request approvals submitted in the +

    6.137.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.138. srsgw-07 - Domain <transfer> approval synchronisation

    6.138.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.138.2. Description

    This test confirms that transfer request approvals submitted in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the response to the <transfer op="request"> @@ -14435,19 +14550,19 @@

    Objective
    MUST respond with a 1000 response. The <domain:clID> element MUST contain the value of the srsgw.eppClid01 input parameter.

    -

    6.136.3. Errors

    This test case may produce the following errors, in addition to +

    6.138.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.136.4. Input parameters

    This test case requires the following input parameters, in +

    6.138.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.136.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.138.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.136.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.138.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.136.7. Dependants

    The following test cases require this test case to have +

    6.138.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.136.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.137. srsgw-08 - Domain <delete> synchronisation

    6.137.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.137.2. Description

    This test confirms that domain objects deleted in the SRS Gateway EPP +

    6.138.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.139. srsgw-08 - Domain <delete> synchronisation

    6.139.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.139.2. Description

    This test confirms that domain objects deleted in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    The client will connect to the SRS Gateway EPP system, authenticate using the credentials provided in epp.clid02 and @@ -14463,19 +14578,19 @@

    Objective

    The domain object MUST have the pendingDelete status and have an RGP status of pendingDeleteRestorable.

    -

    6.137.3. Errors

    This test case may produce the following errors, in addition to +

    6.139.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -

    6.137.4. Input parameters

    This test case requires the following input parameters, in +

    6.139.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.137.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.139.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.137.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.139.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.137.7. Dependants

    The following test cases require this test case to have +

    6.139.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.137.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.138. srsgw-09 - Host <update> synchronization (if applicable)

    6.138.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.138.2. Description

    This test confirms that host objects updated in the SRS Gateway EPP +

    • None specified.

    6.139.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.140. srsgw-09 - Host <update> synchronization (if applicable)

    6.140.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.140.2. Description

    This test confirms that host objects updated in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the epp.hostModel input parameter is attributes, then this test will be skipped.

    @@ -14488,19 +14603,19 @@
    Objective
    perform <info> commands for those objects.

    The two sets of <info> responses MUST be identical.

    -

    6.138.3. Errors

    This test case may produce the following errors, in addition to +

    6.140.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.138.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.140.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.138.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.140.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.138.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.140.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.138.7. Dependants

    The following test cases require this test case to have +

    6.140.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.138.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.139. srsgw-10 - Host <delete> synchronization (if applicable)

    6.139.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.139.2. Description

    This test confirms that host objects deleted in the SRS Gateway EPP +

    6.140.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.141. srsgw-10 - Host <delete> synchronization (if applicable)

    6.141.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.141.2. Description

    This test confirms that host objects deleted in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the epp.hostModel input parameter is attributes, then this test will be skipped.

    @@ -14512,19 +14627,19 @@
    Objective
    perform <info> commands for those objects. The server MUST respond with a 2303 “object does not exist” response.

    -

    6.139.3. Errors

    This test case may produce the following errors, in addition to +

    6.141.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.139.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.141.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.139.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.141.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.139.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.141.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.139.7. Dependants

    The following test cases require this test case to have +

    6.141.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.139.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.140. srsgw-11 - Contact <update> synchronization (if applicable)

    6.140.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.140.2. Description

    This test confirms that contact objects updated in the SRS Gateway +

    • None specified.

    6.141.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.142. srsgw-11 - Contact <update> synchronization (if applicable)

    6.142.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.142.2. Description

    This test confirms that contact objects updated in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the general.minimalPublicDataSet input @@ -14537,19 +14652,19 @@

    Objective
    perform <info> commands for those objects.

    The two sets of <info> responses MUST be identical.

    -

    6.140.3. Errors

    This test case may produce the following errors, in addition to +

    6.142.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.140.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.142.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.140.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.142.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.140.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.142.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.140.7. Dependants

    The following test cases require this test case to have +

    6.142.7. Dependants

    The following test cases require this test case to have successfully passed:

    -

    6.140.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.141. srsgw-12 - Contact <delete> synchronization (if applicable)

    6.141.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.141.2. Description

    This test confirms that contact objects delete in the SRS Gateway EPP +

    6.142.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.143. srsgw-12 - Contact <delete> synchronization (if applicable)

    6.143.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.143.2. Description

    This test confirms that contact objects delete in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the general.minimalPublicDataSet input parameter is true, then this test will be skipped.

    @@ -14561,38 +14676,38 @@
    Objective
    perform <info> commands for those objects. The server MUST respond with a 2303 “object does not exist” response.

    -

    6.141.3. Errors

    This test case may produce the following errors, in addition to +

    6.143.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.141.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.143.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.141.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.143.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.141.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.143.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.141.7. Dependants

    The following test cases require this test case to have +

    6.143.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.141.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.142. srsgw-13 - Domain RDAP synchronization

    6.142.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.142.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides +

    • None specified.

    6.143.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.144. srsgw-13 - Domain RDAP synchronization

    6.144.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.144.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides responses to domain lookups that match those of the primary registry RDAP server.

    The test system will perform RDAP queries for some of the objects created in srsgw-04 against both the primary registry RDAP server and the SRS Gateway RDAP server. After canonicalisation, the responses from each server MUST be identical.

    -

    6.142.3. Errors

    This test case may produce the following errors, in addition to +

    6.144.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.142.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.144.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.142.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.144.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.142.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.144.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.142.7. Dependants

    The following test cases require this test case to have +

    6.144.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.142.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.143. srsgw-14 - Nameserver RDAP synchronization

    6.143.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.143.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides +

    • None specified.

    6.144.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.145. srsgw-14 - Nameserver RDAP synchronization

    6.145.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.145.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides responses to domain lookups that match those of the primary registry RDAP server.

    If the value of the epp.hostModel input parameter is @@ -14601,19 +14716,19 @@

    Objective
    created in srsgw-02 against both the primary registry RDAP server and the SRS Gateway RDAP server. After canonicalisation, the JSON responses from each server MUST be identical.

    -

    6.143.3. Errors

    This test case may produce the following errors, in addition to +

    6.145.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.143.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.145.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.143.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.145.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.143.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.145.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.143.7. Dependants

    The following test cases require this test case to have +

    6.145.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.143.8. Test suites

    This test case is used in the following test suite(s):

    -

    6.144. srsgw-15 - Registrar RDAP synchronization

    6.144.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.144.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides +

    • None specified.

    6.145.8. Test suites

    This test case is used in the following test suite(s):

    +

    6.146. srsgw-15 - Registrar RDAP synchronization

    6.146.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.146.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides responses to registrar (entity) lookups that match those of the primary registry RDAP server.

    The test system will perform RDAP queries for some of the objects @@ -14625,18 +14740,18 @@

    Objective
    those URLs.

    After canonicalisation, the JSON responses from each server MUST be identical.

    -

    6.144.3. Errors

    This test case may produce the following errors, in addition to +

    6.146.3. Errors

    This test case may produce the following errors, in addition to those defined in test suite:

    -
    • None specified.

    6.144.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.146.4. Input parameters

    This test case requires the following input parameters, in addition to those defined in the test suite:

    -
    • None specified.

    6.144.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.146.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test suite:

    -
    • None specified.

    6.144.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.146.6. Dependencies

    This test case requires the following test cases to have successfully passed:

    -

    6.144.7. Dependants

    The following test cases require this test case to have +

    6.146.7. Dependants

    The following test cases require this test case to have successfully passed:

    -
    • None specified.

    6.144.8. Test suites

    This test case is used in the following test suite(s):

    +
    • None specified.

    6.146.8. Test suites

    This test case is used in the following test suite(s):

    7. Input Parameters

    7.1. dns.nameservers

    7.1.1. Description

    The set of nameservers that will be authoritative for the TLD(s).

    This input parameter is an object where the object properties are the TLD names, and the values are objects. For these objects, the properties @@ -14783,7 +14898,7 @@

    Objective
    "epp.clid01" : "clid-01" }

    7.10.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.11. epp.clid02

    7.11.1. Description

    the username used for transfer tests

    +

    7.11. epp.clid02

    7.11.1. Description

    the username used for transfer tests

    7.11.2. Type

    string

    7.11.3. Schema

    • None specified.

    7.11.4. Example

    {
        "epp.clid02" : "clid-02"
     }
    @@ -14817,12 +14932,12 @@ 
    Objective
    "epp.hostName" : "epp.rsp.tech" }

    7.14.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.15. epp.pwd01

    7.15.1. Description

    the password used to log in to the EPP server

    +

    7.15. epp.pwd01

    7.15.1. Description

    the password used to log in to the EPP server

    7.15.2. Type

    string

    7.15.3. Schema

    • None specified.

    7.15.4. Example

    {
        "epp.pwd01" : "foo2bar"
     }
     

    7.15.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.16. epp.pwd02

    7.16.1. Description

    the password used for transfer tests

    +

    7.16. epp.pwd02

    7.16.1. Description

    the password used for transfer tests

    7.16.2. Type

    string

    7.16.3. Schema

    • None specified.

    7.16.4. Example

    {
        "epp.pwd02" : "foo3bar"
     }
    @@ -14844,7 +14959,7 @@ 
    Objective
    ] }

    7.17.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.18. epp.registeredNames

    7.18.1. Description

    An array of domain names that exist in the EPP server and which are +

    7.18. epp.registeredNames

    7.18.1. Description

    An array of domain names that exist in the EPP server and which are therefore unavailable for registration. The domains MUST NOT be under the sponsorship of the epp.clid01 or epp.clid02 registrars. The array MUST @@ -14879,7 +14994,7 @@

    Objective
    ] }

    7.19.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.20. epp.restoreReportRequired

    7.20.1. Description

    Whether the server requires submission of a restore report when a +

    7.20. epp.restoreReportRequired

    7.20.1. Description

    Whether the server requires submission of a restore report when a client attempts to restore a domain.

    If the value of general.gracePeriodsSupported is false, then this input parameter is ignored.

    @@ -14889,7 +15004,7 @@
    Objective
    "epp.restoreReportRequired" : false }

    7.20.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.21. epp.secDNSInterfaces

    7.21.1. Description

    Which of the interfaces defined in Section 4 of RFC 5910 the server +

    7.21. epp.secDNSInterfaces

    7.21.1. Description

    Which of the interfaces defined in Section 4 of RFC 5910 the server supports (either dsData or keyData).

    7.21.2. Type

    string

    7.21.3. Schema

     enum:
    @@ -14900,7 +15015,7 @@ 
    Objective
    "epp.secDNSInterfaces" : "dsData" }

    7.21.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.22. epp.serverIssuedClientCertificate01

    7.22.1. Description

    If the EPP server uses a private CA to issue client certificates, +

    7.22. epp.serverIssuedClientCertificate01

    7.22.1. Description

    If the EPP server uses a private CA to issue client certificates, then a certificate generated using the CSR provided in the epp.clientCSR may be provided using this parameter. This certificate will only be used in conjunction with the @@ -14911,7 +15026,7 @@

    Objective
    "epp.serverIssuedClientCertificate01" : "rst_test_client_cert.pem" }

    7.22.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.23. epp.serverIssuedClientCertificate02

    7.23.1. Description

    If the EPP server uses a private CA to issue client certificates, +

    7.23. epp.serverIssuedClientCertificate02

    7.23.1. Description

    If the EPP server uses a private CA to issue client certificates, then a certificate generated using the CSR provided in the epp.clientCSR may be provided using this parameter. This certificate will only be used in conjunction with the @@ -15189,467 +15304,478 @@

    Objective

    8.82. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE

    8.82.1. Severity

    ERROR

    8.82.2. Description

    TBA

    8.83. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.83.1. Severity

    ERROR

    8.83.2. Description

    TBA

    8.84. EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE

    8.84.1. Severity

    ERROR

    8.84.2. Description

    TBA

    -

    8.85. EPP_GENERIC_COMMAND_ERROR

    8.85.1. Severity

    ERROR

    8.85.2. Description

    The client received a 2400 error from the server.

    -

    8.86. EPP_GREETING_DOES_NOT_MATCH

    8.86.1. Severity

    ERROR

    8.86.2. Description

    TBA

    -

    8.87. EPP_GREETING_INVALID_LANG

    8.87.1. Severity

    ERROR

    8.87.2. Description

    The value of one or more of the <lang> elements in +

    8.85. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA

    8.85.1. Severity

    ERROR

    8.85.2. Description

    TBA

    +

    8.86. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_ATTRIBUTE

    8.86.1. Severity

    ERROR

    8.86.2. Description

    TBA

    +

    8.87. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_OBJECT

    8.87.1. Severity

    ERROR

    8.87.2. Description

    TBA

    +

    8.88. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT

    8.88.1. Severity

    ERROR

    8.88.2. Description

    TBA

    +

    8.89. EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE

    8.89.1. Severity

    ERROR

    8.89.2. Description

    TBA

    +

    8.90. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA

    8.90.1. Severity

    ERROR

    8.90.2. Description

    TBA

    +

    8.91. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_ATTRIBUTE

    8.91.1. Severity

    ERROR

    8.91.2. Description

    TBA

    +

    8.92. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_OBJECT

    8.92.1. Severity

    ERROR

    8.92.2. Description

    TBA

    +

    8.93. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_REGISTRANT

    8.93.1. Severity

    ERROR

    8.93.2. Description

    TBA

    +

    8.94. EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE

    8.94.1. Severity

    ERROR

    8.94.2. Description

    TBA

    +

    8.95. EPP_GENERIC_COMMAND_ERROR

    8.95.1. Severity

    ERROR

    8.95.2. Description

    The client received a 2400 error from the server.

    +

    8.96. EPP_GREETING_DOES_NOT_MATCH

    8.96.1. Severity

    ERROR

    8.96.2. Description

    TBA

    +

    8.97. EPP_GREETING_INVALID_LANG

    8.97.1. Severity

    ERROR

    8.97.2. Description

    The value of one or more of the <lang> elements in the <greeting> are invalid.

    -

    8.88. EPP_GREETING_MISSING_EXTURI

    8.88.1. Severity

    ERROR

    8.88.2. Description

    A mandatory extension namespace URI is missing.

    -

    8.89. EPP_GREETING_MISSING_OBJURI

    8.89.1. Severity

    ERROR

    8.89.2. Description

    A mandatory object namespace URI is missing.

    -

    8.90. EPP_GREETING_RECOMMENDED_EXTENSION_MISSING

    8.90.1. Severity

    WARNING

    8.90.2. Description

    The server does not include the namespace URI of a recommended +

    8.98. EPP_GREETING_MISSING_EXTURI

    8.98.1. Severity

    ERROR

    8.98.2. Description

    A mandatory extension namespace URI is missing.

    +

    8.99. EPP_GREETING_MISSING_OBJURI

    8.99.1. Severity

    ERROR

    8.99.2. Description

    A mandatory object namespace URI is missing.

    +

    8.100. EPP_GREETING_RECOMMENDED_EXTENSION_MISSING

    8.100.1. Severity

    WARNING

    8.100.2. Description

    The server does not include the namespace URI of a recommended extension in an <extURI> element of the <greeting> frame.

    -

    8.91. EPP_GREETING_SVDATE_INVALID

    8.91.1. Severity

    ERROR

    8.91.2. Description

    The value of the <svDate> element in the +

    8.101. EPP_GREETING_SVDATE_INVALID

    8.101.1. Severity

    ERROR

    8.101.2. Description

    The value of the <svDate> element in the <greeting> is invalid.

    -

    8.92. EPP_GREETING_SVID_INVALID

    8.92.1. Severity

    ERROR

    8.92.2. Description

    The value of the <svID> element in the +

    8.102. EPP_GREETING_SVID_INVALID

    8.102.1. Severity

    ERROR

    8.102.2. Description

    The value of the <svID> element in the <greeting> is invalid.

    -

    8.93. EPP_GREETING_UNEXPECTED_EXTURI

    8.93.1. Severity

    ERROR

    8.93.2. Description

    One or more of the <extRI> elements in the +

    8.103. EPP_GREETING_UNEXPECTED_EXTURI

    8.103.1. Severity

    ERROR

    8.103.2. Description

    One or more of the <extRI> elements in the <greeting> contain invalid namespace URIs.

    -

    8.94. EPP_GREETING_UNEXPECTED_OBJURI

    8.94.1. Severity

    ERROR

    8.94.2. Description

    One or more of the <objURI> elements in the +

    8.104. EPP_GREETING_UNEXPECTED_OBJURI

    8.104.1. Severity

    ERROR

    8.104.2. Description

    One or more of the <objURI> elements in the <greeting> contain invalid namespace URIs.

    -

    8.95. EPP_GREETING_VERSION_INVALID

    8.95.1. Severity

    ERROR

    8.95.2. Description

    The value of the <version> element in the +

    8.105. EPP_GREETING_VERSION_INVALID

    8.105.1. Severity

    ERROR

    8.105.2. Description

    The value of the <version> element in the <greeting> is invalid.

    -

    8.96. EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL

    8.96.1. Severity

    ERROR

    8.96.2. Description

    TBA.

    -

    8.97. EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL

    8.97.1. Severity

    ERROR

    8.97.2. Description

    TBA.

    -

    8.98. EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL

    8.98.1. Severity

    ERROR

    8.98.2. Description

    TBA.

    -

    8.99. EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.99.1. Severity

    ERROR

    8.99.2. Description

    TBA

    -

    8.100. EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.100.1. Severity

    ERROR

    8.100.2. Description

    TBA

    -

    8.101. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.101.1. Severity

    ERROR

    8.101.2. Description

    TBA

    -

    8.102. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.102.1. Severity

    ERROR

    8.102.2. Description

    TBA

    -

    8.103. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.103.1. Severity

    ERROR

    8.103.2. Description

    TBA

    -

    8.104. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.104.1. Severity

    ERROR

    8.104.2. Description

    TBA

    -

    8.105. EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.105.1. Severity

    ERROR

    8.105.2. Description

    TBA

    -

    8.106. EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.106.1. Severity

    ERROR

    8.106.2. Description

    TBA

    -

    8.107. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN

    8.107.1. Severity

    ERROR

    8.107.2. Description

    TBA

    -

    8.108. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_NONEXISTENT_DOMAIN

    8.108.1. Severity

    ERROR

    8.108.2. Description

    TBA

    -

    8.109. EPP_HOST_RENAME_SERVER_REJECTS_OUT_OF_BAILIWICK_NAME

    8.109.1. Severity

    ERROR

    8.109.2. Description

    TBA

    -

    8.110. EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME

    8.110.1. Severity

    ERROR

    8.110.2. Description

    TBA

    -

    8.111. EPP_HOST_UPDATE_AUTHZ_ERROR

    8.111.1. Severity

    ERROR

    8.111.2. Description

    TBA

    -

    8.112. EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.112.1. Severity

    ERROR

    8.112.2. Description

    TBA

    -

    8.113. EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.113.1. Severity

    ERROR

    8.113.2. Description

    TBA

    -

    8.114. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.114.1. Severity

    ERROR

    8.114.2. Description

    TBA

    -

    8.115. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.115.1. Severity

    ERROR

    8.115.2. Description

    TBA

    -

    8.116. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.116.1. Severity

    ERROR

    8.116.2. Description

    TBA

    -

    8.117. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.117.1. Severity

    ERROR

    8.117.2. Description

    TBA

    -

    8.118. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT

    8.118.1. Severity

    ERROR

    8.118.2. Description

    TBA

    -

    8.119. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT

    8.119.1. Severity

    ERROR

    8.119.2. Description

    TBA

    -

    8.120. EPP_LOGIN_ERROR

    8.120.1. Severity

    ERROR

    8.120.2. Description

    The client was unable to successfullt authenticate with the EPP +

    8.106. EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL

    8.106.1. Severity

    ERROR

    8.106.2. Description

    TBA.

    +

    8.107. EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL

    8.107.1. Severity

    ERROR

    8.107.2. Description

    TBA.

    +

    8.108. EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL

    8.108.1. Severity

    ERROR

    8.108.2. Description

    TBA.

    +

    8.109. EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.109.1. Severity

    ERROR

    8.109.2. Description

    TBA

    +

    8.110. EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.110.1. Severity

    ERROR

    8.110.2. Description

    TBA

    +

    8.111. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.111.1. Severity

    ERROR

    8.111.2. Description

    TBA

    +

    8.112. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.112.1. Severity

    ERROR

    8.112.2. Description

    TBA

    +

    8.113. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.113.1. Severity

    ERROR

    8.113.2. Description

    TBA

    +

    8.114. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.114.1. Severity

    ERROR

    8.114.2. Description

    TBA

    +

    8.115. EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.115.1. Severity

    ERROR

    8.115.2. Description

    TBA

    +

    8.116. EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.116.1. Severity

    ERROR

    8.116.2. Description

    TBA

    +

    8.117. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN

    8.117.1. Severity

    ERROR

    8.117.2. Description

    TBA

    +

    8.118. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_NONEXISTENT_DOMAIN

    8.118.1. Severity

    ERROR

    8.118.2. Description

    TBA

    +

    8.119. EPP_HOST_RENAME_SERVER_REJECTS_OUT_OF_BAILIWICK_NAME

    8.119.1. Severity

    ERROR

    8.119.2. Description

    TBA

    +

    8.120. EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME

    8.120.1. Severity

    ERROR

    8.120.2. Description

    TBA

    +

    8.121. EPP_HOST_UPDATE_AUTHZ_ERROR

    8.121.1. Severity

    ERROR

    8.121.2. Description

    TBA

    +

    8.122. EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.122.1. Severity

    ERROR

    8.122.2. Description

    TBA

    +

    8.123. EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.123.1. Severity

    ERROR

    8.123.2. Description

    TBA

    +

    8.124. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.124.1. Severity

    ERROR

    8.124.2. Description

    TBA

    +

    8.125. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.125.1. Severity

    ERROR

    8.125.2. Description

    TBA

    +

    8.126. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.126.1. Severity

    ERROR

    8.126.2. Description

    TBA

    +

    8.127. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.127.1. Severity

    ERROR

    8.127.2. Description

    TBA

    +

    8.128. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT

    8.128.1. Severity

    ERROR

    8.128.2. Description

    TBA

    +

    8.129. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT

    8.129.1. Severity

    ERROR

    8.129.2. Description

    TBA

    +

    8.130. EPP_LOGIN_ERROR

    8.130.1. Severity

    ERROR

    8.130.2. Description

    The client was unable to successfullt authenticate with the EPP server.

    -

    8.121. EPP_MISSING_AAAA_RECORDS

    8.121.1. Severity

    WARNING

    8.121.2. Description

    No AAAA record(s) were found for the EPP server +

    8.131. EPP_MISSING_AAAA_RECORDS

    8.131.1. Severity

    WARNING

    8.131.2. Description

    No AAAA record(s) were found for the EPP server hostname.

    -

    8.122. EPP_MISSING_A_RECORDS

    8.122.1. Severity

    ERROR

    8.122.2. Description

    No A record(s) were found for the EPP server +

    8.132. EPP_MISSING_A_RECORDS

    8.132.1. Severity

    ERROR

    8.132.2. Description

    No A record(s) were found for the EPP server hostname.

    -

    8.123. EPP_NO_GREETING_RECEIVED

    8.123.1. Severity

    ERROR

    8.123.2. Description

    No <greeting> was received after successful +

    8.133. EPP_NO_GREETING_RECEIVED

    8.133.1. Severity

    ERROR

    8.133.2. Description

    No <greeting> was received after successful connection.

    -

    8.124. EPP_OBJECT_SHOULD_EXIST

    8.124.1. Severity

    ERROR

    8.124.2. Description

    TBA

    -

    8.125. EPP_OBJECT_SHOULD_NOT_EXIST

    8.125.1. Severity

    ERROR

    8.125.2. Description

    TBA

    -

    8.126. EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.126.1. Severity

    ERROR

    8.126.2. Description

    TBA

    -

    8.127. EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.127.1. Severity

    ERROR

    8.127.2. Description

    TBA

    -

    8.128. EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE

    8.128.1. Severity

    ERROR

    8.128.2. Description

    TBA

    -

    8.129. EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD

    8.129.1. Severity

    ERROR

    8.129.2. Description

    TBA

    -

    8.130. EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE

    8.130.1. Severity

    ERROR

    8.130.2. Description

    TBA

    -

    8.131. EPP_SCHEMA_VALIDATION_ERROR

    8.131.1. Severity

    ERROR

    8.131.2. Description

    The response from the server failed schema validation.

    -

    8.132. EPP_SERVICE_PORT_UNREACHABLE

    8.132.1. Severity

    ERROR

    8.132.2. Description

    The EPP service port (tcp/700) could not be connected to.

    -

    8.133. EPP_TLS_BAD_CIPHER

    8.133.1. Severity

    ERROR

    8.133.2. Description

    The server uses an encryption cipher not recommended in RFC 9325.

    -

    8.134. EPP_TLS_CERTIFICATE_CHAIN_MISSING

    8.134.1. Severity

    ERROR

    8.134.2. Description

    One or more intermediate certificates are missing.

    -

    8.135. EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH

    8.135.1. Severity

    ERROR

    8.135.2. Description

    The hostname in the TLS certificate does not match the EPP server +

    8.134. EPP_OBJECT_SHOULD_EXIST

    8.134.1. Severity

    ERROR

    8.134.2. Description

    TBA

    +

    8.135. EPP_OBJECT_SHOULD_NOT_EXIST

    8.135.1. Severity

    ERROR

    8.135.2. Description

    TBA

    +

    8.136. EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.136.1. Severity

    ERROR

    8.136.2. Description

    TBA

    +

    8.137. EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.137.1. Severity

    ERROR

    8.137.2. Description

    TBA

    +

    8.138. EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE

    8.138.1. Severity

    ERROR

    8.138.2. Description

    TBA

    +

    8.139. EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD

    8.139.1. Severity

    ERROR

    8.139.2. Description

    TBA

    +

    8.140. EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE

    8.140.1. Severity

    ERROR

    8.140.2. Description

    TBA

    +

    8.141. EPP_SCHEMA_VALIDATION_ERROR

    8.141.1. Severity

    ERROR

    8.141.2. Description

    The response from the server failed schema validation.

    +

    8.142. EPP_SERVICE_PORT_NOT_CONSISTENT

    8.142.1. Severity

    ERROR

    8.142.2. Description

    TBA

    +

    8.143. EPP_SERVICE_PORT_UNREACHABLE

    8.143.1. Severity

    ERROR

    8.143.2. Description

    The EPP service port (tcp/700) could not be connected to.

    +

    8.144. EPP_TLS_BAD_CIPHER

    8.144.1. Severity

    ERROR

    8.144.2. Description

    The server uses an encryption cipher not recommended in RFC 9325.

    +

    8.145. EPP_TLS_CERTIFICATE_CHAIN_MISSING

    8.145.1. Severity

    ERROR

    8.145.2. Description

    One or more intermediate certificates are missing.

    +

    8.146. EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH

    8.146.1. Severity

    ERROR

    8.146.2. Description

    The hostname in the TLS certificate does not match the EPP server hostname.

    -

    8.136. EPP_TLS_CONNECTION_ERROR

    8.136.1. Severity

    ERROR

    8.136.2. Description

    There was an error during the TLS handshake while connecting to the +

    8.147. EPP_TLS_CONNECTION_ERROR

    8.147.1. Severity

    ERROR

    8.147.2. Description

    There was an error during the TLS handshake while connecting to the EPP server.

    -

    8.137. EPP_TLS_EXPIRED_CERTIFICATE

    8.137.1. Severity

    ERROR

    8.137.2. Description

    The TLS certificate presented by the EPP server has expired.

    -

    8.138. EPP_TLS_FORBIDDEN_PROTOCOL_SUPPORTED

    8.138.1. Severity

    ERROR

    8.138.2. Description

    The EPP server implements a forbidden protocol.

    -

    8.139. EPP_TLS_REQUIRED_PROTOCOL_NOT_SUPPORTED

    8.139.1. Severity

    ERROR

    8.139.2. Description

    The EPP server does not implement a required protocol.

    -

    8.140. EPP_TLS_UNTRUSTED_CERTIFICATE

    8.140.1. Severity

    ERROR

    8.140.2. Description

    The TLS certificate presented by the EPP server is not issued by a +

    8.148. EPP_TLS_EXPIRED_CERTIFICATE

    8.148.1. Severity

    ERROR

    8.148.2. Description

    The TLS certificate presented by the EPP server has expired.

    +

    8.149. EPP_TLS_FORBIDDEN_PROTOCOL_SUPPORTED

    8.149.1. Severity

    ERROR

    8.149.2. Description

    The EPP server implements a forbidden protocol.

    +

    8.150. EPP_TLS_REQUIRED_PROTOCOL_NOT_SUPPORTED

    8.150.1. Severity

    ERROR

    8.150.2. Description

    The EPP server does not implement a required protocol.

    +

    8.151. EPP_TLS_UNTRUSTED_CERTIFICATE

    8.151.1. Severity

    ERROR

    8.151.2. Description

    The TLS certificate presented by the EPP server is not issued by a trusted Certificate Authority.

    -

    8.141. EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.141.1. Severity

    ERROR

    8.141.2. Description

    TBA

    -

    8.142. EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET

    8.142.1. Severity

    ERROR

    8.142.2. Description

    TBA

    -

    8.143. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.143.1. Severity

    ERROR

    8.143.2. Description

    TBA

    -

    8.144. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_STATUS_CODE

    8.144.1. Severity

    ERROR

    8.144.2. Description

    TBA

    -

    8.145. EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.145.1. Severity

    ERROR

    8.145.2. Description

    TBA

    -

    8.146. EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.146.1. Severity

    ERROR

    8.146.2. Description

    TBA

    -

    8.147. EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO

    8.147.1. Severity

    ERROR

    8.147.2. Description

    TBA

    -

    8.148. EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO

    8.148.1. Severity

    ERROR

    8.148.2. Description

    TBA

    -

    8.149. EPP_TRANSFER_SERVER_ACCEPTS_INVALID_PERIOD

    8.149.1. Severity

    ERROR

    8.149.2. Description

    TBA

    -

    8.150. EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER

    8.150.1. Severity

    ERROR

    8.150.2. Description

    TBA

    -

    8.151. EPP_UNEXPECTED_COMMAND_FAILURE

    8.151.1. Severity

    ERROR

    8.151.2. Description

    TBA

    -

    8.152. EPP_UNEXPECTED_COMMAND_SUCCESS

    8.152.1. Severity

    ERROR

    8.152.2. Description

    TBA

    -

    8.153. EPP_XML_PARSE_ERROR

    8.153.1. Severity

    ERROR

    8.153.2. Description

    The XML response from the server could not be parsed.

    -

    8.154. IDN_SERVER_ACCEPTS_INVALID_LABEL

    8.154.1. Severity

    ERROR

    8.154.2. Description

    TBA.

    -

    8.155. IDN_SERVER_REJECTS_VALID_LABEL

    8.155.1. Severity

    ERROR

    8.155.2. Description

    TBA.

    -

    8.156. IDN_VARIANT_LABEL_NOT_BLOCKED

    8.156.1. Severity

    ERROR

    8.156.2. Description

    TBA.

    -

    8.157. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_FROM_INCORRECT_REGISTRAR

    8.157.1. Severity

    ERROR

    8.157.2. Description

    TBA.

    -

    8.158. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_WITH_INCORRECT_REGISTRANT

    8.158.1. Severity

    ERROR

    8.158.2. Description

    TBA.

    -

    8.159. INTEGRATION_DNS_ANSWER_IS_INCORRECT

    8.159.1. Severity

    ERROR

    8.159.2. Description

    TBA.

    -

    8.160. INTEGRATION_DNS_QUERY_FAILED

    8.160.1. Severity

    ERROR

    8.160.2. Description

    TBA.

    -

    8.161. INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS

    8.161.1. Severity

    ERROR

    8.161.2. Description

    TBA.

    -

    8.162. INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP

    8.162.1. Severity

    ERROR

    8.162.2. Description

    TBA.

    -

    8.163. INTEGRATION_RDAP_REQUEST_FAILED

    8.163.1. Severity

    ERROR

    8.163.2. Description

    TBA.

    -

    8.164. INTEGRATION_RDE_DEADLINE_MISSED

    8.164.1. Severity

    ERROR

    8.164.2. Description

    TBA.

    -

    8.165. INTEGRATION_RDE_MISSING_OBJECTS

    8.165.1. Severity

    ERROR

    8.165.2. Description

    TBA.

    -

    8.166. INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR

    8.166.1. Severity

    ERROR

    8.166.2. Description

    TBA.

    -

    8.167. INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE

    8.167.1. Severity

    ERROR

    8.167.2. Description

    TBA.

    -

    8.168. RDE_CONTACT_HAS_INVALID_CC

    8.168.1. Severity

    ERROR

    8.168.2. Description

    TBA.

    -

    8.169. RDE_CONTACT_HAS_INVALID_EMAIL

    8.169.1. Severity

    ERROR

    8.169.2. Description

    TBA.

    -

    8.170. RDE_CONTACT_HAS_INVALID_ROID

    8.170.1. Severity

    ERROR

    8.170.2. Description

    TBA.

    -

    8.171. RDE_CONTACT_HAS_MULTIPLE_POSTALINFO_TYPES

    8.171.1. Severity

    ERROR

    8.171.2. Description

    TBA.

    -

    8.172. RDE_CONTACT_HAS_NON_UNIQUE_ID

    8.172.1. Severity

    ERROR

    8.172.2. Description

    TBA.

    -

    8.173. RDE_CONTACT_HAS_UNKNOWN_ACRR

    8.173.1. Severity

    ERROR

    8.173.2. Description

    TBA.

    -

    8.174. RDE_CONTACT_HAS_UNKNOWN_CLID

    8.174.1. Severity

    ERROR

    8.174.2. Description

    TBA.

    -

    8.175. RDE_CONTACT_HAS_UNKNOWN_CRRR

    8.175.1. Severity

    ERROR

    8.175.2. Description

    TBA.

    -

    8.176. RDE_CONTACT_HAS_UNKNOWN_RERR

    8.176.1. Severity

    ERROR

    8.176.2. Description

    TBA.

    -

    8.177. RDE_CONTACT_HAS_UNKNOWN_UPRR

    8.177.1. Severity

    ERROR

    8.177.2. Description

    TBA.

    -

    8.178. RDE_DECRYPTION_FAILED

    8.178.1. Severity

    ERROR

    8.178.2. Description

    TBA.

    -

    8.179. RDE_DOMAIN_HAS_INVALID_CLID

    8.179.1. Severity

    ERROR

    8.179.2. Description

    TBA.

    -

    8.180. RDE_DOMAIN_HAS_INVALID_CRDATE

    8.180.1. Severity

    ERROR

    8.180.2. Description

    TBA.

    -

    8.181. RDE_DOMAIN_HAS_INVALID_EXDATE

    8.181.1. Severity

    ERROR

    8.181.2. Description

    TBA.

    -

    8.182. RDE_DOMAIN_HAS_INVALID_NAME

    8.182.1. Severity

    ERROR

    8.182.2. Description

    TBA.

    -

    8.183. RDE_DOMAIN_HAS_INVALID_REGISTRANT

    8.183.1. Severity

    ERROR

    8.183.2. Description

    TBA.

    -

    8.184. RDE_DOMAIN_HAS_INVALID_ROID

    8.184.1. Severity

    ERROR

    8.184.2. Description

    TBA.

    -

    8.185. RDE_DOMAIN_HAS_INVALID_STATUS

    8.185.1. Severity

    ERROR

    8.185.2. Description

    TBA.

    -

    8.186. RDE_DOMAIN_HAS_MISSING_CLID

    8.186.1. Severity

    ERROR

    8.186.2. Description

    TBA.

    -

    8.187. RDE_DOMAIN_HAS_MISSING_CRDATE

    8.187.1. Severity

    ERROR

    8.187.2. Description

    TBA.

    -

    8.188. RDE_DOMAIN_HAS_MISSING_EXDATE

    8.188.1. Severity

    ERROR

    8.188.2. Description

    TBA.

    -

    8.189. RDE_DOMAIN_HAS_MISSING_NAME

    8.189.1. Severity

    ERROR

    8.189.2. Description

    TBA.

    -

    8.190. RDE_DOMAIN_HAS_MISSING_REGISTRANT

    8.190.1. Severity

    ERROR

    8.190.2. Description

    TBA.

    -

    8.191. RDE_DOMAIN_HAS_MISSING_ROID

    8.191.1. Severity

    ERROR

    8.191.2. Description

    TBA.

    -

    8.192. RDE_DOMAIN_HAS_MISSING_STATUS

    8.192.1. Severity

    ERROR

    8.192.2. Description

    TBA.

    -

    8.193. RDE_GREETING_DOES_NOT_MATCH

    8.193.1. Severity

    ERROR

    8.193.2. Description

    TBA.

    -

    8.194. RDE_HOST_HAS_INVALID_CLID

    8.194.1. Severity

    ERROR

    8.194.2. Description

    TBA.

    -

    8.195. RDE_HOST_HAS_INVALID_IP_ADDRESS

    8.195.1. Severity

    ERROR

    8.195.2. Description

    TBA.

    -

    8.196. RDE_HOST_HAS_INVALID_NAME

    8.196.1. Severity

    ERROR

    8.196.2. Description

    TBA.

    -

    8.197. RDE_HOST_HAS_INVALID_ROID

    8.197.1. Severity

    ERROR

    8.197.2. Description

    TBA.

    -

    8.198. RDE_HOST_HAS_INVALID_STATUS

    8.198.1. Severity

    ERROR

    8.198.2. Description

    TBA.

    -

    8.199. RDE_HOST_HAS_MISSING_CLID

    8.199.1. Severity

    ERROR

    8.199.2. Description

    TBA.

    -

    8.200. RDE_HOST_HAS_MISSING_IP_ADDRESS

    8.200.1. Severity

    ERROR

    8.200.2. Description

    TBA.

    -

    8.201. RDE_HOST_HAS_MISSING_NAME

    8.201.1. Severity

    ERROR

    8.201.2. Description

    TBA.

    -

    8.202. RDE_HOST_HAS_MISSING_ROID

    8.202.1. Severity

    ERROR

    8.202.2. Description

    TBA.

    -

    8.203. RDE_HOST_HAS_MISSING_STATUS

    8.203.1. Severity

    ERROR

    8.203.2. Description

    TBA.

    -

    8.204. RDE_IDN_OBJECT_INVALID

    8.204.1. Severity

    ERROR

    8.204.2. Description

    TBA.

    -

    8.205. RDE_IDN_OBJECT_MISSING

    8.205.1. Severity

    ERROR

    8.205.2. Description

    TBA.

    -

    8.206. RDE_IDN_OBJECT_UNEXPECTED

    8.206.1. Severity

    ERROR

    8.206.2. Description

    TBA.

    -

    8.207. RDE_INVALID_CSV

    8.207.1. Severity

    ERROR

    8.207.2. Description

    TBA.

    -

    8.208. RDE_INVALID_FILENAME

    8.208.1. Severity

    ERROR

    8.208.2. Description

    TBA.

    -

    8.209. RDE_INVALID_SIGNATURE

    8.209.1. Severity

    ERROR

    8.209.2. Description

    TBA.

    -

    8.210. RDE_INVALID_XML

    8.210.1. Severity

    ERROR

    8.210.2. Description

    TBA.

    -

    8.211. RDE_MISSING_OBJECT_URI

    8.211.1. Severity

    ERROR

    8.211.2. Description

    TBA.

    -

    8.212. RDE_MIXED_TYPES

    8.212.1. Severity

    ERROR

    8.212.2. Description

    TBA.

    -

    8.213. RDE_NNDN_CONFLICTS_WITH_DOMAIN

    8.213.1. Severity

    ERROR

    8.213.2. Description

    TBA.

    -

    8.214. RDE_OBJECT_COUNT_MISMATCH

    8.214.1. Severity

    ERROR

    8.214.2. Description

    TBA.

    -

    8.215. RDE_POLICY_OBJECT_INVALID

    8.215.1. Severity

    ERROR

    8.215.2. Description

    TBA.

    -

    8.216. RDE_POLICY_OBJECT_MISSING

    8.216.1. Severity

    ERROR

    8.216.2. Description

    TBA.

    -

    8.217. RDE_POLICY_OBJECT_MISSING_OBJECTS

    8.217.1. Severity

    ERROR

    8.217.2. Description

    TBA.

    -

    8.218. RDE_POLICY_OBJECT_UNEXPECTED_OBJECTS

    8.218.1. Severity

    ERROR

    8.218.2. Description

    TBA.

    -

    8.219. RDE_REGISTRAR_HAS_INVALID_GURID

    8.219.1. Severity

    ERROR

    8.219.2. Description

    TBA.

    -

    8.220. RDE_REGISTRAR_HAS_INVALID_ID

    8.220.1. Severity

    ERROR

    8.220.2. Description

    TBA.

    -

    8.221. RDE_REGISTRAR_HAS_INVALID_NAME

    8.221.1. Severity

    ERROR

    8.221.2. Description

    TBA.

    -

    8.222. RDE_REGISTRAR_HAS_MISSING_GURID

    8.222.1. Severity

    ERROR

    8.222.2. Description

    TBA.

    -

    8.223. RDE_REGISTRAR_HAS_MISSING_ID

    8.223.1. Severity

    ERROR

    8.223.2. Description

    TBA.

    -

    8.224. RDE_REGISTRAR_HAS_MISSING_NAME

    8.224.1. Severity

    ERROR

    8.224.2. Description

    TBA.

    -

    8.225. RDE_SCHEMA_VALIDATION_ERROR

    8.225.1. Severity

    ERROR

    8.225.2. Description

    TBA.

    -

    8.226. RDE_UNEXPECTED_OBJECT_URI

    8.226.1. Severity

    ERROR

    8.226.2. Description

    TBA.

    -

    8.227. RDE_XML_PARSE_ERROR

    8.227.1. Severity

    ERROR

    8.227.2. Description

    TBA.

    -

    8.228. RPMS_MISSING_CLAIMS_KEY

    8.228.1. Severity

    ERROR

    8.228.2. Description

    TBA.

    -

    8.229. RPMS_SUNRISE_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.229.1. Severity

    ERROR

    8.229.2. Description

    TBA.

    -

    8.230. RPMS_SUNRISE_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.230.1. Severity

    ERROR

    8.230.2. Description

    TBA.

    -

    8.231. RPMS_SUNRISE_CREATE_UNEXPECTED_FAILURE_USING_VALID_SMD

    8.231.1. Severity

    ERROR

    8.231.2. Description

    TBA.

    -

    8.232. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_SMD

    8.232.1. Severity

    ERROR

    8.232.2. Description

    TBA.

    -

    8.233. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_REVOKED_SMD

    8.233.1. Severity

    ERROR

    8.233.2. Description

    TBA.

    -

    8.234. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_SMD_WITH_REVOKED_SIGNATURE

    8.234.1. Severity

    ERROR

    8.234.2. Description

    TBA.

    -

    8.235. RPMS_TRADEMARK_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.235.1. Severity

    ERROR

    8.235.2. Description

    TBA.

    -

    8.236. RPMS_TRADEMARK_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.236.1. Severity

    ERROR

    8.236.2. Description

    TBA.

    -

    8.237. RPMS_TRADEMARK_CREATE_UNEXPECTED_FAILURE_USING_VALID_CLAIM_KEY

    8.237.1. Severity

    ERROR

    8.237.2. Description

    TBA.

    -

    8.238. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_ACCEPTANCE_DATE

    8.238.1. Severity

    ERROR

    8.238.2. Description

    TBA.

    -

    8.239. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_CLAIM_KEY

    8.239.1. Severity

    ERROR

    8.239.2. Description

    TBA.

    -

    8.240. RPMS_UNEXPECTED_CLAIMS_KEY

    8.240.1. Severity

    ERROR

    8.240.2. Description

    TBA.

    -

    8.241. SRSGW_CONTACT_CREATE_FAILED

    8.241.1. Severity

    ERROR

    8.241.2. Description

    TBA.

    -

    8.242. SRSGW_CONTACT_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.242.1. Severity

    ERROR

    8.242.2. Description

    TBA.

    -

    8.243. SRSGW_CONTACT_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.243.1. Severity

    ERROR

    8.243.2. Description

    TBA.

    -

    8.244. SRSGW_DOMAIN_CREATE_FAILED

    8.244.1. Severity

    ERROR

    8.244.2. Description

    TBA.

    -

    8.245. SRSGW_DOMAIN_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.245.1. Severity

    ERROR

    8.245.2. Description

    TBA.

    -

    8.246. SRSGW_DOMAIN_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.246.1. Severity

    ERROR

    8.246.2. Description

    TBA.

    -

    8.247. SRSGW_DOMAIN_DELETE_DOMAIN_NOT_PENDINGDELETE

    8.247.1. Severity

    ERROR

    8.247.2. Description

    TBA.

    -

    8.248. SRSGW_DOMAIN_DELETE_FAILED

    8.248.1. Severity

    ERROR

    8.248.2. Description

    TBA.

    -

    8.249. SRSGW_DOMAIN_DELETE_RGP_STATUS_NOT_PENDINGDELETERESTORABLE

    8.249.1. Severity

    ERROR

    8.249.2. Description

    TBA.

    -

    8.250. SRSGW_DOMAIN_RENEW_FAILED

    8.250.1. Severity

    ERROR

    8.250.2. Description

    TBA.

    -

    8.251. SRSGW_DOMAIN_RENEW_OBJECT_HAS_INVALID_EXDATE

    8.251.1. Severity

    ERROR

    8.251.2. Description

    TBA.

    -

    8.252. SRSGW_DOMAIN_RENEW_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.252.1. Severity

    ERROR

    8.252.2. Description

    TBA.

    -

    8.253. SRSGW_DOMAIN_TRANSFER_APPROVAL_FAILED

    8.253.1. Severity

    ERROR

    8.253.2. Description

    TBA.

    -

    8.254. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_HAS_INCORRECT_CLID

    8.254.1. Severity

    ERROR

    8.254.2. Description

    TBA.

    -

    8.255. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.255.1. Severity

    ERROR

    8.255.2. Description

    TBA.

    -

    8.256. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_STILL_PENDING_TRANSFER

    8.256.1. Severity

    ERROR

    8.256.2. Description

    TBA.

    -

    8.257. SRSGW_DOMAIN_TRANSFER_REQUEST_FAILED

    8.257.1. Severity

    ERROR

    8.257.2. Description

    TBA.

    -

    8.258. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_HAS_INCORRECT_CLID

    8.258.1. Severity

    ERROR

    8.258.2. Description

    TBA.

    -

    8.259. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_PENDING_TRANSFER

    8.259.1. Severity

    ERROR

    8.259.2. Description

    TBA.

    -

    8.260. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.260.1. Severity

    ERROR

    8.260.2. Description

    TBA.

    -

    8.261. SRSGW_EPP_DNS_RESOLUTION_ERROR

    8.261.1. Severity

    ERROR

    8.261.2. Description

    TBA.

    -

    8.262. SRSGW_EPP_GENERIC_COMMAND_ERROR

    8.262.1. Severity

    ERROR

    8.262.2. Description

    TBA.

    -

    8.263. SRSGW_EPP_LOGIN_ERROR

    8.263.1. Severity

    ERROR

    8.263.2. Description

    TBA.

    -

    8.264. SRSGW_EPP_OBJECT_SHOULD_EXIST

    8.264.1. Severity

    ERROR

    8.264.2. Description

    TBA.

    -

    8.265. SRSGW_EPP_OBJECT_SHOULD_NOT_EXIST

    8.265.1. Severity

    ERROR

    8.265.2. Description

    TBA.

    -

    8.266. SRSGW_EPP_SCHEMA_VALIDATION_ERROR

    8.266.1. Severity

    ERROR

    8.266.2. Description

    TBA.

    -

    8.267. SRSGW_EPP_SERVICE_PORT_UNREACHABLE

    8.267.1. Severity

    ERROR

    8.267.2. Description

    TBA.

    -

    8.268. SRSGW_EPP_TLS_CONNECTION_ERROR

    8.268.1. Severity

    ERROR

    8.268.2. Description

    TBA.

    -

    8.269. SRSGW_EPP_UNEXPECTED_COMMAND_FAILURE

    8.269.1. Severity

    ERROR

    8.269.2. Description

    TBA.

    -

    8.270. SRSGW_EPP_UNEXPECTED_COMMAND_SUCCESS

    8.270.1. Severity

    ERROR

    8.270.2. Description

    TBA.

    -

    8.271. SRSGW_EPP_XML_PARSE_ERROR

    8.271.1. Severity

    ERROR

    8.271.2. Description

    TBA.

    -

    8.272. SRSGW_HOST_CREATE_FAILED

    8.272.1. Severity

    ERROR

    8.272.2. Description

    TBA.

    -

    8.273. SRSGW_HOST_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.273.1. Severity

    ERROR

    8.273.2. Description

    TBA.

    -

    8.274. SRSGW_HOST_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.274.1. Severity

    ERROR

    8.274.2. Description

    TBA.

    -

    8.275. ZM_AAAA_BAD_RDATA

    8.275.1. Severity

    ERROR

    8.275.2. Description

    Not available.

    -

    8.276. ZM_AAAA_QUERY_DROPPED

    8.276.1. Severity

    ERROR

    8.276.2. Description

    Not available.

    -

    8.277. ZM_AAAA_UNEXPECTED_RCODE

    8.277.1. Severity

    ERROR

    8.277.2. Description

    Not available.

    -

    8.278. ZM_ALGORITHM_DEPRECATED

    8.278.1. Severity

    ERROR

    8.278.2. Description

    Not available.

    -

    8.279. ZM_ALGORITHM_NOT_RECOMMENDED

    8.279.1. Severity

    WARNING

    8.279.2. Description

    Not available.

    -

    8.280. ZM_ALGORITHM_NOT_ZONE_SIGN

    8.280.1. Severity

    ERROR

    8.280.2. Description

    Not available.

    -

    8.281. ZM_ALGORITHM_PRIVATE

    8.281.1. Severity

    ERROR

    8.281.2. Description

    Not available.

    -

    8.282. ZM_ALGORITHM_RESERVED

    8.282.1. Severity

    ERROR

    8.282.2. Description

    Not available.

    -

    8.283. ZM_ALGORITHM_UNASSIGNED

    8.283.1. Severity

    ERROR

    8.283.2. Description

    Not available.

    -

    8.284. ZM_A_UNEXPECTED_RCODE

    8.284.1. Severity

    ERROR

    8.284.2. Description

    Not available.

    -

    8.285. ZM_BREAKS_ON_EDNS

    8.285.1. Severity

    ERROR

    8.285.2. Description

    Not available.

    -

    8.286. ZM_CHILD_NS_FAILED

    8.286.1. Severity

    ERROR

    8.286.2. Description

    Not available.

    -

    8.287. ZM_CHILD_NS_SAME_IP

    8.287.1. Severity

    ERROR

    8.287.2. Description

    Not available.

    -

    8.288. ZM_CHILD_ZONE_LAME

    8.288.1. Severity

    ERROR

    8.288.2. Description

    Not available.

    -

    8.289. ZM_CN01_MISSING_NS_RECORD_UDP

    8.289.1. Severity

    ERROR

    8.289.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the +

    8.152. EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.152.1. Severity

    ERROR

    8.152.2. Description

    TBA

    +

    8.153. EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET

    8.153.1. Severity

    ERROR

    8.153.2. Description

    TBA

    +

    8.154. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.154.1. Severity

    ERROR

    8.154.2. Description

    TBA

    +

    8.155. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_STATUS_CODE

    8.155.1. Severity

    ERROR

    8.155.2. Description

    TBA

    +

    8.156. EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.156.1. Severity

    ERROR

    8.156.2. Description

    TBA

    +

    8.157. EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.157.1. Severity

    ERROR

    8.157.2. Description

    TBA

    +

    8.158. EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO

    8.158.1. Severity

    ERROR

    8.158.2. Description

    TBA

    +

    8.159. EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO

    8.159.1. Severity

    ERROR

    8.159.2. Description

    TBA

    +

    8.160. EPP_TRANSFER_SERVER_ACCEPTS_INVALID_PERIOD

    8.160.1. Severity

    ERROR

    8.160.2. Description

    TBA

    +

    8.161. EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER

    8.161.1. Severity

    ERROR

    8.161.2. Description

    TBA

    +

    8.162. EPP_UNEXPECTED_COMMAND_FAILURE

    8.162.1. Severity

    ERROR

    8.162.2. Description

    TBA

    +

    8.163. EPP_UNEXPECTED_COMMAND_SUCCESS

    8.163.1. Severity

    ERROR

    8.163.2. Description

    TBA

    +

    8.164. EPP_XML_PARSE_ERROR

    8.164.1. Severity

    ERROR

    8.164.2. Description

    The XML response from the server could not be parsed.

    +

    8.165. IDN_SERVER_ACCEPTS_INVALID_LABEL

    8.165.1. Severity

    ERROR

    8.165.2. Description

    TBA.

    +

    8.166. IDN_SERVER_REJECTS_VALID_LABEL

    8.166.1. Severity

    ERROR

    8.166.2. Description

    TBA.

    +

    8.167. IDN_VARIANT_LABEL_NOT_BLOCKED

    8.167.1. Severity

    ERROR

    8.167.2. Description

    TBA.

    +

    8.168. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_FROM_INCORRECT_REGISTRAR

    8.168.1. Severity

    ERROR

    8.168.2. Description

    TBA.

    +

    8.169. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_WITH_INCORRECT_REGISTRANT

    8.169.1. Severity

    ERROR

    8.169.2. Description

    TBA.

    +

    8.170. INTEGRATION_DNS_ANSWER_IS_INCORRECT

    8.170.1. Severity

    ERROR

    8.170.2. Description

    TBA.

    +

    8.171. INTEGRATION_DNS_QUERY_FAILED

    8.171.1. Severity

    ERROR

    8.171.2. Description

    TBA.

    +

    8.172. INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS

    8.172.1. Severity

    ERROR

    8.172.2. Description

    TBA.

    +

    8.173. INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP

    8.173.1. Severity

    ERROR

    8.173.2. Description

    TBA.

    +

    8.174. INTEGRATION_RDAP_REQUEST_FAILED

    8.174.1. Severity

    ERROR

    8.174.2. Description

    TBA.

    +

    8.175. INTEGRATION_RDE_DEADLINE_MISSED

    8.175.1. Severity

    ERROR

    8.175.2. Description

    TBA.

    +

    8.176. INTEGRATION_RDE_MISSING_OBJECTS

    8.176.1. Severity

    ERROR

    8.176.2. Description

    TBA.

    +

    8.177. INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR

    8.177.1. Severity

    ERROR

    8.177.2. Description

    TBA.

    +

    8.178. INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE

    8.178.1. Severity

    ERROR

    8.178.2. Description

    TBA.

    +

    8.179. RDE_CONTACT_HAS_INVALID_CC

    8.179.1. Severity

    ERROR

    8.179.2. Description

    TBA.

    +

    8.180. RDE_CONTACT_HAS_INVALID_EMAIL

    8.180.1. Severity

    ERROR

    8.180.2. Description

    TBA.

    +

    8.181. RDE_CONTACT_HAS_INVALID_ROID

    8.181.1. Severity

    ERROR

    8.181.2. Description

    TBA.

    +

    8.182. RDE_CONTACT_HAS_MULTIPLE_POSTALINFO_TYPES

    8.182.1. Severity

    ERROR

    8.182.2. Description

    TBA.

    +

    8.183. RDE_CONTACT_HAS_NON_UNIQUE_ID

    8.183.1. Severity

    ERROR

    8.183.2. Description

    TBA.

    +

    8.184. RDE_CONTACT_HAS_UNKNOWN_ACRR

    8.184.1. Severity

    ERROR

    8.184.2. Description

    TBA.

    +

    8.185. RDE_CONTACT_HAS_UNKNOWN_CLID

    8.185.1. Severity

    ERROR

    8.185.2. Description

    TBA.

    +

    8.186. RDE_CONTACT_HAS_UNKNOWN_CRRR

    8.186.1. Severity

    ERROR

    8.186.2. Description

    TBA.

    +

    8.187. RDE_CONTACT_HAS_UNKNOWN_RERR

    8.187.1. Severity

    ERROR

    8.187.2. Description

    TBA.

    +

    8.188. RDE_CONTACT_HAS_UNKNOWN_UPRR

    8.188.1. Severity

    ERROR

    8.188.2. Description

    TBA.

    +

    8.189. RDE_DECRYPTION_FAILED

    8.189.1. Severity

    ERROR

    8.189.2. Description

    TBA.

    +

    8.190. RDE_DOMAIN_HAS_INVALID_CLID

    8.190.1. Severity

    ERROR

    8.190.2. Description

    TBA.

    +

    8.191. RDE_DOMAIN_HAS_INVALID_CRDATE

    8.191.1. Severity

    ERROR

    8.191.2. Description

    TBA.

    +

    8.192. RDE_DOMAIN_HAS_INVALID_EXDATE

    8.192.1. Severity

    ERROR

    8.192.2. Description

    TBA.

    +

    8.193. RDE_DOMAIN_HAS_INVALID_NAME

    8.193.1. Severity

    ERROR

    8.193.2. Description

    TBA.

    +

    8.194. RDE_DOMAIN_HAS_INVALID_REGISTRANT

    8.194.1. Severity

    ERROR

    8.194.2. Description

    TBA.

    +

    8.195. RDE_DOMAIN_HAS_INVALID_ROID

    8.195.1. Severity

    ERROR

    8.195.2. Description

    TBA.

    +

    8.196. RDE_DOMAIN_HAS_INVALID_STATUS

    8.196.1. Severity

    ERROR

    8.196.2. Description

    TBA.

    +

    8.197. RDE_DOMAIN_HAS_MISSING_CLID

    8.197.1. Severity

    ERROR

    8.197.2. Description

    TBA.

    +

    8.198. RDE_DOMAIN_HAS_MISSING_CRDATE

    8.198.1. Severity

    ERROR

    8.198.2. Description

    TBA.

    +

    8.199. RDE_DOMAIN_HAS_MISSING_EXDATE

    8.199.1. Severity

    ERROR

    8.199.2. Description

    TBA.

    +

    8.200. RDE_DOMAIN_HAS_MISSING_NAME

    8.200.1. Severity

    ERROR

    8.200.2. Description

    TBA.

    +

    8.201. RDE_DOMAIN_HAS_MISSING_REGISTRANT

    8.201.1. Severity

    ERROR

    8.201.2. Description

    TBA.

    +

    8.202. RDE_DOMAIN_HAS_MISSING_ROID

    8.202.1. Severity

    ERROR

    8.202.2. Description

    TBA.

    +

    8.203. RDE_DOMAIN_HAS_MISSING_STATUS

    8.203.1. Severity

    ERROR

    8.203.2. Description

    TBA.

    +

    8.204. RDE_GREETING_DOES_NOT_MATCH

    8.204.1. Severity

    ERROR

    8.204.2. Description

    TBA.

    +

    8.205. RDE_HOST_HAS_INVALID_CLID

    8.205.1. Severity

    ERROR

    8.205.2. Description

    TBA.

    +

    8.206. RDE_HOST_HAS_INVALID_IP_ADDRESS

    8.206.1. Severity

    ERROR

    8.206.2. Description

    TBA.

    +

    8.207. RDE_HOST_HAS_INVALID_NAME

    8.207.1. Severity

    ERROR

    8.207.2. Description

    TBA.

    +

    8.208. RDE_HOST_HAS_INVALID_ROID

    8.208.1. Severity

    ERROR

    8.208.2. Description

    TBA.

    +

    8.209. RDE_HOST_HAS_INVALID_STATUS

    8.209.1. Severity

    ERROR

    8.209.2. Description

    TBA.

    +

    8.210. RDE_HOST_HAS_MISSING_CLID

    8.210.1. Severity

    ERROR

    8.210.2. Description

    TBA.

    +

    8.211. RDE_HOST_HAS_MISSING_IP_ADDRESS

    8.211.1. Severity

    ERROR

    8.211.2. Description

    TBA.

    +

    8.212. RDE_HOST_HAS_MISSING_NAME

    8.212.1. Severity

    ERROR

    8.212.2. Description

    TBA.

    +

    8.213. RDE_HOST_HAS_MISSING_ROID

    8.213.1. Severity

    ERROR

    8.213.2. Description

    TBA.

    +

    8.214. RDE_HOST_HAS_MISSING_STATUS

    8.214.1. Severity

    ERROR

    8.214.2. Description

    TBA.

    +

    8.215. RDE_IDN_OBJECT_INVALID

    8.215.1. Severity

    ERROR

    8.215.2. Description

    TBA.

    +

    8.216. RDE_IDN_OBJECT_MISSING

    8.216.1. Severity

    ERROR

    8.216.2. Description

    TBA.

    +

    8.217. RDE_IDN_OBJECT_UNEXPECTED

    8.217.1. Severity

    ERROR

    8.217.2. Description

    TBA.

    +

    8.218. RDE_INVALID_CSV

    8.218.1. Severity

    ERROR

    8.218.2. Description

    TBA.

    +

    8.219. RDE_INVALID_FILENAME

    8.219.1. Severity

    ERROR

    8.219.2. Description

    TBA.

    +

    8.220. RDE_INVALID_SIGNATURE

    8.220.1. Severity

    ERROR

    8.220.2. Description

    TBA.

    +

    8.221. RDE_INVALID_XML

    8.221.1. Severity

    ERROR

    8.221.2. Description

    TBA.

    +

    8.222. RDE_MISSING_OBJECT_URI

    8.222.1. Severity

    ERROR

    8.222.2. Description

    TBA.

    +

    8.223. RDE_MIXED_TYPES

    8.223.1. Severity

    ERROR

    8.223.2. Description

    TBA.

    +

    8.224. RDE_NNDN_CONFLICTS_WITH_DOMAIN

    8.224.1. Severity

    ERROR

    8.224.2. Description

    TBA.

    +

    8.225. RDE_OBJECT_COUNT_MISMATCH

    8.225.1. Severity

    ERROR

    8.225.2. Description

    TBA.

    +

    8.226. RDE_POLICY_OBJECT_INVALID

    8.226.1. Severity

    ERROR

    8.226.2. Description

    TBA.

    +

    8.227. RDE_POLICY_OBJECT_MISSING

    8.227.1. Severity

    ERROR

    8.227.2. Description

    TBA.

    +

    8.228. RDE_POLICY_OBJECT_MISSING_OBJECTS

    8.228.1. Severity

    ERROR

    8.228.2. Description

    TBA.

    +

    8.229. RDE_POLICY_OBJECT_UNEXPECTED_OBJECTS

    8.229.1. Severity

    ERROR

    8.229.2. Description

    TBA.

    +

    8.230. RDE_REGISTRAR_HAS_INVALID_GURID

    8.230.1. Severity

    ERROR

    8.230.2. Description

    TBA.

    +

    8.231. RDE_REGISTRAR_HAS_INVALID_ID

    8.231.1. Severity

    ERROR

    8.231.2. Description

    TBA.

    +

    8.232. RDE_REGISTRAR_HAS_INVALID_NAME

    8.232.1. Severity

    ERROR

    8.232.2. Description

    TBA.

    +

    8.233. RDE_REGISTRAR_HAS_MISSING_GURID

    8.233.1. Severity

    ERROR

    8.233.2. Description

    TBA.

    +

    8.234. RDE_REGISTRAR_HAS_MISSING_ID

    8.234.1. Severity

    ERROR

    8.234.2. Description

    TBA.

    +

    8.235. RDE_REGISTRAR_HAS_MISSING_NAME

    8.235.1. Severity

    ERROR

    8.235.2. Description

    TBA.

    +

    8.236. RDE_SCHEMA_VALIDATION_ERROR

    8.236.1. Severity

    ERROR

    8.236.2. Description

    TBA.

    +

    8.237. RDE_UNEXPECTED_OBJECT_URI

    8.237.1. Severity

    ERROR

    8.237.2. Description

    TBA.

    +

    8.238. RDE_XML_PARSE_ERROR

    8.238.1. Severity

    ERROR

    8.238.2. Description

    TBA.

    +

    8.239. RPMS_MISSING_CLAIMS_KEY

    8.239.1. Severity

    ERROR

    8.239.2. Description

    TBA.

    +

    8.240. RPMS_SUNRISE_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.240.1. Severity

    ERROR

    8.240.2. Description

    TBA.

    +

    8.241. RPMS_SUNRISE_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.241.1. Severity

    ERROR

    8.241.2. Description

    TBA.

    +

    8.242. RPMS_SUNRISE_CREATE_UNEXPECTED_FAILURE_USING_VALID_SMD

    8.242.1. Severity

    ERROR

    8.242.2. Description

    TBA.

    +

    8.243. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_SMD

    8.243.1. Severity

    ERROR

    8.243.2. Description

    TBA.

    +

    8.244. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_REVOKED_SMD

    8.244.1. Severity

    ERROR

    8.244.2. Description

    TBA.

    +

    8.245. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_SMD_WITH_REVOKED_SIGNATURE

    8.245.1. Severity

    ERROR

    8.245.2. Description

    TBA.

    +

    8.246. RPMS_TRADEMARK_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.246.1. Severity

    ERROR

    8.246.2. Description

    TBA.

    +

    8.247. RPMS_TRADEMARK_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.247.1. Severity

    ERROR

    8.247.2. Description

    TBA.

    +

    8.248. RPMS_TRADEMARK_CREATE_UNEXPECTED_FAILURE_USING_VALID_CLAIM_KEY

    8.248.1. Severity

    ERROR

    8.248.2. Description

    TBA.

    +

    8.249. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_ACCEPTANCE_DATE

    8.249.1. Severity

    ERROR

    8.249.2. Description

    TBA.

    +

    8.250. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_CLAIM_KEY

    8.250.1. Severity

    ERROR

    8.250.2. Description

    TBA.

    +

    8.251. RPMS_UNEXPECTED_CLAIMS_KEY

    8.251.1. Severity

    ERROR

    8.251.2. Description

    TBA.

    +

    8.252. SRSGW_CONTACT_CREATE_FAILED

    8.252.1. Severity

    ERROR

    8.252.2. Description

    TBA.

    +

    8.253. SRSGW_CONTACT_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.253.1. Severity

    ERROR

    8.253.2. Description

    TBA.

    +

    8.254. SRSGW_CONTACT_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.254.1. Severity

    ERROR

    8.254.2. Description

    TBA.

    +

    8.255. SRSGW_DOMAIN_CREATE_FAILED

    8.255.1. Severity

    ERROR

    8.255.2. Description

    TBA.

    +

    8.256. SRSGW_DOMAIN_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.256.1. Severity

    ERROR

    8.256.2. Description

    TBA.

    +

    8.257. SRSGW_DOMAIN_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.257.1. Severity

    ERROR

    8.257.2. Description

    TBA.

    +

    8.258. SRSGW_DOMAIN_DELETE_DOMAIN_NOT_PENDINGDELETE

    8.258.1. Severity

    ERROR

    8.258.2. Description

    TBA.

    +

    8.259. SRSGW_DOMAIN_DELETE_FAILED

    8.259.1. Severity

    ERROR

    8.259.2. Description

    TBA.

    +

    8.260. SRSGW_DOMAIN_DELETE_RGP_STATUS_NOT_PENDINGDELETERESTORABLE

    8.260.1. Severity

    ERROR

    8.260.2. Description

    TBA.

    +

    8.261. SRSGW_DOMAIN_RENEW_FAILED

    8.261.1. Severity

    ERROR

    8.261.2. Description

    TBA.

    +

    8.262. SRSGW_DOMAIN_RENEW_OBJECT_HAS_INVALID_EXDATE

    8.262.1. Severity

    ERROR

    8.262.2. Description

    TBA.

    +

    8.263. SRSGW_DOMAIN_RENEW_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.263.1. Severity

    ERROR

    8.263.2. Description

    TBA.

    +

    8.264. SRSGW_DOMAIN_TRANSFER_APPROVAL_FAILED

    8.264.1. Severity

    ERROR

    8.264.2. Description

    TBA.

    +

    8.265. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_HAS_INCORRECT_CLID

    8.265.1. Severity

    ERROR

    8.265.2. Description

    TBA.

    +

    8.266. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.266.1. Severity

    ERROR

    8.266.2. Description

    TBA.

    +

    8.267. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_STILL_PENDING_TRANSFER

    8.267.1. Severity

    ERROR

    8.267.2. Description

    TBA.

    +

    8.268. SRSGW_DOMAIN_TRANSFER_REQUEST_FAILED

    8.268.1. Severity

    ERROR

    8.268.2. Description

    TBA.

    +

    8.269. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_HAS_INCORRECT_CLID

    8.269.1. Severity

    ERROR

    8.269.2. Description

    TBA.

    +

    8.270. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_PENDING_TRANSFER

    8.270.1. Severity

    ERROR

    8.270.2. Description

    TBA.

    +

    8.271. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.271.1. Severity

    ERROR

    8.271.2. Description

    TBA.

    +

    8.272. SRSGW_EPP_DNS_RESOLUTION_ERROR

    8.272.1. Severity

    ERROR

    8.272.2. Description

    TBA.

    +

    8.273. SRSGW_EPP_GENERIC_COMMAND_ERROR

    8.273.1. Severity

    ERROR

    8.273.2. Description

    TBA.

    +

    8.274. SRSGW_EPP_LOGIN_ERROR

    8.274.1. Severity

    ERROR

    8.274.2. Description

    TBA.

    +

    8.275. SRSGW_EPP_OBJECT_SHOULD_EXIST

    8.275.1. Severity

    ERROR

    8.275.2. Description

    TBA.

    +

    8.276. SRSGW_EPP_OBJECT_SHOULD_NOT_EXIST

    8.276.1. Severity

    ERROR

    8.276.2. Description

    TBA.

    +

    8.277. SRSGW_EPP_SCHEMA_VALIDATION_ERROR

    8.277.1. Severity

    ERROR

    8.277.2. Description

    TBA.

    +

    8.278. SRSGW_EPP_SERVICE_PORT_UNREACHABLE

    8.278.1. Severity

    ERROR

    8.278.2. Description

    TBA.

    +

    8.279. SRSGW_EPP_TLS_CONNECTION_ERROR

    8.279.1. Severity

    ERROR

    8.279.2. Description

    TBA.

    +

    8.280. SRSGW_EPP_UNEXPECTED_COMMAND_FAILURE

    8.280.1. Severity

    ERROR

    8.280.2. Description

    TBA.

    +

    8.281. SRSGW_EPP_UNEXPECTED_COMMAND_SUCCESS

    8.281.1. Severity

    ERROR

    8.281.2. Description

    TBA.

    +

    8.282. SRSGW_EPP_XML_PARSE_ERROR

    8.282.1. Severity

    ERROR

    8.282.2. Description

    TBA.

    +

    8.283. SRSGW_HOST_CREATE_FAILED

    8.283.1. Severity

    ERROR

    8.283.2. Description

    TBA.

    +

    8.284. SRSGW_HOST_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.284.1. Severity

    ERROR

    8.284.2. Description

    TBA.

    +

    8.285. SRSGW_HOST_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.285.1. Severity

    ERROR

    8.285.2. Description

    TBA.

    +

    8.286. ZM_AAAA_BAD_RDATA

    8.286.1. Severity

    ERROR

    8.286.2. Description

    Not available.

    +

    8.287. ZM_AAAA_QUERY_DROPPED

    8.287.1. Severity

    ERROR

    8.287.2. Description

    Not available.

    +

    8.288. ZM_AAAA_UNEXPECTED_RCODE

    8.288.1. Severity

    ERROR

    8.288.2. Description

    Not available.

    +

    8.289. ZM_ALGORITHM_DEPRECATED

    8.289.1. Severity

    ERROR

    8.289.2. Description

    Not available.

    +

    8.290. ZM_ALGORITHM_NOT_RECOMMENDED

    8.290.1. Severity

    WARNING

    8.290.2. Description

    Not available.

    +

    8.291. ZM_ALGORITHM_NOT_ZONE_SIGN

    8.291.1. Severity

    ERROR

    8.291.2. Description

    Not available.

    +

    8.292. ZM_ALGORITHM_PRIVATE

    8.292.1. Severity

    ERROR

    8.292.2. Description

    Not available.

    +

    8.293. ZM_ALGORITHM_RESERVED

    8.293.1. Severity

    ERROR

    8.293.2. Description

    Not available.

    +

    8.294. ZM_ALGORITHM_UNASSIGNED

    8.294.1. Severity

    ERROR

    8.294.2. Description

    Not available.

    +

    8.295. ZM_A_UNEXPECTED_RCODE

    8.295.1. Severity

    ERROR

    8.295.2. Description

    Not available.

    +

    8.296. ZM_BREAKS_ON_EDNS

    8.296.1. Severity

    ERROR

    8.296.2. Description

    Not available.

    +

    8.297. ZM_CHILD_NS_FAILED

    8.297.1. Severity

    ERROR

    8.297.2. Description

    Not available.

    +

    8.298. ZM_CHILD_NS_SAME_IP

    8.298.1. Severity

    ERROR

    8.298.2. Description

    Not available.

    +

    8.299. ZM_CHILD_ZONE_LAME

    8.299.1. Severity

    ERROR

    8.299.2. Description

    Not available.

    +

    8.300. ZM_CN01_MISSING_NS_RECORD_UDP

    8.300.1. Severity

    ERROR

    8.300.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the answer section over UDP.

    -

    8.290. ZM_CN01_MISSING_SOA_RECORD_UDP

    8.290.1. Severity

    ERROR

    8.290.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the +

    8.301. ZM_CN01_MISSING_SOA_RECORD_UDP

    8.301.1. Severity

    ERROR

    8.301.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the answer section over UDP.

    -

    8.291. ZM_CN01_NO_RESPONSE_NS_QUERY_UDP

    8.291.1. Severity

    ERROR

    8.291.2. Description

    Nameserver {ns} does not respond to NS queries over UDP.

    -

    8.292. ZM_CN01_NO_RESPONSE_SOA_QUERY_UDP

    8.292.1. Severity

    ERROR

    8.292.2. Description

    Nameserver {ns} does not respond to SOA queries over UDP.

    -

    8.293. ZM_CN01_NO_RESPONSE_UDP

    8.293.1. Severity

    ERROR

    8.293.2. Description

    Nameserver {ns} does not respond to any queries over UDP.

    -

    8.294. ZM_CN01_NS_RECORD_NOT_AA_UDP

    8.294.1. Severity

    ERROR

    8.294.2. Description

    Nameserver {ns} does not give an authoritative response on an NS +

    8.302. ZM_CN01_NO_RESPONSE_NS_QUERY_UDP

    8.302.1. Severity

    ERROR

    8.302.2. Description

    Nameserver {ns} does not respond to NS queries over UDP.

    +

    8.303. ZM_CN01_NO_RESPONSE_SOA_QUERY_UDP

    8.303.1. Severity

    ERROR

    8.303.2. Description

    Nameserver {ns} does not respond to SOA queries over UDP.

    +

    8.304. ZM_CN01_NO_RESPONSE_UDP

    8.304.1. Severity

    ERROR

    8.304.2. Description

    Nameserver {ns} does not respond to any queries over UDP.

    +

    8.305. ZM_CN01_NS_RECORD_NOT_AA_UDP

    8.305.1. Severity

    ERROR

    8.305.2. Description

    Nameserver {ns} does not give an authoritative response on an NS query over UDP.

    -

    8.295. ZM_CN01_SOA_RECORD_NOT_AA_UDP

    8.295.1. Severity

    ERROR

    8.295.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA +

    8.306. ZM_CN01_SOA_RECORD_NOT_AA_UDP

    8.306.1. Severity

    ERROR

    8.306.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA query over UDP.

    -

    8.296. ZM_CN01_UNEXPECTED_RCODE_NS_QUERY_UDP

    8.296.1. Severity

    ERROR

    8.296.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS +

    8.307. ZM_CN01_UNEXPECTED_RCODE_NS_QUERY_UDP

    8.307.1. Severity

    ERROR

    8.307.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over UDP.

    -

    8.297. ZM_CN01_UNEXPECTED_RCODE_SOA_QUERY_UDP

    8.297.1. Severity

    ERROR

    8.297.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA +

    8.308. ZM_CN01_UNEXPECTED_RCODE_SOA_QUERY_UDP

    8.308.1. Severity

    ERROR

    8.308.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over UDP.

    -

    8.298. ZM_CN01_WRONG_NS_RECORD_UDP

    8.298.1. Severity

    ERROR

    8.298.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.309. ZM_CN01_WRONG_NS_RECORD_UDP

    8.309.1. Severity

    ERROR

    8.309.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over UDP.

    -

    8.299. ZM_CN01_WRONG_SOA_RECORD_UDP

    8.299.1. Severity

    ERROR

    8.299.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.310. ZM_CN01_WRONG_SOA_RECORD_UDP

    8.310.1. Severity

    ERROR

    8.310.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over UDP.

    -

    8.300. ZM_CN02_MISSING_NS_RECORD_TCP

    8.300.1. Severity

    ERROR

    8.300.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the +

    8.311. ZM_CN02_MISSING_NS_RECORD_TCP

    8.311.1. Severity

    ERROR

    8.311.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the answer section over TCP.

    -

    8.301. ZM_CN02_MISSING_SOA_RECORD_TCP

    8.301.1. Severity

    ERROR

    8.301.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the +

    8.312. ZM_CN02_MISSING_SOA_RECORD_TCP

    8.312.1. Severity

    ERROR

    8.312.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the answer section over TCP.

    -

    8.302. ZM_CN02_NO_RESPONSE_NS_QUERY_TCP

    8.302.1. Severity

    ERROR

    8.302.2. Description

    Nameserver {ns} does not respond to NS queries over TCP.

    -

    8.303. ZM_CN02_NO_RESPONSE_SOA_QUERY_TCP

    8.303.1. Severity

    ERROR

    8.303.2. Description

    Nameserver {ns} does not respond to SOA queries over TCP.

    -

    8.304. ZM_CN02_NO_RESPONSE_TCP

    8.304.1. Severity

    ERROR

    8.304.2. Description

    Nameserver {ns} does not respond to any queries over TCP.

    -

    8.305. ZM_CN02_NS_RECORD_NOT_AA_TCP

    8.305.1. Severity

    ERROR

    8.305.2. Description

    Nameserver {ns} does not give an authoritative response on an NS +

    8.313. ZM_CN02_NO_RESPONSE_NS_QUERY_TCP

    8.313.1. Severity

    ERROR

    8.313.2. Description

    Nameserver {ns} does not respond to NS queries over TCP.

    +

    8.314. ZM_CN02_NO_RESPONSE_SOA_QUERY_TCP

    8.314.1. Severity

    ERROR

    8.314.2. Description

    Nameserver {ns} does not respond to SOA queries over TCP.

    +

    8.315. ZM_CN02_NO_RESPONSE_TCP

    8.315.1. Severity

    ERROR

    8.315.2. Description

    Nameserver {ns} does not respond to any queries over TCP.

    +

    8.316. ZM_CN02_NS_RECORD_NOT_AA_TCP

    8.316.1. Severity

    ERROR

    8.316.2. Description

    Nameserver {ns} does not give an authoritative response on an NS query over TCP.

    -

    8.306. ZM_CN02_SOA_RECORD_NOT_AA_TCP

    8.306.1. Severity

    ERROR

    8.306.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA +

    8.317. ZM_CN02_SOA_RECORD_NOT_AA_TCP

    8.317.1. Severity

    ERROR

    8.317.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA query over TCP.

    -

    8.307. ZM_CN02_UNEXPECTED_RCODE_NS_QUERY_TCP

    8.307.1. Severity

    ERROR

    8.307.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS +

    8.318. ZM_CN02_UNEXPECTED_RCODE_NS_QUERY_TCP

    8.318.1. Severity

    ERROR

    8.318.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over TCP.

    -

    8.308. ZM_CN02_UNEXPECTED_RCODE_SOA_QUERY_TCP

    8.308.1. Severity

    ERROR

    8.308.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA +

    8.319. ZM_CN02_UNEXPECTED_RCODE_SOA_QUERY_TCP

    8.319.1. Severity

    ERROR

    8.319.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over TCP.

    -

    8.309. ZM_CN02_WRONG_NS_RECORD_TCP

    8.309.1. Severity

    ERROR

    8.309.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.320. ZM_CN02_WRONG_NS_RECORD_TCP

    8.320.1. Severity

    ERROR

    8.320.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over TCP.

    -

    8.310. ZM_CN02_WRONG_SOA_RECORD_TCP

    8.310.1. Severity

    ERROR

    8.310.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.321. ZM_CN02_WRONG_SOA_RECORD_TCP

    8.321.1. Severity

    ERROR

    8.321.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over TCP.

    -

    8.311. ZM_DEL_NS_SAME_IP

    8.311.1. Severity

    ERROR

    8.311.2. Description

    Not available.

    -

    8.312. ZM_DNSKEY_SMALLER_THAN_REC

    8.312.1. Severity

    WARNING

    8.312.2. Description

    Not available.

    -

    8.313. ZM_DNSKEY_TOO_LARGE_FOR_ALGO

    8.313.1. Severity

    ERROR

    8.313.2. Description

    Not available.

    -

    8.314. ZM_DNSKEY_TOO_SMALL_FOR_ALGO

    8.314.1. Severity

    ERROR

    8.314.2. Description

    Not available.

    -

    8.315. ZM_DNSSEC_03_FAILED

    8.315.1. Severity

    ERROR

    8.315.2. Description

    The dnssec-03 test case failed, but no further +

    8.322. ZM_DEL_NS_SAME_IP

    8.322.1. Severity

    ERROR

    8.322.2. Description

    Not available.

    +

    8.323. ZM_DNSKEY_SMALLER_THAN_REC

    8.323.1. Severity

    WARNING

    8.323.2. Description

    Not available.

    +

    8.324. ZM_DNSKEY_TOO_LARGE_FOR_ALGO

    8.324.1. Severity

    ERROR

    8.324.2. Description

    Not available.

    +

    8.325. ZM_DNSKEY_TOO_SMALL_FOR_ALGO

    8.325.1. Severity

    ERROR

    8.325.2. Description

    Not available.

    +

    8.326. ZM_DNSSEC_03_FAILED

    8.326.1. Severity

    ERROR

    8.326.2. Description

    The dnssec-03 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.316. ZM_DNSSEC_04_FAILED

    8.316.1. Severity

    ERROR

    8.316.2. Description

    The dnssec-04 test case failed, but no further +

    8.327. ZM_DNSSEC_04_FAILED

    8.327.1. Severity

    ERROR

    8.327.2. Description

    The dnssec-04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.317. ZM_DNSSEC_06_FAILED

    8.317.1. Severity

    ERROR

    8.317.2. Description

    The dnssec-06 test case failed, but no further +

    8.328. ZM_DNSSEC_06_FAILED

    8.328.1. Severity

    ERROR

    8.328.2. Description

    The dnssec-06 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.318. ZM_DNSSEC_12_FAILED

    8.318.1. Severity

    ERROR

    8.318.2. Description

    The dnssec-12 test case failed, but no further +

    8.329. ZM_DNSSEC_12_FAILED

    8.329.1. Severity

    ERROR

    8.329.2. Description

    The dnssec-12 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.319. ZM_DNS_ADDRESS01_FAILED

    8.319.1. Severity

    ERROR

    8.319.2. Description

    The dns-address01 test case failed, but no further +

    8.330. ZM_DNS_ADDRESS01_FAILED

    8.330.1. Severity

    ERROR

    8.330.2. Description

    The dns-address01 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.320. ZM_DNS_ADDRESS02_FAILED

    8.320.1. Severity

    ERROR

    8.320.2. Description

    The dns-address02 test case failed, but no further +

    8.331. ZM_DNS_ADDRESS02_FAILED

    8.331.1. Severity

    ERROR

    8.331.2. Description

    The dns-address02 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.321. ZM_DNS_ADDRESS03_FAILED

    8.321.1. Severity

    ERROR

    8.321.2. Description

    The dns-address03 test case failed, but no further +

    8.332. ZM_DNS_ADDRESS03_FAILED

    8.332.1. Severity

    ERROR

    8.332.2. Description

    The dns-address03 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.322. ZM_DNS_DELEGATION04_FAILED

    8.322.1. Severity

    ERROR

    8.322.2. Description

    The dns-delegation04 test case failed, but no further +

    8.333. ZM_DNS_DELEGATION04_FAILED

    8.333.1. Severity

    ERROR

    8.333.2. Description

    The dns-delegation04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.323. ZM_DNS_DELEGATION07_FAILED

    8.323.1. Severity

    ERROR

    8.323.2. Description

    The dns-delegation07 test case failed, but no further +

    8.334. ZM_DNS_DELEGATION07_FAILED

    8.334.1. Severity

    ERROR

    8.334.2. Description

    The dns-delegation07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.324. ZM_DNS_NAMESERVER04_FAILED

    8.324.1. Severity

    ERROR

    8.324.2. Description

    The dns-nameserver04 test case failed, but no further +

    8.335. ZM_DNS_NAMESERVER04_FAILED

    8.335.1. Severity

    ERROR

    8.335.2. Description

    The dns-nameserver04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.325. ZM_DNS_NAMESERVER06_FAILED

    8.325.1. Severity

    ERROR

    8.325.2. Description

    The dns-nameserver06 test case failed, but no further +

    8.336. ZM_DNS_NAMESERVER06_FAILED

    8.336.1. Severity

    ERROR

    8.336.2. Description

    The dns-nameserver06 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.326. ZM_DNS_NAMESERVER08_FAILED

    8.326.1. Severity

    ERROR

    8.326.2. Description

    The dns-nameserver08 test case failed, but no further +

    8.337. ZM_DNS_NAMESERVER08_FAILED

    8.337.1. Severity

    ERROR

    8.337.2. Description

    The dns-nameserver08 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.327. ZM_DNS_NAMESERVER09_FAILED

    8.327.1. Severity

    ERROR

    8.327.2. Description

    The dns-nameserver09 test case failed, but no further +

    8.338. ZM_DNS_NAMESERVER09_FAILED

    8.338.1. Severity

    ERROR

    8.338.2. Description

    The dns-nameserver09 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.328. ZM_DNS_SYNTAX05_FAILED

    8.328.1. Severity

    ERROR

    8.328.2. Description

    The dns-syntax05 test case failed, but no further +

    8.339. ZM_DNS_SYNTAX05_FAILED

    8.339.1. Severity

    ERROR

    8.339.2. Description

    The dns-syntax05 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.329. ZM_DNS_SYNTAX07_FAILED

    8.329.1. Severity

    ERROR

    8.329.2. Description

    The dns-syntax07 test case failed, but no further +

    8.340. ZM_DNS_SYNTAX07_FAILED

    8.340.1. Severity

    ERROR

    8.340.2. Description

    The dns-syntax07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.330. ZM_DNS_ZONE07_FAILED

    8.330.1. Severity

    ERROR

    8.330.2. Description

    The dns-zone07 test case failed, but no further +

    8.341. ZM_DNS_ZONE07_FAILED

    8.341.1. Severity

    ERROR

    8.341.2. Description

    The dns-zone07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.331. ZM_DS01_DS_ALGO_2_MISSING

    8.331.1. Severity

    ERROR

    8.331.2. Description

    DS created with algo 2 (SHA-256) is missing.

    -

    8.332. ZM_DS01_DS_ALGO_DEPRECATED

    8.332.1. Severity

    ERROR

    8.332.2. Description

    The DS digest algorithm is deprecated.

    -

    8.333. ZM_DS01_DS_ALGO_NOT_DS

    8.333.1. Severity

    ERROR

    8.333.2. Description

    The DS digest algorithm is not for DS.

    -

    8.334. ZM_DS01_DS_ALGO_RESERVED

    8.334.1. Severity

    ERROR

    8.334.2. Description

    No DS digest algorithm defined for the digest code.

    -

    8.335. ZM_DS02_DNSKEY_NOT_FOR_ZONE_SIGNING

    8.335.1. Severity

    ERROR

    8.335.2. Description

    Flags field of DNSKEY record with tag {keytag} does not have ZONE bit +

    8.342. ZM_DS01_DS_ALGO_2_MISSING

    8.342.1. Severity

    ERROR

    8.342.2. Description

    DS created with algo 2 (SHA-256) is missing.

    +

    8.343. ZM_DS01_DS_ALGO_DEPRECATED

    8.343.1. Severity

    ERROR

    8.343.2. Description

    The DS digest algorithm is deprecated.

    +

    8.344. ZM_DS01_DS_ALGO_NOT_DS

    8.344.1. Severity

    ERROR

    8.344.2. Description

    The DS digest algorithm is not for DS.

    +

    8.345. ZM_DS01_DS_ALGO_RESERVED

    8.345.1. Severity

    ERROR

    8.345.2. Description

    No DS digest algorithm defined for the digest code.

    +

    8.346. ZM_DS02_DNSKEY_NOT_FOR_ZONE_SIGNING

    8.346.1. Severity

    ERROR

    8.346.2. Description

    Flags field of DNSKEY record with tag {keytag} does not have ZONE bit set although DS with same tag is present in parent. Fetched from the nameservers with IP addresses “{ns_ip_list}”.

    -

    8.336. ZM_DS02_DNSKEY_NOT_SEP

    8.336.1. Severity

    ERROR

    8.336.2. Description

    Flags field of DNSKEY record with tag {keytag} does not have SEP bit +

    8.347. ZM_DS02_DNSKEY_NOT_SEP

    8.347.1. Severity

    ERROR

    8.347.2. Description

    Flags field of DNSKEY record with tag {keytag} does not have SEP bit set although DS with same tag is present in parent. Fetched from the nameservers with IP addresses “{ns_ip_list}”.

    -

    8.337. ZM_DS02_DNSKEY_NOT_SIGNED_BY_ANY_DS

    8.337.1. Severity

    ERROR

    8.337.2. Description

    The DNSKEY RRset has not been signed by any DNSKEY matched by a DS +

    8.348. ZM_DS02_DNSKEY_NOT_SIGNED_BY_ANY_DS

    8.348.1. Severity

    ERROR

    8.348.2. Description

    The DNSKEY RRset has not been signed by any DNSKEY matched by a DS record. Fetched from the nameservers with IP addresses “{ns_ip_list}”.

    -

    8.338. ZM_DS02_NO_DNSKEY_FOR_DS

    8.338.1. Severity

    ERROR

    8.338.2. Description

    The DNSKEY record with tag {keytag} that the DS refers to does not +

    8.349. ZM_DS02_NO_DNSKEY_FOR_DS

    8.349.1. Severity

    ERROR

    8.349.2. Description

    The DNSKEY record with tag {keytag} that the DS refers to does not exist in the DNSKEY RRset. Fetched from the nameservers with IP “{ns_ip_list}”.

    -

    8.339. ZM_DS02_NO_MATCHING_DNSKEY_RRSIG

    8.339.1. Severity

    ERROR

    8.339.2. Description

    The DNSKEY RRset is not signed by the DNSKEY with tag {keytag} that +

    8.350. ZM_DS02_NO_MATCHING_DNSKEY_RRSIG

    8.350.1. Severity

    ERROR

    8.350.2. Description

    The DNSKEY RRset is not signed by the DNSKEY with tag {keytag} that the DS record refers to. Fetched from the nameservers with IP “{ns_ip_list}”.

    -

    8.340. ZM_DS02_NO_MATCH_DS_DNSKEY

    8.340.1. Severity

    ERROR

    8.340.2. Description

    The DS record does not match the DNSKEY with tag {keytag} by +

    8.351. ZM_DS02_NO_MATCH_DS_DNSKEY

    8.351.1. Severity

    ERROR

    8.351.2. Description

    The DS record does not match the DNSKEY with tag {keytag} by algorithm or digest. Fetched from the nameservers with IP “{ns_ip_list}”.

    -

    8.341. ZM_DS02_NO_VALID_DNSKEY_FOR_ANY_DS

    8.341.1. Severity

    ERROR

    8.341.2. Description

    There is no valid DNSKEY matched by any of the DS records. Fetched +

    8.352. ZM_DS02_NO_VALID_DNSKEY_FOR_ANY_DS

    8.352.1. Severity

    ERROR

    8.352.2. Description

    There is no valid DNSKEY matched by any of the DS records. Fetched from the nameservers with IP addresses “{ns_ip_list}”.

    -

    8.342. ZM_DS02_RRSIG_NOT_VALID_BY_DNSKEY

    8.342.1. Severity

    ERROR

    8.342.2. Description

    The DNSKEY RRset is signed with an RRSIG with tag {keytag} which +

    8.353. ZM_DS02_RRSIG_NOT_VALID_BY_DNSKEY

    8.353.1. Severity

    ERROR

    8.353.2. Description

    The DNSKEY RRset is signed with an RRSIG with tag {keytag} which cannot be validated by the matching DNSKEY. Fetched from the nameservers with IP addresses “{ns_ip_list}”.

    -

    8.343. ZM_DS08_DNSKEY_RRSIG_EXPIRED

    8.343.1. Severity

    ERROR

    8.343.2. Description

    DNSKEY RRset is signed with an RRSIG that has expired.

    -

    8.344. ZM_DS08_DNSKEY_RRSIG_NOT_YET_VALID

    8.344.1. Severity

    ERROR

    8.344.2. Description

    DNSKEY RRset is signed with a not yet valid RRSIG.

    -

    8.345. ZM_DS08_MISSING_RRSIG_IN_RESPONSE

    8.345.1. Severity

    ERROR

    8.345.2. Description

    DNSKEY is unsigned which is against expectation.

    -

    8.346. ZM_DS08_NO_MATCHING_DNSKEY

    8.346.1. Severity

    ERROR

    8.346.2. Description

    DNSKEY RRset is signed with an RRSIG that does not match any +

    8.354. ZM_DS08_DNSKEY_RRSIG_EXPIRED

    8.354.1. Severity

    ERROR

    8.354.2. Description

    DNSKEY RRset is signed with an RRSIG that has expired.

    +

    8.355. ZM_DS08_DNSKEY_RRSIG_NOT_YET_VALID

    8.355.1. Severity

    ERROR

    8.355.2. Description

    DNSKEY RRset is signed with a not yet valid RRSIG.

    +

    8.356. ZM_DS08_MISSING_RRSIG_IN_RESPONSE

    8.356.1. Severity

    ERROR

    8.356.2. Description

    DNSKEY is unsigned which is against expectation.

    +

    8.357. ZM_DS08_NO_MATCHING_DNSKEY

    8.357.1. Severity

    ERROR

    8.357.2. Description

    DNSKEY RRset is signed with an RRSIG that does not match any DNSKEY.

    -

    8.347. ZM_DS08_RRSIG_NOT_VALID_BY_DNSKEY

    8.347.1. Severity

    ERROR

    8.347.2. Description

    DNSKEY RRset is signed with an RRSIG that cannot be validated by the +

    8.358. ZM_DS08_RRSIG_NOT_VALID_BY_DNSKEY

    8.358.1. Severity

    ERROR

    8.358.2. Description

    DNSKEY RRset is signed with an RRSIG that cannot be validated by the matching DNSKEY.

    -

    8.348. ZM_DS09_MISSING_RRSIG_IN_RESPONSE

    8.348.1. Severity

    ERROR

    8.348.2. Description

    SOA is unsigned which is against expectation

    -

    8.349. ZM_DS09_NO_MATCHING_DNSKEY

    8.349.1. Severity

    ERROR

    8.349.2. Description

    SOA is signed with an RRSIG that does not match any DNSKEY

    -

    8.350. ZM_DS09_RRSIG_NOT_VALID_BY_DNSKEY

    8.350.1. Severity

    ERROR

    8.350.2. Description

    SOA is signed with an RRSIG that cannot be validated by the matching +

    8.359. ZM_DS09_MISSING_RRSIG_IN_RESPONSE

    8.359.1. Severity

    ERROR

    8.359.2. Description

    SOA is unsigned which is against expectation

    +

    8.360. ZM_DS09_NO_MATCHING_DNSKEY

    8.360.1. Severity

    ERROR

    8.360.2. Description

    SOA is signed with an RRSIG that does not match any DNSKEY

    +

    8.361. ZM_DS09_RRSIG_NOT_VALID_BY_DNSKEY

    8.361.1. Severity

    ERROR

    8.361.2. Description

    SOA is signed with an RRSIG that cannot be validated by the matching DNSKEY

    -

    8.351. ZM_DS09_SOA_RRSIG_EXPIRED

    8.351.1. Severity

    ERROR

    8.351.2. Description

    SOA is signed with an RRSIG that has expired

    -

    8.352. ZM_DS09_SOA_RRSIG_NOT_YET_VALID

    8.352.1. Severity

    ERROR

    8.352.2. Description

    SOA is signed with a not yet valid RRSIG

    -

    8.353. ZM_DS10_ANSWER_VERIFY_ERROR

    8.353.1. Severity

    ERROR

    8.353.2. Description

    RRSIG on record or records in answer section cannot be verified.

    -

    8.354. ZM_DS10_INCONSISTENT_NSEC_NSEC3

    8.354.1. Severity

    ERROR

    8.354.2. Description

    Some servers return NSEC, others return NSEC3.

    -

    8.355. ZM_DS10_MISSING_NSEC_NSEC3

    8.355.1. Severity

    ERROR

    8.355.2. Description

    Missing expected NSEC or NSEC3 in a signed zone.

    -

    8.356. ZM_DS10_MIXED_NSEC_NSEC3

    8.356.1. Severity

    ERROR

    8.356.2. Description

    Both NSEC and NSEC3 are returned from the same server.

    -

    8.357. ZM_DS10_NAME_NOT_COVERED_BY_NSEC

    8.357.1. Severity

    ERROR

    8.357.2. Description

    The non-existent name is not correctly covered by the NSEC +

    8.362. ZM_DS09_SOA_RRSIG_EXPIRED

    8.362.1. Severity

    ERROR

    8.362.2. Description

    SOA is signed with an RRSIG that has expired

    +

    8.363. ZM_DS09_SOA_RRSIG_NOT_YET_VALID

    8.363.1. Severity

    ERROR

    8.363.2. Description

    SOA is signed with a not yet valid RRSIG

    +

    8.364. ZM_DS10_ANSWER_VERIFY_ERROR

    8.364.1. Severity

    ERROR

    8.364.2. Description

    RRSIG on record or records in answer section cannot be verified.

    +

    8.365. ZM_DS10_INCONSISTENT_NSEC_NSEC3

    8.365.1. Severity

    ERROR

    8.365.2. Description

    Some servers return NSEC, others return NSEC3.

    +

    8.366. ZM_DS10_MISSING_NSEC_NSEC3

    8.366.1. Severity

    ERROR

    8.366.2. Description

    Missing expected NSEC or NSEC3 in a signed zone.

    +

    8.367. ZM_DS10_MIXED_NSEC_NSEC3

    8.367.1. Severity

    ERROR

    8.367.2. Description

    Both NSEC and NSEC3 are returned from the same server.

    +

    8.368. ZM_DS10_NAME_NOT_COVERED_BY_NSEC

    8.368.1. Severity

    ERROR

    8.368.2. Description

    The non-existent name is not correctly covered by the NSEC records.

    -

    8.358. ZM_DS10_NAME_NOT_COVERED_BY_NSEC3

    8.358.1. Severity

    ERROR

    8.358.2. Description

    The non-existent name is not correctly covered by the NSEC3 +

    8.369. ZM_DS10_NAME_NOT_COVERED_BY_NSEC3

    8.369.1. Severity

    ERROR

    8.369.2. Description

    The non-existent name is not correctly covered by the NSEC3 records.

    -

    8.359. ZM_DS10_NON_EXISTENT_RESPONSE_ERROR

    8.359.1. Severity

    ERROR

    8.359.2. Description

    No or error in response of an expected non-existent name.

    -

    8.360. ZM_DS10_NSEC3_MISSING_SIGNATURE

    8.360.1. Severity

    ERROR

    8.360.2. Description

    Missing signatures for NSEC3 record or records.

    -

    8.361. ZM_DS10_NSEC3_RRSIG_VERIFY_ERROR

    8.361.1. Severity

    ERROR

    8.361.2. Description

    The signature or signatures on the NSEC3 record or records cannot be +

    8.370. ZM_DS10_NON_EXISTENT_RESPONSE_ERROR

    8.370.1. Severity

    ERROR

    8.370.2. Description

    No or error in response of an expected non-existent name.

    +

    8.371. ZM_DS10_NSEC3_MISSING_SIGNATURE

    8.371.1. Severity

    ERROR

    8.371.2. Description

    Missing signatures for NSEC3 record or records.

    +

    8.372. ZM_DS10_NSEC3_RRSIG_VERIFY_ERROR

    8.372.1. Severity

    ERROR

    8.372.2. Description

    The signature or signatures on the NSEC3 record or records cannot be correctly verfied.

    -

    8.362. ZM_DS10_NSEC_MISSING_SIGNATURE

    8.362.1. Severity

    ERROR

    8.362.2. Description

    Missing signatures for NSEC record or records.

    -

    8.363. ZM_DS10_NSEC_RRSIG_VERIFY_ERROR

    8.363.1. Severity

    ERROR

    8.363.2. Description

    The signature or signatures on the NSEC record or records cannot be +

    8.373. ZM_DS10_NSEC_MISSING_SIGNATURE

    8.373.1. Severity

    ERROR

    8.373.2. Description

    Missing signatures for NSEC record or records.

    +

    8.374. ZM_DS10_NSEC_RRSIG_VERIFY_ERROR

    8.374.1. Severity

    ERROR

    8.374.2. Description

    The signature or signatures on the NSEC record or records cannot be correctly verfied.

    -

    8.364. ZM_DS10_UNSIGNED_ANSWER

    8.364.1. Severity

    ERROR

    8.364.2. Description

    RRSIG is missing for record or records in the answer section.

    -

    8.365. ZM_DS13_ALGO_NOT_SIGNED_DNSKEY

    8.365.1. Severity

    ERROR

    8.365.2. Description

    The DNSKEY RRset is not signed with an algorithm present in the +

    8.375. ZM_DS10_UNSIGNED_ANSWER

    8.375.1. Severity

    ERROR

    8.375.2. Description

    RRSIG is missing for record or records in the answer section.

    +

    8.376. ZM_DS13_ALGO_NOT_SIGNED_DNSKEY

    8.376.1. Severity

    ERROR

    8.376.2. Description

    The DNSKEY RRset is not signed with an algorithm present in the DNSKEY RRset

    -

    8.366. ZM_DS13_ALGO_NOT_SIGNED_NS

    8.366.1. Severity

    ERROR

    8.366.2. Description

    The NS RRset is not signed with an algorithm present in the DNSKEY +

    8.377. ZM_DS13_ALGO_NOT_SIGNED_NS

    8.377.1. Severity

    ERROR

    8.377.2. Description

    The NS RRset is not signed with an algorithm present in the DNSKEY RRset

    -

    8.367. ZM_DS13_ALGO_NOT_SIGNED_SOA

    8.367.1. Severity

    ERROR

    8.367.2. Description

    The SOA RRset is not signed with an algorithm present in the DNSKEY +

    8.378. ZM_DS13_ALGO_NOT_SIGNED_SOA

    8.378.1. Severity

    ERROR

    8.378.2. Description

    The SOA RRset is not signed with an algorithm present in the DNSKEY RRset

    -

    8.368. ZM_DS15_INCONSISTENT_CDNSKEY

    8.368.1. Severity

    ERROR

    8.368.2. Description

    All servers do not have the same CDNSKEY RRset.

    -

    8.369. ZM_DS15_INCONSISTENT_CDS

    8.369.1. Severity

    ERROR

    8.369.2. Description

    All servers do not have the same CDS RRset.

    -

    8.370. ZM_DS15_MISMATCH_CDS_CDNSKEY

    8.370.1. Severity

    ERROR

    8.370.2. Description

    Both CDS and CDNSKEY RRsets are found but they do not match.

    -

    8.371. ZM_DS16_CDS_INVALID_RRSIG

    8.371.1. Severity

    ERROR

    8.371.2. Description

    CDS RRset is signed with an invalid RRSIG.

    -

    8.372. ZM_DS16_CDS_MATCHES_NON_SEP_DNSKEY

    8.372.1. Severity

    ERROR

    8.372.2. Description

    CDS record matches a DNSKEY with SEP bit (bit 15) unset.

    -

    8.373. ZM_DS16_CDS_MATCHES_NON_ZONE_DNSKEY

    8.373.1. Severity

    ERROR

    8.373.2. Description

    CDS record matches a DNSKEY with zone bit (bit 7) unset.

    -

    8.374. ZM_DS16_CDS_MATCHES_NO_DNSKEY

    8.374.1. Severity

    ERROR

    8.374.2. Description

    CDS record does not match any DNSKEY in DNSKEY RRset.

    -

    8.375. ZM_DS16_CDS_NOT_SIGNED_BY_CDS

    8.375.1. Severity

    ERROR

    8.375.2. Description

    CDS RRset is not signed by the key that the CDS record points to.

    -

    8.376. ZM_DS16_CDS_SIGNED_BY_UNKNOWN_DNSKEY

    8.376.1. Severity

    ERROR

    8.376.2. Description

    CDS RRset is signed by a key not in DNSKEY RRset.

    -

    8.377. ZM_DS16_CDS_UNSIGNED

    8.377.1. Severity

    ERROR

    8.377.2. Description

    CDS RRset is unsigned.

    -

    8.378. ZM_DS16_CDS_WITHOUT_DNSKEY

    8.378.1. Severity

    ERROR

    8.378.2. Description

    CDS RRset exists, but there is no DNSKEY RRset.

    -

    8.379. ZM_DS16_DNSKEY_NOT_SIGNED_BY_CDS

    8.379.1. Severity

    ERROR

    8.379.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDS records +

    8.379. ZM_DS15_INCONSISTENT_CDNSKEY

    8.379.1. Severity

    ERROR

    8.379.2. Description

    All servers do not have the same CDNSKEY RRset.

    +

    8.380. ZM_DS15_INCONSISTENT_CDS

    8.380.1. Severity

    ERROR

    8.380.2. Description

    All servers do not have the same CDS RRset.

    +

    8.381. ZM_DS15_MISMATCH_CDS_CDNSKEY

    8.381.1. Severity

    ERROR

    8.381.2. Description

    Both CDS and CDNSKEY RRsets are found but they do not match.

    +

    8.382. ZM_DS16_CDS_INVALID_RRSIG

    8.382.1. Severity

    ERROR

    8.382.2. Description

    CDS RRset is signed with an invalid RRSIG.

    +

    8.383. ZM_DS16_CDS_MATCHES_NON_SEP_DNSKEY

    8.383.1. Severity

    ERROR

    8.383.2. Description

    CDS record matches a DNSKEY with SEP bit (bit 15) unset.

    +

    8.384. ZM_DS16_CDS_MATCHES_NON_ZONE_DNSKEY

    8.384.1. Severity

    ERROR

    8.384.2. Description

    CDS record matches a DNSKEY with zone bit (bit 7) unset.

    +

    8.385. ZM_DS16_CDS_MATCHES_NO_DNSKEY

    8.385.1. Severity

    ERROR

    8.385.2. Description

    CDS record does not match any DNSKEY in DNSKEY RRset.

    +

    8.386. ZM_DS16_CDS_NOT_SIGNED_BY_CDS

    8.386.1. Severity

    ERROR

    8.386.2. Description

    CDS RRset is not signed by the key that the CDS record points to.

    +

    8.387. ZM_DS16_CDS_SIGNED_BY_UNKNOWN_DNSKEY

    8.387.1. Severity

    ERROR

    8.387.2. Description

    CDS RRset is signed by a key not in DNSKEY RRset.

    +

    8.388. ZM_DS16_CDS_UNSIGNED

    8.388.1. Severity

    ERROR

    8.388.2. Description

    CDS RRset is unsigned.

    +

    8.389. ZM_DS16_CDS_WITHOUT_DNSKEY

    8.389.1. Severity

    ERROR

    8.389.2. Description

    CDS RRset exists, but there is no DNSKEY RRset.

    +

    8.390. ZM_DS16_DNSKEY_NOT_SIGNED_BY_CDS

    8.390.1. Severity

    ERROR

    8.390.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDS records point to.

    -

    8.380. ZM_DS16_MIXED_DELETE_CDS

    8.380.1. Severity

    ERROR

    8.380.2. Description

    “Delete” CDS record is mixed with normal CDS record.

    -

    8.381. ZM_DS17_CDNSKEY_INVALID_RRSIG

    8.381.1. Severity

    ERROR

    8.381.2. Description

    CDNSKEY RRset signed with an invalid RRSIG.

    -

    8.382. ZM_DS17_CDNSKEY_IS_NON_SEP

    8.382.1. Severity

    ERROR

    8.382.2. Description

    CDNSKEY record has the SEP bit (bit 15) unset.

    -

    8.383. ZM_DS17_CDNSKEY_IS_NON_ZONE

    8.383.1. Severity

    ERROR

    8.383.2. Description

    CDNSKEY record has the zone bit (bit 7) unset.

    -

    8.384. ZM_DS17_CDNSKEY_MATCHES_NO_DNSKEY

    8.384.1. Severity

    ERROR

    8.384.2. Description

    CDNSKEY record does not match any DNSKEY in DNSKEY RRset.

    -

    8.385. ZM_DS17_CDNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.385.1. Severity

    ERROR

    8.385.2. Description

    CDNSKEY RRset is not signed by the key that the CDNSKEY record points +

    8.391. ZM_DS16_MIXED_DELETE_CDS

    8.391.1. Severity

    ERROR

    8.391.2. Description

    “Delete” CDS record is mixed with normal CDS record.

    +

    8.392. ZM_DS17_CDNSKEY_INVALID_RRSIG

    8.392.1. Severity

    ERROR

    8.392.2. Description

    CDNSKEY RRset signed with an invalid RRSIG.

    +

    8.393. ZM_DS17_CDNSKEY_IS_NON_SEP

    8.393.1. Severity

    ERROR

    8.393.2. Description

    CDNSKEY record has the SEP bit (bit 15) unset.

    +

    8.394. ZM_DS17_CDNSKEY_IS_NON_ZONE

    8.394.1. Severity

    ERROR

    8.394.2. Description

    CDNSKEY record has the zone bit (bit 7) unset.

    +

    8.395. ZM_DS17_CDNSKEY_MATCHES_NO_DNSKEY

    8.395.1. Severity

    ERROR

    8.395.2. Description

    CDNSKEY record does not match any DNSKEY in DNSKEY RRset.

    +

    8.396. ZM_DS17_CDNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.396.1. Severity

    ERROR

    8.396.2. Description

    CDNSKEY RRset is not signed by the key that the CDNSKEY record points to.

    -

    8.386. ZM_DS17_CDNSKEY_SIGNED_BY_UNKNOWN_DNSKEY

    8.386.1. Severity

    ERROR

    8.386.2. Description

    CDNSKEY RRset is signed by a key not in DNSKEY RRset.

    -

    8.387. ZM_DS17_CDNSKEY_UNSIGNED

    8.387.1. Severity

    ERROR

    8.387.2. Description

    CDNSKEY RRset is unsigned.

    -

    8.388. ZM_DS17_CDNSKEY_WITHOUT_DNSKEY

    8.388.1. Severity

    ERROR

    8.388.2. Description

    CDNSKEY RRset exists, but there is no DNSKEY RRset.

    -

    8.389. ZM_DS17_DNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.389.1. Severity

    ERROR

    8.389.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDNSKEY +

    8.397. ZM_DS17_CDNSKEY_SIGNED_BY_UNKNOWN_DNSKEY

    8.397.1. Severity

    ERROR

    8.397.2. Description

    CDNSKEY RRset is signed by a key not in DNSKEY RRset.

    +

    8.398. ZM_DS17_CDNSKEY_UNSIGNED

    8.398.1. Severity

    ERROR

    8.398.2. Description

    CDNSKEY RRset is unsigned.

    +

    8.399. ZM_DS17_CDNSKEY_WITHOUT_DNSKEY

    8.399.1. Severity

    ERROR

    8.399.2. Description

    CDNSKEY RRset exists, but there is no DNSKEY RRset.

    +

    8.400. ZM_DS17_DNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.400.1. Severity

    ERROR

    8.400.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDNSKEY records point to.

    -

    8.390. ZM_DS17_MIXED_DELETE_CDNSKEY

    8.390.1. Severity

    ERROR

    8.390.2. Description

    “Delete” CDNSKEY record is mixed with normal CDNSKEY record.

    -

    8.391. ZM_DS18_NO_MATCH_CDNSKEY_RRSIG_DS

    8.391.1. Severity

    ERROR

    8.391.2. Description

    CDNSKEY RRset is not signed with a DNSKEY record that a DS record +

    8.401. ZM_DS17_MIXED_DELETE_CDNSKEY

    8.401.1. Severity

    ERROR

    8.401.2. Description

    “Delete” CDNSKEY record is mixed with normal CDNSKEY record.

    +

    8.402. ZM_DS18_NO_MATCH_CDNSKEY_RRSIG_DS

    8.402.1. Severity

    ERROR

    8.402.2. Description

    CDNSKEY RRset is not signed with a DNSKEY record that a DS record points to.

    -

    8.392. ZM_DS18_NO_MATCH_CDS_RRSIG_DS

    8.392.1. Severity

    ERROR

    8.392.2. Description

    The CDS RRset is not signed with a DNSKEY record that a DS record +

    8.403. ZM_DS18_NO_MATCH_CDS_RRSIG_DS

    8.403.1. Severity

    ERROR

    8.403.2. Description

    The CDS RRset is not signed with a DNSKEY record that a DS record points to.

    -

    8.393. ZM_EDNS_RESPONSE_WITHOUT_EDNS

    8.393.1. Severity

    ERROR

    8.393.2. Description

    Not available.

    -

    8.394. ZM_EDNS_VERSION_ERROR

    8.394.1. Severity

    ERROR

    8.394.2. Description

    Not available.

    -

    8.395. ZM_EMPTY_ASN_SET

    8.395.1. Severity

    ERROR

    8.395.2. Description

    Not available.

    -

    8.396. ZM_ERROR_ASN_DATABASE

    8.396.1. Severity

    ERROR

    8.396.2. Description

    Not available.

    -

    8.397. ZM_EXTRA_ADDRESS_CHILD

    8.397.1. Severity

    ERROR

    8.397.2. Description

    Not available.

    -

    8.398. ZM_IN_BAILIWICK_ADDR_MISMATCH

    8.398.1. Severity

    ERROR

    8.398.2. Description

    Not available.

    -

    8.399. ZM_IPV4_ONE_ASN

    8.399.1. Severity

    ERROR

    8.399.2. Description

    Not available.

    -

    8.400. ZM_IPV6_ONE_ASN

    8.400.1. Severity

    ERROR

    8.400.2. Description

    Not available.

    -

    8.401. ZM_IS_A_RECURSOR

    8.401.1. Severity

    ERROR

    8.401.2. Description

    Not available.

    -

    8.402. ZM_MISSING_OPT_IN_TRUNCATED

    8.402.1. Severity

    ERROR

    8.402.2. Description

    Not available.

    -

    8.403. ZM_MULTIPLE_NS_SET

    8.403.1. Severity

    ERROR

    8.403.2. Description

    Not available.

    -

    8.404. ZM_MULTIPLE_SOA

    8.404.1. Severity

    ERROR

    8.404.2. Description

    Not available.

    -

    8.405. ZM_MULTIPLE_SOA_MNAMES

    8.405.1. Severity

    ERROR

    8.405.2. Description

    Not available.

    -

    8.406. ZM_MULTIPLE_SOA_RNAMES

    8.406.1. Severity

    ERROR

    8.406.2. Description

    Not available.

    -

    8.407. ZM_MULTIPLE_SOA_TIME_PARAMETER_SET

    8.407.1. Severity

    ERROR

    8.407.2. Description

    Not available.

    -

    8.408. ZM_N10_EDNS_RESPONSE_ERROR

    8.408.1. Severity

    ERROR

    8.408.2. Description

    Expected RCODE value when EDNS ver=1, but error in response.

    -

    8.409. ZM_N10_NO_RESPONSE_EDNS1_QUERY

    8.409.1. Severity

    ERROR

    8.409.2. Description

    Response when EDNS ver=0, but not when 1.

    -

    8.410. ZM_N10_UNEXPECTED_RCODE

    8.410.1. Severity

    ERROR

    8.410.2. Description

    Unexpected RCODE value when EDNS ver=1.

    -

    8.411. ZM_N11_NO_EDNS

    8.411.1. Severity

    ERROR

    8.411.2. Description

    The DNS response, on query with unknown EDNS option-code, does not +

    8.404. ZM_EDNS_RESPONSE_WITHOUT_EDNS

    8.404.1. Severity

    ERROR

    8.404.2. Description

    Not available.

    +

    8.405. ZM_EDNS_VERSION_ERROR

    8.405.1. Severity

    ERROR

    8.405.2. Description

    Not available.

    +

    8.406. ZM_EMPTY_ASN_SET

    8.406.1. Severity

    ERROR

    8.406.2. Description

    Not available.

    +

    8.407. ZM_ERROR_ASN_DATABASE

    8.407.1. Severity

    ERROR

    8.407.2. Description

    Not available.

    +

    8.408. ZM_EXTRA_ADDRESS_CHILD

    8.408.1. Severity

    ERROR

    8.408.2. Description

    Not available.

    +

    8.409. ZM_IN_BAILIWICK_ADDR_MISMATCH

    8.409.1. Severity

    ERROR

    8.409.2. Description

    Not available.

    +

    8.410. ZM_IPV4_ONE_ASN

    8.410.1. Severity

    ERROR

    8.410.2. Description

    Not available.

    +

    8.411. ZM_IPV6_ONE_ASN

    8.411.1. Severity

    ERROR

    8.411.2. Description

    Not available.

    +

    8.412. ZM_IS_A_RECURSOR

    8.412.1. Severity

    ERROR

    8.412.2. Description

    Not available.

    +

    8.413. ZM_MISSING_OPT_IN_TRUNCATED

    8.413.1. Severity

    ERROR

    8.413.2. Description

    Not available.

    +

    8.414. ZM_MULTIPLE_NS_SET

    8.414.1. Severity

    ERROR

    8.414.2. Description

    Not available.

    +

    8.415. ZM_MULTIPLE_SOA

    8.415.1. Severity

    ERROR

    8.415.2. Description

    Not available.

    +

    8.416. ZM_MULTIPLE_SOA_MNAMES

    8.416.1. Severity

    ERROR

    8.416.2. Description

    Not available.

    +

    8.417. ZM_MULTIPLE_SOA_RNAMES

    8.417.1. Severity

    ERROR

    8.417.2. Description

    Not available.

    +

    8.418. ZM_MULTIPLE_SOA_TIME_PARAMETER_SET

    8.418.1. Severity

    ERROR

    8.418.2. Description

    Not available.

    +

    8.419. ZM_N10_EDNS_RESPONSE_ERROR

    8.419.1. Severity

    ERROR

    8.419.2. Description

    Expected RCODE value when EDNS ver=1, but error in response.

    +

    8.420. ZM_N10_NO_RESPONSE_EDNS1_QUERY

    8.420.1. Severity

    ERROR

    8.420.2. Description

    Response when EDNS ver=0, but not when 1.

    +

    8.421. ZM_N10_UNEXPECTED_RCODE

    8.421.1. Severity

    ERROR

    8.421.2. Description

    Unexpected RCODE value when EDNS ver=1.

    +

    8.422. ZM_N11_NO_EDNS

    8.422.1. Severity

    ERROR

    8.422.2. Description

    The DNS response, on query with unknown EDNS option-code, does not contain any EDNS from name servers “{ns_ip_list}”.

    -

    8.412. ZM_N11_NO_RESPONSE

    8.412.1. Severity

    ERROR

    8.412.2. Description

    There is no response on query with unknown EDNS option-code from name +

    8.423. ZM_N11_NO_RESPONSE

    8.423.1. Severity

    ERROR

    8.423.2. Description

    There is no response on query with unknown EDNS option-code from name servers “{ns_ip_list}”.

    -

    8.413. ZM_N11_RETURNS_UNKNOWN_OPTION_CODE

    8.413.1. Severity

    ERROR

    8.413.2. Description

    The DNS response, on query with unknown EDNS option-code, contains an +

    8.424. ZM_N11_RETURNS_UNKNOWN_OPTION_CODE

    8.424.1. Severity

    ERROR

    8.424.2. Description

    The DNS response, on query with unknown EDNS option-code, contains an unknown EDNS option-code from name servers “{ns_ip_list}”.

    -

    8.414. ZM_N11_UNEXPECTED_ANSWER_SECTION

    8.414.1. Severity

    ERROR

    8.414.2. Description

    The DNS response, on query with unknown EDNS option-code, does not +

    8.425. ZM_N11_UNEXPECTED_ANSWER_SECTION

    8.425.1. Severity

    ERROR

    8.425.2. Description

    The DNS response, on query with unknown EDNS option-code, does not contain the expected SOA record in the answer section from name servers “{ns_ip_list}”.

    -

    8.415. ZM_N11_UNEXPECTED_RCODE

    8.415.1. Severity

    ERROR

    8.415.2. Description

    The DNS response, on query with unknown EDNS option-code, has +

    8.426. ZM_N11_UNEXPECTED_RCODE

    8.426.1. Severity

    ERROR

    8.426.2. Description

    The DNS response, on query with unknown EDNS option-code, has unexpected RCODE name “{rcode}” from name servers “{ns_ip_list}”.

    -

    8.416. ZM_N11_UNSET_AA

    8.416.1. Severity

    ERROR

    8.416.2. Description

    The DNS response, on query with unknown EDNS option-code, is +

    8.427. ZM_N11_UNSET_AA

    8.427.1. Severity

    ERROR

    8.427.2. Description

    The DNS response, on query with unknown EDNS option-code, is unexpectedly not authoritative from name servers “{ns_ip_list}”.

    -

    8.417. ZM_NOT_ENOUGH_IPV4_NS_CHILD

    8.417.1. Severity

    ERROR

    8.417.2. Description

    Not available.

    -

    8.418. ZM_NOT_ENOUGH_IPV4_NS_DEL

    8.418.1. Severity

    ERROR

    8.418.2. Description

    Not available.

    -

    8.419. ZM_NOT_ENOUGH_IPV6_NS_CHILD

    8.419.1. Severity

    ERROR

    8.419.2. Description

    Not available.

    -

    8.420. ZM_NOT_ENOUGH_IPV6_NS_DEL

    8.420.1. Severity

    ERROR

    8.420.2. Description

    Not available.

    -

    8.421. ZM_NOT_ENOUGH_NS_CHILD

    8.421.1. Severity

    ERROR

    8.421.2. Description

    Not available.

    -

    8.422. ZM_NOT_ENOUGH_NS_DEL

    8.422.1. Severity

    ERROR

    8.422.2. Description

    Not available.

    -

    8.423. ZM_NO_EDNS_SUPPORT

    8.423.1. Severity

    ERROR

    8.423.2. Description

    Not available.

    -

    8.424. ZM_NO_IPV4_NS_CHILD

    8.424.1. Severity

    ERROR

    8.424.2. Description

    Not available.

    -

    8.425. ZM_NO_IPV4_NS_DEL

    8.425.1. Severity

    ERROR

    8.425.2. Description

    Not available.

    -

    8.426. ZM_NO_IPV6_NS_CHILD

    8.426.1. Severity

    ERROR

    8.426.2. Description

    Not available.

    -

    8.427. ZM_NO_IPV6_NS_DEL

    8.427.1. Severity

    ERROR

    8.427.2. Description

    Not available.

    -

    8.428. ZM_NO_RESPONSE

    8.428.1. Severity

    ERROR

    8.428.2. Description

    Not available.

    -

    8.429. ZM_NO_RESPONSE_DNSKEY

    8.429.1. Severity

    ERROR

    8.429.2. Description

    Not available.

    -

    8.430. ZM_NO_RESPONSE_NS_QUERY

    8.430.1. Severity

    ERROR

    8.430.2. Description

    Not available.

    -

    8.431. ZM_NO_RESPONSE_SOA_QUERY

    8.431.1. Severity

    ERROR

    8.431.2. Description

    Not available.

    -

    8.432. ZM_NO_SOA_IN_RESPONSE

    8.432.1. Severity

    ERROR

    8.432.2. Description

    Not available.

    -

    8.433. ZM_NS_ERROR

    8.433.1. Severity

    ERROR

    8.433.2. Description

    Not available.

    -

    8.434. ZM_NS_IS_CNAME

    8.434.1. Severity

    ERROR

    8.434.2. Description

    Not available.

    -

    8.435. ZM_OUT_OF_BAILIWICK_ADDR_MISMATCH

    8.435.1. Severity

    ERROR

    8.435.2. Description

    Not available.

    -

    8.436. ZM_REFERRAL_SIZE_TOO_LARGE

    8.436.1. Severity

    ERROR

    8.436.2. Description

    Not available.

    -

    8.437. ZM_RNAME_MAIL_DOMAIN_INVALID

    8.437.1. Severity

    ERROR

    8.437.2. Description

    Not available.

    -

    8.438. ZM_RNAME_MAIL_DOMAIN_LOCALHOST

    8.438.1. Severity

    ERROR

    8.438.2. Description

    Not available.

    -

    8.439. ZM_RNAME_MAIL_ILLEGAL_CNAME

    8.439.1. Severity

    ERROR

    8.439.2. Description

    Not available.

    -

    8.440. ZM_RNAME_RFC822_INVALID

    8.440.1. Severity

    ERROR

    8.440.2. Description

    Not available.

    -

    8.441. ZM_UNEXPECTED_RCODE

    8.441.1. Severity

    WARNING

    8.441.2. Description

    Not available.

    -

    8.442. ZM_UNKNOWN_OPTION_CODE

    8.442.1. Severity

    ERROR

    8.442.2. Description

    Not available.

    -

    8.443. ZM_UNSUPPORTED_EDNS_VER

    8.443.1. Severity

    ERROR

    8.443.2. Description

    Not available.

    -

    8.444. ZM_WRONG_SOA

    8.444.1. Severity

    ERROR

    8.444.2. Description

    Not available.

    -

    8.445. ZM_Z_FLAGS_NOTCLEAR

    8.445.1. Severity

    ERROR

    8.445.2. Description

    Not available.

    +

    8.428. ZM_NOT_ENOUGH_IPV4_NS_CHILD

    8.428.1. Severity

    ERROR

    8.428.2. Description

    Not available.

    +

    8.429. ZM_NOT_ENOUGH_IPV4_NS_DEL

    8.429.1. Severity

    ERROR

    8.429.2. Description

    Not available.

    +

    8.430. ZM_NOT_ENOUGH_IPV6_NS_CHILD

    8.430.1. Severity

    ERROR

    8.430.2. Description

    Not available.

    +

    8.431. ZM_NOT_ENOUGH_IPV6_NS_DEL

    8.431.1. Severity

    ERROR

    8.431.2. Description

    Not available.

    +

    8.432. ZM_NOT_ENOUGH_NS_CHILD

    8.432.1. Severity

    ERROR

    8.432.2. Description

    Not available.

    +

    8.433. ZM_NOT_ENOUGH_NS_DEL

    8.433.1. Severity

    ERROR

    8.433.2. Description

    Not available.

    +

    8.434. ZM_NO_EDNS_SUPPORT

    8.434.1. Severity

    ERROR

    8.434.2. Description

    Not available.

    +

    8.435. ZM_NO_IPV4_NS_CHILD

    8.435.1. Severity

    ERROR

    8.435.2. Description

    Not available.

    +

    8.436. ZM_NO_IPV4_NS_DEL

    8.436.1. Severity

    ERROR

    8.436.2. Description

    Not available.

    +

    8.437. ZM_NO_IPV6_NS_CHILD

    8.437.1. Severity

    ERROR

    8.437.2. Description

    Not available.

    +

    8.438. ZM_NO_IPV6_NS_DEL

    8.438.1. Severity

    ERROR

    8.438.2. Description

    Not available.

    +

    8.439. ZM_NO_RESPONSE

    8.439.1. Severity

    ERROR

    8.439.2. Description

    Not available.

    +

    8.440. ZM_NO_RESPONSE_DNSKEY

    8.440.1. Severity

    ERROR

    8.440.2. Description

    Not available.

    +

    8.441. ZM_NO_RESPONSE_NS_QUERY

    8.441.1. Severity

    ERROR

    8.441.2. Description

    Not available.

    +

    8.442. ZM_NO_RESPONSE_SOA_QUERY

    8.442.1. Severity

    ERROR

    8.442.2. Description

    Not available.

    +

    8.443. ZM_NO_SOA_IN_RESPONSE

    8.443.1. Severity

    ERROR

    8.443.2. Description

    Not available.

    +

    8.444. ZM_NS_ERROR

    8.444.1. Severity

    ERROR

    8.444.2. Description

    Not available.

    +

    8.445. ZM_NS_IS_CNAME

    8.445.1. Severity

    ERROR

    8.445.2. Description

    Not available.

    +

    8.446. ZM_OUT_OF_BAILIWICK_ADDR_MISMATCH

    8.446.1. Severity

    ERROR

    8.446.2. Description

    Not available.

    +

    8.447. ZM_REFERRAL_SIZE_TOO_LARGE

    8.447.1. Severity

    ERROR

    8.447.2. Description

    Not available.

    +

    8.448. ZM_RNAME_MAIL_DOMAIN_INVALID

    8.448.1. Severity

    ERROR

    8.448.2. Description

    Not available.

    +

    8.449. ZM_RNAME_MAIL_DOMAIN_LOCALHOST

    8.449.1. Severity

    ERROR

    8.449.2. Description

    Not available.

    +

    8.450. ZM_RNAME_MAIL_ILLEGAL_CNAME

    8.450.1. Severity

    ERROR

    8.450.2. Description

    Not available.

    +

    8.451. ZM_RNAME_RFC822_INVALID

    8.451.1. Severity

    ERROR

    8.451.2. Description

    Not available.

    +

    8.452. ZM_UNEXPECTED_RCODE

    8.452.1. Severity

    WARNING

    8.452.2. Description

    Not available.

    +

    8.453. ZM_UNKNOWN_OPTION_CODE

    8.453.1. Severity

    ERROR

    8.453.2. Description

    Not available.

    +

    8.454. ZM_UNSUPPORTED_EDNS_VER

    8.454.1. Severity

    ERROR

    8.454.2. Description

    Not available.

    +

    8.455. ZM_WRONG_SOA

    8.455.1. Severity

    ERROR

    8.455.2. Description

    Not available.

    +

    8.456. ZM_Z_FLAGS_NOTCLEAR

    8.456.1. Severity

    ERROR

    8.456.2. Description

    Not available.

    9. About this document

    This document was automatically generated from the formal specification for the RST system, which is available in YAML diff --git a/rst-test-specs.json b/rst-test-specs.json index 8124b38..010fc5a 100644 --- a/rst-test-specs.json +++ b/rst-test-specs.json @@ -341,6 +341,46 @@ "Description" : "TBA", "Severity" : "ERROR" }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_ATTRIBUTE" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_OBJECT" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_ATTRIBUTE" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_OBJECT" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_REGISTRANT" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, "EPP_GENERIC_COMMAND_ERROR" : { "Description" : "The client received a 2400 error from the server.", "Severity" : "ERROR" @@ -529,6 +569,10 @@ "Description" : "The response from the server failed schema validation.", "Severity" : "ERROR" }, + "EPP_SERVICE_PORT_NOT_CONSISTENT" : { + "Description" : "TBA", + "Severity" : "ERROR" + }, "EPP_SERVICE_PORT_UNREACHABLE" : { "Description" : "The EPP service port (tcp/700) could not be connected to.", "Severity" : "ERROR" @@ -2907,7 +2951,7 @@ "EPP_DOMAIN_CHECK_INVALID_DOMAIN_INCORRECT_AVAIL", "EPP_DOMAIN_CHECK_REGISTERED_DOMAIN_INCORRECT_AVAIL" ], - "Summary" : "domain command test" + "Summary" : "Domain command test" }, "epp-05" : { "Dependencies" : [ @@ -2922,7 +2966,7 @@ "Input-Parameters" : [ "epp.registeredNameservers" ], - "Summary" : "host command test (if applicable)" + "Summary" : "Host command test (if applicable)" }, "epp-06" : { "Dependencies" : [ @@ -2937,7 +2981,7 @@ "Input-Parameters" : [ "epp.registeredContacts" ], - "Summary" : "contact command test (if applicable for the registry type)" + "Summary" : "Contact command test (if applicable for the registry type)" }, "epp-07" : { "Dependencies" : [ @@ -2965,7 +3009,7 @@ "EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE", "EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL" ], - "Summary" : "contact command test (if applicable for the registry type)" + "Summary" : "Contact command test (if applicable for the registry type)" }, "epp-08" : { "Dependencies" : [ @@ -3008,19 +3052,19 @@ "EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE", "EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL" ], - "Summary" : "contact command test (if applicable for the registry type)" + "Summary" : "Contact command test (if applicable for the registry type)" }, "epp-10" : { "Dependencies" : [ "epp-09" ], - "Description" : "This test will perform `` commands on the objects created during\n`epp-22` and will confirm that the server accepts the `` command\nwith a `1xxx` response code.\n\nIf the `general.minimalPublicDataSet` input parameter is `true`, this\ntest will be skipped.\n\nOnce the `` commands have been submitted, the client will perform\n`` commands to confirm that the objects have actually been removed\nfrom the repository. If the response to the previous `` command\nwas 1001, this step will be skipped.\n", + "Description" : "This test will perform `` commands on the objects created during\n`epp-24` and will confirm that the server accepts the `` command\nwith a `1xxx` response code.\n\nIf the `general.minimalPublicDataSet` input parameter is `true`, this\ntest will be skipped.\n\nOnce the `` commands have been submitted, the client will perform\n`` commands to confirm that the objects have actually been removed\nfrom the repository. If the response to the previous `` command\nwas 1001, this step will be skipped.\n", "Errors" : [ "EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001", "EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS" ], "Input-Parameters" : null, - "Summary" : "contact command test (if applicable for the registry type)" + "Summary" : "Contact command test (if applicable for the registry type)" }, "epp-11" : { "Description" : "This test attempts to create a number of host objects, and validates\nthe server's response. For example, the test will expect that the server\nwill reject a command that creates an object with missing or invalid\nproperties, but will accept a command to create an object with valid\nproperties. Property values will be randomly generated but will contain\nrealistic values. No personal information will be transmitted as part\nof this test.\n\nIf the `epp.hostModel` input parameter is `attributes`, this test will\nbe skipped.\n\nThe test will confirm that the server checks and validates the values of\nthe following elements:\n\n* `` (both in- and out-of-bailiwick, for each TLD in the TLD\n set)\n* ``\n* `` elements (both IPv4 and IPv6)\n\nIf the `epp.hostModel` input parameter is `attributes`, this test will\nbe skipped.\n\nThe client will then perform `` commands on the objects successfully\ncreated to confirm that the server has correctly stored the provided\nvalues.\n", @@ -3042,7 +3086,7 @@ "Errors" : [ "EPP_HOST_UPDATE_AUTHZ_ERROR" ], - "Summary" : "host object access control (if applicable)" + "Summary" : "Host object access control (if applicable)" }, "epp-13" : { "Dependencies" : [ @@ -3057,7 +3101,7 @@ "EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST", "EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES" ], - "Summary" : "host command test (if applicable)" + "Summary" : "Host command test (if applicable)" }, "epp-14" : { "Dependencies" : [ @@ -3084,7 +3128,7 @@ "Input-Parameters" : [ "epp.secDNSInterfaces" ], - "Summary" : "domain command test" + "Summary" : "Domain command test" }, "epp-15" : { "Dependencies" : [ @@ -3098,6 +3142,36 @@ "Summary" : "Registry object integrity test" }, "epp-16" : { + "Dependencies" : [ + "epp-14" + ], + "Description" : "This test will confirm that the client is able to perform an ``\ncommand on the domain names created in `epp-14`, including:\n\n* adding and removing client-assigned status codes\n* adding and removing nameservers (whether objects or attributes)\n* changing registrant object (if applicable)\n* adding and remove DNSSEC information\n\nThe client will also confirm that it cannot perform an `` command\non a domain sponsored by another registrar, and that the server responds\nwith a `2201` authorization error.\n\nOnce the `` commands have been processed, the client will then\nperform `` commands to confirm that the changes have been correctly\nstored by the server.\n", + "Errors" : [ + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_OBJECT", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_OBJECT", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_ATTRIBUTE", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_ATTRIBUTE", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_REGISTRANT", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA", + "EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA" + ], + "Input-Parameters" : null, + "Summary" : "Domain command test" + }, + "epp-17" : { + "Dependencies" : [ + "epp-14" + ], + "Description" : "This test confirms that all EPP service ports respond with consistent object\ninformation.\n\nThe client will establish seperate connections to each EPP service port\n(defined as an IP address and TCP port) and perform `` commands on the\nobjects created in `epp-14`. In all cases, the server **MUST** respond with\na `1000` response and the content of the `` element **MUST** be\nidentical on all service ports.\n", + "Errors" : [ + "EPP_SERVICE_PORT_NOT_CONSISTENT" + ], + "Summary" : "Service Port consistency test" + }, + "epp-18" : { "Dependencies" : [ "epp-14" ], @@ -3108,9 +3182,9 @@ "EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE", "EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS" ], - "Summary" : "domain command test" + "Summary" : "Domain command test" }, - "epp-17" : { + "epp-19" : { "Dependencies" : [ "epp-14" ], @@ -3126,19 +3200,19 @@ "EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS", "EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET" ], - "Summary" : "domain command test" + "Summary" : "Domain command test" }, - "epp-18" : { + "epp-20" : { "Dependencies" : [ "epp-14" ], - "Description" : "This test confirms that the server behaves correctly if the sponsoring registrar of a domain rejects a transfer request.\nThe test procedure matches that of `epp-17`, but the transfer request will be rejected rather than approved. An `` command will be used to confirm that the domain name remains under the sponsorship of the original registrar.", + "Description" : "This test confirms that the server behaves correctly if the sponsoring registrar of a domain rejects a transfer request.\nThe test procedure matches that of `epp-19`, but the transfer request will be rejected rather than approved. An `` command will be used to confirm that the domain name remains under the sponsorship of the original registrar.", "Errors" : [ "EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER" ], - "Summary" : "domain rejection test" + "Summary" : "Domain rejection test" }, - "epp-19" : { + "epp-21" : { "Dependencies" : [ "epp-14" ], @@ -3148,22 +3222,22 @@ "EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE", "EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE" ], - "Summary" : "domain command test" + "Summary" : "Domain command test" }, - "epp-20" : { + "epp-22" : { "Dependencies" : [ - "epp-19" + "epp-21" ], - "Description" : "This test will perform RGP restore operations on the objects deleted\nduring `epp-19`, in order to confirm the correct operation of the server's\nimplementation of RFC 3915.\n\nOnce the restore request has been procssed, the client will perform\n`` commands on the deleted to object to confirm that the domain no\nlonger has the `pendingDelete` status and RGP status.\n", + "Description" : "This test will perform RGP restore operations on the objects deleted\nduring `epp-21`, in order to confirm the correct operation of the server's\nimplementation of RFC 3915.\n\nOnce the restore request has been procssed, the client will perform\n`` commands on the deleted to object to confirm that the domain no\nlonger has the `pendingDelete` status and RGP status.\n", "Errors" : [ "EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE" ], "Input-Parameters" : [ "epp.restoreReportRequired" ], - "Summary" : "domain restore test" + "Summary" : "Domain restore test" }, - "epp-21" : { + "epp-23" : { "Dependencies" : [ "epp-14", "epp-11" @@ -3176,17 +3250,17 @@ "EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN", "EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME" ], - "Summary" : "host rename test (if applicable)" + "Summary" : "Host rename test (if applicable)" }, - "epp-22" : { + "epp-24" : { "Dependencies" : [ - "epp-21" + "epp-23" ], "Description" : "This test will perform `` commands on the objects created during\n`epp-11` and will confirm that the server accepts the `` command\nwith a `1xxx` response code.\n\nIf the `epp.hostModel` input parameter is `attributes`, this test will\nbe skipped.\n\nOnce the `` commands have been submitted, if a `1000` response was\nreceived from the server, the client will perform `` and ``\ncommands to confirm that the objects have been deleted.\n", "Errors" : [ "EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS" ], - "Summary" : "host command test (if applicable)" + "Summary" : "Host command test (if applicable)" }, "idn-01" : { "Description" : "This test confirms that the EPP server correctly accepts or rejects domain\n`` commands for valid and invalid IDN labels, respectively.\n\nIf there are no IDN tables supported under any of the TLDs associated with\nthe test, then this test will be skipped.\n\nFor each supported IDN table, the test client will perform a series of\n`` commands using a pre-defined catalogue of test labels. If\nrequired, the client will create any contact object(s) needed.\n\nThe server **MUST** reject all `` commands for invalid labels and\n**MUST** accept all `` commands for valid labels.\n", @@ -3216,16 +3290,24 @@ "Summary" : "Level 3 variant handling test" }, "integration-01" : { - "Dependencies" : [ - "epp-14", - "epp-11" - ], - "Description" : "This test confirms that the EPP and RDAP systems are properly integrated,\nthat is, that transform commands performed on objects in the EPP system\nare reflected in the RDAP system within the Service Level Requirement of\nthe SLA.\n\nThe test system will perform RDAP queries to confirm that the RDAP server\nprovides responses for the domains created in `epp-14`, and host objects\ncreated in `epp-11` (if applicable). The RDAP server **MUST** provide a 200\nresponse within 1 hour of the object's `` element.\n", + "Description" : "This test confirms that the EPP and RDAP systems are properly integrated,\nthat is, that transform commands performed on objects in the EPP system\nare reflected in the RDAP system within the Service Level Requirement of\nthe SLA.\n\nThe test system will connect to the EPP server and create domain and (if\napplicable) host and contact objects using the same methodology as `epp-14`\n`epp-11`. It will then perform RDAP queries for those objects.\n\nThe RDAP server **MUST** provide a 200 response for every object created\nwithin 1 hour of the object's `` element.\n", "Errors" : [ + "EPP_DNS_RESOLUTION_ERROR", + "EPP_SERVICE_PORT_UNREACHABLE", + "EPP_TLS_CONNECTION_ERROR", + "EPP_LOGIN_ERROR", + "EPP_XML_PARSE_ERROR", + "EPP_GENERIC_COMMAND_ERROR", + "EPP_UNEXPECTED_COMMAND_FAILURE", + "EPP_SCHEMA_VALIDATION_ERROR", "INTEGRATION_RDAP_REQUEST_FAILED", "INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP" ], "Input-Parameters" : [ + "epp.hostName", + "epp.serverIssuedClientCertificate01", + "epp.clid01", + "epp.pwd01", "epp.hostModel", "rdap.baseURLs" ], @@ -3234,9 +3316,9 @@ }, "integration-02" : { "Dependencies" : [ - "epp-14" + "integration-01" ], - "Description" : "This test confirms that the EPP and DNS systems are properly integrated,\nthat is, that transform commands performed on objects in the EPP system\nare reflected in the RDAP system within the Service Level Requirement of\nthe SLA.\n\nThe test system will perform DNS queries to confirm that the DNS servers\nprovides responses for the domain names created in `epp-14`. All DNS\nservers **MUST** provide the correct DNS response within 1 hour of the\nobject's `` element.\n", + "Description" : "This test confirms that the EPP and DNS systems are properly integrated,\nthat is, that transform commands performed on objects in the EPP system\nare reflected in the RDAP system within the Service Level Requirement of\nthe SLA.\n\nThe test system will perform DNS queries to confirm that the DNS servers\nprovide responses for the domain names created in `integration-01`. All DNS\nservers **MUST** provide the correct DNS response for all domains within 1\nhour of the domains's `` element.\n", "Errors" : [ "INTEGRATION_DNS_QUERY_FAILED", "INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS", @@ -3250,10 +3332,9 @@ }, "integration-03" : { "Dependencies" : [ - "epp-14", - "epp-11" + "integration-01" ], - "Description" : "This test confirms that the EPP and RDE systems are properly integrated,\nthat is, that objects created in the EPP system are reflected in a valid\nRDE deposit file within the Service Level Requirement of the SLA.\n\nThe test system will periodically connect to the SFTP server specified by\nthe `integration.rdeSFTPHostname` input parameter, using the username\nspecified in the `integration.rdeSFTPUsername` input parameter and the SSH\nkey in the `integration.rdeSFTPPublicKey` resource, and look for .ryde\nfiles in the directory specified by the `integration.rdeSFTPDirectory`\ninput parameter. Note that operators **MUST** ensure that the IP addresses\nlisted in the `integration.rdeSFTPACL` resource have been added to the\nAccess Control List for the SFTP server (if any).\n\nAll objects created in the `epp-14` and `epp-11` (if applicable) tests\n**MUST** be found within a valid RDE deposit file (that is, the deposit\npasses all the tests in the RDE test suite) within 24 hours of each\nobject's `` element.\n\nFurthermore, for each deposit found in the directory, the corresponding\nRDE report (as described in [Section 2.1 of\ndraft-lozano-icann-registry-interfaces](https://datatracker.ietf.org/doc/html/draft-lozano-icann-registry-interfaces#section-2))\n**MUST** be recieved on the test RRI environment before 23:59:59 UTC on\nthe date specified in the Watermark element of the deposit file.\n\nTo facilitate submission of RDE reports, the RRI test environment will be\nconfigured to accept submissions for the TLDs associated with the test\nfrom clients using the same TLSA DNS hostnames that are configured for the\ntest.\n", + "Description" : "This test confirms that the EPP and RDE systems are properly integrated,\nthat is, that objects created in the EPP system are reflected in a valid\nRDE deposit file within the Service Level Requirement of the SLA.\n\nThe test system will periodically connect to the SFTP server specified by\nthe `integration.rdeSFTPHostname` input parameter, using the username\nspecified in the `integration.rdeSFTPUsername` input parameter and the SSH\nkey in the `integration.rdeSFTPPublicKey` resource, and look for .ryde\nfiles in the directory specified by the `integration.rdeSFTPDirectory`\ninput parameter. Note that operators **MUST** ensure that the IP addresses\nlisted in the `integration.rdeSFTPACL` resource have been added to the\nAccess Control List for the SFTP server (if any).\n\nAll objects created in the `integration-01` test case **MUST** be found\nwithin a valid RDE deposit file (that is, the deposit passes all the tests\nin the RDE test suite) within 24 hours of each object's `` element.\n\nFurthermore, for each deposit found in the directory, the corresponding\nRDE report (as described in [Section 2.1 of\ndraft-lozano-icann-registry-interfaces](https://datatracker.ietf.org/doc/html/draft-lozano-icann-registry-interfaces#section-2))\n**MUST** be recieved on the test RRI environment before 23:59:59 UTC on\nthe date specified in the Watermark element of the deposit file.\n\nTo facilitate submission of RDE reports, the RRI test environment will be\nconfigured to accept submissions for the TLDs associated with the test\nfrom clients using the same TLSA DNS hostnames that are configured for the\ntest.\n", "Errors" : [ "INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE", "INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR", @@ -3973,6 +4054,9 @@ }, "StandardIntegrationTest" : { "Description" : "This test suite verifies that the critical registry services of the TLD are\nproperly integrated and functioning within the requirements of the Service\nLevel Agreement.\n\n# Pass/fail criteria\n\nAs with all other [test suites](#test-suites), for this test suite to pass **all** the listed test cases **MUST** pass: if **any** fail, then the suite as a whole will fail.\n", + "Input-Parameters" : [ + "general.minimalPublicDataSet" + ], "Name" : "Standard Integration Test", "Order" : "10", "Test-Cases" : "^integration-" @@ -4056,5 +4140,5 @@ "Test-Cases" : "^srsgw-" } }, - "Version" : "3.0.263" + "Version" : "3.0.266" } diff --git a/rst-test-specs.yaml b/rst-test-specs.yaml index 3c27905..6f52234 100644 --- a/rst-test-specs.yaml +++ b/rst-test-specs.yaml @@ -1,6 +1,6 @@ --- RST-Test-Plan-Schema-Version: 1.6.1 -Version: 3.0.263 +Version: 3.0.266 Last-Updated: 2024-01-24 Contact: Name: GDS Technical Services @@ -738,6 +738,8 @@ Test-Suites: As with all other [test suites](#test-suites), for this test suite to pass **all** the listed test cases **MUST** pass: if **any** fail, then the suite as a whole will fail. Test-Cases: ^integration- + Input-Parameters: + - general.minimalPublicDataSet Resources: rde.encryptionKey: @@ -2782,6 +2784,7 @@ Test-Cases: - EPP_TLS_CERTIFICATE_CHAIN_MISSING - EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH - EPP_TLS_BAD_CIPHER + epp-02: Summary: Protocol conformance test Description: | @@ -2828,6 +2831,7 @@ Test-Cases: - EPP_GREETING_DOES_NOT_MATCH Input-Parameters: Dependencies: + epp-03: Summary: Authentication test Description: | @@ -2852,8 +2856,9 @@ Test-Cases: Input-Parameters: Resources: Errors: + epp-04: - Summary: domain command test + Summary: Domain command test Description: | The client will perform a series of `` commands and will validate the `avail` attribute of the `` elements in the server @@ -2877,8 +2882,9 @@ Test-Cases: - EPP_DOMAIN_CHECK_VALID_DOMAIN_INCORRECT_AVAIL - EPP_DOMAIN_CHECK_INVALID_DOMAIN_INCORRECT_AVAIL - EPP_DOMAIN_CHECK_REGISTERED_DOMAIN_INCORRECT_AVAIL + epp-05: - Summary: host command test (if applicable) + Summary: Host command test (if applicable) Description: | If the EPP server supports host objects, this test will perform a series of `` commands and will validate the `avail` attribute of the @@ -2902,8 +2908,9 @@ Test-Cases: - EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL - EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL - EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL + epp-06: - Summary: contact command test (if applicable for the registry type) + Summary: Contact command test (if applicable for the registry type) Description: | If the EPP server supports contact objects, this test will perform a series of `` commands and will validate the `avail` attribute of @@ -2923,8 +2930,9 @@ Test-Cases: - EPP_CONTACT_CHECK_VALID_CONTACT_ID_INCORRECT_AVAIL - EPP_CONTACT_CHECK_INVALID_CONTACT_ID_INCORRECT_AVAIL - EPP_CONTACT_CHECK_REGISTERED_CONTACT_ID_INCORRECT_AVAIL + epp-07: - Summary: contact command test (if applicable for the registry type) + Summary: Contact command test (if applicable for the registry type) Description: | This test attempts to create a number of contact objects, and validates the server's response. For example, the test will expect that the server @@ -2987,6 +2995,7 @@ Test-Cases: - EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC - EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE - EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL + epp-08: Summary: Contact object access control (if applicable) Description: | @@ -3005,8 +3014,9 @@ Test-Cases: Errors: - EPP_CONTACT_INFO_RESPONSE_NOT_2201 - EPP_CONTACT_UPDATE_RESPONSE_NOT_2201 + epp-09: - Summary: contact command test (if applicable for the registry type) + Summary: Contact command test (if applicable for the registry type) Description: | This test will perform `` commands on the objects created during `epp-07` and will confirm that the server correctly rejects invalid @@ -3061,11 +3071,12 @@ Test-Cases: - EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC - EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE - EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL + epp-10: - Summary: contact command test (if applicable for the registry type) + Summary: Contact command test (if applicable for the registry type) Description: | This test will perform `` commands on the objects created during - `epp-22` and will confirm that the server accepts the `` command + `epp-24` and will confirm that the server accepts the `` command with a `1xxx` response code. If the `general.minimalPublicDataSet` input parameter is `true`, this @@ -3081,6 +3092,7 @@ Test-Cases: Errors: - EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001 - EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS + epp-11: Summary: host command test (if applicable) Description: | @@ -3116,8 +3128,9 @@ Test-Cases: - EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE - EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST - EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES + epp-12: - Summary: host object access control (if applicable) + Summary: Host object access control (if applicable) Description: | This test will confirm that EPP clients are unable to perform `` commands on objects that they do not sponsor. @@ -3132,8 +3145,9 @@ Test-Cases: - epp-11 Errors: - EPP_HOST_UPDATE_AUTHZ_ERROR + epp-13: - Summary: host command test (if applicable) + Summary: Host command test (if applicable) Description: | This test will perform `` commands on the objects created during `epp-11` and will confirm that the server correctly rejects invalid @@ -3164,8 +3178,9 @@ Test-Cases: - EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE - EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST - EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES + epp-14: - Summary: domain command test + Summary: Domain command test Description: | This test performs a series domain `` commands, using pseudo- random ASCII domain names under each TLD in the TLD set. If the @@ -3238,6 +3253,7 @@ Test-Cases: - EPP_DOMAIN_CREATE_SERVER_ACCEPTS_AUTHINFO - EPP_DOMAIN_CREATE_INFO_RESPONSE_INVALID_ROID - EPP_DOMAIN_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES + epp-15: Summary: Registry object integrity test Description: | @@ -3256,8 +3272,9 @@ Test-Cases: Errors: - EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT - EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT + epp-16: - Summary: domain command test + Summary: Domain command test Description: | This test will confirm that the client is able to perform an `` command on the domain names created in `epp-14`, including: @@ -3288,8 +3305,25 @@ Test-Cases: - EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT - EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA - EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA - epp-16: - Summary: domain command test + + epp-17: + Summary: Service Port consistency test + Description: | + This test confirms that all EPP service ports respond with consistent object + information. + + The client will establish seperate connections to each EPP service port + (defined as an IP address and TCP port) and perform `` commands on the + objects created in `epp-14`. In all cases, the server **MUST** respond with + a `1000` response and the content of the `` element **MUST** be + identical on all service ports. + Dependencies: + - epp-14 + Errors: + - EPP_SERVICE_PORT_NOT_CONSISTENT + + epp-18: + Summary: Domain command test Description: | This test will confirm that the client is able to renew domain names. The client will submit a number of `` commands for the domains created in @@ -3312,8 +3346,8 @@ Test-Cases: - EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE - EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS - epp-17: - Summary: domain command test + epp-19: + Summary: Domain command test Description: | This test will confirm that the client is able to initiate a domain transfer. @@ -3367,13 +3401,13 @@ Test-Cases: - EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS - EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET - epp-18: - Summary: domain rejection test + epp-20: + Summary: Domain rejection test Description: This test confirms that the server behaves correctly if the sponsoring registrar of a domain rejects a transfer request. - The test procedure matches that of `epp-17`, but the transfer request will + The test procedure matches that of `epp-19`, but the transfer request will be rejected rather than approved. An `` command will be used to confirm that the domain name remains under the sponsorship of the original registrar. @@ -3382,8 +3416,8 @@ Test-Cases: Errors: - EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER - epp-19: - Summary: domain command test + epp-21: + Summary: Domain command test Description: | This test will perform `` commands on the objects created during `epp-14` and will confirm that the server accepts the `` command @@ -3404,11 +3438,11 @@ Test-Cases: - EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE - EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE - epp-20: - Summary: domain restore test + epp-22: + Summary: Domain restore test Description: | This test will perform RGP restore operations on the objects deleted - during `epp-19`, in order to confirm the correct operation of the server's + during `epp-21`, in order to confirm the correct operation of the server's implementation of RFC 3915. Once the restore request has been procssed, the client will perform @@ -3417,12 +3451,12 @@ Test-Cases: Input-Parameters: - epp.restoreReportRequired Dependencies: - - epp-19 + - epp-21 Errors: - EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE - epp-21: - Summary: host rename test (if applicable) + epp-23: + Summary: Host rename test (if applicable) Description: | This tests verifies the server's support for host rename operations. @@ -3459,8 +3493,8 @@ Test-Cases: - EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN - EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME - epp-22: - Summary: host command test (if applicable) + epp-24: + Summary: Host command test (if applicable) Description: | This test will perform `` commands on the objects created during `epp-11` and will confirm that the server accepts the `` command @@ -3473,7 +3507,7 @@ Test-Cases: received from the server, the client will perform `` and `` commands to confirm that the objects have been deleted. Dependencies: - - epp-21 + - epp-23 Errors: - EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS rdap-01-domainCaseFoldingValidation: @@ -4213,17 +4247,28 @@ Test-Cases: are reflected in the RDAP system within the Service Level Requirement of the SLA. - The test system will perform RDAP queries to confirm that the RDAP server - provides responses for the domains created in `epp-14`, and host objects - created in `epp-11` (if applicable). The RDAP server **MUST** provide a 200 - response within 1 hour of the object's `` element. + The test system will connect to the EPP server and create domain and (if + applicable) host and contact objects using the same methodology as `epp-14` + `epp-11`. It will then perform RDAP queries for those objects. + + The RDAP server **MUST** provide a 200 response for every object created + within 1 hour of the object's `` element. Input-Parameters: + - epp.hostName + - epp.serverIssuedClientCertificate01 + - epp.clid01 + - epp.pwd01 - epp.hostModel - rdap.baseURLs - Dependencies: - - epp-14 - - epp-11 Errors: + - EPP_DNS_RESOLUTION_ERROR + - EPP_SERVICE_PORT_UNREACHABLE + - EPP_TLS_CONNECTION_ERROR + - EPP_LOGIN_ERROR + - EPP_XML_PARSE_ERROR + - EPP_GENERIC_COMMAND_ERROR + - EPP_UNEXPECTED_COMMAND_FAILURE + - EPP_SCHEMA_VALIDATION_ERROR - INTEGRATION_RDAP_REQUEST_FAILED - INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP integration-02: @@ -4236,13 +4281,13 @@ Test-Cases: the SLA. The test system will perform DNS queries to confirm that the DNS servers - provides responses for the domain names created in `epp-14`. All DNS - servers **MUST** provide the correct DNS response within 1 hour of the - object's `` element. + provide responses for the domain names created in `integration-01`. All DNS + servers **MUST** provide the correct DNS response for all domains within 1 + hour of the domains's `` element. Input-Parameters: - dns.nameservers Dependencies: - - epp-14 + - integration-01 Errors: - INTEGRATION_DNS_QUERY_FAILED - INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS @@ -4264,10 +4309,9 @@ Test-Cases: listed in the `integration.rdeSFTPACL` resource have been added to the Access Control List for the SFTP server (if any). - All objects created in the `epp-14` and `epp-11` (if applicable) tests - **MUST** be found within a valid RDE deposit file (that is, the deposit - passes all the tests in the RDE test suite) within 24 hours of each - object's `` element. + All objects created in the `integration-01` test case **MUST** be found + within a valid RDE deposit file (that is, the deposit passes all the tests + in the RDE test suite) within 24 hours of each object's `` element. Furthermore, for each deposit found in the directory, the corresponding RDE report (as described in [Section 2.1 of @@ -4288,8 +4332,7 @@ Test-Cases: - integration.rdeSFTPUsername - integration.rriACL Dependencies: - - epp-14 - - epp-11 + - integration-01 Errors: - INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE - INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR @@ -7336,6 +7379,51 @@ Errors: EPP_GREETING_DOES_NOT_MATCH: Severity: ERROR Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_OBJECT: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_OBJECT: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_HOST_ATTRIBUTE: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_HOST_ATTRIBUTE: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_REGISTRANT: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_REGISTRANT: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_DNSSEC_DATA: + Severity: ERROR + Description: TBA + + EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_DNSSEC_DATA: + Severity: ERROR + Description: TBA + + EPP_SERVICE_PORT_NOT_CONSISTENT: + Severity: ERROR + Description: TBA + RPMS_MISSING_CLAIMS_KEY: Severity: ERROR Description: TBA.