From be6aebf4626c0905a52e56c6dadf6e45ac145547 Mon Sep 17 00:00:00 2001 From: Gavin Brown Date: Thu, 11 Jan 2024 13:44:58 +0000 Subject: [PATCH] updated --- rst-test-specs.html | 3863 +++++++++++++++++++++---------------------- rst-test-specs.json | 247 ++- rst-test-specs.yaml | 413 +++-- 3 files changed, 2345 insertions(+), 2178 deletions(-) diff --git a/rst-test-specs.html b/rst-test-specs.html index 5788c67..91f2fc2 100644 --- a/rst-test-specs.html +++ b/rst-test-specs.html @@ -168,7 +168,7 @@ -

Registry System Testing - Test Specifications

Version 3.0.244

+

Registry System Testing - Test Specifications

Version 3.0.253

Last Updated: 2024-01-11

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

    Registry System Testing - Test Specifications

    Version 3.0.244

    gTLD Applicant Guidebook (AGB). Each applicant will be required to complete PDT as a prerequisite to delegation into the root zone.

    The Pre-Delegation Test covers all critical registry services and -IDNs, and therefore uses all test suites.

    +IDNs, and therefore uses all standard test suites.

    Note on test environment: this is a “business as usual” test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided MUST relate to @@ -1505,18 +1505,18 @@

    Pass/fail criteria

    - - -epp-16 -     + + +epp-14 + -epp-16 +epp-14 - - -epp-03->epp-16 + + +epp-03->epp-14 @@ -1655,890 +1655,860 @@

    Pass/fail criteria

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

    Pass/fail criteria

    systems comply with the technical and operational requirements of the Registry Agreement.

    The RSP Change Test covers all critical registry services and IDNs, -and therefore uses all test suites.

    +and therefore uses all test standard suites.

    Note on test environment: this is a “business as usual” test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided MUST relate to @@ -3636,18 +3606,18 @@

    Pass/fail criteria

     - - -epp-16 - + + +epp-14 + -epp-16 +epp-14 - - -epp-03->epp-16 + + +epp-03->epp-14 @@ -3786,890 +3756,860 @@

    Pass/fail criteria

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

    Pass/fail criteria

    3.5. IDN Test (RSP Evaluation)

    3.5.1. Description

    This test plan is identical to the Standard IDN Test, but is intended -solely for use by the RSP evaluation program.

    +solely for use in the RSP evaluation program.

    Note on test environment: this is a “business as usual” test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided MUST relate to @@ -6290,18 +6230,18 @@

    Pass/fail criteria

    - - -epp-16 - + + +epp-14 + -epp-16 +epp-14 - - -epp-03->epp-16 + + +epp-03->epp-14 @@ -6440,818 +6380,788 @@

    Pass/fail criteria

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

    Pass/fail criteria

    1. DNS Security Extensions (DNSSEC)
    2. DNSSEC Operations

    3.9.4. Resources

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

    • None specified.

    3.9.5. Errors

    This test plan may produce the following errors:

    -

    3.9.6. Input parameters

    This plan requires the following input parameters:

    -

    3.9.7. Required files

    • None specified.

    3.9.8. RST-API example

    POST /test/987654/inputs HTTP/1.1
+

    3.9.6. Input parameters

    This plan requires the following input parameters:

    +

    3.9.7. Required files

    • None specified.

    3.9.8. RST-API example

    POST /test/987654/inputs HTTP/1.1
 Content-Type: application/json
-Content-Length: 647
+Content-Length: 1085
 
 {
    "dns.nameservers" : {
@@ -8012,6 +7922,24 @@ 
    Pass/fail criteria
    
    "dnssecOps.algorithmRolloverZone" : "example.com",
    "dnssecOps.csk" : false,
    "dnssecOps.kskRolloverZone" : "example.com",
+   "dnssecOps.nameservers" : {
+      "example" : {
+         "ns1.example.com" : [
+            "192.168.53.1",
+            "2001:DB8::53:1"
+         ],
+         "ns2.example.com" : [
+            "192.168.53.2",
+            "2001:DB8::53:2"
+         ]
+      }
+   },
+   "dnssecOps.primaryServer" : "192.168.53.1",
+   "dnssecOps.tsigKey" : {
+      "algorithm" : "hmac-sha256",
+      "name" : "rst-tsig-01",
+      "secret" : "NQO...xQ="
+   },
    "dnssecOps.zskRolloverZone" : "example.com"
 }

    3.9.9. Sequence diagram

     @@ -8344,10 +8272,11 @@

    Pass/fail criteria

    The SRS Gateway test suite requires access to a primary registry system that is logically independent of the SRS Gateway system, and details of the primary -registry system are required as input parameters. RSPs wishing to offer -SRS gateway services MUST identify such a primary -registry system, which MUST be independent of the SRS -gateway system, and MAY be operated by a third party.

    +registry system are required as input parameters.

    +

    RSPs wishing to offer SRS gateway services MUST +identify such a primary registry system, which MUST be +independent of the SRS gateway system, and MAY be +operated by a third party.

    Note on test environment: this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters MAY be provided the relate to a test, @@ -9651,7 +9580,7 @@

    Pass/fail criteria

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

    4.3.2. Test cases

    This suite uses the following test cases:

    -
    1. rdap-01-domainCaseFoldingValidation - Domain label case folding validation
    2. rdap-02-domainNameValidation - Domain Name validation
    3. rdap-03-ipv4Validation - IPv4 address validation
    4. rdap-04-ipv6Validation - IPv6 address validation
    5. rdap-05-stdRdapAsEventActorValidation - asEventActor Validation
    6. rdap-06-stdRdapConformanceValidation - RDAP Conformance validation
    7. rdap-07-stdRdapDomainLookupValidation - Domain Lookup Validation
    8. rdap-08-stdRdapEntitiesValidation - Entities validation
    9. rdap-09-stdRdapEntityLookupValidation - Entity lookup validation
    10. rdap-10-stdRdapErrorResponseBodyValidation - Error Response Body
    11. rdap-11-stdRdapEventsValidation - Events Validation
    12. rdap-12-stdRdapHelpValidation - Help validation
    13. rdap-13-stdRdapIpAddressesValidation - IP Addresses Validation
    14. rdap-14-stdRdapLanguageIdentifierValidation - Language Identifier Validation
    15. rdap-15-stdRdapLdhNameValidation - LDH name
    16. rdap-16-stdRdapLinksValidation - Links validation
    17. rdap-17-stdRdapNameserverLookupValidation - Nameserver lookup validation
    18. rdap-18-stdRdapNameserversSearchValidation - RFC7159RDAP_RFCsNameservers search validation
    19. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks Validation
    20. rdap-20-stdRdapPort43WhoisServerValidation - Port 43 WHOIS Server
    21. rdap-21-stdRdapPublicIdsValidation - Public IDs validation
    22. rdap-22-stdRdapRolesValidation - Roles validation
    23. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation
    24. rdap-24-stdRdapStatusValidation - Status validation
    25. rdap-25-stdRdapUnicodeNameValidation - RFC7159RDAP_RFCsIDNA_RFCsUnicode name
    26. rdap-26-stdRdapVariantsValidation - Variants validation
    27. rdap-27-webUriValidation - Web URI validation

    4.3.3. Test plans

    This suite is used by the following test plans:

    +
    1. rdap-01-domainCaseFoldingValidation - Domain label case folding validation
    2. rdap-02-domainNameValidation - Domain Name validation
    3. rdap-03-ipv4Validation - IPv4 address validation
    4. rdap-04-ipv6Validation - IPv6 address validation
    5. rdap-05-stdRdapAsEventActorValidation - asEventActor Validation
    6. rdap-06-stdRdapConformanceValidation - RDAP Conformance validation
    7. rdap-07-stdRdapDomainLookupValidation - Domain Lookup Validation
    8. rdap-08-stdRdapEntitiesValidation - Entities validation
    9. rdap-09-stdRdapEntityLookupValidation - Entity lookup validation
    10. rdap-10-stdRdapErrorResponseBodyValidation - Error Response Body
    11. rdap-11-stdRdapEventsValidation - Events Validation
    12. rdap-12-stdRdapHelpValidation - Help validation
    13. rdap-13-stdRdapIpAddressesValidation - IP Addresses Validation
    14. rdap-14-stdRdapLanguageIdentifierValidation - Language Identifier Validation
    15. rdap-15-stdRdapLdhNameValidation - LDH name
    16. rdap-16-stdRdapLinksValidation - Links validation
    17. rdap-17-stdRdapNameserverLookupValidation - Nameserver lookup validation
    18. rdap-18-stdRdapNameserversSearchValidation - Nameservers search validation
    19. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks Validation
    20. rdap-20-stdRdapPort43WhoisServerValidation - Port 43 WHOIS Server
    21. rdap-21-stdRdapPublicIdsValidation - Public IDs validation
    22. rdap-22-stdRdapRolesValidation - Roles validation
    23. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation
    24. rdap-24-stdRdapStatusValidation - Status validation
    25. rdap-25-stdRdapUnicodeNameValidation - Unicode name
    26. rdap-26-stdRdapVariantsValidation - Variants validation
    27. rdap-27-webUriValidation - Web URI validation

    4.3.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.3.4. Resources

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

    • None specified.

    4.3.5. Errors

    This test suite may produce the following errors:

    @@ -9920,7 +9849,7 @@

    Pass/fail criteria

    rdap-18-stdRdapNameserversSearchValidation - + rdap-18-stdRdapNameserversSearchValidation @@ -10025,7 +9954,7 @@

    Pass/fail criteria

    rdap-25-stdRdapUnicodeNameValidation - + rdap-25-stdRdapUnicodeNameValidation @@ -10079,7 +10008,7 @@

    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 - intentionally omitted
    15. epp-15 - intentionally omitted
    16. epp-16 - domain <create> command test
    17. epp-17 - Registry object integrity 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. 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. 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:

    @@ -10091,11 +10020,11 @@

    Pass/fail criteria

    - + Perl - + epp-01 @@ -10150,18 +10079,18 @@

    Pass/fail criteria

    - - -epp-16 - + + +epp-14 + -epp-16 +epp-14 - - -epp-03->epp-16 + + +epp-03->epp-14 @@ -10300,159 +10229,129 @@

    Pass/fail criteria

     - - -epp-23 - + + +epp-21 + -epp-23 +epp-21 - - -epp-11->epp-23 + + +epp-11->epp-21 - - -epp-14 - - -epp-14 - - - - - -epp-13->epp-14 - - - epp-15 - - -epp-15 + + +epp-15 epp-14->epp-15 - - - - - -epp-17 - - -epp-17 - - - - - -epp-16->epp-17 - - -epp-18 - + + +epp-16 + -epp-18 +epp-16 - - -epp-16->epp-18 + + +epp-14->epp-16 - - -epp-19 - + + +epp-17 + -epp-19 +epp-17 - - -epp-16->epp-19 + + +epp-14->epp-17 - - -epp-20 - + + +epp-18 + -epp-20 +epp-18 - - -epp-16->epp-20 + + +epp-14->epp-18 - - -epp-21 - + + +epp-19 + -epp-21 +epp-19 - - -epp-16->epp-21 + + +epp-14->epp-19 - - -epp-16->epp-23 + + +epp-14->epp-21 - - -epp-22 - + + +epp-20 + -epp-22 +epp-20 - - -epp-21->epp-22 + + +epp-19->epp-20 - - -epp-24 - + + +epp-22 + -epp-24 +epp-22 - - -epp-23->epp-24 + + +epp-21->epp-22 @@ -11039,9 +10938,9 @@

    Pass/fail criteria

    1. DNSSEC RSP Evaluation Test

    4.8.4. Resources

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

    • None specified.

    4.8.5. Errors

    This test suite may produce the following errors:

    -

    4.8.6. Input parameters

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

    4.8.6. Input parameters

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

    -
    1. dnssecOps.algorithmRolloverZone (string)
    2. dnssecOps.csk (boolean)
    3. dnssecOps.kskRolloverZone (string)
    4. dnssecOps.zskRolloverZone (string)

    4.8.7. Sequence diagram

     +
    1. dnssecOps.algorithmRolloverZone (string)
    2. dnssecOps.csk (boolean)
    3. dnssecOps.kskRolloverZone (string)
    4. dnssecOps.nameservers (object)
    5. dnssecOps.primaryServer (string)
    6. dnssecOps.tsigKey (object)
    7. dnssecOps.zskRolloverZone (string)

    4.8.7. Sequence diagram

     + -epp-16 +epp-14 -epp-16 +epp-14 - + -epp-16->integration-01 +epp-14->integration-01 - + -epp-16->integration-02 +epp-14->integration-02 - + -epp-16->integration-03 +epp-14->integration-03 @@ -16035,19 +15934,30 @@

    Pass/fail criteria

    4.1.1 of RFC 6781 for a zone.

    If the value of the dnssecOps.csk input parameter is true, then this test will be skipped.

    -

    The system will monitor the SOA record in the domain name specified -in the dnssec.zskRolloverZone input parameter. The domain -may be present anywhere in the DNS hierarchy (that is, it does not need -to be a TLD), but MUST have a secure chain of trust up -to the root zone, so that it can be validated using the root zone trust +

    The system will monitor the zone specified in the +dnssec.zskRolloverZone input parameter. The domain may be +present anywhere in the DNS hierarchy (that is, it does not need to be a +TLD), but MUST have a secure chain of trust up to the +root zone, so that it can be validated using the root zone trust anchor.

    -

    During the test period (currently defined as 24 hours) the operator +

    The zone MUST contain at least 10,000 delegations, +where a delegation is considered to be one or more NS +records with owner names that are below the zone’s origin. If NSEC3 is +used for secure denial of existence, the opt-out flag +MUST NOT be set (that is, an RRSIG record +should be present for all NS rrsets, irrespective of +whether a corresponding DS record is published).

    +

    Monitoring will be carried out using SOA queries sent to +multiple validating DNS resolvers, and by validating the result of a a +zone transfer from the server specified in the +dnssecOps.primaryServer input parameter.

    +

    During the test period (currently defined as 48 hours) the operator MUST successfully carry out a ZSK rollover for the domain, where the Zone Signing Key is replaced, without disrupting the chain of trust.

    -

    To simplify testing, applicants may wish to provision domain that is -configured with short TTLs and a short ZSK lifetime, so that a ZSK -rollover is guaranteed to occur within the 24 test period.

    +

    To simplify testing, applicants may wish to provision the zone such +that it is configured with short TTLs and a short ZSK lifetime, so that +a ZSK rollover is guaranteed to occur within the 48 test period.

    6.63.3. Errors

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

    6.63.4. Input parameters

    This test case requires the following input parameters, in @@ -16064,13 +15974,24 @@

    Pass/fail criteria

    rollover (as described in Sections 4.1.2 and 4.13 of RFC 6781 for a zone.

    -

    The system will monitor the SOA record in the domain name specified -in the dnssec.kskRolloverZone input parameter. The domain -may be present anywhere in the DNS hierarchy (that is, it does not need -to be a TLD), but MUST have a secure chain of trust up -to the root zone, so that it can be validated using the root zone trust +

    The system will monitor the zone specified in the +dnssec.zskRolloverZone input parameter. The domain may be +present anywhere in the DNS hierarchy (that is, it does not need to be a +TLD), but MUST have a secure chain of trust up to the +root zone, so that it can be validated using the root zone trust anchor.

    -

    During the test period (currently defined as 24 hours) the operator +

    The zone MUST contain at least 10,000 delegations, +where a delegation is considered to be one or more NS +records with owner names that are below the zone’s origin. If NSEC3 is +used for secure denial of existence, the opt-out flag +MUST NOT be set (that is, an RRSIG record +should be present for all NS rrsets, irrespective of +whether a corresponding DS record is published).

    +

    Monitoring will be carried out using SOA queries sent to +multiple validating DNS resolvers, and by validating the result of a a +zone transfer from the server specified in the +dnssecOps.primaryServer input parameter.

    +

    During the test period (currently defined as 48 hours) the operator MUST successfully carry out a KSK rollover for the domain, where the Key Signing Key is replaced, and the DS record in the parent zone is updated, without disrupting the chain of trust.

    @@ -16090,13 +16011,24 @@

    Pass/fail criteria

    rollover (as described in Section 4.1.4 of RFC 6781 for a zone.

    -

    The system will monitor the SOA record in the domain name specified -in the dnssec.algorithmRolloverZone input parameter. The -domain may be present anywhere in the DNS hierarchy (that is, it does -not need to be a TLD), but MUST have a secure chain of -trust up to the root zone, so that it can be validated using the root -zone trust anchor.

    -

    During the test period (currently defined as 72 hours) the operator +

    The system will monitor the zone specified in the +dnssec.zskRolloverZone input parameter. The domain may be +present anywhere in the DNS hierarchy (that is, it does not need to be a +TLD), but MUST have a secure chain of trust up to the +root zone, so that it can be validated using the root zone trust +anchor.

    +

    The zone MUST contain at least 10,000 delegations, +where a delegation is considered to be one or more NS +records with owner names that are below the zone’s origin. If NSEC3 is +used for secure denial of existence, the opt-out flag +MUST NOT be set (that is, an RRSIG record +should be present for all NS rrsets, irrespective of +whether a corresponding DS record is published).

    +

    Monitoring will be carried out using SOA queries sent to +multiple validating DNS resolvers, and by validating the result of a a +zone transfer from the server specified in the +dnssecOps.primaryServer input parameter.

    +

    During the test period (currently defined as 48 hours) the operator MUST successfully carry out an algorithm rollover for the domain (including an update to the DS record in the parent zone), where the algorithm used to secure the domain is changed, without @@ -16110,7 +16042,7 @@

    Pass/fail criteria

    RSASHA256 to ECDSAP256SHA256.

    6.65.3. Errors

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

    -

    6.65.4. Input parameters

    This test case requires the following input parameters, in +

    6.65.4. Input parameters

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

    6.65.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test @@ -16234,7 +16166,7 @@

    Pass/fail criteria

    successfully passed:

    • None specified.

    6.68.7. Dependants

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

    -

    6.68.8. Test suites

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

    +

    6.68.8. Test suites

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

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

    6.69.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.69.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 @@ -16432,7 +16364,7 @@

    Pass/fail criteria

    successfully passed:

    6.74.8. Test suites

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

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

    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 -objects created during epp-24 and will confirm that the +objects created during epp-22 and will confirm that the server accepts the <delete> command with a 1xxx response code.

    If the general.minimalPublicDataSet input parameter is @@ -16487,7 +16419,7 @@

    Pass/fail criteria

    successfully passed:

    • None specified.

    6.76.7. Dependants

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

    -

    6.76.8. Test suites

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

    +

    6.76.8. Test suites

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

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

    6.77.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.77.2. Description

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

    @@ -16539,33 +16471,7 @@

    Pass/fail criteria

    6.78.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. epp-14 - intentionally omitted

    6.79.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.79.2. Description

    intentionally omitted

    -

    6.79.3. Errors

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

    -
    • None specified.

    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.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.79.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 - successfully passed:

    -
    • None specified.

    6.79.8. Test suites

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

    -

    6.80. epp-15 - intentionally omitted

    6.80.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.80.2. Description

    intentionally omitted

    -

    6.80.3. Errors

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

    -
    • None specified.

    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.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.80.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 - successfully passed:

    -
    • None specified.

    6.80.8. Test suites

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

    -

    6.81. epp-16 - domain <create> command test

    6.81.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.81.2. Description

    This test performs a series domain <create> +

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

    6.79.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.79.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 @@ -16625,43 +16531,43 @@

    Pass/fail criteria

  • DNSSEC information provided in the <create> command is present and correct.
    • -

    6.81.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.81.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:

    -

    6.81.5. Resources

    The following resources may be required to prepare for this +

    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.81.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.81.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.81.8. Test suites

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

    -

    6.82. epp-17 - Registry object integrity test

    6.82.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.82.2. Description

    This test confirms that the EPP server will refuse a request to +

    6.79.8. Test suites

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

    +

    6.80. epp-15 - Registry object integrity test

    6.80.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.80.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 attributes, and the general.minimalPublicDataSet input parameter is true, then this test will be skipped.

    The client will submit <delete> commands for any -contact and host objects created during epp-16. The server +contact and host objects created during epp-14. The server MUST respond with a 2305 “Object association prohibits operation” error.

    -

    6.82.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.82.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.82.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.82.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.82.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.82.8. Test suites

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

    -

    6.83. epp-18 - domain <renew> command test

    6.83.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.83.2. Description

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

    • None specified.

    6.80.8. Test suites

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

    +

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

    6.81.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.81.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-16.

    +for the domains created in epp-14.

    • Following a succesful <renew> command, the expiry date of the domain MUST have been increased by the @@ -16675,23 +16581,23 @@

      Pass/fail criteria

      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.83.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.83.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.83.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.83.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:

    -

    6.83.7. Dependants

    The following test cases require this test case to have +

    6.81.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. epp-19 - domain <transfer> command test

    6.84.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.84.2. Description

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

    • None specified.

    6.81.8. Test suites

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

    +

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

    6.82.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.82.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 -epp-16) to a randomly-determined value. If the server +epp-14) to a randomly-determined value. If the server implements RFC 9154, it MUST reject the <update> command if the authInfo code is insufficently secure.

    @@ -16725,38 +16631,38 @@

    Pass/fail criteria

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

    -

    6.84.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.84.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.84.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.84.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:

    -

    6.84.7. Dependants

    The following test cases require this test case to have +

    6.82.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. epp-20 - domain <transfer> rejection test

    6.85.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.85.2. Description

    This test confirms that the server behaves correctly if the +

    • None specified.

    6.82.8. Test suites

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

    +

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

    6.83.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.83.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-19, but the transfer request +procedure matches that of epp-17, 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.85.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:

    -

    6.85.4. Input parameters

    This test case requires the following input parameters, in +

    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.85.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.85.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:

    -

    6.85.7. Dependants

    The following test cases require this test case to have +

    6.83.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. epp-21 - domain <delete> command test

    6.86.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.86.2. Description

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

    • None specified.

    6.83.8. Test suites

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

    +

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

    6.84.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.84.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.

    Once the <delete> commands have been processed, @@ -16770,38 +16676,38 @@

    Pass/fail criteria

    pendingDelete status and the redemptionPeriod RGP status. -

    6.86.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:

    -

    6.86.4. Input parameters

    This test case requires the following input parameters, in +

    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.86.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.86.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:

    -

    6.86.7. Dependants

    The following test cases require this test case to have +

    6.84.7. Dependants

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

    -

    6.86.8. Test suites

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

    -

    6.87. epp-22 - domain restore test

    6.87.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.87.2. Description

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

    6.84.8. Test suites

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

    +

    6.85. epp-20 - domain restore test

    6.85.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.85.2. 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 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.87.3. Errors

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

    6.85.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.85.4. Input parameters

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

    -

    6.87.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.87.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.87.7. Dependants

    The following test cases require this test case to have +

    6.85.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. epp-23 - host rename test (if applicable)

    6.88.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.88.2. Description

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

    • None specified.

    6.85.8. Test suites

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

    +

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

    6.86.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.86.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.

    @@ -16821,25 +16727,25 @@

    Pass/fail criteria

    be used for this test.
  • an <update> command which places the object within a domain sponsored by the test client is accepted. A domain -created during the epp-16 test case will be used as the new +created during the epp-14 test case will be used as the new parent domain.

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

    -

    6.88.3. Errors

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

    6.86.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.86.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.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.88.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.88.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:

    -

    6.88.8. Test suites

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

    -

    6.89. epp-24 - host <delete> command test (if applicable)

    6.89.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.89.2. Description

    This test will perform <delete> commands on the +

    6.86.8. Test suites

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

    +

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

    6.87.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.87.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.

    @@ -16849,19 +16755,19 @@

    Pass/fail criteria

    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.89.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.89.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:

    -
    • None specified.

    6.89.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    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:

    -
    • None specified.

    6.89.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.87.6. Dependencies

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

    -

    6.89.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.89.8. Test suites

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

    -

    6.90. idn-01 - Label validation test

    6.90.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.90.2. Description

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

    • None specified.

    6.87.8. Test suites

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

    +

    6.88. idn-01 - Label validation test

    6.88.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.88.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 @@ -16874,19 +16780,19 @@

    Pass/fail criteria

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

    -

    6.90.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.90.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.90.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.90.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.90.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.90.8. Test suites

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

    -

    6.91. idn-02 - Level 1 variant handling test

    6.91.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.91.2. Description

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

    • None specified.

    6.88.8. Test suites

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

    +

    6.89. idn-02 - Level 1 variant handling test

    6.89.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.89.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 @@ -16898,19 +16804,19 @@

    Pass/fail criteria

    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.91.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.91.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.91.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.91.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.91.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.91.8. Test suites

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

    -

    6.92. idn-03 - Level 2 variant handling test

    6.92.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.92.2. Description

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

    • None specified.

    6.89.8. Test suites

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

    +

    6.90. idn-03 - Level 2 variant handling test

    6.90.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.90.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.

    @@ -16929,19 +16835,19 @@

    Pass/fail criteria

    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.92.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:

    -
    • None specified.

    6.92.4. Input parameters

    This test case requires the following input parameters, in +

    • 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.92.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.92.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.92.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.92.8. Test suites

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

    -

    6.93. idn-04 - Level 3 variant handling test

    6.93.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.93.2. Description

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

    • None specified.

    6.90.8. Test suites

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

    +

    6.91. idn-04 - Level 3 variant handling test

    6.91.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.91.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.

    @@ -16960,62 +16866,62 @@

    Pass/fail criteria

    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.93.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.93.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.93.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.93.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.93.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.91.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. integration-01 - EPP -> RDAP Integration Test

    6.94.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.94.2. Description

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

    • None specified.

    6.91.8. Test suites

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

    +

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

    6.92.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.92.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-16, and host objects created in epp-11 (if +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.94.3. Errors

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

    6.92.3. Errors

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

    -

    6.94.4. Input parameters

    This test case requires the following input parameters, in +

    6.92.4. Input parameters

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

    -

    6.94.5. Resources

    The following resources may be required to prepare for this +

    6.92.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.94.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.92.6. Dependencies

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

    -

    6.94.7. Dependants

    The following test cases require this test case to have +

    6.92.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. integration-02 - EPP -> DNS Integration Test

    6.95.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.95.2. Description

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

    • None specified.

    6.92.8. Test suites

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

    +

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

    6.93.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.93.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-16. All DNS servers MUST provide the +epp-14. All DNS servers MUST provide the correct DNS response within 1 hour of the object’s <crDate> element.

    -

    6.95.3. Errors

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

    6.93.3. Errors

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

    -

    6.95.4. Input parameters

    This test case requires the following input parameters, in +

    6.93.4. Input parameters

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

    -

    6.95.5. Resources

    The following resources may be required to prepare for this +

    6.93.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.95.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.93.6. Dependencies

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

    -

    6.95.7. Dependants

    The following test cases require this test case to have +

    6.93.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. integration-03 - EPP -> RDE Integration Test

    6.96.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.96.2. Description

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

    • None specified.

    6.93.8. Test suites

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

    +

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

    6.94.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.94.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.

    @@ -17029,7 +16935,7 @@

    Pass/fail criteria

    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-16 and +

    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 @@ -17044,19 +16950,19 @@

    Pass/fail criteria

    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.96.3. Errors

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

    6.94.3. Errors

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

    -

    6.96.4. Input parameters

    This test case requires the following input parameters, in +

    6.94.4. Input parameters

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

    -

    6.96.5. Resources

    The following resources may be required to prepare for this +

    6.94.5. Resources

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

    -

    6.96.6. Dependencies

    This test case requires the following test cases to have +

    6.94.6. Dependencies

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

    -

    6.96.7. Dependants

    The following test cases require this test case to have +

    6.94.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. minimumRPMs-01 - Claims <check> command test

    6.97.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.97.2. Description

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

    • None specified.

    6.94.8. Test suites

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

    +

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

    6.95.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.95.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 @@ -17077,20 +16983,20 @@

    Pass/fail criteria

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

    6.97.3. Errors

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

    6.95.3. Errors

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

    -

    6.97.4. Input parameters

    This test case requires the following input parameters, in +

    6.95.4. Input parameters

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

    -
    • None specified.

    6.97.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.95.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.97.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.95.6. Dependencies

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

    -
    • None specified.

    6.97.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.95.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. minimumRPMs-02 - Sunrise domain/launch application <create> command test -

    6.98.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.98.2. Description

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

    • None specified.

    6.95.8. Test suites

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

    +

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

    6.96.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.96.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 @@ -17122,19 +17028,19 @@

    Pass/fail criteria

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

    6.98.3. Errors

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

    6.96.3. Errors

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

    -

    6.98.4. Input parameters

    This test case requires the following input parameters, in +

    6.96.4. Input parameters

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

    -
    • None specified.

    6.98.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.96.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.98.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.96.6. Dependencies

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

    -
    • None specified.

    6.98.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.96.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. minimumRPMs-03 - Trademark claims domain <create> command test

    6.99.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.99.2. Description

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

    • None specified.

    6.96.8. Test suites

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

    +

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

    6.97.1. Maturity Level

    • ALPHA: very rough outline, much more work needed

    6.97.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 @@ -17160,9 +17066,41 @@

    Pass/fail criteria

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

    6.97.3. Errors

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

    +

    6.97.4. Input parameters

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

    +
    • None specified.

    6.97.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.97.6. Dependencies

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

    +
    • 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-01-domainCaseFoldingValidation - Domain label case folding 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.

    +

    6.98.3. Errors

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

    +
    • None specified.

    6.98.4. Input parameters

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

    +
    • None specified.

    6.98.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.98.6. Dependencies

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

    +
    • 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-02-domainNameValidation - Domain Name 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.

    6.99.3. Errors

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

    -

    6.99.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.99.4. Input parameters

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

    • None specified.

    6.99.5. Resources

    The following resources may be required to prepare for this test case, in addition to those defined in the test @@ -17172,7 +17110,7 @@

    Pass/fail criteria

    • 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-01-domainCaseFoldingValidation - Domain label case folding 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-03-ipv4Validation - IPv4 address 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 information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -17188,7 +17126,7 @@

    Pass/fail criteria

    • 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-02-domainNameValidation - Domain Name 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-04-ipv6Validation - IPv6 address 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.

    @@ -17204,7 +17142,7 @@

    Pass/fail criteria

    • 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-03-ipv4Validation - IPv4 address 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-05-stdRdapAsEventActorValidation - asEventActor 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.

    @@ -17220,7 +17158,7 @@

    Pass/fail criteria

    • 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-04-ipv6Validation - IPv6 address 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 +

    6.103. rdap-06-stdRdapConformanceValidation - RDAP Conformance 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.

    @@ -17236,7 +17174,7 @@

    Pass/fail criteria

    • 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-05-stdRdapAsEventActorValidation - asEventActor 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-07-stdRdapDomainLookupValidation - Domain Lookup 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.

    @@ -17252,7 +17190,7 @@

    Pass/fail criteria

    • 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-06-stdRdapConformanceValidation - RDAP Conformance 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-08-stdRdapEntitiesValidation - Entities 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 information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -17268,7 +17206,7 @@

    Pass/fail criteria

    • 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-07-stdRdapDomainLookupValidation - Domain Lookup 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-09-stdRdapEntityLookupValidation - Entity lookup 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.

    @@ -17284,7 +17222,7 @@

    Pass/fail criteria

    • 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-08-stdRdapEntitiesValidation - Entities 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-10-stdRdapErrorResponseBodyValidation - Error Response Body

    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.

    @@ -17300,7 +17238,7 @@

    Pass/fail criteria

    • 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-09-stdRdapEntityLookupValidation - Entity lookup 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 +

    6.108. rdap-11-stdRdapEventsValidation - Events 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.

    @@ -17316,7 +17254,7 @@

    Pass/fail criteria

    • 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-10-stdRdapErrorResponseBodyValidation - Error Response Body

    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-12-stdRdapHelpValidation - Help 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.

    @@ -17332,7 +17270,7 @@

    Pass/fail criteria

    • 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-11-stdRdapEventsValidation - Events 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-13-stdRdapIpAddressesValidation - IP Addresses 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 information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -17348,7 +17286,7 @@

    Pass/fail criteria

    • 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-12-stdRdapHelpValidation - Help 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-14-stdRdapLanguageIdentifierValidation - Language Identifier 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.

    @@ -17364,7 +17302,7 @@

    Pass/fail criteria

    • 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-13-stdRdapIpAddressesValidation - IP Addresses 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-15-stdRdapLdhNameValidation - LDH name

    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.

    @@ -17380,7 +17318,7 @@

    Pass/fail criteria

    • 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-14-stdRdapLanguageIdentifierValidation - Language Identifier 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 +

    6.113. rdap-16-stdRdapLinksValidation - Links 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.

    @@ -17396,7 +17334,7 @@

    Pass/fail criteria

    • 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-15-stdRdapLdhNameValidation - LDH name

    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-17-stdRdapNameserverLookupValidation - Nameserver lookup 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.

    @@ -17412,7 +17350,7 @@

    Pass/fail criteria

    • 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-16-stdRdapLinksValidation - Links 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-18-stdRdapNameserversSearchValidation - Nameservers search 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 information, see https://github.com/icann/rdap-conformance-tool/blob/master/doc/RDAPConformanceToolSpecifications.pdf.

    @@ -17428,7 +17366,7 @@

    Pass/fail criteria

    • 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. rdap-17-stdRdapNameserverLookupValidation - Nameserver lookup 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 +

    6.116. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks 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.

    @@ -17444,7 +17382,7 @@

    Pass/fail criteria

    • 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. rdap-18-stdRdapNameserversSearchValidation - RFC7159RDAP_RFCsNameservers search 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 +

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

    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.

    @@ -17460,7 +17398,7 @@

    Pass/fail criteria

    • 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. rdap-19-stdRdapNoticesRemarksValidation - Notices and Remarks Validation

    6.118.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.118.2. Description

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

    6.118. rdap-21-stdRdapPublicIdsValidation - Public IDs validation

    6.118.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.118.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.

    @@ -17476,7 +17414,7 @@

    Pass/fail criteria

    • 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. rdap-20-stdRdapPort43WhoisServerValidation - Port 43 WHOIS Server

    6.119.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.119.2. Description

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

    6.119. rdap-22-stdRdapRolesValidation - Roles validation

    6.119.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.119.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.

    @@ -17492,7 +17430,7 @@

    Pass/fail criteria

    • 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. rdap-21-stdRdapPublicIdsValidation - Public IDs validation

    6.120.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.120.2. Description

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

    6.120. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation

    6.120.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.120.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.

    @@ -17508,7 +17446,7 @@

    Pass/fail criteria

    • 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. rdap-22-stdRdapRolesValidation - Roles validation

    6.121.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.121.2. Description

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

    6.121. rdap-24-stdRdapStatusValidation - Status validation

    6.121.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.121.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.

    @@ -17524,7 +17462,7 @@

    Pass/fail criteria

    • None specified.

    6.121.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. rdap-23-stdRdapSecureDnsValidation - Secure DNS validation

    6.122.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.122.2. Description

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

    6.122. rdap-25-stdRdapUnicodeNameValidation - Unicode name

    6.122.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.122.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.

    @@ -17540,7 +17478,7 @@

    Pass/fail criteria

    • None specified.

    6.122.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. rdap-24-stdRdapStatusValidation - Status validation

    6.123.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.123.2. Description

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

    6.123. rdap-26-stdRdapVariantsValidation - Variants validation

    6.123.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.123.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.

    @@ -17556,7 +17494,7 @@

    Pass/fail criteria

    • None specified.

    6.123.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. rdap-25-stdRdapUnicodeNameValidation - RFC7159RDAP_RFCsIDNA_RFCsUnicode name

    6.124.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.124.2. Description

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

    6.124. rdap-27-webUriValidation - Web URI validation

    6.124.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.124.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.

    @@ -17572,13 +17510,17 @@

    Pass/fail criteria

    • None specified.

    6.124.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. rdap-26-stdRdapVariantsValidation - Variants validation

    6.125.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.125.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.125. rde-01 - validate deposit filename format

    6.125.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.125.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.125.3. Errors

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

    -
    • None specified.

    6.125.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.125.5. Resources

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

    Pass/fail criteria

    • None specified.

    6.125.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. rdap-27-webUriValidation - Web URI validation

    6.126.1. Maturity Level

    • GAMMA: finalized and ready for review

    6.126.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.126. rde-02 - validate signature over deposit file

    6.126.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.126.2. Description

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

    6.126.3. Errors

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

    -
    • None specified.

    6.126.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.126.5. Resources

    The following resources may be required to prepare for this +

    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.126.6. Dependencies

    This test case requires the following test cases to have @@ -17604,109 +17544,75 @@

    Pass/fail criteria

    • None specified.

    6.126.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-01 - validate deposit filename format

    6.127.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.127.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.127. rde-03 - decrypt deposit file(s)

    6.127.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.127.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.127.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.127.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 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 +

    6.127.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 successfully passed:

    • None specified.

    6.127.8. Test suites

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

    -

    6.128. rde-02 - validate signature over deposit file

    6.128.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.128.2. Description

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

    -

    6.128.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 - addition to those defined in the test suite:

    -

    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.128.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 - successfully passed:

    -
    • None specified.

    6.128.8. Test suites

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

    -

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

    6.129.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.129.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.129.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 - addition to those defined in the test suite:

    -
    • 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:

    -

    6.129.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 - successfully passed:

    -
    • None specified.

    6.129.8. Test suites

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

    -

    6.130. rde-04 - validate XML/CSV

    6.130.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.130.2. Description

    6.128. rde-04 - validate XML/CSV

    6.128.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.128.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.130.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.130.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.130.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.130.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.130.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.130.8. Test suites

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

    -

    6.131. rde-05 - validate object types

    6.131.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.131.2. Description

    The header object MUST reference the correct object +

    • None specified.

    6.128.8. Test suites

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

    +

    6.129. rde-05 - validate object types

    6.129.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.129.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 input parameters.

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

    -

    6.131.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.131.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.131.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.131.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.131.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.131.8. Test suites

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

    -

    6.132. rde-06 - validate object counts

    6.132.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.132.2. Description

    The number of each type of 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-06 - validate object counts

    6.130.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.130.2. Description

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

    -

    6.132.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.132.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:

    -
    • None specified.

    6.132.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    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.132.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.132.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.132.8. Test suites

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

    -

    6.133. rde-07 - validate domain objects

    6.133.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.133.2. Description

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

    • None specified.

    6.130.8. Test suites

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

    +

    6.131. rde-07 - validate domain objects

    6.131.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.131.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:

    @@ -17724,19 +17630,19 @@

    Pass/fail criteria

    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.133.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.133.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.133.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.133.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.133.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.133.8. Test suites

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

    -

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

    6.134.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.134.2. Description

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

    • None specified.

    6.131.8. Test suites

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

    +

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

    6.132.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.132.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:

    @@ -17751,19 +17657,19 @@

    Pass/fail criteria

    If the applicant uses the host attribute model, then this test will be skipped.

    -

    6.134.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:

    -

    6.134.4. Input parameters

    This test case requires the following input parameters, in +

    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.134.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.134.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.134.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.134.8. Test suites

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

    -

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

    6.135.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.135.2. Description

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

    • None specified.

    6.132.8. Test suites

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

    +

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

    6.133.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.133.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.

    The required properties are:

    @@ -17791,19 +17697,19 @@

    Pass/fail criteria

    If the applicant uses the “thin” registry model, then this test will be skipped.

    -

    6.135.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.135.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.135.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.135.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.135.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:

    -
    • None specified.

    6.135.8. Test suites

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

    -

    6.136. rde-10 - validate registrar objects

    6.136.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.136.2. Description

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

    • None specified.

    6.133.8. Test suites

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

    +

    6.134. rde-10 - validate registrar objects

    6.134.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.134.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:

    @@ -17812,69 +17718,69 @@

    Pass/fail criteria

  • <rdeRegistrar:name>
  • <rdeRegistrar:gurid> (IANA ID)
    • -

    6.136.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.136.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.136.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.136.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.136.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:

    -
    • None specified.

    6.136.8. Test suites

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

    -

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

    6.137.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.137.2. Description

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

    • None specified.

    6.134.8. Test suites

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

    +

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

    6.135.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.135.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.137.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.137.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.137.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.137.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:

    -
    • None specified.

    6.137.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.135.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. rde-12 - validate NNDN objects

    6.138.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.138.2. Description

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

    • None specified.

    6.135.8. Test suites

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

    +

    6.136. rde-12 - validate NNDN objects

    6.136.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.136.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.138.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.138.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.138.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.138.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:

    -
    • None specified.

    6.138.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.136.7. Dependants

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

    -
    • None specified.

    6.138.8. Test suites

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

    -

    6.139. rde-13 - validate EPP parameters object

    6.139.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.139.2. Description

    The EPP Parameters object MUST match the +

    • None specified.

    6.136.8. Test suites

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

    +

    6.137. rde-13 - validate EPP parameters object

    6.137.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.137.2. Description

    The EPP Parameters object MUST match the <greeting> element returned by the EPP server.

    -

    6.139.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.139.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:

    -

    6.139.5. Resources

    The following resources may be required to prepare for this +

    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:

    -

    6.139.6. Dependencies

    This test case requires the following test cases to have +

    6.137.6. Dependencies

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

    -
    • None specified.

    6.139.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.137.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. rde-14 - validate policy object (if applicable)

    6.140.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.140.2. Description

    The object policies included in the +

    • None specified.

    6.137.8. Test suites

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

    +

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

    6.138.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.138.2. Description

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

    @@ -17886,37 +17792,37 @@

    Pass/fail criteria

    attributes, then host objects MUST NOT be present in the deposit. -

    6.140.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.140.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.140.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.140.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:

    -
    • None specified.

    6.140.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.138.7. Dependants

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

    -
    • None specified.

    6.140.8. Test suites

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

    -

    6.141. srsgw-01 - IPv4 and IPv6 connectivity

    6.141.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.141.2. Description

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

    • None specified.

    6.138.8. Test suites

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

    +

    6.139. srsgw-01 - IPv4 and IPv6 connectivity

    6.139.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.139.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.141.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:

    -
    • None specified.

    6.141.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    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.141.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.141.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:

    -
    • None specified.

    6.141.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.139.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-02 - Host <create> synchronization (if applicable)

    6.142.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.142.2. Description

    This test confirms that host objects created 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-02 - Host <create> 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 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.

    @@ -17934,19 +17840,19 @@

    Pass/fail criteria

    response.

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

    -

    6.142.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:

    -

    6.142.4. Input parameters

    This test case requires the following input parameters, in +

    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.142.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.142.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:

    -
    • None specified.

    6.142.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.140.7. Dependants

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

    -

    6.142.8. Test suites

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

    -

    6.143. srsgw-03 - Contact <create> 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 created in the SRS Gateway +

    6.140.8. Test suites

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

    +

    6.141. srsgw-03 - Contact <create> 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 created in the SRS Gateway EPP system are correctly synchronized with the primary registry system.

    If the value of the general.minimalPublicDataSet input @@ -17963,19 +17869,19 @@

    Pass/fail criteria

    response.

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

    -

    6.143.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:

    -

    6.143.4. Input parameters

    This test case requires the following input parameters, in +

    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.143.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.143.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:

    -
    • None specified.

    6.143.7. Dependants

    The following test cases require this test case to have +

    • None specified.

    6.141.7. Dependants

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

    -

    6.143.8. Test suites

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

    -

    6.144. srsgw-04 - Domain <create> synchronization

    6.144.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.144.2. Description

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

    6.141.8. Test suites

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

    +

    6.142. srsgw-04 - Domain <create> synchronization

    6.142.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.142.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 @@ -17992,19 +17898,19 @@

    Pass/fail criteria

    response.

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

    -

    6.144.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:

    -

    6.144.4. Input parameters

    This test case requires the following input parameters, in +

    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.144.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.144.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.144.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.144.8. Test suites

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

    -

    6.145. srsgw-05 - Domain <renew> synchronisation

    6.145.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.145.2. Description

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

    6.142.8. Test suites

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

    +

    6.143. srsgw-05 - Domain <renew> synchronisation

    6.143.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.143.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, @@ -18019,19 +17925,19 @@

    Pass/fail criteria

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

    -

    6.145.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:

    -

    6.145.4. Input parameters

    This test case requires the following input parameters, in +

    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.145.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.145.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.145.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:

    -

    6.145.8. Test suites

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

    -

    6.146. srsgw-06 - Domain <transfer> synchronisation

    6.146.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.146.2. Description

    This test confirms that transfer requests submitted in the SRS +

    6.143.8. Test suites

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

    +

    6.144. srsgw-06 - Domain <transfer> synchronisation

    6.144.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.144.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, @@ -18055,19 +17961,19 @@

    Pass/fail criteria

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

    6.146.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:

    -

    6.146.4. Input parameters

    This test case requires the following input parameters, in +

    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.146.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.146.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.146.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:

    -

    6.146.8. Test suites

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

    -

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

    6.147.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.147.2. Description

    This test confirms that transfer request approvals submitted in the +

    6.144.8. Test suites

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

    +

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

    6.145.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.145.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"> @@ -18083,19 +17989,19 @@

    Pass/fail criteria

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

    -

    6.147.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:

    -

    6.147.4. Input parameters

    This test case requires the following input parameters, in +

    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.147.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.147.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.147.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:

    -

    6.147.8. Test suites

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

    -

    6.148. srsgw-08 - Domain <delete> synchronisation

    6.148.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.148.2. Description

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

    6.145.8. Test suites

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

    +

    6.146. srsgw-08 - Domain <delete> synchronisation

    6.146.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.146.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 @@ -18111,19 +18017,19 @@

    Pass/fail criteria

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

    -

    6.148.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:

    -

    6.148.4. Input parameters

    This test case requires the following input parameters, in +

    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.148.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.148.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.148.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.148.8. Test suites

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

    -

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

    6.149.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.149.2. Description

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

    • None specified.

    6.146.8. Test suites

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

    +

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

    6.147.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.147.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.

    @@ -18136,19 +18042,19 @@

    Pass/fail criteria

    perform <info> commands for those objects.

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

    -

    6.149.3. Errors

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

    6.147.3. Errors

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

    -
    • None specified.

    6.149.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.147.4. Input parameters

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

    -
    • None specified.

    6.149.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.147.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.149.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.147.6. Dependencies

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

    -

    6.149.7. Dependants

    The following test cases require this test case to have +

    6.147.7. Dependants

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

    -

    6.149.8. Test suites

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

    -

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

    6.150.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.150.2. Description

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

    6.147.8. Test suites

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

    +

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

    6.148.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.148.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.

    @@ -18160,19 +18066,19 @@

    Pass/fail criteria

    perform <info> commands for those objects. The server MUST respond with a 2303 “object does not exist” response.

    -

    6.150.3. Errors

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

    6.148.3. Errors

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

    -
    • None specified.

    6.150.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.148.4. Input parameters

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

    -
    • None specified.

    6.150.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.148.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.150.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.148.6. Dependencies

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

    -

    6.150.7. Dependants

    The following test cases require this test case to have +

    6.148.7. Dependants

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

    -
    • None specified.

    6.150.8. Test suites

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

    -

    6.151. srsgw-11 - Contact <update> synchronization (if applicable)

    6.151.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.151.2. Description

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

    • None specified.

    6.148.8. Test suites

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

    +

    6.149. srsgw-11 - Contact <update> synchronization (if applicable)

    6.149.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.149.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 @@ -18185,19 +18091,19 @@

    Pass/fail criteria

    perform <info> commands for those objects.

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

    -

    6.151.3. Errors

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

    6.149.3. Errors

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

    -
    • None specified.

    6.151.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.149.4. Input parameters

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

    -
    • None specified.

    6.151.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.149.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.151.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.149.6. Dependencies

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

    -

    6.151.7. Dependants

    The following test cases require this test case to have +

    6.149.7. Dependants

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

    -

    6.151.8. Test suites

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

    -

    6.152. srsgw-12 - Contact <delete> synchronization (if applicable)

    6.152.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.152.2. Description

    This test confirms that contact objects delete in the SRS Gateway EPP +

    6.149.8. Test suites

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

    +

    6.150. srsgw-12 - Contact <delete> synchronization (if applicable)

    6.150.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.150.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.

    @@ -18209,38 +18115,38 @@

    Pass/fail criteria

    perform <info> commands for those objects. The server MUST respond with a 2303 “object does not exist” response.

    -

    6.152.3. Errors

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

    6.150.3. Errors

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

    -
    • None specified.

    6.152.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.150.4. Input parameters

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

    -
    • None specified.

    6.152.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.150.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.152.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.150.6. Dependencies

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

    -

    6.152.7. Dependants

    The following test cases require this test case to have +

    6.150.7. Dependants

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

    -
    • None specified.

    6.152.8. Test suites

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

    -

    6.153. srsgw-13 - Domain RDAP synchronization

    6.153.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.153.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides +

    • None specified.

    6.150.8. Test suites

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

    +

    6.151. srsgw-13 - Domain RDAP synchronization

    6.151.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.151.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.153.3. Errors

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

    6.151.3. Errors

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

    -
    • None specified.

    6.153.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.151.4. Input parameters

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

    -
    • None specified.

    6.153.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.151.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.153.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.151.6. Dependencies

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

    -

    6.153.7. Dependants

    The following test cases require this test case to have +

    6.151.7. Dependants

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

    -
    • None specified.

    6.153.8. Test suites

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

    -

    6.154. srsgw-14 - Nameserver RDAP synchronization

    6.154.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.154.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides +

    • None specified.

    6.151.8. Test suites

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

    +

    6.152. srsgw-14 - Nameserver RDAP synchronization

    6.152.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.152.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 @@ -18249,19 +18155,19 @@

    Pass/fail criteria

    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.154.3. Errors

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

    6.152.3. Errors

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

    -
    • None specified.

    6.154.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.152.4. Input parameters

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

    -
    • None specified.

    6.154.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.152.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.154.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.152.6. Dependencies

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

    -

    6.154.7. Dependants

    The following test cases require this test case to have +

    6.152.7. Dependants

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

    -
    • None specified.

    6.154.8. Test suites

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

    -

    6.155. srsgw-15 - Registrar RDAP synchronization

    6.155.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.155.2. Description

    This test confirms that the SRS Gateway’s RDAP service provides +

    • None specified.

    6.152.8. Test suites

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

    +

    6.153. srsgw-15 - Registrar RDAP synchronization

    6.153.1. Maturity Level

    • BETA: complete but likely to require further changes

    6.153.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 @@ -18273,20 +18179,20 @@

    Pass/fail criteria

    those URLs.

    After canonicalisation, the JSON responses from each server MUST be identical.

    -

    6.155.3. Errors

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

    6.153.3. Errors

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

    -
    • None specified.

    6.155.4. Input parameters

    This test case requires the following input parameters, in +

    • None specified.

    6.153.4. Input parameters

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

    -
    • None specified.

    6.155.5. Resources

    The following resources may be required to prepare for this +

    • None specified.

    6.153.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.155.6. Dependencies

    This test case requires the following test cases to have +

    • None specified.

    6.153.6. Dependencies

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

    -

    6.155.7. Dependants

    The following test cases require this test case to have +

    6.153.7. Dependants

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

    -
    • None specified.

    6.155.8. Test suites

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

    +
    • None specified.

    6.153.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 array where the object properties are the +

    This input parameter is an object where the object properties are the TLD names, and the values are objects. For these objects, the properties are the nameserver names, and the values are arrays of IPv4 and IPv6 addresses.

    @@ -18357,953 +18263,1014 @@

    Pass/fail criteria

    "dnssecOps.kskRolloverZone" : "example.com" }

    7.5.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.6. dnssecOps.zskRolloverZone

    7.6.1. Description

    The domain name which will be monitored for the occurrence of a ZSK -rollover.

    -

    7.6.2. Type

    string

    7.6.3. Schema

    • None specified.

    7.6.4. Example

    {
-   "dnssecOps.zskRolloverZone" : "example.com"
+

    7.6. dnssecOps.nameservers

    7.6.1. Description

    The set of nameservers that will be authoritative for the zones used +in the DNSSEC operations test suite.

    +

    This input parameter is an object where the object properties are the +zone names, and the values are objects. For these objects, the +properties are the nameserver names, and the values are arrays of IPv4 +and IPv6 addresses.

    +

    7.6.2. Type

    object

    7.6.3. Schema

    +patternProperties:
+  ^[a-z]+[a-z0-9\.]*[a-z]\$:
+    items:
+      format:
+      - ipv4
+      - ipv6
+      type: string
+    type: array
+type: object
+

    7.6.4. Example

    {
+   "dnssecOps.nameservers" : {
+      "example" : {
+         "ns1.example.com" : [
+            "192.168.53.1",
+            "2001:DB8::53:1"
+         ],
+         "ns2.example.com" : [
+            "192.168.53.2",
+            "2001:DB8::53:2"
+         ]
+      }
+   }
 }

    7.6.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.7. epp.clid01

    7.7.1. Description

    the username used to log in to the EPP server

    -

    7.7.2. Type

    string

    7.7.3. Schema

    • None specified.

    7.7.4. Example

    {
-   "epp.clid01" : "clid-01"
+
    • None specified.

    7.7. dnssecOps.primaryServer

    7.7.1. Description

    The primary nameserver from which zones can be transferred.

    +

    7.7.2. Type

    string

    7.7.3. Schema

    +format:
+- ipv4
+- ipv6
+type: string
+

    7.7.4. Example

    {
+   "dnssecOps.primaryServer" : "192.168.53.1"
 }

    7.7.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.8. epp.clid02

    7.8.1. Description

    the username used for transfer tests

    -

    7.8.2. Type

    string

    7.8.3. Schema

    • None specified.

    7.8.4. Example

    {
-   "epp.clid02" : "clid-02"
+
    • None specified.

    7.8. dnssecOps.tsigKey

    7.8.1. Description

    The TSIG key which should be used to perform zone transfers.

    +

    7.8.2. Type

    object

    7.8.3. Schema

    +properties:
+  algorithm:
+    type: string
+  name:
+    type: string
+  secret:
+    type: string
+type: object
+

    7.8.4. Example

    {
+   "dnssecOps.tsigKey" : {
+      "algorithm" : "hmac-sha256",
+      "name" : "rst-tsig-01",
+      "secret" : "NQO...xQ="
+   }
 }

    7.8.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.9. epp.hostModel

    7.9.1. Description

    The host model supported by the EPP server. The possible values for -this parameter are: * objects * attributes

    +
    • None specified.

    7.9. dnssecOps.zskRolloverZone

    7.9.1. Description

    The domain name which will be monitored for the occurrence of a ZSK +rollover.

    7.9.2. Type

    string

    7.9.3. Schema

    • None specified.

    7.9.4. Example

    {
-   "epp.hostModel" : "objects"
+   "dnssecOps.zskRolloverZone" : "example.com"
 }

    7.9.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.10. epp.hostName

    7.10.1. Description

    the fully-qualified domain name of the EPP server

    +

    7.10. epp.clid01

    7.10.1. Description

    the username used to log in to the EPP server

    7.10.2. Type

    string

    7.10.3. Schema

    • None specified.

    7.10.4. Example

    {
-   "epp.hostName" : "epp.rsp.tech"
+   "epp.clid01" : "clid-01"
 }

    7.10.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.11. epp.pwd01

    7.11.1. Description

    the password used to log in to the EPP server

    +

    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.pwd01" : "foo2bar"
+   "epp.clid02" : "clid-02"
 }

    7.11.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.12. epp.pwd02

    7.12.1. Description

    the password used for transfer tests

    +
    • None specified.

    7.12. epp.hostModel

    7.12.1. Description

    The host model supported by the EPP server. The possible values for +this parameter are: * objects * attributes

    7.12.2. Type

    string

    7.12.3. Schema

    • None specified.

    7.12.4. Example

    {
-   "epp.pwd02" : "foo3bar"
+   "epp.hostModel" : "objects"
 }

    7.12.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.13. epp.registeredContacts

    7.13.1. Description

    An array of contact IDs that exist in the EPP server and which are +

    7.13. epp.hostName

    7.13.1. Description

    the fully-qualified domain name of the EPP server

    +

    7.13.2. Type

    string

    7.13.3. Schema

    • None specified.

    7.13.4. Example

    {
+   "epp.hostName" : "epp.rsp.tech"
+}
+

    7.13.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.14. epp.pwd01

    7.14.1. Description

    the password used to log in to the EPP server

    +

    7.14.2. Type

    string

    7.14.3. Schema

    • None specified.

    7.14.4. Example

    {
+   "epp.pwd01" : "foo2bar"
+}
+

    7.14.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.15. epp.pwd02

    7.15.1. Description

    the password used for transfer tests

    +

    7.15.2. Type

    string

    7.15.3. Schema

    • None specified.

    7.15.4. Example

    {
+   "epp.pwd02" : "foo3bar"
+}
+

    7.15.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.16. epp.registeredContacts

    7.16.1. Description

    An array of contact IDs that exist in the EPP server and which are therefore unavailable for registration.

    If the value of general.minimalPublicDataSet is false, this array MUST contain one member for each TLD in the TLD set. However, if it is false, the array MUST be empty.

    -

    7.13.2. Type

    array

    7.13.3. Schema

    • None specified.

    7.13.4. Example

    {
+
    7.16.2. Type
    array
    7.16.3. Schema
    • None specified.
    7.16.4. Example
    {
    "epp.registeredContacts" : [
       "abc123",
       "def321"
    ]
 }
-
    7.13.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.14. epp.registeredNames

    7.14.1. Description

    An array of domain names that exist in the EPP server and which are +

    7.16.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.17. epp.registeredNames

    7.17.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 contain one member for each TLD in the TLD set.

    -

    7.14.2. Type

    array

    7.14.3. Schema

    • None specified.

    7.14.4. Example

    {
+
    7.17.2. Type
    array
    7.17.3. Schema
    • None specified.
    7.17.4. Example
    {
    "epp.registeredNames" : [
       "example.example1",
       "example.example2"
    ]
 }
-
    7.14.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.15. epp.registeredNameservers

    7.15.1. Description

    An array of host objects that exist in the EPP server and which are +

    7.17.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.18. epp.registeredNameservers

    7.18.1. Description

    An array of host objects that exist in the EPP server and which are therefore unavailable for registration.

    If the value of epp.hostModel is objects, this array MUST contain one member for each TLD in the TLD set. However, if it is attributes, the array MUST be empty.

    -

    7.15.2. Type

    array

    7.15.3. Schema

    • None specified.

    7.15.4. Example

    {
+
    7.18.2. Type
    array
    7.18.3. Schema
    • None specified.
    7.18.4. Example
    {
    "epp.registeredNameservers" : [
       "ns1.example.com",
       "ns2.example.org"
    ]
 }
-
    7.15.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.16. epp.restoreReportRequired

    7.16.1. Description

    Whether the server requires submission of a restore report when a +

    7.18.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.19. epp.restoreReportRequired

    7.19.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.

    -

    7.16.2. Type

    boolean

    7.16.3. Schema

    • None specified.

    7.16.4. Example

    {
+
    7.19.2. Type
    boolean
    7.19.3. Schema
    • None specified.
    7.19.4. Example
    {
    "epp.restoreReportRequired" : false
 }
-
    7.16.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.17. epp.secDNSInterfaces

    7.17.1. Description

    Which of the interfaces defined in Section 4 of RFC 5910 the server +

    7.19.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.20. epp.secDNSInterfaces

    7.20.1. Description

    Which of the interfaces defined in Section 4 of RFC 5910 the server supports (either dsData or keyData).

    -

    7.17.2. Type

    string

    7.17.3. Schema

    • None specified.

    7.17.4. Example

    {
+
    7.20.2. Type
    string
    7.20.3. Schema
    • None specified.
    7.20.4. Example
    {
    "epp.secDNSInterfaces" : "dsData"
 }
-
    7.17.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.18. epp.serverIssuedClientCertificate01

    7.18.1. Description

    If the EPP server uses a private CA to issue client certificates, +

    7.20.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.21. epp.serverIssuedClientCertificate01

    7.21.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 epp.clid01 and epp.pwd01 credentials. If the server will accept ICANN’s own client certificate, this parameter SHOULD be empty.

    -

    7.18.2. Type

    string

    7.18.3. Schema

    • None specified.

    7.18.4. Example

    {
+
    7.21.2. Type
    string
    7.21.3. Schema
    • None specified.
    7.21.4. Example
    {
    "epp.serverIssuedClientCertificate01" : "rst_test_client_cert.pem"
 }
-
    7.18.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.19. epp.serverIssuedClientCertificate02

    7.19.1. Description

    If the EPP server uses a private CA to issue client certificates, +

    7.21.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.22. epp.serverIssuedClientCertificate02

    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 epp.clid02 and epp.pwd02 credentials. If the server will accept ICANN’s own client certificate, this parameter SHOULD be empty.

    -

    7.19.2. Type

    string

    7.19.3. Schema

    • None specified.

    7.19.4. Example

    {
+
    7.22.2. Type
    string
    7.22.3. Schema
    • None specified.
    7.22.4. Example
    {
    "epp.serverIssuedClientCertificate02" : "rst_test_client_cert.pem"
 }
-
    7.19.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.20. general.minimalPublicDataSet

    7.20.1. Description

    if true, then the registry only supports the minimum public data set, +

    7.22.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.23. general.minimalPublicDataSet

    7.23.1. Description

    if true, then the registry only supports the minimum public data set, and does not collect registrant and/or technical contact information from registrars.

    -

    7.20.2. Type

    boolean

    7.20.3. Schema

    • None specified.

    7.20.4. Example

    {
+
    7.23.2. Type
    boolean
    7.23.3. Schema
    • None specified.
    7.23.4. Example
    {
    "general.minimalPublicDataSet" : true
 }
-
    7.20.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.21. integration.rdeSFTPDirectory

    7.21.1. Description

    The directory on the SFTP server where deposit files may be +

    7.23.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.24. integration.rdeSFTPDirectory

    7.24.1. Description

    The directory on the SFTP server where deposit files may be found.

    -

    7.21.2. Type

    string

    7.21.3. Schema

    • None specified.

    7.21.4. Example

    {
+
    7.24.2. Type
    string
    7.24.3. Schema
    • None specified.
    7.24.4. Example
    {
    "integration.rdeSFTPDirectory" : "/path/to/deposits"
 }
-
    7.21.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.22. integration.rdeSFTPHostname

    7.22.1. Description

    The hostname of the operator’s SFTP server.

    -

    7.22.2. Type

    string

    7.22.3. Schema

    • None specified.

    7.22.4. Example

    {
+

    7.24.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.25. integration.rdeSFTPHostname

    7.25.1. Description

    The hostname of the operator’s SFTP server.

    +

    7.25.2. Type

    string

    7.25.3. Schema

    • None specified.

    7.25.4. Example

    {
    "integration.rdeSFTPHostname" : "sftp.rsp.tech"
 }
-

    7.22.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.23. integration.rdeSFTPUsername

    7.23.1. Description

    The username that can be used to connect to the SFTP server.

    -

    7.23.2. Type

    string

    7.23.3. Schema

    • None specified.

    7.23.4. Example

    {
+

    7.25.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.26. integration.rdeSFTPUsername

    7.26.1. Description

    The username that can be used to connect to the SFTP server.

    +

    7.26.2. Type

    string

    7.26.3. Schema

    • None specified.

    7.26.4. Example

    {
    "integration.rdeSFTPUsername" : "icann"
 }
-

    7.23.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.24. integration.rriACL

    7.24.1. Description

    An array of IP addresses from which requests to the RRI will be +

    7.26.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.27. integration.rriACL

    7.27.1. Description

    An array of IP addresses from which requests to the RRI will be sent.

    -

    7.24.2. Type

    array

    7.24.3. Schema

    • None specified.

    7.24.4. Example

    {
+
    7.27.2. Type
    array
    7.27.3. Schema
    • None specified.
    7.27.4. Example
    {
    "integration.rriACL" : [
       "192.168.22.1",
       "2001:DB8::22:1"
    ]
 }
-
    7.24.5. Test cases
    This input parameter is used in the following test cases:
    
-

    7.25. minimumRPMS.claimsTLD

    7.25.1. Description

    A TLD, or other registry-class zone, which has been configured to be +

    7.27.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.28. minimumRPMS.claimsTLD

    7.28.1. Description

    A TLD, or other registry-class zone, which has been configured to be in perpetual trademark claims.

    -

    7.25.2. Type

    string

    7.25.3. Schema

    • None specified.

    7.25.4. Example

    {
+
    7.28.2. Type
    string
    7.28.3. Schema
    • None specified.
    7.28.4. Example
    {
    "minimumRPMS.claimsTLD" : "tmclaims.rsp.tech"
 }
-
    7.25.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.26. minimumRPMS.sunriseModels

    7.26.1. Description

    The sunrise models supported by the EPP server. The possible values +

    7.28.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.29. minimumRPMS.sunriseModels

    7.29.1. Description

    The sunrise models supported by the EPP server. The possible values for this parameter are: * start-date * end-date * both

    -

    7.26.2. Type

    string

    7.26.3. Schema

    • None specified.

    7.26.4. Example

    {
+
    7.29.2. Type
    string
    7.29.3. Schema
    • None specified.
    7.29.4. Example
    {
    "minimumRPMS.sunriseModels" : "start-date"
 }
-
    7.26.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.27. minimumRPMS.sunriseTLD

    7.27.1. Description

    A TLD, or other registry-class zone, which has been configured to be +

    7.29.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.30. minimumRPMS.sunriseTLD

    7.30.1. Description

    A TLD, or other registry-class zone, which has been configured to be in perpetual sunrise.

    -

    7.27.2. Type

    string

    7.27.3. Schema

    • None specified.

    7.27.4. Example

    {
+
    7.30.2. Type
    string
    7.30.3. Schema
    • None specified.
    7.30.4. Example
    {
    "minimumRPMS.sunriseTLD" : "tmclaims.rsp.tech"
 }
-
    7.27.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.28. rdap.baseURLs

    7.28.1. Description

    -

    7.28.2. Type

    object

    7.28.3. Schema

    +

    7.30.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.31. rdap.baseURLs

    7.31.1. Description

    +

    7.31.2. Type

    object

    7.31.3. Schema

     patternProperties:
   ^[a-z][a-\0-9-]*[a-z]\$:
     format: url
     type: string
 type: object
-

    7.28.4. Example

    {
+

    7.31.4. Example

    {
    "rdap.baseURLs" : {
       "example" : "https://rdap.example.com/example/"
    }
 }
-

    7.28.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.29. rdap.testDomains

    7.29.1. Description

    The domain(s) that will be queried to validate domain responses. This +

    7.31.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.32. rdap.testDomains

    7.32.1. Description

    The domain(s) that will be queried to validate domain responses. This input parameter is an object, where the object properties are the TLD names and the values domain names.

    -

    7.29.2. Type

    object

    7.29.3. Schema

    +
    7.32.2. Type
    object
    7.32.3. Schema
     patternProperties:
   ^[a-z][a-\0-9-]*[a-z]\$:
     format: hostname
     type: string
 type: object
-
    7.29.4. Example
    {
+
    7.32.4. Example
    {
    "rdap.testDomains" : {
       "example" : "example.example"
    }
 }
-
    7.29.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.30. rdap.testEntities

    7.30.1. Description

    The entities(s) that will be queried to validate entity responses. +

    7.32.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.33. rdap.testEntities

    7.33.1. Description

    The entities(s) that will be queried to validate entity responses. This input parameter is an object, where the object properties are the TLD names and the values entity handles.

    -

    7.30.2. Type

    object

    7.30.3. Schema

    +
    7.33.2. Type
    object
    7.33.3. Schema
     patternProperties:
   ^[a-z][a-\0-9-]*[a-z]\$:
     type: string
 type: object
-
    7.30.4. Example
    {
+
    7.33.4. Example
    {
    "rdap.testEntities" : {
       "example" : "9999"
    }
 }
-
    7.30.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.31. rdap.testNameservers

    7.31.1. Description

    The nameservers(s) that will be queried to validate nameserver +

    7.33.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.34. rdap.testNameservers

    7.34.1. Description

    The nameservers(s) that will be queried to validate nameserver responses. This input parameter is an object, where the object properties are the TLD names and the values host names.

    -

    7.31.2. Type

    object

    7.31.3. Schema

    +
    7.34.2. Type
    object
    7.34.3. Schema
     patternProperties:
   ^[a-z][a-\0-9-]*[a-z]\$:
     format: hostname
     type: string
 type: object
-
    7.31.4. Example
    {
+
    7.34.4. Example
    {
    "rdap.testNameservers" : {
       "example" : "ns1.example.com"
    }
 }
-
    7.31.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.32. rde.depositFile

    7.32.1. Description

    an RDE deposit file. The TLD to which the deposit relates +

    7.34.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.35. rde.depositFile

    7.35.1. Description

    an RDE deposit file. The TLD to which the deposit relates MUST match one of the TLDs that are associated with the test object.

    -

    7.32.2. Type

    file

    7.32.3. Schema

    • None specified.

    7.32.4. Example

    {
+
    7.35.2. Type
    file
    7.35.3. Schema
    • None specified.
    7.35.4. Example
    {
    "rde.depositFile" : "example_20231004_FULL_S1_R0.ryde"
 }
-
    7.32.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.33. rde.publicKey

    7.33.1. Description

    a PGP public key block

    -

    7.33.2. Type

    file

    7.33.3. Schema

    • None specified.

    7.33.4. Example

    {
+

    7.35.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.36. rde.publicKey

    7.36.1. Description

    a PGP public key block

    +

    7.36.2. Type

    file

    7.36.3. Schema

    • None specified.

    7.36.4. Example

    {
    "rde.publicKey" : "rsp-rde-signing-key.asc"
 }
-

    7.33.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.34. rde.signatureFile

    7.34.1. Description

    an ASCII-armoured OpenPGP signature covering the deposit file

    -

    7.34.2. Type

    file

    7.34.3. Schema

    • None specified.

    7.34.4. Example

    {
+

    7.36.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.37. rde.signatureFile

    7.37.1. Description

    an ASCII-armoured OpenPGP signature covering the deposit file

    +

    7.37.2. Type

    file

    7.37.3. Schema

    • None specified.

    7.37.4. Example

    {
    "rde.signatureFile" : "example_20231004_FULL_S1_R0.sig"
 }
-

    7.34.5. Test cases

    This input parameter is used in the following test cases:

    -

    7.35. srsgw.eppClid01

    7.35.1. Description

    the username used to log in to the SRS Gateway EPP server

    -

    7.35.2. Type

    string

    7.35.3. Schema

    • None specified.

    7.35.4. Example

    {
+

    7.37.5. Test cases

    This input parameter is used in the following test cases:

    +

    7.38. srsgw.eppClid01

    7.38.1. Description

    the username used to log in to the SRS Gateway EPP server

    +

    7.38.2. Type

    string

    7.38.3. Schema

    • None specified.

    7.38.4. Example

    {
    "srsgw.eppClid01" : "clid-01"
 }
-

    7.35.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.36. srsgw.eppClid02

    7.36.1. Description

    the username used for transfer tests

    -

    7.36.2. Type

    string

    7.36.3. Schema

    • None specified.

    7.36.4. Example

    {
+

    7.38.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.39. srsgw.eppClid02

    7.39.1. Description

    the username used for transfer tests

    +

    7.39.2. Type

    string

    7.39.3. Schema

    • None specified.

    7.39.4. Example

    {
    "srsgw.eppClid02" : "clid-02"
 }
-

    7.36.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.37. srsgw.eppHostName

    7.37.1. Description

    the fully-qualified domain name of the SRS Gateway EPP server

    -

    7.37.2. Type

    string

    7.37.3. Schema

    • None specified.

    7.37.4. Example

    {
+

    7.39.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.40. srsgw.eppHostName

    7.40.1. Description

    the fully-qualified domain name of the SRS Gateway EPP server

    +

    7.40.2. Type

    string

    7.40.3. Schema

    • None specified.

    7.40.4. Example

    {
    "srsgw.eppHostName" : "epp.rsp.tech"
 }
-

    7.37.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.38. srsgw.eppPwd01

    7.38.1. Description

    the password used to log in to the SRS Gateway EPP server

    -

    7.38.2. Type

    string

    7.38.3. Schema

    • None specified.

    7.38.4. Example

    {
+

    7.40.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.41. srsgw.eppPwd01

    7.41.1. Description

    the password used to log in to the SRS Gateway EPP server

    +

    7.41.2. Type

    string

    7.41.3. Schema

    • None specified.

    7.41.4. Example

    {
    "srsgw.eppPwd01" : "foo2bar"
 }
-

    7.38.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.39. srsgw.eppPwd02

    7.39.1. Description

    the password used for transfer tests

    -

    7.39.2. Type

    string

    7.39.3. Schema

    • None specified.

    7.39.4. Example

    {
+

    7.41.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.42. srsgw.eppPwd02

    7.42.1. Description

    the password used for transfer tests

    +

    7.42.2. Type

    string

    7.42.3. Schema

    • None specified.

    7.42.4. Example

    {
    "srsgw.eppPwd02" : "foo3bar"
 }
-

    7.39.5. Test cases

    This input parameter is used in the following test cases:

    -
    • None specified.

    7.40. srsgw.rdapBaseURLs

    7.40.1. Description

    The RDAP base URL(s) for the TLD(s). This input parameter is an +

    7.42.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.43. srsgw.rdapBaseURLs

    7.43.1. Description

    The RDAP base URL(s) for the TLD(s). This input parameter is an object, where the object properties are the TLD names and the values are strings containing the base URL. The URL MUST end with a slash (“/”).

    -

    7.40.2. Type

    object

    7.40.3. Schema

    • None specified.

    7.40.4. Example

    {
+
    7.43.2. Type
    object
    7.43.3. Schema
    • None specified.
    7.43.4. Example
    {
    "srsgw.rdapBaseURLs" : {
       "example" : "https://rdap.example.com/example/"
    }
 }
-
    7.40.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.41. srsgw.serverIssuedClientCertificate01

    7.41.1. Description

    If the EPP server uses a private CA to issue client certificates, +

    7.43.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.44. srsgw.serverIssuedClientCertificate01

    7.44.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 srsgw.eppClid01 and srsgw.eppPwd01 credentials. If the server will accept ICANN’s own client certificate, this parameter SHOULD be empty.

    -

    7.41.2. Type

    string

    7.41.3. Schema

    • None specified.

    7.41.4. Example

    {
+
    7.44.2. Type
    string
    7.44.3. Schema
    • None specified.
    7.44.4. Example
    {
    "srsgw.serverIssuedClientCertificate01" : null
 }
-
    7.41.5. Test cases
    This input parameter is used in the following test cases:
    
-
    • None specified.

    7.42. srsgw.serverIssuedClientCertificate02

    7.42.1. Description

    If the EPP server uses a private CA to issue client certificates, +

    7.44.5. Test cases

    This input parameter is used in the following test cases:

    +
    • None specified.

    7.45. srsgw.serverIssuedClientCertificate02

    7.45.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 srsgw.eppClid02 and srsgw.eppPwd02 credentials. If the server will accept ICANN’s own client certificate, this parameter SHOULD be empty.

    -

    7.42.2. Type

    string

    7.42.3. Schema

    • None specified.

    7.42.4. Example

    {
+
    7.45.2. Type
    string
    7.45.3. Schema
    • None specified.
    7.45.4. Example
    {
    "srsgw.serverIssuedClientCertificate02" : null
 }
-
    7.42.5. Test cases
    This input parameter is used in the following test cases:
    
+

    7.45.5. Test cases

    This input parameter is used in the following test cases:

    • None specified.

    8. Errors

    8.1. DNSSEC_DNS_QUERY_ERROR

    8.1.1. Severity

    ERROR

    8.1.2. Description

    An error occurred while performing DNS query(s).

    8.2. DNSSEC_INVALID_DIGEST_ALGORITHM

    8.2.1. Severity

    ERROR

    8.2.2. Description

    An invalid algorithm is used in the provided DS record(s).

    8.3. DNSSEC_INVALID_SIGNING_ALGORITHM

    8.3.1. Severity

    ERROR

    8.3.2. Description

    An invalid algorithm is used to sign the zone.

    8.4. DNSSEC_OPS_ALGORITHM_ROLLOVER_CHAIN_OF_TRUST_BROKEN

    8.4.1. Severity

    ERROR

    8.4.2. Description

    TBA.

    8.5. DNSSEC_OPS_ALGORITHM_ROLLOVER_NOT_COMPLETED

    8.5.1. Severity

    ERROR

    8.5.2. Description

    TBA.

    -

    8.6. DNSSEC_OPS_KSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN

    8.6.1. Severity

    ERROR

    8.6.2. Description

    TBA.

    -

    8.7. DNSSEC_OPS_KSK_ROLLOVER_NOT_COMPLETED

    8.7.1. Severity

    ERROR

    8.7.2. Description

    TBA.

    -

    8.8. DNSSEC_OPS_ZSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN

    8.8.1. Severity

    ERROR

    8.8.2. Description

    TBA.

    -

    8.9. DNSSEC_OPS_ZSK_ROLLOVER_NOT_COMPLETED

    8.9.1. Severity

    ERROR

    8.9.2. Description

    TBA.

    -

    8.10. EPP_CONTACT_CHECK_INVALID_CONTACT_ID_INCORRECT_AVAIL

    8.10.1. Severity

    ERROR

    8.10.2. Description

    TBA.

    -

    8.11. EPP_CONTACT_CHECK_REGISTERED_CONTACT_ID_INCORRECT_AVAIL

    8.11.1. Severity

    ERROR

    8.11.2. Description

    TBA.

    -

    8.12. EPP_CONTACT_CHECK_VALID_CONTACT_ID_INCORRECT_AVAIL

    8.12.1. Severity

    ERROR

    8.12.2. Description

    TBA.

    -

    8.13. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC

    8.13.1. Severity

    ERROR

    8.13.2. Description

    TBA.

    -

    8.14. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CITY

    8.14.1. Severity

    ERROR

    8.14.2. Description

    TBA.

    -

    8.15. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL

    8.15.1. Severity

    ERROR

    8.15.2. Description

    TBA.

    -

    8.16. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ID

    8.16.1. Severity

    ERROR

    8.16.2. Description

    TBA.

    -

    8.17. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_NAME

    8.17.1. Severity

    ERROR

    8.17.2. Description

    TBA.

    -

    8.18. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ORG

    8.18.1. Severity

    ERROR

    8.18.2. Description

    TBA.

    -

    8.19. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_PC

    8.19.1. Severity

    ERROR

    8.19.2. Description

    TBA.

    -

    8.20. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_POSTALINFO_TYPE

    8.20.1. Severity

    ERROR

    8.20.2. Description

    TBA.

    -

    8.21. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_SP

    8.21.1. Severity

    ERROR

    8.21.2. Description

    TBA.

    -

    8.22. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STATUS

    8.22.1. Severity

    ERROR

    8.22.2. Description

    TBA.

    -

    8.23. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STREET

    8.23.1. Severity

    ERROR

    8.23.2. Description

    TBA.

    -

    8.24. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE

    8.24.1. Severity

    ERROR

    8.24.2. Description

    TBA.

    -

    8.25. EPP_CONTACT_CREATE_INFO_RESPONSE_NOT_1000

    8.25.1. Severity

    ERROR

    8.25.2. Description

    TBA.

    -

    8.26. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_CC

    8.26.1. Severity

    ERROR

    8.26.2. Description

    TBA.

    -

    8.27. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_EMAIL

    8.27.1. Severity

    ERROR

    8.27.2. Description

    TBA.

    -

    8.28. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_ID

    8.28.1. Severity

    ERROR

    8.28.2. Description

    TBA.

    -

    8.29. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_POSTALINFO_TYPE

    8.29.1. Severity

    ERROR

    8.29.2. Description

    TBA.

    -

    8.30. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_STATUS

    8.30.1. Severity

    ERROR

    8.30.2. Description

    TBA.

    -

    8.31. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_VOICE

    8.31.1. Severity

    ERROR

    8.31.2. Description

    TBA.

    -

    8.32. EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS

    8.32.1. Severity

    ERROR

    8.32.2. Description

    TBA.

    -

    8.33. EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001

    8.33.1. Severity

    ERROR

    8.33.2. Description

    TBA.

    -

    8.34. EPP_CONTACT_INFO_RESPONSE_NOT_2201

    8.34.1. Severity

    ERROR

    8.34.2. Description

    TBA.

    -

    8.35. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC

    8.35.1. Severity

    ERROR

    8.35.2. Description

    TBA.

    -

    8.36. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CITY

    8.36.1. Severity

    ERROR

    8.36.2. Description

    TBA.

    -

    8.37. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL

    8.37.1. Severity

    ERROR

    8.37.2. Description

    TBA.

    -

    8.38. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ID

    8.38.1. Severity

    ERROR

    8.38.2. Description

    TBA.

    -

    8.39. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_NAME

    8.39.1. Severity

    ERROR

    8.39.2. Description

    TBA.

    -

    8.40. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ORG

    8.40.1. Severity

    ERROR

    8.40.2. Description

    TBA.

    -

    8.41. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_PC

    8.41.1. Severity

    ERROR

    8.41.2. Description

    TBA.

    -

    8.42. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_POSTALINFO_TYPE

    8.42.1. Severity

    ERROR

    8.42.2. Description

    TBA.

    -

    8.43. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_SP

    8.43.1. Severity

    ERROR

    8.43.2. Description

    TBA.

    -

    8.44. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STATUS

    8.44.1. Severity

    ERROR

    8.44.2. Description

    TBA.

    -

    8.45. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STREET

    8.45.1. Severity

    ERROR

    8.45.2. Description

    TBA.

    -

    8.46. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE

    8.46.1. Severity

    ERROR

    8.46.2. Description

    TBA.

    -

    8.47. EPP_CONTACT_UPDATE_INFO_RESPONSE_NOT_1000

    8.47.1. Severity

    ERROR

    8.47.2. Description

    TBA.

    -

    8.48. EPP_CONTACT_UPDATE_RESPONSE_NOT_2201

    8.48.1. Severity

    ERROR

    8.48.2. Description

    TBA.

    -

    8.49. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_CC

    8.49.1. Severity

    ERROR

    8.49.2. Description

    TBA.

    -

    8.50. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_CITY

    8.50.1. Severity

    ERROR

    8.50.2. Description

    TBA.

    -

    8.51. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_EMAIL

    8.51.1. Severity

    ERROR

    8.51.2. Description

    TBA.

    -

    8.52. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_ORG

    8.52.1. Severity

    ERROR

    8.52.2. Description

    TBA.

    -

    8.53. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_PC

    8.53.1. Severity

    ERROR

    8.53.2. Description

    TBA.

    -

    8.54. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_POSTALINFO_TYPE

    8.54.1. Severity

    ERROR

    8.54.2. Description

    TBA.

    -

    8.55. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_SP

    8.55.1. Severity

    ERROR

    8.55.2. Description

    TBA.

    -

    8.56. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_STATUS

    8.56.1. Severity

    ERROR

    8.56.2. Description

    TBA.

    -

    8.57. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_STREET

    8.57.1. Severity

    ERROR

    8.57.2. Description

    TBA.

    -

    8.58. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_VOICE

    8.58.1. Severity

    ERROR

    8.58.2. Description

    TBA.

    -

    8.59. EPP_DNS_RESOLUTION_ERROR

    8.59.1. Severity

    ERROR

    8.59.2. Description

    There was an error while performing a DNS query for the EPP server +

    8.6. DNSSEC_OPS_INVALID_ALGORITHM

    8.6.1. Severity

    ERROR

    8.6.2. Description

    TBA.

    +

    8.7. DNSSEC_OPS_KSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN

    8.7.1. Severity

    ERROR

    8.7.2. Description

    TBA.

    +

    8.8. DNSSEC_OPS_KSK_ROLLOVER_NOT_COMPLETED

    8.8.1. Severity

    ERROR

    8.8.2. Description

    TBA.

    +

    8.9. DNSSEC_OPS_XFR_FAILED

    8.9.1. Severity

    ERROR

    8.9.2. Description

    TBA.

    +

    8.10. DNSSEC_OPS_ZSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN

    8.10.1. Severity

    ERROR

    8.10.2. Description

    TBA.

    +

    8.11. DNSSEC_OPS_ZSK_ROLLOVER_NOT_COMPLETED

    8.11.1. Severity

    ERROR

    8.11.2. Description

    TBA.

    +

    8.12. EPP_CONTACT_CHECK_INVALID_CONTACT_ID_INCORRECT_AVAIL

    8.12.1. Severity

    ERROR

    8.12.2. Description

    TBA.

    +

    8.13. EPP_CONTACT_CHECK_REGISTERED_CONTACT_ID_INCORRECT_AVAIL

    8.13.1. Severity

    ERROR

    8.13.2. Description

    TBA.

    +

    8.14. EPP_CONTACT_CHECK_VALID_CONTACT_ID_INCORRECT_AVAIL

    8.14.1. Severity

    ERROR

    8.14.2. Description

    TBA.

    +

    8.15. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC

    8.15.1. Severity

    ERROR

    8.15.2. Description

    TBA.

    +

    8.16. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CITY

    8.16.1. Severity

    ERROR

    8.16.2. Description

    TBA.

    +

    8.17. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL

    8.17.1. Severity

    ERROR

    8.17.2. Description

    TBA.

    +

    8.18. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ID

    8.18.1. Severity

    ERROR

    8.18.2. Description

    TBA.

    +

    8.19. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_NAME

    8.19.1. Severity

    ERROR

    8.19.2. Description

    TBA.

    +

    8.20. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ORG

    8.20.1. Severity

    ERROR

    8.20.2. Description

    TBA.

    +

    8.21. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_PC

    8.21.1. Severity

    ERROR

    8.21.2. Description

    TBA.

    +

    8.22. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_POSTALINFO_TYPE

    8.22.1. Severity

    ERROR

    8.22.2. Description

    TBA.

    +

    8.23. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_SP

    8.23.1. Severity

    ERROR

    8.23.2. Description

    TBA.

    +

    8.24. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STATUS

    8.24.1. Severity

    ERROR

    8.24.2. Description

    TBA.

    +

    8.25. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STREET

    8.25.1. Severity

    ERROR

    8.25.2. Description

    TBA.

    +

    8.26. EPP_CONTACT_CREATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE

    8.26.1. Severity

    ERROR

    8.26.2. Description

    TBA.

    +

    8.27. EPP_CONTACT_CREATE_INFO_RESPONSE_NOT_1000

    8.27.1. Severity

    ERROR

    8.27.2. Description

    TBA.

    +

    8.28. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_CC

    8.28.1. Severity

    ERROR

    8.28.2. Description

    TBA.

    +

    8.29. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_EMAIL

    8.29.1. Severity

    ERROR

    8.29.2. Description

    TBA.

    +

    8.30. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_ID

    8.30.1. Severity

    ERROR

    8.30.2. Description

    TBA.

    +

    8.31. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_POSTALINFO_TYPE

    8.31.1. Severity

    ERROR

    8.31.2. Description

    TBA.

    +

    8.32. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_STATUS

    8.32.1. Severity

    ERROR

    8.32.2. Description

    TBA.

    +

    8.33. EPP_CONTACT_CREATE_SERVER_ACCEPTS_INVALID_VOICE

    8.33.1. Severity

    ERROR

    8.33.2. Description

    TBA.

    +

    8.34. EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS

    8.34.1. Severity

    ERROR

    8.34.2. Description

    TBA.

    +

    8.35. EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001

    8.35.1. Severity

    ERROR

    8.35.2. Description

    TBA.

    +

    8.36. EPP_CONTACT_INFO_RESPONSE_NOT_2201

    8.36.1. Severity

    ERROR

    8.36.2. Description

    TBA.

    +

    8.37. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CC

    8.37.1. Severity

    ERROR

    8.37.2. Description

    TBA.

    +

    8.38. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_CITY

    8.38.1. Severity

    ERROR

    8.38.2. Description

    TBA.

    +

    8.39. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_EMAIL

    8.39.1. Severity

    ERROR

    8.39.2. Description

    TBA.

    +

    8.40. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ID

    8.40.1. Severity

    ERROR

    8.40.2. Description

    TBA.

    +

    8.41. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_NAME

    8.41.1. Severity

    ERROR

    8.41.2. Description

    TBA.

    +

    8.42. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_ORG

    8.42.1. Severity

    ERROR

    8.42.2. Description

    TBA.

    +

    8.43. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_PC

    8.43.1. Severity

    ERROR

    8.43.2. Description

    TBA.

    +

    8.44. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_POSTALINFO_TYPE

    8.44.1. Severity

    ERROR

    8.44.2. Description

    TBA.

    +

    8.45. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_SP

    8.45.1. Severity

    ERROR

    8.45.2. Description

    TBA.

    +

    8.46. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STATUS

    8.46.1. Severity

    ERROR

    8.46.2. Description

    TBA.

    +

    8.47. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_STREET

    8.47.1. Severity

    ERROR

    8.47.2. Description

    TBA.

    +

    8.48. EPP_CONTACT_UPDATE_INFO_RESPONSE_MISSING_OR_INCORRECT_VOICE

    8.48.1. Severity

    ERROR

    8.48.2. Description

    TBA.

    +

    8.49. EPP_CONTACT_UPDATE_INFO_RESPONSE_NOT_1000

    8.49.1. Severity

    ERROR

    8.49.2. Description

    TBA.

    +

    8.50. EPP_CONTACT_UPDATE_RESPONSE_NOT_2201

    8.50.1. Severity

    ERROR

    8.50.2. Description

    TBA.

    +

    8.51. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_CC

    8.51.1. Severity

    ERROR

    8.51.2. Description

    TBA.

    +

    8.52. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_CITY

    8.52.1. Severity

    ERROR

    8.52.2. Description

    TBA.

    +

    8.53. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_EMAIL

    8.53.1. Severity

    ERROR

    8.53.2. Description

    TBA.

    +

    8.54. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_ORG

    8.54.1. Severity

    ERROR

    8.54.2. Description

    TBA.

    +

    8.55. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_PC

    8.55.1. Severity

    ERROR

    8.55.2. Description

    TBA.

    +

    8.56. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_POSTALINFO_TYPE

    8.56.1. Severity

    ERROR

    8.56.2. Description

    TBA.

    +

    8.57. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_SP

    8.57.1. Severity

    ERROR

    8.57.2. Description

    TBA.

    +

    8.58. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_STATUS

    8.58.1. Severity

    ERROR

    8.58.2. Description

    TBA.

    +

    8.59. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_STREET

    8.59.1. Severity

    ERROR

    8.59.2. Description

    TBA.

    +

    8.60. EPP_CONTACT_UPDATE_SERVER_ACCEPTS_INVALID_VOICE

    8.60.1. Severity

    ERROR

    8.60.2. Description

    TBA.

    +

    8.61. EPP_DNS_RESOLUTION_ERROR

    8.61.1. Severity

    ERROR

    8.61.2. Description

    There was an error while performing a DNS query for the EPP server hostname.

    -

    8.60. EPP_DOMAIN_CHECK_INVALID_DOMAIN_INCORRECT_AVAIL

    8.60.1. Severity

    ERROR

    8.60.2. Description

    TBA.

    -

    8.61. EPP_DOMAIN_CHECK_REGISTERED_DOMAIN_INCORRECT_AVAIL

    8.61.1. Severity

    ERROR

    8.61.2. Description

    TBA.

    -

    8.62. EPP_DOMAIN_CHECK_VALID_DOMAIN_INCORRECT_AVAIL

    8.62.1. Severity

    ERROR

    8.62.2. Description

    TBA.

    -

    8.63. EPP_DOMAIN_CREATE_INFO_RESPONSE_INVALID_ROID

    8.63.1. Severity

    ERROR

    8.63.2. Description

    TBA

    -

    8.64. EPP_DOMAIN_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.64.1. Severity

    ERROR

    8.64.2. Description

    TBA

    -

    8.65. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_AUTHINFO

    8.65.1. Severity

    ERROR

    8.65.2. Description

    TBA

    -

    8.66. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_ATTRIBUTES

    8.66.1. Severity

    ERROR

    8.66.2. Description

    TBA

    -

    8.67. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_ATTRIBUTES_WITHOUT_GLUE

    8.67.1. Severity

    ERROR

    8.67.2. Description

    TBA

    -

    8.68. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_OBJECTS

    8.68.1. Severity

    ERROR

    8.68.2. Description

    TBA

    -

    8.69. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_DNSSEC_DATA

    8.69.1. Severity

    ERROR

    8.69.2. Description

    TBA

    -

    8.70. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_DOMAIN_NAME

    8.70.1. Severity

    ERROR

    8.70.2. Description

    TBA

    -

    8.71. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_HOST_ATTRIBUTE

    8.71.1. Severity

    ERROR

    8.71.2. Description

    TBA

    -

    8.72. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_HOST_ATTRIBUTES

    8.72.1. Severity

    ERROR

    8.72.2. Description

    TBA

    -

    8.73. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_PERIOD

    8.73.1. Severity

    ERROR

    8.73.2. Description

    TBA

    -

    8.74. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NON_EXISTENT_CONTACT_OBJECT

    8.74.1. Severity

    ERROR

    8.74.2. Description

    TBA

    -

    8.75. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NON_EXISTENT_HOST_OBJECT

    8.75.1. Severity

    ERROR

    8.75.2. Description

    TBA

    -

    8.76. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NO_REGISTRANT_FOR_THICK_REGISTRY

    8.76.1. Severity

    ERROR

    8.76.2. Description

    TBA

    -

    8.77. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_REGISTRANT_FOR_THIN_REGISTRY

    8.77.1. Severity

    ERROR

    8.77.2. Description

    TBA

    -

    8.78. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE

    8.78.1. Severity

    ERROR

    8.78.2. Description

    TBA

    -

    8.79. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.79.1. Severity

    ERROR

    8.79.2. Description

    TBA

    -

    8.80. EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE

    8.80.1. Severity

    ERROR

    8.80.2. Description

    TBA

    -

    8.81. EPP_GENERIC_COMMAND_ERROR

    8.81.1. Severity

    ERROR

    8.81.2. Description

    The client received a 2400 error from the server.

    -

    8.82. EPP_GREETING_INVALID_LANG

    8.82.1. Severity

    ERROR

    8.82.2. Description

    The value of one or more of the <lang> elements in +

    8.62. EPP_DOMAIN_CHECK_INVALID_DOMAIN_INCORRECT_AVAIL

    8.62.1. Severity

    ERROR

    8.62.2. Description

    TBA.

    +

    8.63. EPP_DOMAIN_CHECK_REGISTERED_DOMAIN_INCORRECT_AVAIL

    8.63.1. Severity

    ERROR

    8.63.2. Description

    TBA.

    +

    8.64. EPP_DOMAIN_CHECK_VALID_DOMAIN_INCORRECT_AVAIL

    8.64.1. Severity

    ERROR

    8.64.2. Description

    TBA.

    +

    8.65. EPP_DOMAIN_CREATE_INFO_RESPONSE_INVALID_ROID

    8.65.1. Severity

    ERROR

    8.65.2. Description

    TBA

    +

    8.66. EPP_DOMAIN_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.66.1. Severity

    ERROR

    8.66.2. Description

    TBA

    +

    8.67. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_AUTHINFO

    8.67.1. Severity

    ERROR

    8.67.2. Description

    TBA

    +

    8.68. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_ATTRIBUTES

    8.68.1. Severity

    ERROR

    8.68.2. Description

    TBA

    +

    8.69. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_ATTRIBUTES_WITHOUT_GLUE

    8.69.1. Severity

    ERROR

    8.69.2. Description

    TBA

    +

    8.70. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_HOST_OBJECTS

    8.70.1. Severity

    ERROR

    8.70.2. Description

    TBA

    +

    8.71. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_DNSSEC_DATA

    8.71.1. Severity

    ERROR

    8.71.2. Description

    TBA

    +

    8.72. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_DOMAIN_NAME

    8.72.1. Severity

    ERROR

    8.72.2. Description

    TBA

    +

    8.73. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_HOST_ATTRIBUTE

    8.73.1. Severity

    ERROR

    8.73.2. Description

    TBA

    +

    8.74. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_HOST_ATTRIBUTES

    8.74.1. Severity

    ERROR

    8.74.2. Description

    TBA

    +

    8.75. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_INVALID_PERIOD

    8.75.1. Severity

    ERROR

    8.75.2. Description

    TBA

    +

    8.76. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NON_EXISTENT_CONTACT_OBJECT

    8.76.1. Severity

    ERROR

    8.76.2. Description

    TBA

    +

    8.77. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NON_EXISTENT_HOST_OBJECT

    8.77.1. Severity

    ERROR

    8.77.2. Description

    TBA

    +

    8.78. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_NO_REGISTRANT_FOR_THICK_REGISTRY

    8.78.1. Severity

    ERROR

    8.78.2. Description

    TBA

    +

    8.79. EPP_DOMAIN_CREATE_SERVER_ACCEPTS_REGISTRANT_FOR_THIN_REGISTRY

    8.79.1. Severity

    ERROR

    8.79.2. Description

    TBA

    +

    8.80. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE

    8.80.1. Severity

    ERROR

    8.80.2. Description

    TBA

    +

    8.81. EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.81.1. Severity

    ERROR

    8.81.2. Description

    TBA

    +

    8.82. EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE

    8.82.1. Severity

    ERROR

    8.82.2. Description

    TBA

    +

    8.83. EPP_GENERIC_COMMAND_ERROR

    8.83.1. Severity

    ERROR

    8.83.2. Description

    The client received a 2400 error from the server.

    +

    8.84. EPP_GREETING_INVALID_LANG

    8.84.1. Severity

    ERROR

    8.84.2. Description

    The value of one or more of the <lang> elements in the <greeting> are invalid.

    -

    8.83. EPP_GREETING_MISSING_EXTURI

    8.83.1. Severity

    ERROR

    8.83.2. Description

    A mandatory extension namespace URI is missing.

    -

    8.84. EPP_GREETING_MISSING_OBJURI

    8.84.1. Severity

    ERROR

    8.84.2. Description

    A mandatory object namespace URI is missing.

    -

    8.85. EPP_GREETING_RECOMMENDED_EXTENSION_MISSING

    8.85.1. Severity

    WARNING

    8.85.2. Description

    The server does not include the namespace URI of a recommended +

    8.85. EPP_GREETING_MISSING_EXTURI

    8.85.1. Severity

    ERROR

    8.85.2. Description

    A mandatory extension namespace URI is missing.

    +

    8.86. EPP_GREETING_MISSING_OBJURI

    8.86.1. Severity

    ERROR

    8.86.2. Description

    A mandatory object namespace URI is missing.

    +

    8.87. EPP_GREETING_RECOMMENDED_EXTENSION_MISSING

    8.87.1. Severity

    WARNING

    8.87.2. Description

    The server does not include the namespace URI of a recommended extension in an <extURI> element of the <greeting> frame.

    -

    8.86. EPP_GREETING_SVDATE_INVALID

    8.86.1. Severity

    ERROR

    8.86.2. Description

    The value of the <svDate> element in the +

    8.88. EPP_GREETING_SVDATE_INVALID

    8.88.1. Severity

    ERROR

    8.88.2. Description

    The value of the <svDate> element in the <greeting> is invalid.

    -

    8.87. EPP_GREETING_SVID_INVALID

    8.87.1. Severity

    ERROR

    8.87.2. Description

    The value of the <svID> element in the +

    8.89. EPP_GREETING_SVID_INVALID

    8.89.1. Severity

    ERROR

    8.89.2. Description

    The value of the <svID> element in the <greeting> is invalid.

    -

    8.88. EPP_GREETING_UNEXPECTED_EXTURI

    8.88.1. Severity

    ERROR

    8.88.2. Description

    One or more of the <extRI> elements in the +

    8.90. EPP_GREETING_UNEXPECTED_EXTURI

    8.90.1. Severity

    ERROR

    8.90.2. Description

    One or more of the <extRI> elements in the <greeting> contain invalid namespace URIs.

    -

    8.89. EPP_GREETING_UNEXPECTED_OBJURI

    8.89.1. Severity

    ERROR

    8.89.2. Description

    One or more of the <objURI> elements in the +

    8.91. EPP_GREETING_UNEXPECTED_OBJURI

    8.91.1. Severity

    ERROR

    8.91.2. Description

    One or more of the <objURI> elements in the <greeting> contain invalid namespace URIs.

    -

    8.90. EPP_GREETING_VERSION_INVALID

    8.90.1. Severity

    ERROR

    8.90.2. Description

    The value of the <version> element in the +

    8.92. EPP_GREETING_VERSION_INVALID

    8.92.1. Severity

    ERROR

    8.92.2. Description

    The value of the <version> element in the <greeting> is invalid.

    -

    8.91. EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL

    8.91.1. Severity

    ERROR

    8.91.2. Description

    TBA.

    -

    8.92. EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL

    8.92.1. Severity

    ERROR

    8.92.2. Description

    TBA.

    -

    8.93. EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL

    8.93.1. Severity

    ERROR

    8.93.2. Description

    TBA.

    -

    8.94. EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.94.1. Severity

    ERROR

    8.94.2. Description

    TBA

    -

    8.95. EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.95.1. Severity

    ERROR

    8.95.2. Description

    TBA

    -

    8.96. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.96.1. Severity

    ERROR

    8.96.2. Description

    TBA

    -

    8.97. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.97.1. Severity

    ERROR

    8.97.2. Description

    TBA

    -

    8.98. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.98.1. Severity

    ERROR

    8.98.2. Description

    TBA

    -

    8.99. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.99.1. Severity

    ERROR

    8.99.2. Description

    TBA

    -

    8.100. EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.100.1. Severity

    ERROR

    8.100.2. Description

    TBA

    -

    8.101. EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.101.1. Severity

    ERROR

    8.101.2. Description

    TBA

    -

    8.102. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN

    8.102.1. Severity

    ERROR

    8.102.2. Description

    TBA

    -

    8.103. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_NONEXISTENT_DOMAIN

    8.103.1. Severity

    ERROR

    8.103.2. Description

    TBA

    -

    8.104. EPP_HOST_RENAME_SERVER_REJECTS_OUT_OF_BAILIWICK_NAME

    8.104.1. Severity

    ERROR

    8.104.2. Description

    TBA

    -

    8.105. EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME

    8.105.1. Severity

    ERROR

    8.105.2. Description

    TBA

    -

    8.106. EPP_HOST_UPDATE_AUTHZ_ERROR

    8.106.1. Severity

    ERROR

    8.106.2. Description

    TBA

    -

    8.107. EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.107.1. Severity

    ERROR

    8.107.2. Description

    TBA

    -

    8.108. EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.108.1. Severity

    ERROR

    8.108.2. Description

    TBA

    -

    8.109. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.109.1. Severity

    ERROR

    8.109.2. Description

    TBA

    -

    8.110. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.110.1. Severity

    ERROR

    8.110.2. Description

    TBA

    -

    8.111. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.111.1. Severity

    ERROR

    8.111.2. Description

    TBA

    -

    8.112. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.112.1. Severity

    ERROR

    8.112.2. Description

    TBA

    -

    8.113. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT

    8.113.1. Severity

    ERROR

    8.113.2. Description

    TBA

    -

    8.114. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT

    8.114.1. Severity

    ERROR

    8.114.2. Description

    TBA

    -

    8.115. EPP_LOGIN_ERROR

    8.115.1. Severity

    ERROR

    8.115.2. Description

    The client was unable to successfullt authenticate with the EPP +

    8.93. EPP_HOST_CHECK_INVALID_HOST_INCORRECT_AVAIL

    8.93.1. Severity

    ERROR

    8.93.2. Description

    TBA.

    +

    8.94. EPP_HOST_CHECK_REGISTERED_HOST_INCORRECT_AVAIL

    8.94.1. Severity

    ERROR

    8.94.2. Description

    TBA.

    +

    8.95. EPP_HOST_CHECK_VALID_HOST_INCORRECT_AVAIL

    8.95.1. Severity

    ERROR

    8.95.2. Description

    TBA.

    +

    8.96. EPP_HOST_CREATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.96.1. Severity

    ERROR

    8.96.2. Description

    TBA

    +

    8.97. EPP_HOST_CREATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.97.1. Severity

    ERROR

    8.97.2. Description

    TBA

    +

    8.98. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.98.1. Severity

    ERROR

    8.98.2. Description

    TBA

    +

    8.99. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.99.1. Severity

    ERROR

    8.99.2. Description

    TBA

    +

    8.100. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.100.1. Severity

    ERROR

    8.100.2. Description

    TBA

    +

    8.101. EPP_HOST_CREATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.101.1. Severity

    ERROR

    8.101.2. Description

    TBA

    +

    8.102. EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS

    8.102.1. Severity

    ERROR

    8.102.2. Description

    TBA

    +

    8.103. EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.103.1. Severity

    ERROR

    8.103.2. Description

    TBA

    +

    8.104. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN

    8.104.1. Severity

    ERROR

    8.104.2. Description

    TBA

    +

    8.105. EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_NONEXISTENT_DOMAIN

    8.105.1. Severity

    ERROR

    8.105.2. Description

    TBA

    +

    8.106. EPP_HOST_RENAME_SERVER_REJECTS_OUT_OF_BAILIWICK_NAME

    8.106.1. Severity

    ERROR

    8.106.2. Description

    TBA

    +

    8.107. EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME

    8.107.1. Severity

    ERROR

    8.107.2. Description

    TBA

    +

    8.108. EPP_HOST_UPDATE_AUTHZ_ERROR

    8.108.1. Severity

    ERROR

    8.108.2. Description

    TBA

    +

    8.109. EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES

    8.109.1. Severity

    ERROR

    8.109.2. Description

    TBA

    +

    8.110. EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST

    8.110.1. Severity

    ERROR

    8.110.2. Description

    TBA

    +

    8.111. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_HOSTNAME

    8.111.1. Severity

    ERROR

    8.111.2. Description

    TBA

    +

    8.112. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPV4_ADDRESS

    8.112.1. Severity

    ERROR

    8.112.2. Description

    TBA

    +

    8.113. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_IPv6_ADDRESS

    8.113.1. Severity

    ERROR

    8.113.2. Description

    TBA

    +

    8.114. EPP_HOST_UPDATE_SERVER_ACCEPTS_INVALID_STATUS_CODE

    8.114.1. Severity

    ERROR

    8.114.2. Description

    TBA

    +

    8.115. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT

    8.115.1. Severity

    ERROR

    8.115.2. Description

    TBA

    +

    8.116. EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT

    8.116.1. Severity

    ERROR

    8.116.2. Description

    TBA

    +

    8.117. EPP_LOGIN_ERROR

    8.117.1. Severity

    ERROR

    8.117.2. Description

    The client was unable to successfullt authenticate with the EPP server.

    -

    8.116. EPP_MISSING_AAAA_RECORDS

    8.116.1. Severity

    WARNING

    8.116.2. Description

    No AAAA record(s) were found for the EPP server +

    8.118. EPP_MISSING_AAAA_RECORDS

    8.118.1. Severity

    WARNING

    8.118.2. Description

    No AAAA record(s) were found for the EPP server hostname.

    -

    8.117. EPP_MISSING_A_RECORDS

    8.117.1. Severity

    ERROR

    8.117.2. Description

    No A record(s) were found for the EPP server +

    8.119. EPP_MISSING_A_RECORDS

    8.119.1. Severity

    ERROR

    8.119.2. Description

    No A record(s) were found for the EPP server hostname.

    -

    8.118. EPP_NO_GREETING_RECEIVED

    8.118.1. Severity

    ERROR

    8.118.2. Description

    No <greeting> was received after successful +

    8.120. EPP_NO_GREETING_RECEIVED

    8.120.1. Severity

    ERROR

    8.120.2. Description

    No <greeting> was received after successful connection.

    -

    8.119. EPP_OBJECT_SHOULD_EXIST

    8.119.1. Severity

    ERROR

    8.119.2. Description

    TBA

    -

    8.120. EPP_OBJECT_SHOULD_NOT_EXIST

    8.120.1. Severity

    ERROR

    8.120.2. Description

    TBA

    -

    8.121. EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.121.1. Severity

    ERROR

    8.121.2. Description

    TBA

    -

    8.122. EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.122.1. Severity

    ERROR

    8.122.2. Description

    TBA

    -

    8.123. EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE

    8.123.1. Severity

    ERROR

    8.123.2. Description

    TBA

    -

    8.124. EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD

    8.124.1. Severity

    ERROR

    8.124.2. Description

    TBA

    -

    8.125. EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE

    8.125.1. Severity

    ERROR

    8.125.2. Description

    TBA

    -

    8.126. EPP_SCHEMA_VALIDATION_ERROR

    8.126.1. Severity

    ERROR

    8.126.2. Description

    The response from the server failed schema validation.

    -

    8.127. EPP_SERVICE_PORT_UNREACHABLE

    8.127.1. Severity

    ERROR

    8.127.2. Description

    The EPP service port (tcp/700) could not be connected to.

    -

    8.128. EPP_TLS_BAD_CIPHER

    8.128.1. Severity

    ERROR

    8.128.2. Description

    The server uses an encryption cipher not recommended in RFC 9325.

    -

    8.129. EPP_TLS_CERTIFICATE_CHAIN_MISSING

    8.129.1. Severity

    ERROR

    8.129.2. Description

    One or more intermediate certificates are missing.

    -

    8.130. EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH

    8.130.1. Severity

    ERROR

    8.130.2. Description

    The hostname in the TLS certificate does not match the EPP server +

    8.121. EPP_OBJECT_SHOULD_EXIST

    8.121.1. Severity

    ERROR

    8.121.2. Description

    TBA

    +

    8.122. EPP_OBJECT_SHOULD_NOT_EXIST

    8.122.1. Severity

    ERROR

    8.122.2. Description

    TBA

    +

    8.123. EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.123.1. Severity

    ERROR

    8.123.2. Description

    TBA

    +

    8.124. EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.124.1. Severity

    ERROR

    8.124.2. Description

    TBA

    +

    8.125. EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE

    8.125.1. Severity

    ERROR

    8.125.2. Description

    TBA

    +

    8.126. EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD

    8.126.1. Severity

    ERROR

    8.126.2. Description

    TBA

    +

    8.127. EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE

    8.127.1. Severity

    ERROR

    8.127.2. Description

    TBA

    +

    8.128. EPP_SCHEMA_VALIDATION_ERROR

    8.128.1. Severity

    ERROR

    8.128.2. Description

    The response from the server failed schema validation.

    +

    8.129. EPP_SERVICE_PORT_UNREACHABLE

    8.129.1. Severity

    ERROR

    8.129.2. Description

    The EPP service port (tcp/700) could not be connected to.

    +

    8.130. EPP_TLS_BAD_CIPHER

    8.130.1. Severity

    ERROR

    8.130.2. Description

    The server uses an encryption cipher not recommended in RFC 9325.

    +

    8.131. EPP_TLS_CERTIFICATE_CHAIN_MISSING

    8.131.1. Severity

    ERROR

    8.131.2. Description

    One or more intermediate certificates are missing.

    +

    8.132. EPP_TLS_CERTIFICATE_HOSTNAME_MISMATCH

    8.132.1. Severity

    ERROR

    8.132.2. Description

    The hostname in the TLS certificate does not match the EPP server hostname.

    -

    8.131. EPP_TLS_CONNECTION_ERROR

    8.131.1. Severity

    ERROR

    8.131.2. Description

    There was an error during the TLS handshake while connecting to the +

    8.133. EPP_TLS_CONNECTION_ERROR

    8.133.1. Severity

    ERROR

    8.133.2. Description

    There was an error during the TLS handshake while connecting to the EPP server.

    -

    8.132. EPP_TLS_EXPIRED_CERTIFICATE

    8.132.1. Severity

    ERROR

    8.132.2. Description

    The TLS certificate presented by the EPP server has expired.

    -

    8.133. EPP_TLS_FORBIDDEN_PROTOCOL_SUPPORTED

    8.133.1. Severity

    ERROR

    8.133.2. Description

    The EPP server implements a forbidden protocol.

    -

    8.134. EPP_TLS_REQUIRED_PROTOCOL_NOT_SUPPORTED

    8.134.1. Severity

    ERROR

    8.134.2. Description

    The EPP server does not implement a required protocol.

    -

    8.135. EPP_TLS_UNTRUSTED_CERTIFICATE

    8.135.1. Severity

    ERROR

    8.135.2. Description

    The TLS certificate presented by the EPP server is not issued by a +

    8.134. EPP_TLS_EXPIRED_CERTIFICATE

    8.134.1. Severity

    ERROR

    8.134.2. Description

    The TLS certificate presented by the EPP server has expired.

    +

    8.135. EPP_TLS_FORBIDDEN_PROTOCOL_SUPPORTED

    8.135.1. Severity

    ERROR

    8.135.2. Description

    The EPP server implements a forbidden protocol.

    +

    8.136. EPP_TLS_REQUIRED_PROTOCOL_NOT_SUPPORTED

    8.136.1. Severity

    ERROR

    8.136.2. Description

    The EPP server does not implement a required protocol.

    +

    8.137. EPP_TLS_UNTRUSTED_CERTIFICATE

    8.137.1. Severity

    ERROR

    8.137.2. Description

    The TLS certificate presented by the EPP server is not issued by a trusted Certificate Authority.

    -

    8.136. EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.136.1. Severity

    ERROR

    8.136.2. Description

    TBA

    -

    8.137. EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET

    8.137.1. Severity

    ERROR

    8.137.2. Description

    TBA

    -

    8.138. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.138.1. Severity

    ERROR

    8.138.2. Description

    TBA

    -

    8.139. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_STATUS_CODE

    8.139.1. Severity

    ERROR

    8.139.2. Description

    TBA

    -

    8.140. EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.140.1. Severity

    ERROR

    8.140.2. Description

    TBA

    -

    8.141. EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.141.1. Severity

    ERROR

    8.141.2. Description

    TBA

    -

    8.142. EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO

    8.142.1. Severity

    ERROR

    8.142.2. Description

    TBA

    -

    8.143. EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO

    8.143.1. Severity

    ERROR

    8.143.2. Description

    TBA

    -

    8.144. EPP_TRANSFER_SERVER_ACCEPTS_INVALID_PERIOD

    8.144.1. Severity

    ERROR

    8.144.2. Description

    TBA

    -

    8.145. EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER

    8.145.1. Severity

    ERROR

    8.145.2. Description

    TBA

    -

    8.146. EPP_UNEXPECTED_COMMAND_FAILURE

    8.146.1. Severity

    ERROR

    8.146.2. Description

    TBA

    -

    8.147. EPP_UNEXPECTED_COMMAND_SUCCESS

    8.147.1. Severity

    ERROR

    8.147.2. Description

    TBA

    -

    8.148. EPP_XML_PARSE_ERROR

    8.148.1. Severity

    ERROR

    8.148.2. Description

    The XML response from the server could not be parsed.

    -

    8.149. IDN_SERVER_ACCEPTS_INVALID_LABEL

    8.149.1. Severity

    ERROR

    8.149.2. Description

    TBA.

    -

    8.150. IDN_SERVER_REJECTS_VALID_LABEL

    8.150.1. Severity

    ERROR

    8.150.2. Description

    TBA.

    -

    8.151. IDN_VARIANT_LABEL_NOT_BLOCKED

    8.151.1. Severity

    ERROR

    8.151.2. Description

    TBA.

    -

    8.152. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_FROM_INCORRECT_REGISTRAR

    8.152.1. Severity

    ERROR

    8.152.2. Description

    TBA.

    -

    8.153. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_WITH_INCORRECT_REGISTRANT

    8.153.1. Severity

    ERROR

    8.153.2. Description

    TBA.

    -

    8.154. INTEGRATION_DNS_ANSWER_IS_INCORRECT

    8.154.1. Severity

    ERROR

    8.154.2. Description

    TBA.

    -

    8.155. INTEGRATION_DNS_QUERY_FAILED

    8.155.1. Severity

    ERROR

    8.155.2. Description

    TBA.

    -

    8.156. INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS

    8.156.1. Severity

    ERROR

    8.156.2. Description

    TBA.

    -

    8.157. INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP

    8.157.1. Severity

    ERROR

    8.157.2. Description

    TBA.

    -

    8.158. INTEGRATION_RDAP_REQUEST_FAILED

    8.158.1. Severity

    ERROR

    8.158.2. Description

    TBA.

    -

    8.159. INTEGRATION_RDE_DEADLINE_MISSED

    8.159.1. Severity

    ERROR

    8.159.2. Description

    TBA.

    -

    8.160. INTEGRATION_RDE_MISSING_OBJECTS

    8.160.1. Severity

    ERROR

    8.160.2. Description

    TBA.

    -

    8.161. INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR

    8.161.1. Severity

    ERROR

    8.161.2. Description

    TBA.

    -

    8.162. INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE

    8.162.1. Severity

    ERROR

    8.162.2. Description

    TBA.

    -

    8.163. RDE_CONTACT_HAS_INVALID_CC

    8.163.1. Severity

    ERROR

    8.163.2. Description

    TBA.

    -

    8.164. RDE_CONTACT_HAS_INVALID_CITY

    8.164.1. Severity

    ERROR

    8.164.2. Description

    TBA.

    -

    8.165. RDE_CONTACT_HAS_INVALID_CLID

    8.165.1. Severity

    ERROR

    8.165.2. Description

    TBA.

    -

    8.166. RDE_CONTACT_HAS_INVALID_EMAIL

    8.166.1. Severity

    ERROR

    8.166.2. Description

    TBA.

    -

    8.167. RDE_CONTACT_HAS_INVALID_ID

    8.167.1. Severity

    ERROR

    8.167.2. Description

    TBA.

    -

    8.168. RDE_CONTACT_HAS_INVALID_NAME

    8.168.1. Severity

    ERROR

    8.168.2. Description

    TBA.

    -

    8.169. RDE_CONTACT_HAS_INVALID_POSTALINFO_TYPE

    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_INVALID_STATUS

    8.171.1. Severity

    ERROR

    8.171.2. Description

    TBA.

    -

    8.172. RDE_CONTACT_HAS_INVALID_STREET

    8.172.1. Severity

    ERROR

    8.172.2. Description

    TBA.

    -

    8.173. RDE_CONTACT_HAS_INVALID_VOICE

    8.173.1. Severity

    ERROR

    8.173.2. Description

    TBA.

    -

    8.174. RDE_CONTACT_HAS_MISSING_CC

    8.174.1. Severity

    ERROR

    8.174.2. Description

    TBA.

    -

    8.175. RDE_CONTACT_HAS_MISSING_CITY

    8.175.1. Severity

    ERROR

    8.175.2. Description

    TBA.

    -

    8.176. RDE_CONTACT_HAS_MISSING_CLID

    8.176.1. Severity

    ERROR

    8.176.2. Description

    TBA.

    -

    8.177. RDE_CONTACT_HAS_MISSING_EMAIL

    8.177.1. Severity

    ERROR

    8.177.2. Description

    TBA.

    -

    8.178. RDE_CONTACT_HAS_MISSING_ID

    8.178.1. Severity

    ERROR

    8.178.2. Description

    TBA.

    -

    8.179. RDE_CONTACT_HAS_MISSING_NAME

    8.179.1. Severity

    ERROR

    8.179.2. Description

    TBA.

    -

    8.180. RDE_CONTACT_HAS_MISSING_POSTALINFO

    8.180.1. Severity

    ERROR

    8.180.2. Description

    TBA.

    -

    8.181. RDE_CONTACT_HAS_MISSING_ROID

    8.181.1. Severity

    ERROR

    8.181.2. Description

    TBA.

    -

    8.182. RDE_CONTACT_HAS_MISSING_STATUS

    8.182.1. Severity

    ERROR

    8.182.2. Description

    TBA.

    -

    8.183. RDE_CONTACT_HAS_MISSING_STREET

    8.183.1. Severity

    ERROR

    8.183.2. Description

    TBA.

    -

    8.184. RDE_CONTACT_HAS_MISSING_VOICE

    8.184.1. Severity

    ERROR

    8.184.2. Description

    TBA.

    -

    8.185. RDE_DECRYPTION_FAILED

    8.185.1. Severity

    ERROR

    8.185.2. Description

    TBA.

    -

    8.186. RDE_DOMAIN_HAS_INVALID_CLID

    8.186.1. Severity

    ERROR

    8.186.2. Description

    TBA.

    -

    8.187. RDE_DOMAIN_HAS_INVALID_CRDATE

    8.187.1. Severity

    ERROR

    8.187.2. Description

    TBA.

    -

    8.188. RDE_DOMAIN_HAS_INVALID_EXDATE

    8.188.1. Severity

    ERROR

    8.188.2. Description

    TBA.

    -

    8.189. RDE_DOMAIN_HAS_INVALID_NAME

    8.189.1. Severity

    ERROR

    8.189.2. Description

    TBA.

    -

    8.190. RDE_DOMAIN_HAS_INVALID_REGISTRANT

    8.190.1. Severity

    ERROR

    8.190.2. Description

    TBA.

    -

    8.191. RDE_DOMAIN_HAS_INVALID_ROID

    8.191.1. Severity

    ERROR

    8.191.2. Description

    TBA.

    -

    8.192. RDE_DOMAIN_HAS_INVALID_STATUS

    8.192.1. Severity

    ERROR

    8.192.2. Description

    TBA.

    -

    8.193. RDE_DOMAIN_HAS_MISSING_CLID

    8.193.1. Severity

    ERROR

    8.193.2. Description

    TBA.

    -

    8.194. RDE_DOMAIN_HAS_MISSING_CRDATE

    8.194.1. Severity

    ERROR

    8.194.2. Description

    TBA.

    -

    8.195. RDE_DOMAIN_HAS_MISSING_EXDATE

    8.195.1. Severity

    ERROR

    8.195.2. Description

    TBA.

    -

    8.196. RDE_DOMAIN_HAS_MISSING_NAME

    8.196.1. Severity

    ERROR

    8.196.2. Description

    TBA.

    -

    8.197. RDE_DOMAIN_HAS_MISSING_REGISTRANT

    8.197.1. Severity

    ERROR

    8.197.2. Description

    TBA.

    -

    8.198. RDE_DOMAIN_HAS_MISSING_ROID

    8.198.1. Severity

    ERROR

    8.198.2. Description

    TBA.

    -

    8.199. RDE_DOMAIN_HAS_MISSING_STATUS

    8.199.1. Severity

    ERROR

    8.199.2. Description

    TBA.

    -

    8.200. RDE_GREETING_DOES_NOT_MATCH_EPP_SERVER

    8.200.1. Severity

    ERROR

    8.200.2. Description

    TBA.

    -

    8.201. RDE_HOST_HAS_INVALID_CLID

    8.201.1. Severity

    ERROR

    8.201.2. Description

    TBA.

    -

    8.202. RDE_HOST_HAS_INVALID_IP_ADDRESS

    8.202.1. Severity

    ERROR

    8.202.2. Description

    TBA.

    -

    8.203. RDE_HOST_HAS_INVALID_NAME

    8.203.1. Severity

    ERROR

    8.203.2. Description

    TBA.

    -

    8.204. RDE_HOST_HAS_INVALID_ROID

    8.204.1. Severity

    ERROR

    8.204.2. Description

    TBA.

    -

    8.205. RDE_HOST_HAS_INVALID_STATUS

    8.205.1. Severity

    ERROR

    8.205.2. Description

    TBA.

    -

    8.206. RDE_HOST_HAS_MISSING_CLID

    8.206.1. Severity

    ERROR

    8.206.2. Description

    TBA.

    -

    8.207. RDE_HOST_HAS_MISSING_IP_ADDRESS

    8.207.1. Severity

    ERROR

    8.207.2. Description

    TBA.

    -

    8.208. RDE_HOST_HAS_MISSING_NAME

    8.208.1. Severity

    ERROR

    8.208.2. Description

    TBA.

    -

    8.209. RDE_HOST_HAS_MISSING_ROID

    8.209.1. Severity

    ERROR

    8.209.2. Description

    TBA.

    -

    8.210. RDE_HOST_HAS_MISSING_STATUS

    8.210.1. Severity

    ERROR

    8.210.2. Description

    TBA.

    -

    8.211. RDE_IDN_OBJECT_INVALID

    8.211.1. Severity

    ERROR

    8.211.2. Description

    TBA.

    -

    8.212. RDE_IDN_OBJECT_MISSING

    8.212.1. Severity

    ERROR

    8.212.2. Description

    TBA.

    -

    8.213. RDE_IDN_OBJECT_UNEXPECTED

    8.213.1. Severity

    ERROR

    8.213.2. Description

    TBA.

    -

    8.214. RDE_INVALID_CSV

    8.214.1. Severity

    ERROR

    8.214.2. Description

    TBA.

    -

    8.215. RDE_INVALID_FILENAME

    8.215.1. Severity

    ERROR

    8.215.2. Description

    TBA.

    -

    8.216. RDE_INVALID_SIGNATURE

    8.216.1. Severity

    ERROR

    8.216.2. Description

    TBA.

    -

    8.217. RDE_INVALID_XML

    8.217.1. Severity

    ERROR

    8.217.2. Description

    TBA.

    -

    8.218. RDE_MISSING_OBJECT_URI

    8.218.1. Severity

    ERROR

    8.218.2. Description

    TBA.

    -

    8.219. RDE_MIXED_TYPES

    8.219.1. Severity

    ERROR

    8.219.2. Description

    TBA.

    -

    8.220. RDE_NNDN_CONFLICTS_WITH_DOMAIN

    8.220.1. Severity

    ERROR

    8.220.2. Description

    TBA.

    -

    8.221. RDE_OBJECT_COUNT_MISMATCH

    8.221.1. Severity

    ERROR

    8.221.2. Description

    TBA.

    -

    8.222. RDE_POLICY_OBJECT_INVALID

    8.222.1. Severity

    ERROR

    8.222.2. Description

    TBA.

    -

    8.223. RDE_POLICY_OBJECT_MISSING

    8.223.1. Severity

    ERROR

    8.223.2. Description

    TBA.

    -

    8.224. RDE_POLICY_OBJECT_MISSING_OBJECTS

    8.224.1. Severity

    ERROR

    8.224.2. Description

    TBA.

    -

    8.225. RDE_POLICY_OBJECT_UNEXPECTED_OBJECTS

    8.225.1. Severity

    ERROR

    8.225.2. Description

    TBA.

    -

    8.226. RDE_REGISTRAR_HAS_INVALID_GURID

    8.226.1. Severity

    ERROR

    8.226.2. Description

    TBA.

    -

    8.227. RDE_REGISTRAR_HAS_INVALID_ID

    8.227.1. Severity

    ERROR

    8.227.2. Description

    TBA.

    -

    8.228. RDE_REGISTRAR_HAS_INVALID_NAME

    8.228.1. Severity

    ERROR

    8.228.2. Description

    TBA.

    -

    8.229. RDE_REGISTRAR_HAS_MISSING_GURID

    8.229.1. Severity

    ERROR

    8.229.2. Description

    TBA.

    -

    8.230. RDE_REGISTRAR_HAS_MISSING_ID

    8.230.1. Severity

    ERROR

    8.230.2. Description

    TBA.

    -

    8.231. RDE_REGISTRAR_HAS_MISSING_NAME

    8.231.1. Severity

    ERROR

    8.231.2. Description

    TBA.

    -

    8.232. RDE_SCHEMA_VALIDATION_ERROR

    8.232.1. Severity

    ERROR

    8.232.2. Description

    TBA.

    -

    8.233. RDE_UNEXPECTED_OBJECT_URI

    8.233.1. Severity

    ERROR

    8.233.2. Description

    TBA.

    -

    8.234. RDE_XML_PARSE_ERROR

    8.234.1. Severity

    ERROR

    8.234.2. Description

    TBA.

    -

    8.235. RPMS_MISSING_CLAIMS_KEY

    8.235.1. Severity

    ERROR

    8.235.2. Description

    TBA.

    -

    8.236. RPMS_SUNRISE_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.236.1. Severity

    ERROR

    8.236.2. Description

    TBA.

    -

    8.237. RPMS_SUNRISE_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.237.1. Severity

    ERROR

    8.237.2. Description

    TBA.

    -

    8.238. RPMS_SUNRISE_CREATE_UNEXPECTED_FAILURE_USING_VALID_SMD

    8.238.1. Severity

    ERROR

    8.238.2. Description

    TBA.

    -

    8.239. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_SMD

    8.239.1. Severity

    ERROR

    8.239.2. Description

    TBA.

    -

    8.240. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_REVOKED_SMD

    8.240.1. Severity

    ERROR

    8.240.2. Description

    TBA.

    -

    8.241. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_SMD_WITH_REVOKED_SIGNATURE

    8.241.1. Severity

    ERROR

    8.241.2. Description

    TBA.

    -

    8.242. RPMS_TRADEMARK_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.242.1. Severity

    ERROR

    8.242.2. Description

    TBA.

    -

    8.243. RPMS_TRADEMARK_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.243.1. Severity

    ERROR

    8.243.2. Description

    TBA.

    -

    8.244. RPMS_TRADEMARK_CREATE_UNEXPECTED_FAILURE_USING_VALID_CLAIM_KEY

    8.244.1. Severity

    ERROR

    8.244.2. Description

    TBA.

    -

    8.245. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_ACCEPTANCE_DATE

    8.245.1. Severity

    ERROR

    8.245.2. Description

    TBA.

    -

    8.246. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_CLAIM_KEY

    8.246.1. Severity

    ERROR

    8.246.2. Description

    TBA.

    -

    8.247. RPMS_UNEXPECTED_CLAIMS_KEY

    8.247.1. Severity

    ERROR

    8.247.2. Description

    TBA.

    -

    8.248. SRSGW_CONTACT_CREATE_FAILED

    8.248.1. Severity

    ERROR

    8.248.2. Description

    TBA.

    -

    8.249. SRSGW_CONTACT_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.249.1. Severity

    ERROR

    8.249.2. Description

    TBA.

    -

    8.250. SRSGW_CONTACT_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.250.1. Severity

    ERROR

    8.250.2. Description

    TBA.

    -

    8.251. SRSGW_DOMAIN_CREATE_FAILED

    8.251.1. Severity

    ERROR

    8.251.2. Description

    TBA.

    -

    8.252. SRSGW_DOMAIN_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.252.1. Severity

    ERROR

    8.252.2. Description

    TBA.

    -

    8.253. SRSGW_DOMAIN_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.253.1. Severity

    ERROR

    8.253.2. Description

    TBA.

    -

    8.254. SRSGW_DOMAIN_DELETE_DOMAIN_NOT_PENDINGDELETE

    8.254.1. Severity

    ERROR

    8.254.2. Description

    TBA.

    -

    8.255. SRSGW_DOMAIN_DELETE_FAILED

    8.255.1. Severity

    ERROR

    8.255.2. Description

    TBA.

    -

    8.256. SRSGW_DOMAIN_DELETE_RGP_STATUS_NOT_PENDINGDELETERESTORABLE

    8.256.1. Severity

    ERROR

    8.256.2. Description

    TBA.

    -

    8.257. SRSGW_DOMAIN_RENEW_FAILED

    8.257.1. Severity

    ERROR

    8.257.2. Description

    TBA.

    -

    8.258. SRSGW_DOMAIN_RENEW_OBJECT_HAS_INVALID_EXDATE

    8.258.1. Severity

    ERROR

    8.258.2. Description

    TBA.

    -

    8.259. SRSGW_DOMAIN_RENEW_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.259.1. Severity

    ERROR

    8.259.2. Description

    TBA.

    -

    8.260. SRSGW_DOMAIN_TRANSFER_APPROVAL_FAILED

    8.260.1. Severity

    ERROR

    8.260.2. Description

    TBA.

    -

    8.261. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_HAS_INCORRECT_CLID

    8.261.1. Severity

    ERROR

    8.261.2. Description

    TBA.

    -

    8.262. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.262.1. Severity

    ERROR

    8.262.2. Description

    TBA.

    -

    8.263. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_STILL_PENDING_TRANSFER

    8.263.1. Severity

    ERROR

    8.263.2. Description

    TBA.

    -

    8.264. SRSGW_DOMAIN_TRANSFER_REQUEST_FAILED

    8.264.1. Severity

    ERROR

    8.264.2. Description

    TBA.

    -

    8.265. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_HAS_INCORRECT_CLID

    8.265.1. Severity

    ERROR

    8.265.2. Description

    TBA.

    -

    8.266. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_PENDING_TRANSFER

    8.266.1. Severity

    ERROR

    8.266.2. Description

    TBA.

    -

    8.267. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.267.1. Severity

    ERROR

    8.267.2. Description

    TBA.

    -

    8.268. SRSGW_EPP_DNS_RESOLUTION_ERROR

    8.268.1. Severity

    ERROR

    8.268.2. Description

    TBA.

    -

    8.269. SRSGW_EPP_GENERIC_COMMAND_ERROR

    8.269.1. Severity

    ERROR

    8.269.2. Description

    TBA.

    -

    8.270. SRSGW_EPP_LOGIN_ERROR

    8.270.1. Severity

    ERROR

    8.270.2. Description

    TBA.

    -

    8.271. SRSGW_EPP_OBJECT_SHOULD_EXIST

    8.271.1. Severity

    ERROR

    8.271.2. Description

    TBA.

    -

    8.272. SRSGW_EPP_OBJECT_SHOULD_NOT_EXIST

    8.272.1. Severity

    ERROR

    8.272.2. Description

    TBA.

    -

    8.273. SRSGW_EPP_SCHEMA_VALIDATION_ERROR

    8.273.1. Severity

    ERROR

    8.273.2. Description

    TBA.

    -

    8.274. SRSGW_EPP_SERVICE_PORT_UNREACHABLE

    8.274.1. Severity

    ERROR

    8.274.2. Description

    TBA.

    -

    8.275. SRSGW_EPP_TLS_CONNECTION_ERROR

    8.275.1. Severity

    ERROR

    8.275.2. Description

    TBA.

    -

    8.276. SRSGW_EPP_UNEXPECTED_COMMAND_FAILURE

    8.276.1. Severity

    ERROR

    8.276.2. Description

    TBA.

    -

    8.277. SRSGW_EPP_UNEXPECTED_COMMAND_SUCCESS

    8.277.1. Severity

    ERROR

    8.277.2. Description

    TBA.

    -

    8.278. SRSGW_EPP_XML_PARSE_ERROR

    8.278.1. Severity

    ERROR

    8.278.2. Description

    TBA.

    -

    8.279. SRSGW_HOST_CREATE_FAILED

    8.279.1. Severity

    ERROR

    8.279.2. Description

    TBA.

    -

    8.280. SRSGW_HOST_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.280.1. Severity

    ERROR

    8.280.2. Description

    TBA.

    -

    8.281. SRSGW_HOST_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.281.1. Severity

    ERROR

    8.281.2. Description

    TBA.

    -

    8.282. ZM_AAAA_BAD_RDATA

    8.282.1. Severity

    ERROR

    8.282.2. Description

    Not available.

    -

    8.283. ZM_AAAA_QUERY_DROPPED

    8.283.1. Severity

    ERROR

    8.283.2. Description

    Not available.

    -

    8.284. ZM_AAAA_UNEXPECTED_RCODE

    8.284.1. Severity

    ERROR

    8.284.2. Description

    Not available.

    -

    8.285. ZM_AAAA_WELL_PROCESSED

    8.285.1. Severity

    INFO

    8.285.2. Description

    Not available.

    -

    8.286. ZM_ADDRESSES_MATCH

    8.286.1. Severity

    INFO

    8.286.2. Description

    Not available.

    -

    8.287. ZM_ALGORITHM_DEPRECATED

    8.287.1. Severity

    ERROR

    8.287.2. Description

    Not available.

    -

    8.288. ZM_ALGORITHM_NOT_RECOMMENDED

    8.288.1. Severity

    WARNING

    8.288.2. Description

    Not available.

    -

    8.289. ZM_ALGORITHM_NOT_ZONE_SIGN

    8.289.1. Severity

    ERROR

    8.289.2. Description

    Not available.

    -

    8.290. ZM_ALGORITHM_OK

    8.290.1. Severity

    INFO

    8.290.2. Description

    Not available.

    -

    8.291. ZM_ALGORITHM_PRIVATE

    8.291.1. Severity

    ERROR

    8.291.2. Description

    Not available.

    -

    8.292. ZM_ALGORITHM_RESERVED

    8.292.1. Severity

    ERROR

    8.292.2. Description

    Not available.

    -

    8.293. ZM_ALGORITHM_UNASSIGNED

    8.293.1. Severity

    ERROR

    8.293.2. Description

    Not available.

    -

    8.294. ZM_A_UNEXPECTED_RCODE

    8.294.1. Severity

    ERROR

    8.294.2. Description

    Not available.

    -

    8.295. ZM_BREAKS_ON_EDNS

    8.295.1. Severity

    ERROR

    8.295.2. Description

    Not available.

    -

    8.296. ZM_CHILD_DISTINCT_NS_IP

    8.296.1. Severity

    INFO

    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_IPV4_DISABLED

    8.300.1. Severity

    NOTICE

    8.300.2. Description

    IPv4 is disabled. No DNS queries are sent to these name servers: +

    8.138. EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.138.1. Severity

    ERROR

    8.138.2. Description

    TBA

    +

    8.139. EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET

    8.139.1. Severity

    ERROR

    8.139.2. Description

    TBA

    +

    8.140. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS

    8.140.1. Severity

    ERROR

    8.140.2. Description

    TBA

    +

    8.141. EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_STATUS_CODE

    8.141.1. Severity

    ERROR

    8.141.2. Description

    TBA

    +

    8.142. EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE

    8.142.1. Severity

    ERROR

    8.142.2. Description

    TBA

    +

    8.143. EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED

    8.143.1. Severity

    ERROR

    8.143.2. Description

    TBA

    +

    8.144. EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO

    8.144.1. Severity

    ERROR

    8.144.2. Description

    TBA

    +

    8.145. EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO

    8.145.1. Severity

    ERROR

    8.145.2. Description

    TBA

    +

    8.146. EPP_TRANSFER_SERVER_ACCEPTS_INVALID_PERIOD

    8.146.1. Severity

    ERROR

    8.146.2. Description

    TBA

    +

    8.147. EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER

    8.147.1. Severity

    ERROR

    8.147.2. Description

    TBA

    +

    8.148. EPP_UNEXPECTED_COMMAND_FAILURE

    8.148.1. Severity

    ERROR

    8.148.2. Description

    TBA

    +

    8.149. EPP_UNEXPECTED_COMMAND_SUCCESS

    8.149.1. Severity

    ERROR

    8.149.2. Description

    TBA

    +

    8.150. EPP_XML_PARSE_ERROR

    8.150.1. Severity

    ERROR

    8.150.2. Description

    The XML response from the server could not be parsed.

    +

    8.151. IDN_SERVER_ACCEPTS_INVALID_LABEL

    8.151.1. Severity

    ERROR

    8.151.2. Description

    TBA.

    +

    8.152. IDN_SERVER_REJECTS_VALID_LABEL

    8.152.1. Severity

    ERROR

    8.152.2. Description

    TBA.

    +

    8.153. IDN_VARIANT_LABEL_NOT_BLOCKED

    8.153.1. Severity

    ERROR

    8.153.2. Description

    TBA.

    +

    8.154. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_FROM_INCORRECT_REGISTRAR

    8.154.1. Severity

    ERROR

    8.154.2. Description

    TBA.

    +

    8.155. IDN_VARIANT_SERVER_ACCEPTS_VARIANT_CREATE_WITH_INCORRECT_REGISTRANT

    8.155.1. Severity

    ERROR

    8.155.2. Description

    TBA.

    +

    8.156. INTEGRATION_DNS_ANSWER_IS_INCORRECT

    8.156.1. Severity

    ERROR

    8.156.2. Description

    TBA.

    +

    8.157. INTEGRATION_DNS_QUERY_FAILED

    8.157.1. Severity

    ERROR

    8.157.2. Description

    TBA.

    +

    8.158. INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS

    8.158.1. Severity

    ERROR

    8.158.2. Description

    TBA.

    +

    8.159. INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP

    8.159.1. Severity

    ERROR

    8.159.2. Description

    TBA.

    +

    8.160. INTEGRATION_RDAP_REQUEST_FAILED

    8.160.1. Severity

    ERROR

    8.160.2. Description

    TBA.

    +

    8.161. INTEGRATION_RDE_DEADLINE_MISSED

    8.161.1. Severity

    ERROR

    8.161.2. Description

    TBA.

    +

    8.162. INTEGRATION_RDE_MISSING_OBJECTS

    8.162.1. Severity

    ERROR

    8.162.2. Description

    TBA.

    +

    8.163. INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR

    8.163.1. Severity

    ERROR

    8.163.2. Description

    TBA.

    +

    8.164. INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE

    8.164.1. Severity

    ERROR

    8.164.2. Description

    TBA.

    +

    8.165. RDE_CONTACT_HAS_INVALID_CC

    8.165.1. Severity

    ERROR

    8.165.2. Description

    TBA.

    +

    8.166. RDE_CONTACT_HAS_INVALID_CITY

    8.166.1. Severity

    ERROR

    8.166.2. Description

    TBA.

    +

    8.167. RDE_CONTACT_HAS_INVALID_CLID

    8.167.1. Severity

    ERROR

    8.167.2. Description

    TBA.

    +

    8.168. RDE_CONTACT_HAS_INVALID_EMAIL

    8.168.1. Severity

    ERROR

    8.168.2. Description

    TBA.

    +

    8.169. RDE_CONTACT_HAS_INVALID_ID

    8.169.1. Severity

    ERROR

    8.169.2. Description

    TBA.

    +

    8.170. RDE_CONTACT_HAS_INVALID_NAME

    8.170.1. Severity

    ERROR

    8.170.2. Description

    TBA.

    +

    8.171. RDE_CONTACT_HAS_INVALID_POSTALINFO_TYPE

    8.171.1. Severity

    ERROR

    8.171.2. Description

    TBA.

    +

    8.172. RDE_CONTACT_HAS_INVALID_ROID

    8.172.1. Severity

    ERROR

    8.172.2. Description

    TBA.

    +

    8.173. RDE_CONTACT_HAS_INVALID_STATUS

    8.173.1. Severity

    ERROR

    8.173.2. Description

    TBA.

    +

    8.174. RDE_CONTACT_HAS_INVALID_STREET

    8.174.1. Severity

    ERROR

    8.174.2. Description

    TBA.

    +

    8.175. RDE_CONTACT_HAS_INVALID_VOICE

    8.175.1. Severity

    ERROR

    8.175.2. Description

    TBA.

    +

    8.176. RDE_CONTACT_HAS_MISSING_CC

    8.176.1. Severity

    ERROR

    8.176.2. Description

    TBA.

    +

    8.177. RDE_CONTACT_HAS_MISSING_CITY

    8.177.1. Severity

    ERROR

    8.177.2. Description

    TBA.

    +

    8.178. RDE_CONTACT_HAS_MISSING_CLID

    8.178.1. Severity

    ERROR

    8.178.2. Description

    TBA.

    +

    8.179. RDE_CONTACT_HAS_MISSING_EMAIL

    8.179.1. Severity

    ERROR

    8.179.2. Description

    TBA.

    +

    8.180. RDE_CONTACT_HAS_MISSING_ID

    8.180.1. Severity

    ERROR

    8.180.2. Description

    TBA.

    +

    8.181. RDE_CONTACT_HAS_MISSING_NAME

    8.181.1. Severity

    ERROR

    8.181.2. Description

    TBA.

    +

    8.182. RDE_CONTACT_HAS_MISSING_POSTALINFO

    8.182.1. Severity

    ERROR

    8.182.2. Description

    TBA.

    +

    8.183. RDE_CONTACT_HAS_MISSING_ROID

    8.183.1. Severity

    ERROR

    8.183.2. Description

    TBA.

    +

    8.184. RDE_CONTACT_HAS_MISSING_STATUS

    8.184.1. Severity

    ERROR

    8.184.2. Description

    TBA.

    +

    8.185. RDE_CONTACT_HAS_MISSING_STREET

    8.185.1. Severity

    ERROR

    8.185.2. Description

    TBA.

    +

    8.186. RDE_CONTACT_HAS_MISSING_VOICE

    8.186.1. Severity

    ERROR

    8.186.2. Description

    TBA.

    +

    8.187. RDE_DECRYPTION_FAILED

    8.187.1. Severity

    ERROR

    8.187.2. Description

    TBA.

    +

    8.188. RDE_DOMAIN_HAS_INVALID_CLID

    8.188.1. Severity

    ERROR

    8.188.2. Description

    TBA.

    +

    8.189. RDE_DOMAIN_HAS_INVALID_CRDATE

    8.189.1. Severity

    ERROR

    8.189.2. Description

    TBA.

    +

    8.190. RDE_DOMAIN_HAS_INVALID_EXDATE

    8.190.1. Severity

    ERROR

    8.190.2. Description

    TBA.

    +

    8.191. RDE_DOMAIN_HAS_INVALID_NAME

    8.191.1. Severity

    ERROR

    8.191.2. Description

    TBA.

    +

    8.192. RDE_DOMAIN_HAS_INVALID_REGISTRANT

    8.192.1. Severity

    ERROR

    8.192.2. Description

    TBA.

    +

    8.193. RDE_DOMAIN_HAS_INVALID_ROID

    8.193.1. Severity

    ERROR

    8.193.2. Description

    TBA.

    +

    8.194. RDE_DOMAIN_HAS_INVALID_STATUS

    8.194.1. Severity

    ERROR

    8.194.2. Description

    TBA.

    +

    8.195. RDE_DOMAIN_HAS_MISSING_CLID

    8.195.1. Severity

    ERROR

    8.195.2. Description

    TBA.

    +

    8.196. RDE_DOMAIN_HAS_MISSING_CRDATE

    8.196.1. Severity

    ERROR

    8.196.2. Description

    TBA.

    +

    8.197. RDE_DOMAIN_HAS_MISSING_EXDATE

    8.197.1. Severity

    ERROR

    8.197.2. Description

    TBA.

    +

    8.198. RDE_DOMAIN_HAS_MISSING_NAME

    8.198.1. Severity

    ERROR

    8.198.2. Description

    TBA.

    +

    8.199. RDE_DOMAIN_HAS_MISSING_REGISTRANT

    8.199.1. Severity

    ERROR

    8.199.2. Description

    TBA.

    +

    8.200. RDE_DOMAIN_HAS_MISSING_ROID

    8.200.1. Severity

    ERROR

    8.200.2. Description

    TBA.

    +

    8.201. RDE_DOMAIN_HAS_MISSING_STATUS

    8.201.1. Severity

    ERROR

    8.201.2. Description

    TBA.

    +

    8.202. RDE_GREETING_DOES_NOT_MATCH_EPP_SERVER

    8.202.1. Severity

    ERROR

    8.202.2. Description

    TBA.

    +

    8.203. RDE_HOST_HAS_INVALID_CLID

    8.203.1. Severity

    ERROR

    8.203.2. Description

    TBA.

    +

    8.204. RDE_HOST_HAS_INVALID_IP_ADDRESS

    8.204.1. Severity

    ERROR

    8.204.2. Description

    TBA.

    +

    8.205. RDE_HOST_HAS_INVALID_NAME

    8.205.1. Severity

    ERROR

    8.205.2. Description

    TBA.

    +

    8.206. RDE_HOST_HAS_INVALID_ROID

    8.206.1. Severity

    ERROR

    8.206.2. Description

    TBA.

    +

    8.207. RDE_HOST_HAS_INVALID_STATUS

    8.207.1. Severity

    ERROR

    8.207.2. Description

    TBA.

    +

    8.208. RDE_HOST_HAS_MISSING_CLID

    8.208.1. Severity

    ERROR

    8.208.2. Description

    TBA.

    +

    8.209. RDE_HOST_HAS_MISSING_IP_ADDRESS

    8.209.1. Severity

    ERROR

    8.209.2. Description

    TBA.

    +

    8.210. RDE_HOST_HAS_MISSING_NAME

    8.210.1. Severity

    ERROR

    8.210.2. Description

    TBA.

    +

    8.211. RDE_HOST_HAS_MISSING_ROID

    8.211.1. Severity

    ERROR

    8.211.2. Description

    TBA.

    +

    8.212. RDE_HOST_HAS_MISSING_STATUS

    8.212.1. Severity

    ERROR

    8.212.2. Description

    TBA.

    +

    8.213. RDE_IDN_OBJECT_INVALID

    8.213.1. Severity

    ERROR

    8.213.2. Description

    TBA.

    +

    8.214. RDE_IDN_OBJECT_MISSING

    8.214.1. Severity

    ERROR

    8.214.2. Description

    TBA.

    +

    8.215. RDE_IDN_OBJECT_UNEXPECTED

    8.215.1. Severity

    ERROR

    8.215.2. Description

    TBA.

    +

    8.216. RDE_INVALID_CSV

    8.216.1. Severity

    ERROR

    8.216.2. Description

    TBA.

    +

    8.217. RDE_INVALID_FILENAME

    8.217.1. Severity

    ERROR

    8.217.2. Description

    TBA.

    +

    8.218. RDE_INVALID_SIGNATURE

    8.218.1. Severity

    ERROR

    8.218.2. Description

    TBA.

    +

    8.219. RDE_INVALID_XML

    8.219.1. Severity

    ERROR

    8.219.2. Description

    TBA.

    +

    8.220. RDE_MISSING_OBJECT_URI

    8.220.1. Severity

    ERROR

    8.220.2. Description

    TBA.

    +

    8.221. RDE_MIXED_TYPES

    8.221.1. Severity

    ERROR

    8.221.2. Description

    TBA.

    +

    8.222. RDE_NNDN_CONFLICTS_WITH_DOMAIN

    8.222.1. Severity

    ERROR

    8.222.2. Description

    TBA.

    +

    8.223. RDE_OBJECT_COUNT_MISMATCH

    8.223.1. Severity

    ERROR

    8.223.2. Description

    TBA.

    +

    8.224. RDE_POLICY_OBJECT_INVALID

    8.224.1. Severity

    ERROR

    8.224.2. Description

    TBA.

    +

    8.225. RDE_POLICY_OBJECT_MISSING

    8.225.1. Severity

    ERROR

    8.225.2. Description

    TBA.

    +

    8.226. RDE_POLICY_OBJECT_MISSING_OBJECTS

    8.226.1. Severity

    ERROR

    8.226.2. Description

    TBA.

    +

    8.227. RDE_POLICY_OBJECT_UNEXPECTED_OBJECTS

    8.227.1. Severity

    ERROR

    8.227.2. Description

    TBA.

    +

    8.228. RDE_REGISTRAR_HAS_INVALID_GURID

    8.228.1. Severity

    ERROR

    8.228.2. Description

    TBA.

    +

    8.229. RDE_REGISTRAR_HAS_INVALID_ID

    8.229.1. Severity

    ERROR

    8.229.2. Description

    TBA.

    +

    8.230. RDE_REGISTRAR_HAS_INVALID_NAME

    8.230.1. Severity

    ERROR

    8.230.2. Description

    TBA.

    +

    8.231. RDE_REGISTRAR_HAS_MISSING_GURID

    8.231.1. Severity

    ERROR

    8.231.2. Description

    TBA.

    +

    8.232. RDE_REGISTRAR_HAS_MISSING_ID

    8.232.1. Severity

    ERROR

    8.232.2. Description

    TBA.

    +

    8.233. RDE_REGISTRAR_HAS_MISSING_NAME

    8.233.1. Severity

    ERROR

    8.233.2. Description

    TBA.

    +

    8.234. RDE_SCHEMA_VALIDATION_ERROR

    8.234.1. Severity

    ERROR

    8.234.2. Description

    TBA.

    +

    8.235. RDE_UNEXPECTED_OBJECT_URI

    8.235.1. Severity

    ERROR

    8.235.2. Description

    TBA.

    +

    8.236. RDE_XML_PARSE_ERROR

    8.236.1. Severity

    ERROR

    8.236.2. Description

    TBA.

    +

    8.237. RPMS_MISSING_CLAIMS_KEY

    8.237.1. Severity

    ERROR

    8.237.2. Description

    TBA.

    +

    8.238. RPMS_SUNRISE_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.238.1. Severity

    ERROR

    8.238.2. Description

    TBA.

    +

    8.239. RPMS_SUNRISE_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.239.1. Severity

    ERROR

    8.239.2. Description

    TBA.

    +

    8.240. RPMS_SUNRISE_CREATE_UNEXPECTED_FAILURE_USING_VALID_SMD

    8.240.1. Severity

    ERROR

    8.240.2. Description

    TBA.

    +

    8.241. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_SMD

    8.241.1. Severity

    ERROR

    8.241.2. Description

    TBA.

    +

    8.242. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_REVOKED_SMD

    8.242.1. Severity

    ERROR

    8.242.2. Description

    TBA.

    +

    8.243. RPMS_SUNRISE_CREATE_UNEXPECTED_SUCCESS_USING_SMD_WITH_REVOKED_SIGNATURE

    8.243.1. Severity

    ERROR

    8.243.2. Description

    TBA.

    +

    8.244. RPMS_TRADEMARK_CREATE_INFO_OBJECT_DOES_NOT_EXIST

    8.244.1. Severity

    ERROR

    8.244.2. Description

    TBA.

    +

    8.245. RPMS_TRADEMARK_CREATE_INFO_OBJECT_IS_HAS_MISSING_OR_INVALID_PROPERTIES

    8.245.1. Severity

    ERROR

    8.245.2. Description

    TBA.

    +

    8.246. RPMS_TRADEMARK_CREATE_UNEXPECTED_FAILURE_USING_VALID_CLAIM_KEY

    8.246.1. Severity

    ERROR

    8.246.2. Description

    TBA.

    +

    8.247. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_ACCEPTANCE_DATE

    8.247.1. Severity

    ERROR

    8.247.2. Description

    TBA.

    +

    8.248. RPMS_TRADEMARK_CREATE_UNEXPECTED_SUCCESS_USING_INVALID_CLAIM_KEY

    8.248.1. Severity

    ERROR

    8.248.2. Description

    TBA.

    +

    8.249. RPMS_UNEXPECTED_CLAIMS_KEY

    8.249.1. Severity

    ERROR

    8.249.2. Description

    TBA.

    +

    8.250. SRSGW_CONTACT_CREATE_FAILED

    8.250.1. Severity

    ERROR

    8.250.2. Description

    TBA.

    +

    8.251. SRSGW_CONTACT_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.251.1. Severity

    ERROR

    8.251.2. Description

    TBA.

    +

    8.252. SRSGW_CONTACT_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.252.1. Severity

    ERROR

    8.252.2. Description

    TBA.

    +

    8.253. SRSGW_DOMAIN_CREATE_FAILED

    8.253.1. Severity

    ERROR

    8.253.2. Description

    TBA.

    +

    8.254. SRSGW_DOMAIN_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.254.1. Severity

    ERROR

    8.254.2. Description

    TBA.

    +

    8.255. SRSGW_DOMAIN_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.255.1. Severity

    ERROR

    8.255.2. Description

    TBA.

    +

    8.256. SRSGW_DOMAIN_DELETE_DOMAIN_NOT_PENDINGDELETE

    8.256.1. Severity

    ERROR

    8.256.2. Description

    TBA.

    +

    8.257. SRSGW_DOMAIN_DELETE_FAILED

    8.257.1. Severity

    ERROR

    8.257.2. Description

    TBA.

    +

    8.258. SRSGW_DOMAIN_DELETE_RGP_STATUS_NOT_PENDINGDELETERESTORABLE

    8.258.1. Severity

    ERROR

    8.258.2. Description

    TBA.

    +

    8.259. SRSGW_DOMAIN_RENEW_FAILED

    8.259.1. Severity

    ERROR

    8.259.2. Description

    TBA.

    +

    8.260. SRSGW_DOMAIN_RENEW_OBJECT_HAS_INVALID_EXDATE

    8.260.1. Severity

    ERROR

    8.260.2. Description

    TBA.

    +

    8.261. SRSGW_DOMAIN_RENEW_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.261.1. Severity

    ERROR

    8.261.2. Description

    TBA.

    +

    8.262. SRSGW_DOMAIN_TRANSFER_APPROVAL_FAILED

    8.262.1. Severity

    ERROR

    8.262.2. Description

    TBA.

    +

    8.263. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_HAS_INCORRECT_CLID

    8.263.1. Severity

    ERROR

    8.263.2. Description

    TBA.

    +

    8.264. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.264.1. Severity

    ERROR

    8.264.2. Description

    TBA.

    +

    8.265. SRSGW_DOMAIN_TRANSFER_APPROVAL_OBJECT_STILL_PENDING_TRANSFER

    8.265.1. Severity

    ERROR

    8.265.2. Description

    TBA.

    +

    8.266. SRSGW_DOMAIN_TRANSFER_REQUEST_FAILED

    8.266.1. Severity

    ERROR

    8.266.2. Description

    TBA.

    +

    8.267. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_HAS_INCORRECT_CLID

    8.267.1. Severity

    ERROR

    8.267.2. Description

    TBA.

    +

    8.268. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_PENDING_TRANSFER

    8.268.1. Severity

    ERROR

    8.268.2. Description

    TBA.

    +

    8.269. SRSGW_DOMAIN_TRANSFER_REQUEST_OBJECT_NOT_UPDATED_WITHIN_DEADLINE

    8.269.1. Severity

    ERROR

    8.269.2. Description

    TBA.

    +

    8.270. SRSGW_EPP_DNS_RESOLUTION_ERROR

    8.270.1. Severity

    ERROR

    8.270.2. Description

    TBA.

    +

    8.271. SRSGW_EPP_GENERIC_COMMAND_ERROR

    8.271.1. Severity

    ERROR

    8.271.2. Description

    TBA.

    +

    8.272. SRSGW_EPP_LOGIN_ERROR

    8.272.1. Severity

    ERROR

    8.272.2. Description

    TBA.

    +

    8.273. SRSGW_EPP_OBJECT_SHOULD_EXIST

    8.273.1. Severity

    ERROR

    8.273.2. Description

    TBA.

    +

    8.274. SRSGW_EPP_OBJECT_SHOULD_NOT_EXIST

    8.274.1. Severity

    ERROR

    8.274.2. Description

    TBA.

    +

    8.275. SRSGW_EPP_SCHEMA_VALIDATION_ERROR

    8.275.1. Severity

    ERROR

    8.275.2. Description

    TBA.

    +

    8.276. SRSGW_EPP_SERVICE_PORT_UNREACHABLE

    8.276.1. Severity

    ERROR

    8.276.2. Description

    TBA.

    +

    8.277. SRSGW_EPP_TLS_CONNECTION_ERROR

    8.277.1. Severity

    ERROR

    8.277.2. Description

    TBA.

    +

    8.278. SRSGW_EPP_UNEXPECTED_COMMAND_FAILURE

    8.278.1. Severity

    ERROR

    8.278.2. Description

    TBA.

    +

    8.279. SRSGW_EPP_UNEXPECTED_COMMAND_SUCCESS

    8.279.1. Severity

    ERROR

    8.279.2. Description

    TBA.

    +

    8.280. SRSGW_EPP_XML_PARSE_ERROR

    8.280.1. Severity

    ERROR

    8.280.2. Description

    TBA.

    +

    8.281. SRSGW_HOST_CREATE_FAILED

    8.281.1. Severity

    ERROR

    8.281.2. Description

    TBA.

    +

    8.282. SRSGW_HOST_CREATE_OBJECT_HAS_MISSING_OR_INVALID_PROPERTIES

    8.282.1. Severity

    ERROR

    8.282.2. Description

    TBA.

    +

    8.283. SRSGW_HOST_CREATE_OBJECT_NOT_FOUND_WITHIN_DEADLINE

    8.283.1. Severity

    ERROR

    8.283.2. Description

    TBA.

    +

    8.284. ZM_AAAA_BAD_RDATA

    8.284.1. Severity

    ERROR

    8.284.2. Description

    Not available.

    +

    8.285. ZM_AAAA_QUERY_DROPPED

    8.285.1. Severity

    ERROR

    8.285.2. Description

    Not available.

    +

    8.286. ZM_AAAA_UNEXPECTED_RCODE

    8.286.1. Severity

    ERROR

    8.286.2. Description

    Not available.

    +

    8.287. ZM_AAAA_WELL_PROCESSED

    8.287.1. Severity

    INFO

    8.287.2. Description

    Not available.

    +

    8.288. ZM_ADDRESSES_MATCH

    8.288.1. Severity

    INFO

    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_OK

    8.292.1. Severity

    INFO

    8.292.2. Description

    Not available.

    +

    8.293. ZM_ALGORITHM_PRIVATE

    8.293.1. Severity

    ERROR

    8.293.2. Description

    Not available.

    +

    8.294. ZM_ALGORITHM_RESERVED

    8.294.1. Severity

    ERROR

    8.294.2. Description

    Not available.

    +

    8.295. ZM_ALGORITHM_UNASSIGNED

    8.295.1. Severity

    ERROR

    8.295.2. Description

    Not available.

    +

    8.296. ZM_A_UNEXPECTED_RCODE

    8.296.1. Severity

    ERROR

    8.296.2. Description

    Not available.

    +

    8.297. ZM_BREAKS_ON_EDNS

    8.297.1. Severity

    ERROR

    8.297.2. Description

    Not available.

    +

    8.298. ZM_CHILD_DISTINCT_NS_IP

    8.298.1. Severity

    INFO

    8.298.2. Description

    Not available.

    +

    8.299. ZM_CHILD_NS_FAILED

    8.299.1. Severity

    ERROR

    8.299.2. Description

    Not available.

    +

    8.300. ZM_CHILD_NS_SAME_IP

    8.300.1. Severity

    ERROR

    8.300.2. Description

    Not available.

    +

    8.301. ZM_CHILD_ZONE_LAME

    8.301.1. Severity

    ERROR

    8.301.2. Description

    Not available.

    +

    8.302. ZM_CN01_IPV4_DISABLED

    8.302.1. Severity

    NOTICE

    8.302.2. Description

    IPv4 is disabled. No DNS queries are sent to these name servers: “{ns_list}”.

    -

    8.301. ZM_CN01_IPV6_DISABLED

    8.301.1. Severity

    NOTICE

    8.301.2. Description

    IPv6 is disabled. No DNS queries are sent to these name servers: +

    8.303. ZM_CN01_IPV6_DISABLED

    8.303.1. Severity

    NOTICE

    8.303.2. Description

    IPv6 is disabled. No DNS queries are sent to these name servers: “{ns_list}”.

    -

    8.302. ZM_CN01_MISSING_NS_RECORD_UDP

    8.302.1. Severity

    ERROR

    8.302.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the +

    8.304. ZM_CN01_MISSING_NS_RECORD_UDP

    8.304.1. Severity

    ERROR

    8.304.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the answer section over UDP.

    -

    8.303. ZM_CN01_MISSING_SOA_RECORD_UDP

    8.303.1. Severity

    ERROR

    8.303.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the +

    8.305. ZM_CN01_MISSING_SOA_RECORD_UDP

    8.305.1. Severity

    ERROR

    8.305.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the answer section over UDP.

    -

    8.304. ZM_CN01_NO_RESPONSE_NS_QUERY_UDP

    8.304.1. Severity

    ERROR

    8.304.2. Description

    Nameserver {ns} does not respond to NS queries over UDP.

    -

    8.305. ZM_CN01_NO_RESPONSE_SOA_QUERY_UDP

    8.305.1. Severity

    ERROR

    8.305.2. Description

    Nameserver {ns} does not respond to SOA queries over UDP.

    -

    8.306. ZM_CN01_NO_RESPONSE_UDP

    8.306.1. Severity

    ERROR

    8.306.2. Description

    Nameserver {ns} does not respond to any queries over UDP.

    -

    8.307. ZM_CN01_NS_RECORD_NOT_AA_UDP

    8.307.1. Severity

    ERROR

    8.307.2. Description

    Nameserver {ns} does not give an authoritative response on an NS +

    8.306. ZM_CN01_NO_RESPONSE_NS_QUERY_UDP

    8.306.1. Severity

    ERROR

    8.306.2. Description

    Nameserver {ns} does not respond to NS queries over UDP.

    +

    8.307. ZM_CN01_NO_RESPONSE_SOA_QUERY_UDP

    8.307.1. Severity

    ERROR

    8.307.2. Description

    Nameserver {ns} does not respond to SOA queries over UDP.

    +

    8.308. ZM_CN01_NO_RESPONSE_UDP

    8.308.1. Severity

    ERROR

    8.308.2. Description

    Nameserver {ns} does not respond to any queries over UDP.

    +

    8.309. ZM_CN01_NS_RECORD_NOT_AA_UDP

    8.309.1. Severity

    ERROR

    8.309.2. Description

    Nameserver {ns} does not give an authoritative response on an NS query over UDP.

    -

    8.308. ZM_CN01_SOA_RECORD_NOT_AA_UDP

    8.308.1. Severity

    ERROR

    8.308.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA +

    8.310. ZM_CN01_SOA_RECORD_NOT_AA_UDP

    8.310.1. Severity

    ERROR

    8.310.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA query over UDP.

    -

    8.309. ZM_CN01_UNEXPECTED_RCODE_NS_QUERY_UDP

    8.309.1. Severity

    ERROR

    8.309.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS +

    8.311. ZM_CN01_UNEXPECTED_RCODE_NS_QUERY_UDP

    8.311.1. Severity

    ERROR

    8.311.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over UDP.

    -

    8.310. ZM_CN01_UNEXPECTED_RCODE_SOA_QUERY_UDP

    8.310.1. Severity

    ERROR

    8.310.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA +

    8.312. ZM_CN01_UNEXPECTED_RCODE_SOA_QUERY_UDP

    8.312.1. Severity

    ERROR

    8.312.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over UDP.

    -

    8.311. ZM_CN01_WRONG_NS_RECORD_UDP

    8.311.1. Severity

    ERROR

    8.311.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.313. ZM_CN01_WRONG_NS_RECORD_UDP

    8.313.1. Severity

    ERROR

    8.313.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over UDP.

    -

    8.312. ZM_CN01_WRONG_SOA_RECORD_UDP

    8.312.1. Severity

    ERROR

    8.312.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.314. ZM_CN01_WRONG_SOA_RECORD_UDP

    8.314.1. Severity

    ERROR

    8.314.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over UDP.

    -

    8.313. ZM_CN02_MISSING_NS_RECORD_TCP

    8.313.1. Severity

    ERROR

    8.313.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the +

    8.315. ZM_CN02_MISSING_NS_RECORD_TCP

    8.315.1. Severity

    ERROR

    8.315.2. Description

    Nameserver {ns} reponds to a NS query with no NS records in the answer section over TCP.

    -

    8.314. ZM_CN02_MISSING_SOA_RECORD_TCP

    8.314.1. Severity

    ERROR

    8.314.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the +

    8.316. ZM_CN02_MISSING_SOA_RECORD_TCP

    8.316.1. Severity

    ERROR

    8.316.2. Description

    Nameserver {ns} reponds to a SOA query with no SOA records in the answer section over TCP.

    -

    8.315. ZM_CN02_NO_RESPONSE_NS_QUERY_TCP

    8.315.1. Severity

    ERROR

    8.315.2. Description

    Nameserver {ns} does not respond to NS queries over TCP.

    -

    8.316. ZM_CN02_NO_RESPONSE_SOA_QUERY_TCP

    8.316.1. Severity

    ERROR

    8.316.2. Description

    Nameserver {ns} does not respond to SOA queries over TCP.

    -

    8.317. ZM_CN02_NO_RESPONSE_TCP

    8.317.1. Severity

    ERROR

    8.317.2. Description

    Nameserver {ns} does not respond to any queries over TCP.

    -

    8.318. ZM_CN02_NS_RECORD_NOT_AA_TCP

    8.318.1. Severity

    ERROR

    8.318.2. Description

    Nameserver {ns} does not give an authoritative response on an NS +

    8.317. ZM_CN02_NO_RESPONSE_NS_QUERY_TCP

    8.317.1. Severity

    ERROR

    8.317.2. Description

    Nameserver {ns} does not respond to NS queries over TCP.

    +

    8.318. ZM_CN02_NO_RESPONSE_SOA_QUERY_TCP

    8.318.1. Severity

    ERROR

    8.318.2. Description

    Nameserver {ns} does not respond to SOA queries over TCP.

    +

    8.319. ZM_CN02_NO_RESPONSE_TCP

    8.319.1. Severity

    ERROR

    8.319.2. Description

    Nameserver {ns} does not respond to any queries over TCP.

    +

    8.320. ZM_CN02_NS_RECORD_NOT_AA_TCP

    8.320.1. Severity

    ERROR

    8.320.2. Description

    Nameserver {ns} does not give an authoritative response on an NS query over TCP.

    -

    8.319. ZM_CN02_SOA_RECORD_NOT_AA_TCP

    8.319.1. Severity

    ERROR

    8.319.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA +

    8.321. ZM_CN02_SOA_RECORD_NOT_AA_TCP

    8.321.1. Severity

    ERROR

    8.321.2. Description

    Nameserver {ns} does not give an authoritative response on an SOA query over TCP.

    -

    8.320. ZM_CN02_UNEXPECTED_RCODE_NS_QUERY_TCP

    8.320.1. Severity

    ERROR

    8.320.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS +

    8.322. ZM_CN02_UNEXPECTED_RCODE_NS_QUERY_TCP

    8.322.1. Severity

    ERROR

    8.322.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over TCP.

    -

    8.321. ZM_CN02_UNEXPECTED_RCODE_SOA_QUERY_TCP

    8.321.1. Severity

    ERROR

    8.321.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA +

    8.323. ZM_CN02_UNEXPECTED_RCODE_SOA_QUERY_TCP

    8.323.1. Severity

    ERROR

    8.323.2. Description

    Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over TCP.

    -

    8.322. ZM_CN02_WRONG_NS_RECORD_TCP

    8.322.1. Severity

    ERROR

    8.322.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.324. ZM_CN02_WRONG_NS_RECORD_TCP

    8.324.1. Severity

    ERROR

    8.324.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over TCP.

    -

    8.323. ZM_CN02_WRONG_SOA_RECORD_TCP

    8.323.1. Severity

    ERROR

    8.323.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} +

    8.325. ZM_CN02_WRONG_SOA_RECORD_TCP

    8.325.1. Severity

    ERROR

    8.325.2. Description

    Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over TCP.

    -

    8.324. ZM_CN04_EMPTY_PREFIX_SET

    8.324.1. Severity

    ERROR

    8.324.2. Description

    Prefix database returned no information for IP address {ns_ip}.

    -

    8.325. ZM_CN04_ERROR_PREFIX_DATABASE

    8.325.1. Severity

    ERROR

    8.325.2. Description

    Prefix database error. No data to analyze for IP address {ns_ip}.

    -

    8.326. ZM_CN04_IPV4_DIFFERENT_PREFIX

    8.326.1. Severity

    INFO

    8.326.2. Description

    The following name server(s) are announced in unique IPv4 prefix(es): +

    8.326. ZM_CN04_EMPTY_PREFIX_SET

    8.326.1. Severity

    ERROR

    8.326.2. Description

    Prefix database returned no information for IP address {ns_ip}.

    +

    8.327. ZM_CN04_ERROR_PREFIX_DATABASE

    8.327.1. Severity

    ERROR

    8.327.2. Description

    Prefix database error. No data to analyze for IP address {ns_ip}.

    +

    8.328. ZM_CN04_IPV4_DIFFERENT_PREFIX

    8.328.1. Severity

    INFO

    8.328.2. Description

    The following name server(s) are announced in unique IPv4 prefix(es): “{ns_list}”

    -

    8.327. ZM_CN04_IPV4_SAME_PREFIX

    8.327.1. Severity

    WARNING

    8.327.2. Description

    The following name server(s) are announced in the same IPv4 prefix +

    8.329. ZM_CN04_IPV4_SAME_PREFIX

    8.329.1. Severity

    WARNING

    8.329.2. Description

    The following name server(s) are announced in the same IPv4 prefix ({ip_prefix}): “{ns_list}”

    -

    8.328. ZM_CN04_IPV6_DIFFERENT_PREFIX

    8.328.1. Severity

    INFO

    8.328.2. Description

    The following name server(s) are announced in unique IPv6 prefix(es): +

    8.330. ZM_CN04_IPV6_DIFFERENT_PREFIX

    8.330.1. Severity

    INFO

    8.330.2. Description

    The following name server(s) are announced in unique IPv6 prefix(es): “{ns_list}”

    -

    8.329. ZM_CN04_IPV6_SAME_PREFIX

    8.329.1. Severity

    WARNING

    8.329.2. Description

    The following name server(s) are announced in the same IPv6 prefix +

    8.331. ZM_CN04_IPV6_SAME_PREFIX

    8.331.1. Severity

    WARNING

    8.331.2. Description

    The following name server(s) are announced in the same IPv6 prefix ({ip_prefix}): “{ns_list}”

    -

    8.330. ZM_DEL_DISTINCT_NS_IP

    8.330.1. Severity

    INFO

    8.330.2. Description

    Not available.

    -

    8.331. ZM_DEL_NS_SAME_IP

    8.331.1. Severity

    ERROR

    8.331.2. Description

    Not available.

    -

    8.332. ZM_DNSKEY_SMALLER_THAN_REC

    8.332.1. Severity

    WARNING

    8.332.2. Description

    Not available.

    -

    8.333. ZM_DNSKEY_TOO_LARGE_FOR_ALGO

    8.333.1. Severity

    ERROR

    8.333.2. Description

    Not available.

    -

    8.334. ZM_DNSKEY_TOO_SMALL_FOR_ALGO

    8.334.1. Severity

    ERROR

    8.334.2. Description

    Not available.

    -

    8.335. ZM_DNSSEC_03_FAILED

    8.335.1. Severity

    ERROR

    8.335.2. Description

    The dnssec-03 test case failed, but no further +

    8.332. ZM_DEL_DISTINCT_NS_IP

    8.332.1. Severity

    INFO

    8.332.2. Description

    Not available.

    +

    8.333. ZM_DEL_NS_SAME_IP

    8.333.1. Severity

    ERROR

    8.333.2. Description

    Not available.

    +

    8.334. ZM_DNSKEY_SMALLER_THAN_REC

    8.334.1. Severity

    WARNING

    8.334.2. Description

    Not available.

    +

    8.335. ZM_DNSKEY_TOO_LARGE_FOR_ALGO

    8.335.1. Severity

    ERROR

    8.335.2. Description

    Not available.

    +

    8.336. ZM_DNSKEY_TOO_SMALL_FOR_ALGO

    8.336.1. Severity

    ERROR

    8.336.2. Description

    Not available.

    +

    8.337. ZM_DNSSEC_03_FAILED

    8.337.1. Severity

    ERROR

    8.337.2. Description

    The dnssec-03 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.336. ZM_DNSSEC_04_FAILED

    8.336.1. Severity

    ERROR

    8.336.2. Description

    The dnssec-04 test case failed, but no further +

    8.338. ZM_DNSSEC_04_FAILED

    8.338.1. Severity

    ERROR

    8.338.2. Description

    The dnssec-04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.337. ZM_DNSSEC_06_FAILED

    8.337.1. Severity

    ERROR

    8.337.2. Description

    The dnssec-06 test case failed, but no further +

    8.339. ZM_DNSSEC_06_FAILED

    8.339.1. Severity

    ERROR

    8.339.2. Description

    The dnssec-06 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.338. ZM_DNSSEC_12_FAILED

    8.338.1. Severity

    ERROR

    8.338.2. Description

    The dnssec-12 test case failed, but no further +

    8.340. ZM_DNSSEC_12_FAILED

    8.340.1. Severity

    ERROR

    8.340.2. Description

    The dnssec-12 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.339. ZM_DNS_ADDRESS01_FAILED

    8.339.1. Severity

    ERROR

    8.339.2. Description

    The dns-address01 test case failed, but no further +

    8.341. ZM_DNS_ADDRESS01_FAILED

    8.341.1. Severity

    ERROR

    8.341.2. Description

    The dns-address01 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.340. ZM_DNS_ADDRESS02_FAILED

    8.340.1. Severity

    ERROR

    8.340.2. Description

    The dns-address02 test case failed, but no further +

    8.342. ZM_DNS_ADDRESS02_FAILED

    8.342.1. Severity

    ERROR

    8.342.2. Description

    The dns-address02 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.341. ZM_DNS_ADDRESS03_FAILED

    8.341.1. Severity

    ERROR

    8.341.2. Description

    The dns-address03 test case failed, but no further +

    8.343. ZM_DNS_ADDRESS03_FAILED

    8.343.1. Severity

    ERROR

    8.343.2. Description

    The dns-address03 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.342. ZM_DNS_DELEGATION04_FAILED

    8.342.1. Severity

    ERROR

    8.342.2. Description

    The dns-delegation04 test case failed, but no further +

    8.344. ZM_DNS_DELEGATION04_FAILED

    8.344.1. Severity

    ERROR

    8.344.2. Description

    The dns-delegation04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.343. ZM_DNS_DELEGATION07_FAILED

    8.343.1. Severity

    ERROR

    8.343.2. Description

    The dns-delegation07 test case failed, but no further +

    8.345. ZM_DNS_DELEGATION07_FAILED

    8.345.1. Severity

    ERROR

    8.345.2. Description

    The dns-delegation07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.344. ZM_DNS_NAMESERVER04_FAILED

    8.344.1. Severity

    ERROR

    8.344.2. Description

    The dns-nameserver04 test case failed, but no further +

    8.346. ZM_DNS_NAMESERVER04_FAILED

    8.346.1. Severity

    ERROR

    8.346.2. Description

    The dns-nameserver04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.345. ZM_DNS_NAMESERVER06_FAILED

    8.345.1. Severity

    ERROR

    8.345.2. Description

    The dns-nameserver06 test case failed, but no further +

    8.347. ZM_DNS_NAMESERVER06_FAILED

    8.347.1. Severity

    ERROR

    8.347.2. Description

    The dns-nameserver06 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.346. ZM_DNS_NAMESERVER07_FAILED

    8.346.1. Severity

    ERROR

    8.346.2. Description

    The dns-nameserver07 test case failed, but no further +

    8.348. ZM_DNS_NAMESERVER07_FAILED

    8.348.1. Severity

    ERROR

    8.348.2. Description

    The dns-nameserver07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.347. ZM_DNS_NAMESERVER08_FAILED

    8.347.1. Severity

    ERROR

    8.347.2. Description

    The dns-nameserver08 test case failed, but no further +

    8.349. ZM_DNS_NAMESERVER08_FAILED

    8.349.1. Severity

    ERROR

    8.349.2. Description

    The dns-nameserver08 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.348. ZM_DNS_NAMESERVER09_FAILED

    8.348.1. Severity

    ERROR

    8.348.2. Description

    The dns-nameserver09 test case failed, but no further +

    8.350. ZM_DNS_NAMESERVER09_FAILED

    8.350.1. Severity

    ERROR

    8.350.2. Description

    The dns-nameserver09 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.349. ZM_DNS_SYNTAX04_FAILED

    8.349.1. Severity

    ERROR

    8.349.2. Description

    The dns-syntax04 test case failed, but no further +

    8.351. ZM_DNS_SYNTAX04_FAILED

    8.351.1. Severity

    ERROR

    8.351.2. Description

    The dns-syntax04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.350. ZM_DNS_SYNTAX05_FAILED

    8.350.1. Severity

    ERROR

    8.350.2. Description

    The dns-syntax05 test case failed, but no further +

    8.352. ZM_DNS_SYNTAX05_FAILED

    8.352.1. Severity

    ERROR

    8.352.2. Description

    The dns-syntax05 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.351. ZM_DNS_SYNTAX07_FAILED

    8.351.1. Severity

    ERROR

    8.351.2. Description

    The dns-syntax07 test case failed, but no further +

    8.353. ZM_DNS_SYNTAX07_FAILED

    8.353.1. Severity

    ERROR

    8.353.2. Description

    The dns-syntax07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.352. ZM_DNS_ZONE02_FAILED

    8.352.1. Severity

    ERROR

    8.352.2. Description

    The dns-zone02 test case failed, but no further +

    8.354. ZM_DNS_ZONE02_FAILED

    8.354.1. Severity

    ERROR

    8.354.2. Description

    The dns-zone02 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.353. ZM_DNS_ZONE03_FAILED

    8.353.1. Severity

    ERROR

    8.353.2. Description

    The dns-zone03 test case failed, but no further +

    8.355. ZM_DNS_ZONE03_FAILED

    8.355.1. Severity

    ERROR

    8.355.2. Description

    The dns-zone03 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.354. ZM_DNS_ZONE04_FAILED

    8.354.1. Severity

    ERROR

    8.354.2. Description

    The dns-zone04 test case failed, but no further +

    8.356. ZM_DNS_ZONE04_FAILED

    8.356.1. Severity

    ERROR

    8.356.2. Description

    The dns-zone04 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.355. ZM_DNS_ZONE05_FAILED

    8.355.1. Severity

    ERROR

    8.355.2. Description

    The dns-zone05 test case failed, but no further +

    8.357. ZM_DNS_ZONE05_FAILED

    8.357.1. Severity

    ERROR

    8.357.2. Description

    The dns-zone05 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.356. ZM_DNS_ZONE06_FAILED

    8.356.1. Severity

    ERROR

    8.356.2. Description

    The dns-zone06 test case failed, but no further +

    8.358. ZM_DNS_ZONE06_FAILED

    8.358.1. Severity

    ERROR

    8.358.2. Description

    The dns-zone06 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.357. ZM_DNS_ZONE07_FAILED

    8.357.1. Severity

    ERROR

    8.357.2. Description

    The dns-zone07 test case failed, but no further +

    8.359. ZM_DNS_ZONE07_FAILED

    8.359.1. Severity

    ERROR

    8.359.2. Description

    The dns-zone07 test case failed, but no further information is available. Please consult the result log for this test case.

    -

    8.358. ZM_DS01_DIGEST_NOT_SUPPORTED_BY_ZM

    8.358.1. Severity

    NOTICE

    8.358.2. Description

    DS Digest cannot be validated by this installation of Zonemaster.

    -

    8.359. ZM_DS01_DS_ALGO_2_MISSING

    8.359.1. Severity

    ERROR

    8.359.2. Description

    DS created with algo 2 (SHA-256) is missing.

    -

    8.360. ZM_DS01_DS_ALGO_DEPRECATED

    8.360.1. Severity

    ERROR

    8.360.2. Description

    The DS digest algorithm is deprecated.

    -

    8.361. ZM_DS01_DS_ALGO_NOT_DS

    8.361.1. Severity

    ERROR

    8.361.2. Description

    The DS digest algorithm is not for DS.

    -

    8.362. ZM_DS01_DS_ALGO_RESERVED

    8.362.1. Severity

    ERROR

    8.362.2. Description

    No DS digest algorithm defined for the digest code.

    -

    8.363. ZM_DS02_ALGO_NOT_SUPPORTED_BY_ZM

    8.363.1. Severity

    NOTICE

    8.363.2. Description

    DNSKEY with tag {keytag} uses unsupported algorithm {algo_num} +

    8.360. ZM_DS01_DIGEST_NOT_SUPPORTED_BY_ZM

    8.360.1. Severity

    NOTICE

    8.360.2. Description

    DS Digest cannot be validated by this installation of Zonemaster.

    +

    8.361. ZM_DS01_DS_ALGO_2_MISSING

    8.361.1. Severity

    ERROR

    8.361.2. Description

    DS created with algo 2 (SHA-256) is missing.

    +

    8.362. ZM_DS01_DS_ALGO_DEPRECATED

    8.362.1. Severity

    ERROR

    8.362.2. Description

    The DS digest algorithm is deprecated.

    +

    8.363. ZM_DS01_DS_ALGO_NOT_DS

    8.363.1. Severity

    ERROR

    8.363.2. Description

    The DS digest algorithm is not for DS.

    +

    8.364. ZM_DS01_DS_ALGO_RESERVED

    8.364.1. Severity

    ERROR

    8.364.2. Description

    No DS digest algorithm defined for the digest code.

    +

    8.365. ZM_DS02_ALGO_NOT_SUPPORTED_BY_ZM

    8.365.1. Severity

    NOTICE

    8.365.2. Description

    DNSKEY with tag {keytag} uses unsupported algorithm {algo_num} ({algo_mnemo}) by this installation of Zonemaster. Fetched from the nameservers with IP addresses “{ns_ip_list}”.

    -

    8.364. ZM_DS02_DNSKEY_NOT_FOR_ZONE_SIGNING

    8.364.1. Severity

    ERROR

    8.364.2. Description

    Flags field of DNSKEY record with tag {keytag} does not have ZONE bit +

    8.366. ZM_DS02_DNSKEY_NOT_FOR_ZONE_SIGNING

    8.366.1. Severity

    ERROR

    8.366.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.365. ZM_DS02_DNSKEY_NOT_SEP

    8.365.1. Severity

    ERROR

    8.365.2. Description

    Flags field of DNSKEY record with tag {keytag} does not have SEP bit +

    8.367. ZM_DS02_DNSKEY_NOT_SEP

    8.367.1. Severity

    ERROR

    8.367.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.366. ZM_DS02_DNSKEY_NOT_SIGNED_BY_ANY_DS

    8.366.1. Severity

    ERROR

    8.366.2. Description

    The DNSKEY RRset has not been signed by any DNSKEY matched by a DS +

    8.368. ZM_DS02_DNSKEY_NOT_SIGNED_BY_ANY_DS

    8.368.1. Severity

    ERROR

    8.368.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.367. ZM_DS02_NO_DNSKEY_FOR_DS

    8.367.1. Severity

    ERROR

    8.367.2. Description

    The DNSKEY record with tag {keytag} that the DS refers to does not +

    8.369. ZM_DS02_NO_DNSKEY_FOR_DS

    8.369.1. Severity

    ERROR

    8.369.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.368. ZM_DS02_NO_MATCHING_DNSKEY_RRSIG

    8.368.1. Severity

    ERROR

    8.368.2. Description

    The DNSKEY RRset is not signed by the DNSKEY with tag {keytag} that +

    8.370. ZM_DS02_NO_MATCHING_DNSKEY_RRSIG

    8.370.1. Severity

    ERROR

    8.370.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.369. ZM_DS02_NO_MATCH_DS_DNSKEY

    8.369.1. Severity

    ERROR

    8.369.2. Description

    The DS record does not match the DNSKEY with tag {keytag} by +

    8.371. ZM_DS02_NO_MATCH_DS_DNSKEY

    8.371.1. Severity

    ERROR

    8.371.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.370. ZM_DS02_NO_VALID_DNSKEY_FOR_ANY_DS

    8.370.1. Severity

    ERROR

    8.370.2. Description

    There is no valid DNSKEY matched by any of the DS records. Fetched +

    8.372. ZM_DS02_NO_VALID_DNSKEY_FOR_ANY_DS

    8.372.1. Severity

    ERROR

    8.372.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.371. ZM_DS02_RRSIG_NOT_VALID_BY_DNSKEY

    8.371.1. Severity

    ERROR

    8.371.2. Description

    The DNSKEY RRset is signed with an RRSIG with tag {keytag} which +

    8.373. ZM_DS02_RRSIG_NOT_VALID_BY_DNSKEY

    8.373.1. Severity

    ERROR

    8.373.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.372. ZM_DS08_ALGO_NOT_SUPPORTED_BY_ZM

    8.372.1. Severity

    NOTICE

    8.372.2. Description

    This installation of Zonemaster does not support the DNSKEY +

    8.374. ZM_DS08_ALGO_NOT_SUPPORTED_BY_ZM

    8.374.1. Severity

    NOTICE

    8.374.2. Description

    This installation of Zonemaster does not support the DNSKEY algorithm.

    -

    8.373. ZM_DS08_DNSKEY_RRSIG_EXPIRED

    8.373.1. Severity

    ERROR

    8.373.2. Description

    DNSKEY RRset is signed with an RRSIG that has expired.

    -

    8.374. ZM_DS08_DNSKEY_RRSIG_NOT_YET_VALID

    8.374.1. Severity

    ERROR

    8.374.2. Description

    DNSKEY RRset is signed with a not yet valid RRSIG.

    -

    8.375. ZM_DS08_MISSING_RRSIG_IN_RESPONSE

    8.375.1. Severity

    ERROR

    8.375.2. Description

    DNSKEY is unsigned which is against expectation.

    -

    8.376. ZM_DS08_NO_MATCHING_DNSKEY

    8.376.1. Severity

    ERROR

    8.376.2. Description

    DNSKEY RRset is signed with an RRSIG that does not match any +

    8.375. ZM_DS08_DNSKEY_RRSIG_EXPIRED

    8.375.1. Severity

    ERROR

    8.375.2. Description

    DNSKEY RRset is signed with an RRSIG that has expired.

    +

    8.376. ZM_DS08_DNSKEY_RRSIG_NOT_YET_VALID

    8.376.1. Severity

    ERROR

    8.376.2. Description

    DNSKEY RRset is signed with a not yet valid RRSIG.

    +

    8.377. ZM_DS08_MISSING_RRSIG_IN_RESPONSE

    8.377.1. Severity

    ERROR

    8.377.2. Description

    DNSKEY is unsigned which is against expectation.

    +

    8.378. ZM_DS08_NO_MATCHING_DNSKEY

    8.378.1. Severity

    ERROR

    8.378.2. Description

    DNSKEY RRset is signed with an RRSIG that does not match any DNSKEY.

    -

    8.377. ZM_DS08_RRSIG_NOT_VALID_BY_DNSKEY

    8.377.1. Severity

    ERROR

    8.377.2. Description

    DNSKEY RRset is signed with an RRSIG that cannot be validated by the +

    8.379. ZM_DS08_RRSIG_NOT_VALID_BY_DNSKEY

    8.379.1. Severity

    ERROR

    8.379.2. Description

    DNSKEY RRset is signed with an RRSIG that cannot be validated by the matching DNSKEY.

    -

    8.378. ZM_DS09_ALGO_NOT_SUPPORTED_BY_ZM

    8.378.1. Severity

    NOTICE

    8.378.2. Description

    This installation of Zonemaster does not support the DNSKEY +

    8.380. ZM_DS09_ALGO_NOT_SUPPORTED_BY_ZM

    8.380.1. Severity

    NOTICE

    8.380.2. Description

    This installation of Zonemaster does not support the DNSKEY algorithm.

    -

    8.379. ZM_DS09_MISSING_RRSIG_IN_RESPONSE

    8.379.1. Severity

    ERROR

    8.379.2. Description

    SOA is unsigned which is against expectation

    -

    8.380. ZM_DS09_NO_MATCHING_DNSKEY

    8.380.1. Severity

    ERROR

    8.380.2. Description

    SOA is signed with an RRSIG that does not match any DNSKEY

    -

    8.381. ZM_DS09_RRSIG_NOT_VALID_BY_DNSKEY

    8.381.1. Severity

    ERROR

    8.381.2. Description

    SOA is signed with an RRSIG that cannot be validated by the matching +

    8.381. ZM_DS09_MISSING_RRSIG_IN_RESPONSE

    8.381.1. Severity

    ERROR

    8.381.2. Description

    SOA is unsigned which is against expectation

    +

    8.382. ZM_DS09_NO_MATCHING_DNSKEY

    8.382.1. Severity

    ERROR

    8.382.2. Description

    SOA is signed with an RRSIG that does not match any DNSKEY

    +

    8.383. ZM_DS09_RRSIG_NOT_VALID_BY_DNSKEY

    8.383.1. Severity

    ERROR

    8.383.2. Description

    SOA is signed with an RRSIG that cannot be validated by the matching DNSKEY

    -

    8.382. ZM_DS09_SOA_RRSIG_EXPIRED

    8.382.1. Severity

    ERROR

    8.382.2. Description

    SOA is signed with an RRSIG that has expired

    -

    8.383. ZM_DS09_SOA_RRSIG_NOT_YET_VALID

    8.383.1. Severity

    ERROR

    8.383.2. Description

    SOA is signed with a not yet valid RRSIG

    -

    8.384. ZM_DS10_ALGO_NOT_SUPPORTED_BY_ZM

    8.384.1. Severity

    NOTICE

    8.384.2. Description

    This installation of Zonemaster does not support the DNSKEY +

    8.384. ZM_DS09_SOA_RRSIG_EXPIRED

    8.384.1. Severity

    ERROR

    8.384.2. Description

    SOA is signed with an RRSIG that has expired

    +

    8.385. ZM_DS09_SOA_RRSIG_NOT_YET_VALID

    8.385.1. Severity

    ERROR

    8.385.2. Description

    SOA is signed with a not yet valid RRSIG

    +

    8.386. ZM_DS10_ALGO_NOT_SUPPORTED_BY_ZM

    8.386.1. Severity

    NOTICE

    8.386.2. Description

    This installation of Zonemaster does not support the DNSKEY algorithm.

    -

    8.385. ZM_DS10_ANSWER_VERIFY_ERROR

    8.385.1. Severity

    ERROR

    8.385.2. Description

    RRSIG on record or records in answer section cannot be verified.

    -

    8.386. ZM_DS10_HAS_NSEC

    8.386.1. Severity

    INFO

    8.386.2. Description

    Consistent NSEC returned from servers.

    -

    8.387. ZM_DS10_HAS_NSEC3

    8.387.1. Severity

    INFO

    8.387.2. Description

    Consistent NSEC3 returned from servers.

    -

    8.388. ZM_DS10_INCONSISTENT_NSEC_NSEC3

    8.388.1. Severity

    ERROR

    8.388.2. Description

    Some servers return NSEC, others return NSEC3.

    -

    8.389. ZM_DS10_MISSING_NSEC_NSEC3

    8.389.1. Severity

    ERROR

    8.389.2. Description

    Missing expected NSEC or NSEC3 in a signed zone.

    -

    8.390. ZM_DS10_MIXED_NSEC_NSEC3

    8.390.1. Severity

    ERROR

    8.390.2. Description

    Both NSEC and NSEC3 are returned from the same server.

    -

    8.391. ZM_DS10_NAME_NOT_COVERED_BY_NSEC

    8.391.1. Severity

    ERROR

    8.391.2. Description

    The non-existent name is not correctly covered by the NSEC +

    8.387. ZM_DS10_ANSWER_VERIFY_ERROR

    8.387.1. Severity

    ERROR

    8.387.2. Description

    RRSIG on record or records in answer section cannot be verified.

    +

    8.388. ZM_DS10_HAS_NSEC

    8.388.1. Severity

    INFO

    8.388.2. Description

    Consistent NSEC returned from servers.

    +

    8.389. ZM_DS10_HAS_NSEC3

    8.389.1. Severity

    INFO

    8.389.2. Description

    Consistent NSEC3 returned from servers.

    +

    8.390. ZM_DS10_INCONSISTENT_NSEC_NSEC3

    8.390.1. Severity

    ERROR

    8.390.2. Description

    Some servers return NSEC, others return NSEC3.

    +

    8.391. ZM_DS10_MISSING_NSEC_NSEC3

    8.391.1. Severity

    ERROR

    8.391.2. Description

    Missing expected NSEC or NSEC3 in a signed zone.

    +

    8.392. ZM_DS10_MIXED_NSEC_NSEC3

    8.392.1. Severity

    ERROR

    8.392.2. Description

    Both NSEC and NSEC3 are returned from the same server.

    +

    8.393. ZM_DS10_NAME_NOT_COVERED_BY_NSEC

    8.393.1. Severity

    ERROR

    8.393.2. Description

    The non-existent name is not correctly covered by the NSEC records.

    -

    8.392. ZM_DS10_NAME_NOT_COVERED_BY_NSEC3

    8.392.1. Severity

    ERROR

    8.392.2. Description

    The non-existent name is not correctly covered by the NSEC3 +

    8.394. ZM_DS10_NAME_NOT_COVERED_BY_NSEC3

    8.394.1. Severity

    ERROR

    8.394.2. Description

    The non-existent name is not correctly covered by the NSEC3 records.

    -

    8.393. ZM_DS10_NON_EXISTENT_RESPONSE_ERROR

    8.393.1. Severity

    ERROR

    8.393.2. Description

    No or error in response of an expected non-existent name.

    -

    8.394. ZM_DS10_NSEC3_MISSING_SIGNATURE

    8.394.1. Severity

    ERROR

    8.394.2. Description

    Missing signatures for NSEC3 record or records.

    -

    8.395. ZM_DS10_NSEC3_RRSIG_VERIFY_ERROR

    8.395.1. Severity

    ERROR

    8.395.2. Description

    The signature or signatures on the NSEC3 record or records cannot be +

    8.395. ZM_DS10_NON_EXISTENT_RESPONSE_ERROR

    8.395.1. Severity

    ERROR

    8.395.2. Description

    No or error in response of an expected non-existent name.

    +

    8.396. ZM_DS10_NSEC3_MISSING_SIGNATURE

    8.396.1. Severity

    ERROR

    8.396.2. Description

    Missing signatures for NSEC3 record or records.

    +

    8.397. ZM_DS10_NSEC3_RRSIG_VERIFY_ERROR

    8.397.1. Severity

    ERROR

    8.397.2. Description

    The signature or signatures on the NSEC3 record or records cannot be correctly verfied.

    -

    8.396. ZM_DS10_NSEC_MISSING_SIGNATURE

    8.396.1. Severity

    ERROR

    8.396.2. Description

    Missing signatures for NSEC record or records.

    -

    8.397. ZM_DS10_NSEC_RRSIG_VERIFY_ERROR

    8.397.1. Severity

    ERROR

    8.397.2. Description

    The signature or signatures on the NSEC record or records cannot be +

    8.398. ZM_DS10_NSEC_MISSING_SIGNATURE

    8.398.1. Severity

    ERROR

    8.398.2. Description

    Missing signatures for NSEC record or records.

    +

    8.399. ZM_DS10_NSEC_RRSIG_VERIFY_ERROR

    8.399.1. Severity

    ERROR

    8.399.2. Description

    The signature or signatures on the NSEC record or records cannot be correctly verfied.

    -

    8.398. ZM_DS10_UNSIGNED_ANSWER

    8.398.1. Severity

    ERROR

    8.398.2. Description

    RRSIG is missing for record or records in the answer section.

    -

    8.399. ZM_DS13_ALGO_NOT_SIGNED_DNSKEY

    8.399.1. Severity

    ERROR

    8.399.2. Description

    The DNSKEY RRset is not signed with an algorithm present in the +

    8.400. ZM_DS10_UNSIGNED_ANSWER

    8.400.1. Severity

    ERROR

    8.400.2. Description

    RRSIG is missing for record or records in the answer section.

    +

    8.401. ZM_DS13_ALGO_NOT_SIGNED_DNSKEY

    8.401.1. Severity

    ERROR

    8.401.2. Description

    The DNSKEY RRset is not signed with an algorithm present in the DNSKEY RRset

    -

    8.400. ZM_DS13_ALGO_NOT_SIGNED_NS

    8.400.1. Severity

    ERROR

    8.400.2. Description

    The NS RRset is not signed with an algorithm present in the DNSKEY +

    8.402. ZM_DS13_ALGO_NOT_SIGNED_NS

    8.402.1. Severity

    ERROR

    8.402.2. Description

    The NS RRset is not signed with an algorithm present in the DNSKEY RRset

    -

    8.401. ZM_DS13_ALGO_NOT_SIGNED_SOA

    8.401.1. Severity

    ERROR

    8.401.2. Description

    The SOA RRset is not signed with an algorithm present in the DNSKEY +

    8.403. ZM_DS13_ALGO_NOT_SIGNED_SOA

    8.403.1. Severity

    ERROR

    8.403.2. Description

    The SOA RRset is not signed with an algorithm present in the DNSKEY RRset

    -

    8.402. ZM_DS15_HAS_CDNSKEY_NO_CDS

    8.402.1. Severity

    NOTICE

    8.402.2. Description

    CDNSKEY RRset is found, but no CDS RRset.

    -

    8.403. ZM_DS15_HAS_CDS_AND_CDNSKEY

    8.403.1. Severity

    INFO

    8.403.2. Description

    CDNSKEY and CDS RRsets are found.

    -

    8.404. ZM_DS15_HAS_CDS_NO_CDNSKEY

    8.404.1. Severity

    NOTICE

    8.404.2. Description

    CDS RRset is found, but no CDNSKEY RRset.

    -

    8.405. ZM_DS15_INCONSISTENT_CDNSKEY

    8.405.1. Severity

    ERROR

    8.405.2. Description

    All servers do not have the same CDNSKEY RRset.

    -

    8.406. ZM_DS15_INCONSISTENT_CDS

    8.406.1. Severity

    ERROR

    8.406.2. Description

    All servers do not have the same CDS RRset.

    -

    8.407. ZM_DS15_MISMATCH_CDS_CDNSKEY

    8.407.1. Severity

    ERROR

    8.407.2. Description

    Both CDS and CDNSKEY RRsets are found but they do not match.

    -

    8.408. ZM_DS15_NO_CDS_CDNSKEY

    8.408.1. Severity

    INFO

    8.408.2. Description

    No CDS or CDNSKEY RRsets are found on any name server.

    -

    8.409. ZM_DS16_CDS_INVALID_RRSIG

    8.409.1. Severity

    ERROR

    8.409.2. Description

    CDS RRset is signed with an invalid RRSIG.

    -

    8.410. ZM_DS16_CDS_MATCHES_NON_SEP_DNSKEY

    8.410.1. Severity

    ERROR

    8.410.2. Description

    CDS record matches a DNSKEY with SEP bit (bit 15) unset.

    -

    8.411. ZM_DS16_CDS_MATCHES_NON_ZONE_DNSKEY

    8.411.1. Severity

    ERROR

    8.411.2. Description

    CDS record matches a DNSKEY with zone bit (bit 7) unset.

    -

    8.412. ZM_DS16_CDS_MATCHES_NO_DNSKEY

    8.412.1. Severity

    ERROR

    8.412.2. Description

    CDS record does not match any DNSKEY in DNSKEY RRset.

    -

    8.413. ZM_DS16_CDS_NOT_SIGNED_BY_CDS

    8.413.1. Severity

    ERROR

    8.413.2. Description

    CDS RRset is not signed by the key that the CDS record points to.

    -

    8.414. ZM_DS16_CDS_SIGNED_BY_UNKNOWN_DNSKEY

    8.414.1. Severity

    ERROR

    8.414.2. Description

    CDS RRset is signed by a key not in DNSKEY RRset.

    -

    8.415. ZM_DS16_CDS_UNSIGNED

    8.415.1. Severity

    ERROR

    8.415.2. Description

    CDS RRset is unsigned.

    -

    8.416. ZM_DS16_CDS_WITHOUT_DNSKEY

    8.416.1. Severity

    ERROR

    8.416.2. Description

    CDS RRset exists, but there is no DNSKEY RRset.

    -

    8.417. ZM_DS16_DELETE_CDS

    8.417.1. Severity

    INFO

    8.417.2. Description

    CDS RRset has a “delete” CDS record as a single record.

    -

    8.418. ZM_DS16_DNSKEY_NOT_SIGNED_BY_CDS

    8.418.1. Severity

    ERROR

    8.418.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDS records +

    8.404. ZM_DS15_HAS_CDNSKEY_NO_CDS

    8.404.1. Severity

    NOTICE

    8.404.2. Description

    CDNSKEY RRset is found, but no CDS RRset.

    +

    8.405. ZM_DS15_HAS_CDS_AND_CDNSKEY

    8.405.1. Severity

    INFO

    8.405.2. Description

    CDNSKEY and CDS RRsets are found.

    +

    8.406. ZM_DS15_HAS_CDS_NO_CDNSKEY

    8.406.1. Severity

    NOTICE

    8.406.2. Description

    CDS RRset is found, but no CDNSKEY RRset.

    +

    8.407. ZM_DS15_INCONSISTENT_CDNSKEY

    8.407.1. Severity

    ERROR

    8.407.2. Description

    All servers do not have the same CDNSKEY RRset.

    +

    8.408. ZM_DS15_INCONSISTENT_CDS

    8.408.1. Severity

    ERROR

    8.408.2. Description

    All servers do not have the same CDS RRset.

    +

    8.409. ZM_DS15_MISMATCH_CDS_CDNSKEY

    8.409.1. Severity

    ERROR

    8.409.2. Description

    Both CDS and CDNSKEY RRsets are found but they do not match.

    +

    8.410. ZM_DS15_NO_CDS_CDNSKEY

    8.410.1. Severity

    INFO

    8.410.2. Description

    No CDS or CDNSKEY RRsets are found on any name server.

    +

    8.411. ZM_DS16_CDS_INVALID_RRSIG

    8.411.1. Severity

    ERROR

    8.411.2. Description

    CDS RRset is signed with an invalid RRSIG.

    +

    8.412. ZM_DS16_CDS_MATCHES_NON_SEP_DNSKEY

    8.412.1. Severity

    ERROR

    8.412.2. Description

    CDS record matches a DNSKEY with SEP bit (bit 15) unset.

    +

    8.413. ZM_DS16_CDS_MATCHES_NON_ZONE_DNSKEY

    8.413.1. Severity

    ERROR

    8.413.2. Description

    CDS record matches a DNSKEY with zone bit (bit 7) unset.

    +

    8.414. ZM_DS16_CDS_MATCHES_NO_DNSKEY

    8.414.1. Severity

    ERROR

    8.414.2. Description

    CDS record does not match any DNSKEY in DNSKEY RRset.

    +

    8.415. ZM_DS16_CDS_NOT_SIGNED_BY_CDS

    8.415.1. Severity

    ERROR

    8.415.2. Description

    CDS RRset is not signed by the key that the CDS record points to.

    +

    8.416. ZM_DS16_CDS_SIGNED_BY_UNKNOWN_DNSKEY

    8.416.1. Severity

    ERROR

    8.416.2. Description

    CDS RRset is signed by a key not in DNSKEY RRset.

    +

    8.417. ZM_DS16_CDS_UNSIGNED

    8.417.1. Severity

    ERROR

    8.417.2. Description

    CDS RRset is unsigned.

    +

    8.418. ZM_DS16_CDS_WITHOUT_DNSKEY

    8.418.1. Severity

    ERROR

    8.418.2. Description

    CDS RRset exists, but there is no DNSKEY RRset.

    +

    8.419. ZM_DS16_DELETE_CDS

    8.419.1. Severity

    INFO

    8.419.2. Description

    CDS RRset has a “delete” CDS record as a single record.

    +

    8.420. ZM_DS16_DNSKEY_NOT_SIGNED_BY_CDS

    8.420.1. Severity

    ERROR

    8.420.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDS records point to.

    -

    8.419. ZM_DS16_MIXED_DELETE_CDS

    8.419.1. Severity

    ERROR

    8.419.2. Description

    “Delete” CDS record is mixed with normal CDS record.

    -

    8.420. ZM_DS17_CDNSKEY_INVALID_RRSIG

    8.420.1. Severity

    ERROR

    8.420.2. Description

    CDNSKEY RRset signed with an invalid RRSIG.

    -

    8.421. ZM_DS17_CDNSKEY_IS_NON_SEP

    8.421.1. Severity

    ERROR

    8.421.2. Description

    CDNSKEY record has the SEP bit (bit 15) unset.

    -

    8.422. ZM_DS17_CDNSKEY_IS_NON_ZONE

    8.422.1. Severity

    ERROR

    8.422.2. Description

    CDNSKEY record has the zone bit (bit 7) unset.

    -

    8.423. ZM_DS17_CDNSKEY_MATCHES_NO_DNSKEY

    8.423.1. Severity

    ERROR

    8.423.2. Description

    CDNSKEY record does not match any DNSKEY in DNSKEY RRset.

    -

    8.424. ZM_DS17_CDNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.424.1. Severity

    ERROR

    8.424.2. Description

    CDNSKEY RRset is not signed by the key that the CDNSKEY record points +

    8.421. ZM_DS16_MIXED_DELETE_CDS

    8.421.1. Severity

    ERROR

    8.421.2. Description

    “Delete” CDS record is mixed with normal CDS record.

    +

    8.422. ZM_DS17_CDNSKEY_INVALID_RRSIG

    8.422.1. Severity

    ERROR

    8.422.2. Description

    CDNSKEY RRset signed with an invalid RRSIG.

    +

    8.423. ZM_DS17_CDNSKEY_IS_NON_SEP

    8.423.1. Severity

    ERROR

    8.423.2. Description

    CDNSKEY record has the SEP bit (bit 15) unset.

    +

    8.424. ZM_DS17_CDNSKEY_IS_NON_ZONE

    8.424.1. Severity

    ERROR

    8.424.2. Description

    CDNSKEY record has the zone bit (bit 7) unset.

    +

    8.425. ZM_DS17_CDNSKEY_MATCHES_NO_DNSKEY

    8.425.1. Severity

    ERROR

    8.425.2. Description

    CDNSKEY record does not match any DNSKEY in DNSKEY RRset.

    +

    8.426. ZM_DS17_CDNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.426.1. Severity

    ERROR

    8.426.2. Description

    CDNSKEY RRset is not signed by the key that the CDNSKEY record points to.

    -

    8.425. ZM_DS17_CDNSKEY_SIGNED_BY_UNKNOWN_DNSKEY

    8.425.1. Severity

    ERROR

    8.425.2. Description

    CDNSKEY RRset is signed by a key not in DNSKEY RRset.

    -

    8.426. ZM_DS17_CDNSKEY_UNSIGNED

    8.426.1. Severity

    ERROR

    8.426.2. Description

    CDNSKEY RRset is unsigned.

    -

    8.427. ZM_DS17_CDNSKEY_WITHOUT_DNSKEY

    8.427.1. Severity

    ERROR

    8.427.2. Description

    CDNSKEY RRset exists, but there is no DNSKEY RRset.

    -

    8.428. ZM_DS17_DELETE_CDNSKEY

    8.428.1. Severity

    INFO

    8.428.2. Description

    CDNSKEY RRset has a “delete” CDNSKEY record as a single record.

    -

    8.429. ZM_DS17_DNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.429.1. Severity

    ERROR

    8.429.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDNSKEY +

    8.427. ZM_DS17_CDNSKEY_SIGNED_BY_UNKNOWN_DNSKEY

    8.427.1. Severity

    ERROR

    8.427.2. Description

    CDNSKEY RRset is signed by a key not in DNSKEY RRset.

    +

    8.428. ZM_DS17_CDNSKEY_UNSIGNED

    8.428.1. Severity

    ERROR

    8.428.2. Description

    CDNSKEY RRset is unsigned.

    +

    8.429. ZM_DS17_CDNSKEY_WITHOUT_DNSKEY

    8.429.1. Severity

    ERROR

    8.429.2. Description

    CDNSKEY RRset exists, but there is no DNSKEY RRset.

    +

    8.430. ZM_DS17_DELETE_CDNSKEY

    8.430.1. Severity

    INFO

    8.430.2. Description

    CDNSKEY RRset has a “delete” CDNSKEY record as a single record.

    +

    8.431. ZM_DS17_DNSKEY_NOT_SIGNED_BY_CDNSKEY

    8.431.1. Severity

    ERROR

    8.431.2. Description

    DNSKEY RRset is not signed by the key or keys that the CDNSKEY records point to.

    -

    8.430. ZM_DS17_MIXED_DELETE_CDNSKEY

    8.430.1. Severity

    ERROR

    8.430.2. Description

    “Delete” CDNSKEY record is mixed with normal CDNSKEY record.

    -

    8.431. ZM_DS18_NO_MATCH_CDNSKEY_RRSIG_DS

    8.431.1. Severity

    ERROR

    8.431.2. Description

    CDNSKEY RRset is not signed with a DNSKEY record that a DS record +

    8.432. ZM_DS17_MIXED_DELETE_CDNSKEY

    8.432.1. Severity

    ERROR

    8.432.2. Description

    “Delete” CDNSKEY record is mixed with normal CDNSKEY record.

    +

    8.433. ZM_DS18_NO_MATCH_CDNSKEY_RRSIG_DS

    8.433.1. Severity

    ERROR

    8.433.2. Description

    CDNSKEY RRset is not signed with a DNSKEY record that a DS record points to.

    -

    8.432. ZM_DS18_NO_MATCH_CDS_RRSIG_DS

    8.432.1. Severity

    ERROR

    8.432.2. Description

    The CDS RRset is not signed with a DNSKEY record that a DS record +

    8.434. ZM_DS18_NO_MATCH_CDS_RRSIG_DS

    8.434.1. Severity

    ERROR

    8.434.2. Description

    The CDS RRset is not signed with a DNSKEY record that a DS record points to.

    -

    8.433. ZM_EDNS_RESPONSE_WITHOUT_EDNS

    8.433.1. Severity

    ERROR

    8.433.2. Description

    Not available.

    -

    8.434. ZM_EDNS_VERSION_ERROR

    8.434.1. Severity

    ERROR

    8.434.2. Description

    Not available.

    -

    8.435. ZM_EMPTY_ASN_SET

    8.435.1. Severity

    ERROR

    8.435.2. Description

    Not available.

    -

    8.436. ZM_ENOUGH_IPV4_NS_CHILD

    8.436.1. Severity

    INFO

    8.436.2. Description

    Not available.

    -

    8.437. ZM_ENOUGH_IPV4_NS_DEL

    8.437.1. Severity

    INFO

    8.437.2. Description

    Not available.

    -

    8.438. ZM_ENOUGH_IPV6_NS_CHILD

    8.438.1. Severity

    INFO

    8.438.2. Description

    Not available.

    -

    8.439. ZM_ENOUGH_IPV6_NS_DEL

    8.439.1. Severity

    INFO

    8.439.2. Description

    Not available.

    -

    8.440. ZM_ENOUGH_NS_CHILD

    8.440.1. Severity

    INFO

    8.440.2. Description

    Not available.

    -

    8.441. ZM_ENOUGH_NS_DEL

    8.441.1. Severity

    INFO

    8.441.2. Description

    Not available.

    -

    8.442. ZM_ERROR_ASN_DATABASE

    8.442.1. Severity

    ERROR

    8.442.2. Description

    Not available.

    -

    8.443. ZM_EXTRA_ADDRESS_CHILD

    8.443.1. Severity

    ERROR

    8.443.2. Description

    Not available.

    -

    8.444. ZM_IN_BAILIWICK_ADDR_MISMATCH

    8.444.1. Severity

    ERROR

    8.444.2. Description

    Not available.

    -

    8.445. ZM_IPV4_DIFFERENT_ASN

    8.445.1. Severity

    INFO

    8.445.2. Description

    Not available.

    -

    8.446. ZM_IPV4_ONE_ASN

    8.446.1. Severity

    ERROR

    8.446.2. Description

    Not available.

    -

    8.447. ZM_IPV4_SAME_ASN

    8.447.1. Severity

    NOTICE

    8.447.2. Description

    Not available.

    -

    8.448. ZM_IPV6_DIFFERENT_ASN

    8.448.1. Severity

    INFO

    8.448.2. Description

    Not available.

    -

    8.449. ZM_IPV6_ONE_ASN

    8.449.1. Severity

    ERROR

    8.449.2. Description

    Not available.

    -

    8.450. ZM_IPV6_SAME_ASN

    8.450.1. Severity

    NOTICE

    8.450.2. Description

    Not available.

    -

    8.451. ZM_IS_A_RECURSOR

    8.451.1. Severity

    ERROR

    8.451.2. Description

    Not available.

    -

    8.452. ZM_KEY_SIZE_OK

    8.452.1. Severity

    INFO

    8.452.2. Description

    Not available.

    -

    8.453. ZM_MISSING_OPT_IN_TRUNCATED

    8.453.1. Severity

    ERROR

    8.453.2. Description

    Not available.

    -

    8.454. ZM_MULTIPLE_NS_SET

    8.454.1. Severity

    ERROR

    8.454.2. Description

    Not available.

    -

    8.455. ZM_MULTIPLE_SOA

    8.455.1. Severity

    ERROR

    8.455.2. Description

    Not available.

    -

    8.456. ZM_MULTIPLE_SOA_MNAMES

    8.456.1. Severity

    ERROR

    8.456.2. Description

    Not available.

    -

    8.457. ZM_MULTIPLE_SOA_RNAMES

    8.457.1. Severity

    ERROR

    8.457.2. Description

    Not available.

    -

    8.458. ZM_MULTIPLE_SOA_TIME_PARAMETER_SET

    8.458.1. Severity

    ERROR

    8.458.2. Description

    Not available.

    -

    8.459. ZM_N10_EDNS_RESPONSE_ERROR

    8.459.1. Severity

    ERROR

    8.459.2. Description

    Expected RCODE value when EDNS ver=1, but error in response.

    -

    8.460. ZM_N10_NO_RESPONSE_EDNS1_QUERY

    8.460.1. Severity

    ERROR

    8.460.2. Description

    Response when EDNS ver=0, but not when 1.

    -

    8.461. ZM_N10_UNEXPECTED_RCODE

    8.461.1. Severity

    ERROR

    8.461.2. Description

    Unexpected RCODE value when EDNS ver=1.

    -

    8.462. ZM_N11_NO_EDNS

    8.462.1. Severity

    ERROR

    8.462.2. Description

    The DNS response, on query with unknown EDNS option-code, does not +

    8.435. ZM_EDNS_RESPONSE_WITHOUT_EDNS

    8.435.1. Severity

    ERROR

    8.435.2. Description

    Not available.

    +

    8.436. ZM_EDNS_VERSION_ERROR

    8.436.1. Severity

    ERROR

    8.436.2. Description

    Not available.

    +

    8.437. ZM_EMPTY_ASN_SET

    8.437.1. Severity

    ERROR

    8.437.2. Description

    Not available.

    +

    8.438. ZM_ENOUGH_IPV4_NS_CHILD

    8.438.1. Severity

    INFO

    8.438.2. Description

    Not available.

    +

    8.439. ZM_ENOUGH_IPV4_NS_DEL

    8.439.1. Severity

    INFO

    8.439.2. Description

    Not available.

    +

    8.440. ZM_ENOUGH_IPV6_NS_CHILD

    8.440.1. Severity

    INFO

    8.440.2. Description

    Not available.

    +

    8.441. ZM_ENOUGH_IPV6_NS_DEL

    8.441.1. Severity

    INFO

    8.441.2. Description

    Not available.

    +

    8.442. ZM_ENOUGH_NS_CHILD

    8.442.1. Severity

    INFO

    8.442.2. Description

    Not available.

    +

    8.443. ZM_ENOUGH_NS_DEL

    8.443.1. Severity

    INFO

    8.443.2. Description

    Not available.

    +

    8.444. ZM_ERROR_ASN_DATABASE

    8.444.1. Severity

    ERROR

    8.444.2. Description

    Not available.

    +

    8.445. ZM_EXTRA_ADDRESS_CHILD

    8.445.1. Severity

    ERROR

    8.445.2. Description

    Not available.

    +

    8.446. ZM_IN_BAILIWICK_ADDR_MISMATCH

    8.446.1. Severity

    ERROR

    8.446.2. Description

    Not available.

    +

    8.447. ZM_IPV4_DIFFERENT_ASN

    8.447.1. Severity

    INFO

    8.447.2. Description

    Not available.

    +

    8.448. ZM_IPV4_ONE_ASN

    8.448.1. Severity

    ERROR

    8.448.2. Description

    Not available.

    +

    8.449. ZM_IPV4_SAME_ASN

    8.449.1. Severity

    NOTICE

    8.449.2. Description

    Not available.

    +

    8.450. ZM_IPV6_DIFFERENT_ASN

    8.450.1. Severity

    INFO

    8.450.2. Description

    Not available.

    +

    8.451. ZM_IPV6_ONE_ASN

    8.451.1. Severity

    ERROR

    8.451.2. Description

    Not available.

    +

    8.452. ZM_IPV6_SAME_ASN

    8.452.1. Severity

    NOTICE

    8.452.2. Description

    Not available.

    +

    8.453. ZM_IS_A_RECURSOR

    8.453.1. Severity

    ERROR

    8.453.2. Description

    Not available.

    +

    8.454. ZM_KEY_SIZE_OK

    8.454.1. Severity

    INFO

    8.454.2. Description

    Not available.

    +

    8.455. ZM_MISSING_OPT_IN_TRUNCATED

    8.455.1. Severity

    ERROR

    8.455.2. Description

    Not available.

    +

    8.456. ZM_MULTIPLE_NS_SET

    8.456.1. Severity

    ERROR

    8.456.2. Description

    Not available.

    +

    8.457. ZM_MULTIPLE_SOA

    8.457.1. Severity

    ERROR

    8.457.2. Description

    Not available.

    +

    8.458. ZM_MULTIPLE_SOA_MNAMES

    8.458.1. Severity

    ERROR

    8.458.2. Description

    Not available.

    +

    8.459. ZM_MULTIPLE_SOA_RNAMES

    8.459.1. Severity

    ERROR

    8.459.2. Description

    Not available.

    +

    8.460. ZM_MULTIPLE_SOA_TIME_PARAMETER_SET

    8.460.1. Severity

    ERROR

    8.460.2. Description

    Not available.

    +

    8.461. ZM_N10_EDNS_RESPONSE_ERROR

    8.461.1. Severity

    ERROR

    8.461.2. Description

    Expected RCODE value when EDNS ver=1, but error in response.

    +

    8.462. ZM_N10_NO_RESPONSE_EDNS1_QUERY

    8.462.1. Severity

    ERROR

    8.462.2. Description

    Response when EDNS ver=0, but not when 1.

    +

    8.463. ZM_N10_UNEXPECTED_RCODE

    8.463.1. Severity

    ERROR

    8.463.2. Description

    Unexpected RCODE value when EDNS ver=1.

    +

    8.464. ZM_N11_NO_EDNS

    8.464.1. Severity

    ERROR

    8.464.2. Description

    The DNS response, on query with unknown EDNS option-code, does not contain any EDNS from name servers “{ns_ip_list}”.

    -

    8.463. ZM_N11_NO_RESPONSE

    8.463.1. Severity

    ERROR

    8.463.2. Description

    There is no response on query with unknown EDNS option-code from name +

    8.465. ZM_N11_NO_RESPONSE

    8.465.1. Severity

    ERROR

    8.465.2. Description

    There is no response on query with unknown EDNS option-code from name servers “{ns_ip_list}”.

    -

    8.464. ZM_N11_RETURNS_UNKNOWN_OPTION_CODE

    8.464.1. Severity

    ERROR

    8.464.2. Description

    The DNS response, on query with unknown EDNS option-code, contains an +

    8.466. ZM_N11_RETURNS_UNKNOWN_OPTION_CODE

    8.466.1. Severity

    ERROR

    8.466.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.465. ZM_N11_UNEXPECTED_ANSWER_SECTION

    8.465.1. Severity

    ERROR

    8.465.2. Description

    The DNS response, on query with unknown EDNS option-code, does not +

    8.467. ZM_N11_UNEXPECTED_ANSWER_SECTION

    8.467.1. Severity

    ERROR

    8.467.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.466. ZM_N11_UNEXPECTED_RCODE

    8.466.1. Severity

    ERROR

    8.466.2. Description

    The DNS response, on query with unknown EDNS option-code, has +

    8.468. ZM_N11_UNEXPECTED_RCODE

    8.468.1. Severity

    ERROR

    8.468.2. Description

    The DNS response, on query with unknown EDNS option-code, has unexpected RCODE name “{rcode}” from name servers “{ns_ip_list}”.

    -

    8.467. ZM_N11_UNSET_AA

    8.467.1. Severity

    ERROR

    8.467.2. Description

    The DNS response, on query with unknown EDNS option-code, is +

    8.469. ZM_N11_UNSET_AA

    8.469.1. Severity

    ERROR

    8.469.2. Description

    The DNS response, on query with unknown EDNS option-code, is unexpectedly not authoritative from name servers “{ns_ip_list}”.

    -

    8.468. ZM_N15_NO_VERSION

    8.468.1. Severity

    INFO

    8.468.2. Description

    The following name server(s) do not respond to software version +

    8.470. ZM_N15_NO_VERSION

    8.470.1. Severity

    INFO

    8.470.2. Description

    The following name server(s) do not respond to software version queries. Returned from name servers: “{ns_ip_list}”

    -

    8.469. ZM_N15_SOFTWARE_VERSION

    8.469.1. Severity

    INFO

    8.469.2. Description

    The following name server(s) respond to software version query +

    8.471. ZM_N15_SOFTWARE_VERSION

    8.471.1. Severity

    INFO

    8.471.2. Description

    The following name server(s) respond to software version query “{query_name}” with string “{string}”. Returned from name servers: “{ns_ip_list}”

    -

    8.470. ZM_NOT_ENOUGH_IPV4_NS_CHILD

    8.470.1. Severity

    ERROR

    8.470.2. Description

    Not available.

    -

    8.471. ZM_NOT_ENOUGH_IPV4_NS_DEL

    8.471.1. Severity

    ERROR

    8.471.2. Description

    Not available.

    -

    8.472. ZM_NOT_ENOUGH_IPV6_NS_CHILD

    8.472.1. Severity

    ERROR

    8.472.2. Description

    Not available.

    -

    8.473. ZM_NOT_ENOUGH_IPV6_NS_DEL

    8.473.1. Severity

    ERROR

    8.473.2. Description

    Not available.

    -

    8.474. ZM_NOT_ENOUGH_NS_CHILD

    8.474.1. Severity

    ERROR

    8.474.2. Description

    Not available.

    -

    8.475. ZM_NOT_ENOUGH_NS_DEL

    8.475.1. Severity

    ERROR

    8.475.2. Description

    Not available.

    -

    8.476. ZM_NO_EDNS_SUPPORT

    8.476.1. Severity

    ERROR

    8.476.2. Description

    Not available.

    -

    8.477. ZM_NO_IPV4_NS_CHILD

    8.477.1. Severity

    ERROR

    8.477.2. Description

    Not available.

    -

    8.478. ZM_NO_IPV4_NS_DEL

    8.478.1. Severity

    ERROR

    8.478.2. Description

    Not available.

    -

    8.479. ZM_NO_IPV6_NS_CHILD

    8.479.1. Severity

    ERROR

    8.479.2. Description

    Not available.

    -

    8.480. ZM_NO_IPV6_NS_DEL

    8.480.1. Severity

    ERROR

    8.480.2. Description

    Not available.

    -

    8.481. ZM_NO_NS_CNAME

    8.481.1. Severity

    INFO

    8.481.2. Description

    Not available.

    -

    8.482. ZM_NO_RECURSOR

    8.482.1. Severity

    INFO

    8.482.2. Description

    Not available.

    -

    8.483. ZM_NO_RESPONSE

    8.483.1. Severity

    ERROR

    8.483.2. Description

    Not available.

    -

    8.484. ZM_NO_RESPONSE_DNSKEY

    8.484.1. Severity

    ERROR

    8.484.2. Description

    Not available.

    -

    8.485. ZM_NO_RESPONSE_NS_QUERY

    8.485.1. Severity

    ERROR

    8.485.2. Description

    Not available.

    -

    8.486. ZM_NO_RESPONSE_SOA_QUERY

    8.486.1. Severity

    ERROR

    8.486.2. Description

    Not available.

    -

    8.487. ZM_NO_SOA_IN_RESPONSE

    8.487.1. Severity

    ERROR

    8.487.2. Description

    Not available.

    -

    8.488. ZM_NS_ERROR

    8.488.1. Severity

    ERROR

    8.488.2. Description

    Not available.

    -

    8.489. ZM_NS_IS_CNAME

    8.489.1. Severity

    ERROR

    8.489.2. Description

    Not available.

    -

    8.490. ZM_ONE_NS_SET

    8.490.1. Severity

    INFO

    8.490.2. Description

    Not available.

    -

    8.491. ZM_ONE_SOA

    8.491.1. Severity

    INFO

    8.491.2. Description

    Not available.

    -

    8.492. ZM_ONE_SOA_MNAME

    8.492.1. Severity

    INFO

    8.492.2. Description

    Not available.

    -

    8.493. ZM_ONE_SOA_RNAME

    8.493.1. Severity

    INFO

    8.493.2. Description

    Not available.

    -

    8.494. ZM_ONE_SOA_TIME_PARAMETER_SET

    8.494.1. Severity

    INFO

    8.494.2. Description

    Not available.

    -

    8.495. ZM_OUT_OF_BAILIWICK_ADDR_MISMATCH

    8.495.1. Severity

    ERROR

    8.495.2. Description

    Not available.

    -

    8.496. ZM_REFERRAL_SIZE_OK

    8.496.1. Severity

    INFO

    8.496.2. Description

    Not available.

    -

    8.497. ZM_REFERRAL_SIZE_TOO_LARGE

    8.497.1. Severity

    WARNING

    8.497.2. Description

    Not available.

    -

    8.498. ZM_RNAME_MAIL_DOMAIN_INVALID

    8.498.1. Severity

    ERROR

    8.498.2. Description

    Not available.

    -

    8.499. ZM_RNAME_MAIL_DOMAIN_LOCALHOST

    8.499.1. Severity

    ERROR

    8.499.2. Description

    Not available.

    -

    8.500. ZM_RNAME_MAIL_ILLEGAL_CNAME

    8.500.1. Severity

    ERROR

    8.500.2. Description

    Not available.

    -

    8.501. ZM_RNAME_RFC822_INVALID

    8.501.1. Severity

    ERROR

    8.501.2. Description

    Not available.

    -

    8.502. ZM_RNAME_RFC822_VALID

    8.502.1. Severity

    INFO

    8.502.2. Description

    Not available.

    -

    8.503. ZM_UNEXPECTED_RCODE

    8.503.1. Severity

    WARNING

    8.503.2. Description

    Not available.

    -

    8.504. ZM_UNKNOWN_OPTION_CODE

    8.504.1. Severity

    ERROR

    8.504.2. Description

    Not available.

    -

    8.505. ZM_UNSUPPORTED_EDNS_VER

    8.505.1. Severity

    ERROR

    8.505.2. Description

    Not available.

    -

    8.506. ZM_WRONG_SOA

    8.506.1. Severity

    ERROR

    8.506.2. Description

    Not available.

    -

    8.507. ZM_Z01_MNAME_HAS_LOCALHOST_ADDR

    8.507.1. Severity

    WARNING

    8.507.2. Description

    SOA MNAME name server “{nsname}” resolves to a localhost IP address +

    8.472. ZM_NOT_ENOUGH_IPV4_NS_CHILD

    8.472.1. Severity

    ERROR

    8.472.2. Description

    Not available.

    +

    8.473. ZM_NOT_ENOUGH_IPV4_NS_DEL

    8.473.1. Severity

    ERROR

    8.473.2. Description

    Not available.

    +

    8.474. ZM_NOT_ENOUGH_IPV6_NS_CHILD

    8.474.1. Severity

    ERROR

    8.474.2. Description

    Not available.

    +

    8.475. ZM_NOT_ENOUGH_IPV6_NS_DEL

    8.475.1. Severity

    ERROR

    8.475.2. Description

    Not available.

    +

    8.476. ZM_NOT_ENOUGH_NS_CHILD

    8.476.1. Severity

    ERROR

    8.476.2. Description

    Not available.

    +

    8.477. ZM_NOT_ENOUGH_NS_DEL

    8.477.1. Severity

    ERROR

    8.477.2. Description

    Not available.

    +

    8.478. ZM_NO_EDNS_SUPPORT

    8.478.1. Severity

    ERROR

    8.478.2. Description

    Not available.

    +

    8.479. ZM_NO_IPV4_NS_CHILD

    8.479.1. Severity

    ERROR

    8.479.2. Description

    Not available.

    +

    8.480. ZM_NO_IPV4_NS_DEL

    8.480.1. Severity

    ERROR

    8.480.2. Description

    Not available.

    +

    8.481. ZM_NO_IPV6_NS_CHILD

    8.481.1. Severity

    ERROR

    8.481.2. Description

    Not available.

    +

    8.482. ZM_NO_IPV6_NS_DEL

    8.482.1. Severity

    ERROR

    8.482.2. Description

    Not available.

    +

    8.483. ZM_NO_NS_CNAME

    8.483.1. Severity

    INFO

    8.483.2. Description

    Not available.

    +

    8.484. ZM_NO_RECURSOR

    8.484.1. Severity

    INFO

    8.484.2. Description

    Not available.

    +

    8.485. ZM_NO_RESPONSE

    8.485.1. Severity

    ERROR

    8.485.2. Description

    Not available.

    +

    8.486. ZM_NO_RESPONSE_DNSKEY

    8.486.1. Severity

    ERROR

    8.486.2. Description

    Not available.

    +

    8.487. ZM_NO_RESPONSE_NS_QUERY

    8.487.1. Severity

    ERROR

    8.487.2. Description

    Not available.

    +

    8.488. ZM_NO_RESPONSE_SOA_QUERY

    8.488.1. Severity

    ERROR

    8.488.2. Description

    Not available.

    +

    8.489. ZM_NO_SOA_IN_RESPONSE

    8.489.1. Severity

    ERROR

    8.489.2. Description

    Not available.

    +

    8.490. ZM_NS_ERROR

    8.490.1. Severity

    ERROR

    8.490.2. Description

    Not available.

    +

    8.491. ZM_NS_IS_CNAME

    8.491.1. Severity

    ERROR

    8.491.2. Description

    Not available.

    +

    8.492. ZM_ONE_NS_SET

    8.492.1. Severity

    INFO

    8.492.2. Description

    Not available.

    +

    8.493. ZM_ONE_SOA

    8.493.1. Severity

    INFO

    8.493.2. Description

    Not available.

    +

    8.494. ZM_ONE_SOA_MNAME

    8.494.1. Severity

    INFO

    8.494.2. Description

    Not available.

    +

    8.495. ZM_ONE_SOA_RNAME

    8.495.1. Severity

    INFO

    8.495.2. Description

    Not available.

    +

    8.496. ZM_ONE_SOA_TIME_PARAMETER_SET

    8.496.1. Severity

    INFO

    8.496.2. Description

    Not available.

    +

    8.497. ZM_OUT_OF_BAILIWICK_ADDR_MISMATCH

    8.497.1. Severity

    ERROR

    8.497.2. Description

    Not available.

    +

    8.498. ZM_REFERRAL_SIZE_OK

    8.498.1. Severity

    INFO

    8.498.2. Description

    Not available.

    +

    8.499. ZM_REFERRAL_SIZE_TOO_LARGE

    8.499.1. Severity

    WARNING

    8.499.2. Description

    Not available.

    +

    8.500. ZM_RNAME_MAIL_DOMAIN_INVALID

    8.500.1. Severity

    ERROR

    8.500.2. Description

    Not available.

    +

    8.501. ZM_RNAME_MAIL_DOMAIN_LOCALHOST

    8.501.1. Severity

    ERROR

    8.501.2. Description

    Not available.

    +

    8.502. ZM_RNAME_MAIL_ILLEGAL_CNAME

    8.502.1. Severity

    ERROR

    8.502.2. Description

    Not available.

    +

    8.503. ZM_RNAME_RFC822_INVALID

    8.503.1. Severity

    ERROR

    8.503.2. Description

    Not available.

    +

    8.504. ZM_RNAME_RFC822_VALID

    8.504.1. Severity

    INFO

    8.504.2. Description

    Not available.

    +

    8.505. ZM_UNEXPECTED_RCODE

    8.505.1. Severity

    WARNING

    8.505.2. Description

    Not available.

    +

    8.506. ZM_UNKNOWN_OPTION_CODE

    8.506.1. Severity

    ERROR

    8.506.2. Description

    Not available.

    +

    8.507. ZM_UNSUPPORTED_EDNS_VER

    8.507.1. Severity

    ERROR

    8.507.2. Description

    Not available.

    +

    8.508. ZM_WRONG_SOA

    8.508.1. Severity

    ERROR

    8.508.2. Description

    Not available.

    +

    8.509. ZM_Z01_MNAME_HAS_LOCALHOST_ADDR

    8.509.1. Severity

    WARNING

    8.509.2. Description

    SOA MNAME name server “{nsname}” resolves to a localhost IP address ({ns_ip}).

    -

    8.508. ZM_Z01_MNAME_IS_DOT

    8.508.1. Severity

    NOTICE

    8.508.2. Description

    SOA MNAME is specified as “.” which usually means “no server”. +

    8.510. ZM_Z01_MNAME_IS_DOT

    8.510.1. Severity

    NOTICE

    8.510.2. Description

    SOA MNAME is specified as “.” which usually means “no server”. Fetched from name servers “{ns_ip_list}”.

    -

    8.509. ZM_Z01_MNAME_IS_LOCALHOST

    8.509.1. Severity

    WARNING

    8.509.2. Description

    SOA MNAME name server is “localhost”, which is invalid. Fetched from +

    8.511. ZM_Z01_MNAME_IS_LOCALHOST

    8.511.1. Severity

    WARNING

    8.511.2. Description

    SOA MNAME name server is “localhost”, which is invalid. Fetched from name servers “{ns_ip_list}”.

    -

    8.510. ZM_Z01_MNAME_MISSING_SOA_RECORD

    8.510.1. Severity

    WARNING

    8.510.2. Description

    SOA MNAME name server “{ns}” reponds to an SOA query with no SOA +

    8.512. ZM_Z01_MNAME_MISSING_SOA_RECORD

    8.512.1. Severity

    WARNING

    8.512.2. Description

    SOA MNAME name server “{ns}” reponds to an SOA query with no SOA records in the answer section.

    -

    8.511. ZM_Z01_MNAME_NOT_AUTHORITATIVE

    8.511.1. Severity

    WARNING

    8.511.2. Description

    SOA MNAME name server “{ns}” is not authoritative for the zone.

    -

    8.512. ZM_Z01_MNAME_NOT_IN_NS_LIST

    8.512.1. Severity

    INFO

    8.512.2. Description

    SOA MNAME name server “{nsname}” is not listed as NS record for the +

    8.513. ZM_Z01_MNAME_NOT_AUTHORITATIVE

    8.513.1. Severity

    WARNING

    8.513.2. Description

    SOA MNAME name server “{ns}” is not authoritative for the zone.

    +

    8.514. ZM_Z01_MNAME_NOT_IN_NS_LIST

    8.514.1. Severity

    INFO

    8.514.2. Description

    SOA MNAME name server “{nsname}” is not listed as NS record for the zone.

    -

    8.513. ZM_Z01_MNAME_NOT_MASTER

    8.513.1. Severity

    WARNING

    8.513.2. Description

    SOA MNAME name server(s) “{ns_list}” do(es) not have the highest SOA +

    8.515. ZM_Z01_MNAME_NOT_MASTER

    8.515.1. Severity

    WARNING

    8.515.2. Description

    SOA MNAME name server(s) “{ns_list}” do(es) not have the highest SOA SERIAL (expected “{soaserial}” but got “{soaserial_list}”)

    -

    8.514. ZM_Z01_MNAME_NOT_RESOLVE

    8.514.1. Severity

    WARNING

    8.514.2. Description

    SOA MNAME name server “{nsname}” cannot be resolved into an IP +

    8.516. ZM_Z01_MNAME_NOT_RESOLVE

    8.516.1. Severity

    WARNING

    8.516.2. Description

    SOA MNAME name server “{nsname}” cannot be resolved into an IP address.

    -

    8.515. ZM_Z01_MNAME_NO_RESPONSE

    8.515.1. Severity

    WARNING

    8.515.2. Description

    SOA MNAME name server “{ns}” does not respond to an SOA query.

    -

    8.516. ZM_Z01_MNAME_UNEXPECTED_RCODE

    8.516.1. Severity

    WARNING

    8.516.2. Description

    SOA MNAME name server “{ns}” gives unexpected RCODE name (“{rcode}”) +

    8.517. ZM_Z01_MNAME_NO_RESPONSE

    8.517.1. Severity

    WARNING

    8.517.2. Description

    SOA MNAME name server “{ns}” does not respond to an SOA query.

    +

    8.518. ZM_Z01_MNAME_UNEXPECTED_RCODE

    8.518.1. Severity

    WARNING

    8.518.2. Description

    SOA MNAME name server “{ns}” gives unexpected RCODE name (“{rcode}”) in response to an SOA query.

    -

    8.517. ZM_Z_FLAGS_NOTCLEAR

    8.517.1. Severity

    ERROR

    8.517.2. Description

    Not available.

    +

    8.519. ZM_Z_FLAGS_NOTCLEAR

    8.519.1. Severity

    ERROR

    8.519.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 faa3d52..83b5892 100644 --- a/rst-test-specs.json +++ b/rst-test-specs.json @@ -25,6 +25,10 @@ "Description" : "TBA.", "Severity" : "ERROR" }, + "DNSSEC_OPS_INVALID_ALGORITHM" : { + "Description" : "TBA.", + "Severity" : "ERROR" + }, "DNSSEC_OPS_KSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN" : { "Description" : "TBA.", "Severity" : "ERROR" @@ -33,6 +37,10 @@ "Description" : "TBA.", "Severity" : "ERROR" }, + "DNSSEC_OPS_XFR_FAILED" : { + "Description" : "TBA.", + "Severity" : "ERROR" + }, "DNSSEC_OPS_ZSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN" : { "Description" : "TBA.", "Severity" : "ERROR" @@ -2076,7 +2084,7 @@ }, "Input-Parameters" : { "dns.nameservers" : { - "Description" : "The set of nameservers that will be authoritative for the TLD(s).\n\nThis input parameter is an array where the object properties are the\nTLD names, and the values are objects. For these objects, the properties\nare the nameserver names, and the values are arrays of IPv4 and IPv6\naddresses.\n\nThere **MUST** be at least two nameservers, and at least two nameservers\n**MUST** have at least one IPv6 address.\n", + "Description" : "The set of nameservers that will be authoritative for the TLD(s).\n\nThis input parameter is an object where the object properties are the\nTLD names, and the values are objects. For these objects, the properties\nare the nameserver names, and the values are arrays of IPv4 and IPv6\naddresses.\n\nThere **MUST** be at least two nameservers, and at least two nameservers\n**MUST** have at least one IPv6 address.\n", "Example" : { "example" : { "ns1.example.com" : [ @@ -2135,6 +2143,72 @@ "Example" : "example.com", "Type" : "string" }, + "dnssecOps.nameservers" : { + "Description" : "The set of nameservers that will be authoritative for the zones used in the\nDNSSEC operations test suite.\n\nThis input parameter is an object where the object properties are the\nzone names, and the values are objects. For these objects, the properties\nare the nameserver names, and the values are arrays of IPv4 and IPv6\naddresses.\n", + "Example" : { + "example" : { + "ns1.example.com" : [ + "192.168.53.1", + "2001:DB8::53:1" + ], + "ns2.example.com" : [ + "192.168.53.2", + "2001:DB8::53:2" + ] + } + }, + "Schema" : { + "patternProperties" : { + "^[a-z]+[a-z0-9\\.]*[a-z]\\$" : { + "items" : { + "format" : [ + "ipv4", + "ipv6" + ], + "type" : "string" + }, + "type" : "array" + } + }, + "type" : "object" + }, + "Type" : "object" + }, + "dnssecOps.primaryServer" : { + "Description" : "The primary nameserver from which zones can be transferred.", + "Example" : "192.168.53.1", + "Schema" : { + "format" : [ + "ipv4", + "ipv6" + ], + "type" : "string" + }, + "Type" : "string" + }, + "dnssecOps.tsigKey" : { + "Description" : "The TSIG key which should be used to perform zone transfers.", + "Example" : { + "algorithm" : "hmac-sha256", + "name" : "rst-tsig-01", + "secret" : "NQO...xQ=" + }, + "Schema" : { + "properties" : { + "algorithm" : { + "type" : "string" + }, + "name" : { + "type" : "string" + }, + "secret" : { + "type" : "string" + } + }, + "type" : "object" + }, + "Type" : "object" + }, "dnssecOps.zskRolloverZone" : { "Description" : "The domain name which will be monitored for the occurrence of a ZSK\nrollover.\n", "Example" : "example.com", @@ -3116,7 +3190,7 @@ "Summary" : "Permitted DS record hash algorithm(s)" }, "dnssecOps01-ZSKRollover" : { - "Description" : "This test case verifies the RSP's ability to perform a ZSK rollover (as\ndescribed in [Section 4.1.1 of\nRFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.1) for\na zone.\n\nIf the value of the `dnssecOps.csk` input parameter is `true`, then this\ntest will be skipped.\n\nThe system will monitor the SOA record in the domain name specified in the\n`dnssec.zskRolloverZone` input parameter. The domain may be present\nanywhere in the DNS hierarchy (that is, it does not need to be a TLD), but\n**MUST** have a secure chain of trust up to the root zone, so that it can\nbe validated using the root zone trust anchor.\n\nDuring the test period (currently defined as 24 hours) the operator\n**MUST** successfully carry out a ZSK rollover for the domain, where the\nZone Signing Key is replaced, without disrupting the chain of trust.\n\nTo simplify testing, applicants may wish to provision domain that is\nconfigured with short TTLs and a short ZSK lifetime, so that a ZSK\nrollover is guaranteed to occur within the 24 test period.\n", + "Description" : "This test case verifies the RSP's ability to perform a ZSK rollover (as\ndescribed in [Section 4.1.1 of\nRFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.1) for\na zone.\n\nIf the value of the `dnssecOps.csk` input parameter is `true`, then this\ntest will be skipped.\n\nThe system will monitor the zone specified in the `dnssec.zskRolloverZone`\ninput parameter. The domain may be present anywhere in the DNS hierarchy\n(that is, it does not need to be a TLD), but **MUST** have a secure chain of\ntrust up to the root zone, so that it can be validated using the root zone\ntrust anchor.\n\nThe zone **MUST** contain at least 10,000 delegations, where a delegation is\nconsidered to be one or more `NS` records with owner names that are below\nthe zone's origin. If NSEC3 is used for secure denial of existence, the\nopt-out flag `MUST NOT` be set *(that is, an `RRSIG` record should be\npresent for all `NS` rrsets, irrespective of whether a corresponding `DS`\nrecord is published)*.\n\nMonitoring will be carried out using `SOA` queries sent to multiple\nvalidating DNS resolvers, and by validating the result of a a zone transfer\nfrom the server specified in the `dnssecOps.primaryServer` input parameter.\n\nDuring the test period (currently defined as 48 hours) the operator\n**MUST** successfully carry out a ZSK rollover for the domain, where the\nZone Signing Key is replaced, without disrupting the chain of trust.\n\nTo simplify testing, applicants may wish to provision the zone such that it\nis configured with short TTLs and a short ZSK lifetime, so that a ZSK\nrollover is guaranteed to occur within the 48 test period.\n", "Errors" : [ "DNSSEC_OPS_ZSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN", "DNSSEC_OPS_ZSK_ROLLOVER_NOT_COMPLETED" @@ -3128,7 +3202,7 @@ "Summary" : "ZSK rollover" }, "dnssecOps02-KSKRollover" : { - "Description" : "This test case verifies the RSP's ability to perform a CSK/KSK rollover\n(as described in [Sections 4.1.2 and 4.13 of\nRFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.2) for\na zone.\n\nThe system will monitor the SOA record in the domain name specified in the\n`dnssec.kskRolloverZone` input parameter. The domain may be present\nanywhere in the DNS hierarchy (that is, it does not need to be a TLD), but\n**MUST** have a secure chain of trust up to the root zone, so that it can\nbe validated using the root zone trust anchor.\n\nDuring the test period (currently defined as 24 hours) the operator\n**MUST** successfully carry out a KSK rollover for the domain, where the\nKey Signing Key is replaced, and the DS record in the parent zone is\nupdated, without disrupting the chain of trust.\n", + "Description" : "This test case verifies the RSP's ability to perform a CSK/KSK rollover\n(as described in [Sections 4.1.2 and 4.13 of\nRFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.2) for\na zone.\n\nThe system will monitor the zone specified in the `dnssec.zskRolloverZone`\ninput parameter. The domain may be present anywhere in the DNS hierarchy\n(that is, it does not need to be a TLD), but **MUST** have a secure chain of\ntrust up to the root zone, so that it can be validated using the root zone\ntrust anchor.\n\nThe zone **MUST** contain at least 10,000 delegations, where a delegation is\nconsidered to be one or more `NS` records with owner names that are below\nthe zone's origin. If NSEC3 is used for secure denial of existence, the\nopt-out flag `MUST NOT` be set *(that is, an `RRSIG` record should be\npresent for all `NS` rrsets, irrespective of whether a corresponding `DS`\nrecord is published)*.\n\nMonitoring will be carried out using `SOA` queries sent to multiple\nvalidating DNS resolvers, and by validating the result of a a zone transfer\nfrom the server specified in the `dnssecOps.primaryServer` input parameter.\n\nDuring the test period (currently defined as 48 hours) the operator\n**MUST** successfully carry out a KSK rollover for the domain, where the\nKey Signing Key is replaced, and the DS record in the parent zone is\nupdated, without disrupting the chain of trust.\n", "Errors" : [ "DNSSEC_OPS_KSK_ROLLOVER_CHAIN_OF_TRUST_BROKEN", "DNSSEC_OPS_KSK_ROLLOVER_NOT_COMPLETED" @@ -3139,10 +3213,11 @@ "Summary" : "KSK rollover" }, "dnssecOps03-AlgorithmRollover" : { - "Description" : "This test case verifies the RSP's ability to perform an algorithm rollover\n(as described in [Section 4.1.4 of\nRFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.2) for\na zone.\n\nThe system will monitor the SOA record in the domain name specified in the\n`dnssec.algorithmRolloverZone` input parameter. The domain may be present\nanywhere in the DNS hierarchy (that is, it does not need to be a TLD), but\n**MUST** have a secure chain of trust up to the root zone, so that it can\nbe validated using the root zone trust anchor.\n\nDuring the test period (currently defined as 72 hours) the operator\n**MUST** successfully carry out an algorithm rollover for the domain\n(including an update to the DS record in the parent zone), where the\nalgorithm used to secure the domain is changed, without disrupting the\nchain of trust.\n\nNote that the specific algorithms being rolled to and from are not\nsignificant (although they **MUST** be present in the IANA registry); it\nis not required that the new algorithm be more \"secure\" than the original\nalgorithm; only that they are different. So a rollover from algorithm 13\n(`ECDSAP256SHA256`) to algorithm 8 (`RSASHA256`) will be accepted as well\nas a rollover from `RSASHA256` to `ECDSAP256SHA256`.\n", + "Description" : "This test case verifies the RSP's ability to perform an algorithm rollover\n(as described in [Section 4.1.4 of\nRFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.2) for\na zone.\n\nThe system will monitor the zone specified in the `dnssec.zskRolloverZone`\ninput parameter. The domain may be present anywhere in the DNS hierarchy\n(that is, it does not need to be a TLD), but **MUST** have a secure chain of\ntrust up to the root zone, so that it can be validated using the root zone\ntrust anchor.\n\nThe zone **MUST** contain at least 10,000 delegations, where a delegation is\nconsidered to be one or more `NS` records with owner names that are below\nthe zone's origin. If NSEC3 is used for secure denial of existence, the\nopt-out flag `MUST NOT` be set *(that is, an `RRSIG` record should be\npresent for all `NS` rrsets, irrespective of whether a corresponding `DS`\nrecord is published)*.\n\nMonitoring will be carried out using `SOA` queries sent to multiple\nvalidating DNS resolvers, and by validating the result of a a zone transfer\nfrom the server specified in the `dnssecOps.primaryServer` input parameter.\n\nDuring the test period (currently defined as 48 hours) the operator\n**MUST** successfully carry out an algorithm rollover for the domain\n(including an update to the DS record in the parent zone), where the\nalgorithm used to secure the domain is changed, without disrupting the\nchain of trust.\n\nNote that the specific algorithms being rolled to and from are not\nsignificant (although they **MUST** be present in the IANA registry); it\nis not required that the new algorithm be more \"secure\" than the original\nalgorithm; only that they are different. So a rollover from algorithm 13\n(`ECDSAP256SHA256`) to algorithm 8 (`RSASHA256`) will be accepted as well\nas a rollover from `RSASHA256` to `ECDSAP256SHA256`.\n", "Errors" : [ "DNSSEC_OPS_ALGORITHM_ROLLOVER_CHAIN_OF_TRUST_BROKEN", - "DNSSEC_OPS_ALGORITHM_ROLLOVER_NOT_COMPLETED" + "DNSSEC_OPS_ALGORITHM_ROLLOVER_NOT_COMPLETED", + "DNSSEC_OPS_INVALID_ALGORITHM" ], "Input-Parameters" : [ "dnssecOps.algorithmRolloverZone" @@ -3310,7 +3385,7 @@ "Dependencies" : [ "epp-09" ], - "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", + "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", "Errors" : [ "EPP_CONTACT_DELETE_RESPONSE_NOT_1000_OR_1001", "EPP_CONTACT_DELETE_OBJECT_STILL_EXISTS" @@ -3356,14 +3431,6 @@ "Summary" : "host command test (if applicable)" }, "epp-14" : { - "Description" : "intentionally omitted", - "Summary" : "intentionally omitted" - }, - "epp-15" : { - "Description" : "intentionally omitted", - "Summary" : "intentionally omitted" - }, - "epp-16" : { "Dependencies" : [ "epp-03" ], @@ -3390,22 +3457,22 @@ ], "Summary" : "domain command test" }, - "epp-17" : { + "epp-15" : { "Dependencies" : [ - "epp-16" + "epp-14" ], - "Description" : "This test confirms that the EPP server will refuse a request to delete a\nlinked object.\n\nIf the `epp.hostModel` input parameter is `attributes`, **and** the\n`general.minimalPublicDataSet` input parameter is `true`, then this test\nwill be skipped.\n\nThe client will submit `` commands for any contact and host\nobjects created during `epp-16`. The server **MUST** respond with a `2305`\n\"Object association prohibits operation\" error.\n", + "Description" : "This test confirms that the EPP server will refuse a request to delete a\nlinked object.\n\nIf the `epp.hostModel` input parameter is `attributes`, **and** the\n`general.minimalPublicDataSet` input parameter is `true`, then this test\nwill be skipped.\n\nThe client will submit `` commands for any contact and host\nobjects created during `epp-14`. The server **MUST** respond with a `2305`\n\"Object association prohibits operation\" error.\n", "Errors" : [ "EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT", "EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT" ], "Summary" : "Registry object integrity test" }, - "epp-18" : { + "epp-16" : { "Dependencies" : [ - "epp-16" + "epp-14" ], - "Description" : "This test will confirm that the client is able to renew domain names. The\nclient will submit a number of `` commands for the domains created in\n`epp-16`.\n\n* Following a succesful `` command, the expiry date of the domain\n **MUST** have been increased by the period specified by the client;\n* The domain **MUST** have an RGP status of `renewPeriod`;\n* The server **MUST** reject a `` command if it would result in\n the expiry date being more than 10 years into the future.\n\nThe client will issue the `` commands and then perform ``\ncommands to ensure that the expiry date and RGP status of the domain are\nset correctly.\n", + "Description" : "This test will confirm that the client is able to renew domain names. The\nclient will submit a number of `` commands for the domains created in\n`epp-14`.\n\n* Following a succesful `` command, the expiry date of the domain\n **MUST** have been increased by the period specified by the client;\n* The domain **MUST** have an RGP status of `renewPeriod`;\n* The server **MUST** reject a `` command if it would result in\n the expiry date being more than 10 years into the future.\n\nThe client will issue the `` commands and then perform ``\ncommands to ensure that the expiry date and RGP status of the domain are\nset correctly.\n", "Errors" : [ "EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD", "EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE", @@ -3414,11 +3481,11 @@ ], "Summary" : "domain command test" }, - "epp-19" : { + "epp-17" : { "Dependencies" : [ - "epp-16" + "epp-14" ], - "Description" : "This test will confirm that the client is able to initiate a domain\ntransfer.\n\nThe client will perform an `` command to set the authInfo code for\nthe test domain (taken from the set created in `epp-16`) to a\nrandomly-determined value. If the server implements RFC 9154, it **MUST**\nreject the `` command if the authInfo code is insufficently\nsecure.\n\nThen, using a second set of credentials, the client will connect to the\nEPP server and authenticate, submit `` commands, and validate\nthe responses.\n\nThis test will confirm that:\n\n* the server rejects a `` command with an invalid authInfo code\n* the server rejects a command which would extend the domain's validity\n period more than 10 years into the future\n* the server accepts a `` command with a valid authInfo code\n and period.\n\nThe client will use an `` command to ensure that the\n`pendingTransfer` status code is added to the domain after a successul\ntransfer request.\n\nOnce the transfer request has been accepted, the sponsoring client will\nwait for a message to be received on the server's message queue, and will\nthen approve the transfer. This message **MUST** be received within 120\nseconds of the transfer request.\n\nOnce the gaining registrar has also received a message on the queue, the\nclient will use an `` command to confirm that:\n\n* the domain is now under the sponsorship of the gaining registrar\n* the authInfo code has been reset by the server (if the server supports\n RFC 9154).\n\nThis message **MUST** be received within 120 seconds of the transfer\napproval.\n", + "Description" : "This test will confirm that the client is able to initiate a domain\ntransfer.\n\nThe client will perform an `` command to set the authInfo code for\nthe test domain (taken from the set created in `epp-14`) to a\nrandomly-determined value. If the server implements RFC 9154, it **MUST**\nreject the `` command if the authInfo code is insufficently\nsecure.\n\nThen, using a second set of credentials, the client will connect to the\nEPP server and authenticate, submit `` commands, and validate\nthe responses.\n\nThis test will confirm that:\n\n* the server rejects a `` command with an invalid authInfo code\n* the server rejects a command which would extend the domain's validity\n period more than 10 years into the future\n* the server accepts a `` command with a valid authInfo code\n and period.\n\nThe client will use an `` command to ensure that the\n`pendingTransfer` status code is added to the domain after a successul\ntransfer request.\n\nOnce the transfer request has been accepted, the sponsoring client will\nwait for a message to be received on the server's message queue, and will\nthen approve the transfer. This message **MUST** be received within 120\nseconds of the transfer request.\n\nOnce the gaining registrar has also received a message on the queue, the\nclient will use an `` command to confirm that:\n\n* the domain is now under the sponsorship of the gaining registrar\n* the authInfo code has been reset by the server (if the server supports\n RFC 9154).\n\nThis message **MUST** be received within 120 seconds of the transfer\napproval.\n", "Errors" : [ "EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO", "EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO", @@ -3432,21 +3499,21 @@ ], "Summary" : "domain command test" }, - "epp-20" : { + "epp-18" : { "Dependencies" : [ - "epp-16" + "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-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.", + "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.", "Errors" : [ "EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER" ], "Summary" : "domain rejection test" }, - "epp-21" : { + "epp-19" : { "Dependencies" : [ - "epp-16" + "epp-14" ], - "Description" : "This test will perform `` commands on the objects created during\n`epp-16` and will confirm that the server accepts the `` command\nwith a `1xxx` response code.\n\nOnce the `` commands have been processed, the client will perform\n`` commands on the deleted to object to confirm that:\n\n* if the server responded to the `` command with a `1000`\n response, then the domain no longer exists\n* if the server responded to the `` command with a `1001`\n response, then the domain has the `pendingDelete` status and the\n `redemptionPeriod` RGP status.\n", + "Description" : "This test will perform `` commands on the objects created during\n`epp-14` and will confirm that the server accepts the `` command\nwith a `1xxx` response code.\n\nOnce the `` commands have been processed, the client will perform\n`` commands on the deleted to object to confirm that:\n\n* if the server responded to the `` command with a `1000`\n response, then the domain no longer exists\n* if the server responded to the `` command with a `1001`\n response, then the domain has the `pendingDelete` status and the\n `redemptionPeriod` RGP status.\n", "Errors" : [ "EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS", "EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE", @@ -3454,11 +3521,11 @@ ], "Summary" : "domain command test" }, - "epp-22" : { + "epp-20" : { "Dependencies" : [ - "epp-21" + "epp-19" ], - "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", + "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", "Errors" : [ "EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE" ], @@ -3467,12 +3534,12 @@ ], "Summary" : "domain restore test" }, - "epp-23" : { + "epp-21" : { "Dependencies" : [ - "epp-16", + "epp-14", "epp-11" ], - "Description" : "This tests verifies the server's support for host rename operations.\n\nIf the `epp.hostModel` input parameter is `attributes`, this test will\nbe skipped.\n\nThe client will perform `` commands on the objects created during\n`epp-11` and will confirm that the server correctly accepts or rejects the\ncommands, for example:\n\n* an `` command which specifies a syntatically invalid host name\n is rejected;\n* an `` command which places the object out-of-bailiwick is\n accepted;\n* an `` command which places the object within a non-existent\n domain is rejected;\n* an `` command which places the object within a domain sponsored\n by another registrar is rejected. The domain name(s) provided in the\n `epp.registeredNames` parameter will be used for this test.\n* an `` command which places the object within a domain sponsored\n by the test client is accepted. A domain created during the `epp-16`\n test case will be used as the new parent domain.\n\nThe client will then perform `` commands on the objects successfully\nupdated, to confirm that the server has correctly stored the updated\nvalues.\n", + "Description" : "This tests verifies the server's support for host rename operations.\n\nIf the `epp.hostModel` input parameter is `attributes`, this test will\nbe skipped.\n\nThe client will perform `` commands on the objects created during\n`epp-11` and will confirm that the server correctly accepts or rejects the\ncommands, for example:\n\n* an `` command which specifies a syntatically invalid host name\n is rejected;\n* an `` command which places the object out-of-bailiwick is\n accepted;\n* an `` command which places the object within a non-existent\n domain is rejected;\n* an `` command which places the object within a domain sponsored\n by another registrar is rejected. The domain name(s) provided in the\n `epp.registeredNames` parameter will be used for this test.\n* an `` command which places the object within a domain sponsored\n by the test client is accepted. A domain created during the `epp-14`\n test case will be used as the new parent domain.\n\nThe client will then perform `` commands on the objects successfully\nupdated, to confirm that the server has correctly stored the updated\nvalues.\n", "Errors" : [ "EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME", "EPP_HOST_RENAME_SERVER_REJECTS_OUT_OF_BAILIWICK_NAME", @@ -3482,9 +3549,9 @@ ], "Summary" : "host rename test (if applicable)" }, - "epp-24" : { + "epp-22" : { "Dependencies" : [ - "epp-23" + "epp-21" ], "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" : [ @@ -3521,10 +3588,10 @@ }, "integration-01" : { "Dependencies" : [ - "epp-16", + "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-16`, 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 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", "Errors" : [ "INTEGRATION_RDAP_REQUEST_FAILED", "INTEGRATION_DOMAIN_NOT_PRESENT_IN_RDAP" @@ -3538,9 +3605,9 @@ }, "integration-02" : { "Dependencies" : [ - "epp-16" + "epp-14" ], - "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-16`. 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\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", "Errors" : [ "INTEGRATION_DNS_QUERY_FAILED", "INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS", @@ -3554,10 +3621,10 @@ }, "integration-03" : { "Dependencies" : [ - "epp-16", + "epp-14", "epp-11" ], - "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-16` 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 `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", "Errors" : [ "INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE", "INTEGRATION_RDE_SFTP_SERVER_AUTHENTICATION_ERROR", @@ -3609,137 +3676,137 @@ "Summary" : "Trademark claims domain command test" }, "rdap-01-domainCaseFoldingValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Domain label case folding validation" }, "rdap-02-domainNameValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Domain Name validation" }, "rdap-03-ipv4Validation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "IPv4 address validation" }, "rdap-04-ipv6Validation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "IPv6 address validation" }, "rdap-05-stdRdapAsEventActorValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "asEventActor Validation" }, "rdap-06-stdRdapConformanceValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "RDAP Conformance validation" }, "rdap-07-stdRdapDomainLookupValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Domain Lookup Validation" }, "rdap-08-stdRdapEntitiesValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Entities validation" }, "rdap-09-stdRdapEntityLookupValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Entity lookup validation" }, "rdap-10-stdRdapErrorResponseBodyValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Error Response Body" }, "rdap-11-stdRdapEventsValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Events Validation" }, "rdap-12-stdRdapHelpValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Help validation" }, "rdap-13-stdRdapIpAddressesValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "IP Addresses Validation" }, "rdap-14-stdRdapLanguageIdentifierValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Language Identifier Validation" }, "rdap-15-stdRdapLdhNameValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "LDH name" }, "rdap-16-stdRdapLinksValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Links validation" }, "rdap-17-stdRdapNameserverLookupValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Nameserver lookup validation" }, "rdap-18-stdRdapNameserversSearchValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", - "Summary" : "RFC7159RDAP_RFCsNameservers search validation" + "Summary" : "Nameservers search validation" }, "rdap-19-stdRdapNoticesRemarksValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Notices and Remarks Validation" }, "rdap-20-stdRdapPort43WhoisServerValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Port 43 WHOIS Server" }, "rdap-21-stdRdapPublicIdsValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Public IDs validation" }, "rdap-22-stdRdapRolesValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Roles validation" }, "rdap-23-stdRdapSecureDnsValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Secure DNS validation" }, "rdap-24-stdRdapStatusValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Status validation" }, "rdap-25-stdRdapUnicodeNameValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", - "Summary" : "RFC7159RDAP_RFCsIDNA_RFCsUnicode name" + "Summary" : "Unicode name" }, "rdap-26-stdRdapVariantsValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Variants validation" }, "rdap-27-webUriValidation" : { - "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n.\n", + "Description" : "This test case comes from the RDAP Conformance Tool. For more information, see\n .\n", "Maturity" : "GAMMA", "Summary" : "Web URI validation" }, @@ -4090,7 +4157,7 @@ ] }, "DNSRSPEvaluationTest" : { - "Description" : "DNS RSPs provide primary or secondary authoritative DNS services.\nTherefore, this test plan only covers the DNS area.\n\nRSPs wishing to offer DNSSEC services in addition to authoritative DNS\nwill also be evaluated using the DNSSEC RSP Evaluation Test below.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "DNS RSPs provide primary or secondary authoritative DNS services. Therefore,\nthis test plan only covers the DNS area.\n\nRSPs wishing to offer DNSSEC services in addition to authoritative DNS will\nalso be evaluated using the DNSSEC RSP Evaluation Test below.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "DNS RSP Evaluation Test", "Order" : "8", "Test-Suites" : [ @@ -4098,7 +4165,7 @@ ] }, "DNSSECRSPEvaluationTest" : { - "Description" : "DNSSEC RSPs provide signing of TLD zone files as a service. They do not\nprovide primary or secondary authoritative DNS services.\n\nRSPs wishing to offer DNSSEC services in addition to authoritative DNS\nwill also be evaluated using the DNSSEC RSP Evaluation Test below.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "DNSSEC RSPs provide signing of TLD zone files as a service. They do not\nprovide primary or secondary authoritative DNS services.\n\nRSPs wishing to offer DNSSEC services in addition to authoritative DNS will\nalso be evaluated using the DNSSEC RSP Evaluation Test below.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "DNSSEC RSP Evaluation Test", "Order" : "9", "Test-Suites" : [ @@ -4107,7 +4174,7 @@ ] }, "MainRSPEvaluationTest" : { - "Description" : "The Main RSP is responsible for the creation and maintenance of domain\nname registrations in a Shared Registration System (SRS). This encompasses\nthe lifecycle of a domain name registration using domain registrars and\nprotocols such as the Extensible Provisioning Protocol (EPP) and adherence\nto policies regarding the use and transparency domain name registrations\nthrough reporting, the Registration Data Access Protocol (RDAP), and other\nmechanisms.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "The Main RSP is responsible for the creation and maintenance of domain name\nregistrations in a Shared Registration System (SRS). This encompasses the\nlifecycle of a domain name registration using domain registrars and\nprotocols such as the Extensible Provisioning Protocol (EPP) and adherence\nto policies regarding the use and transparency domain name registrations\nthrough reporting, the Registration Data Access Protocol (RDAP), and other\nmechanisms.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "Main RSP Evaluation Test", "Order" : "7", "Test-Suites" : [ @@ -4118,7 +4185,7 @@ ] }, "RSPEvaluationIDNTest" : { - "Description" : "This test plan is identical to the Standard IDN Test, but is intended\nsolely for use by the RSP evaluation program.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "This test plan is identical to the Standard IDN Test, but is intended\nsolely for use in the RSP evaluation program.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "IDN Test (RSP Evaluation)", "Order" : "5", "Test-Suites" : [ @@ -4126,7 +4193,7 @@ ] }, "SRSGatewayRSPTest" : { - "Description" : "SRS Gateway RSPs provide a proxy between a subset of Registrars and the\nRegistry. It uses a local cache to speed up EPP query commands, but\nforwards all EPP transform commands to the primary registry system. TLD\nregistries need to deploy a proxy setup in order to operate in certain\nmarkets worldwide.\n\nThe [SRS Gateway test suite](#Test-Suite-StandardSRSGateway) requires\naccess to a primary registry system that is logically independent of the\nSRS Gateway system, and details of the primary registry system are\nrequired as input parameters. RSPs wishing to offer SRS gateway services\n**MUST** identify such a primary registry system, which **MUST** be\nindependent of the SRS gateway system, and MAY be operated by a third\nparty.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "SRS Gateway RSPs provide a proxy between a subset of Registrars and the\nRegistry. It uses a local cache to speed up EPP query commands, but forwards\nall EPP transform commands to the primary registry system. TLD registries\nneed to deploy a proxy setup in order to operate in certain markets\nworldwide.\n\nThe [SRS Gateway test suite](#Test-Suite-StandardSRSGateway) requires access\nto a primary registry system that is logically independent of the SRS\nGateway system, and details of the primary registry system are required as\ninput parameters.\n\nRSPs wishing to offer SRS gateway services **MUST** identify such a primary\nregistry system, which **MUST** be independent of the SRS gateway system,\nand **MAY** be operated by a third party.\n\n**Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "SRS Gateway RSP Evaluation Test", "Order" : "10", "Test-Suites" : [ @@ -4134,7 +4201,7 @@ ] }, "SRSGatewayTest" : { - "Description" : "An SRS Gateway service is a Shared Registry System implementation that\nacts as a proxy between a subset of Registrars and the Registry. It uses\na local cache to speed up EPP query commands, but forwards all EPP\ntransform commands to the primary registry system. TLD registries need to\ndeploy a proxy setup in order to operate in certain markets worldwide.\n\nThe purpose of an SRS Gateway Test is to verify that the Registry\nOperator’s proxy setup operates in accordance with the technical and\noperational criteria for EPP systems described in the gTLD Applicant\nGuidebook (AGB). Furthermore, it **MUST** keep its own database\nsynchronized with that of the TLD registry.\n\nThe SRS Gateway Test Change Test uses the SRS gateway test suite only.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "An SRS Gateway service is a Shared Registry System implementation that acts\nas a proxy between a subset of Registrars and the Registry. It uses a local\ncache to speed up EPP query commands, but forwards all EPP transform\ncommands to the primary registry system. TLD registries need to deploy a\nproxy setup in order to operate in certain markets worldwide.\n\nThe purpose of an SRS Gateway Test is to verify that the Registry Operator’s\nproxy setup operates in accordance with the technical and operational\ncriteria for EPP systems described in the gTLD Applicant Guidebook (AGB).\nFurthermore, it **MUST** keep its own database synchronized with that of the\nTLD registry.\n\nThe SRS Gateway Test Change Test uses the SRS gateway test suite only.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "SRS Gateway Test", "Order" : "6", "Test-Suites" : [ @@ -4151,7 +4218,7 @@ ] }, "StandardPreDelegationTest" : { - "Description" : "The purpose of the Pre-Delegation Test is to verify that the applicant has\nmet its commitment to establish registry operations in accordance with the\ntechnical and operational criteria described in the gTLD Applicant\nGuidebook (AGB). Each applicant will be required to complete PDT as a\nprerequisite to delegation into the root zone.\n\nThe Pre-Delegation Test covers all critical registry services and IDNs,\nand therefore uses all test suites.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "The purpose of the Pre-Delegation Test is to verify that the applicant has\nmet its commitment to establish registry operations in accordance with the\ntechnical and operational criteria described in the gTLD Applicant Guidebook\n(AGB). Each applicant will be required to complete PDT as a prerequisite to\ndelegation into the root zone.\n\nThe Pre-Delegation Test covers all critical registry services and IDNs, and\ntherefore uses all standard test suites.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "Pre-Delegation Test", "Order" : "1", "Test-Suites" : [ @@ -4165,7 +4232,7 @@ ] }, "StandardRSPChangeTest" : { - "Description" : "A Registry Operator may apply to ICANN to change a Material Subcontracting\nArrangement (MSA) and appoint a new Registry Services Provider. Before\nthis change can be approved, the new RSP **MUST** complete Registry System\nTesting to ensure their systems comply with the technical and operational\nrequirements of the Registry Agreement.\n\nThe RSP Change Test covers all critical registry services and IDNs, and\ntherefore uses all test suites.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", + "Description" : "A Registry Operator may apply to ICANN to change a Material Subcontracting\nArrangement (MSA) and appoint a new Registry Services Provider. Before\nthis change can be approved, the new RSP **MUST** complete Registry System\nTesting to ensure their systems comply with the technical and operational\nrequirements of the Registry Agreement.\n\nThe RSP Change Test covers all critical registry services and IDNs, and\ntherefore uses all test standard suites.\n\n**Note on test environment:** this is a \"business as usual\" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment.\n\n# Pass/fail criteria\n\nAs with all other [test plans](#test-plans), for this test to pass, **all** the listed test cases **MUST** pass: if **any** fail, then the test as a whole will fail.\n", "Name" : "RSP Change Test", "Order" : "2", "Test-Suites" : [ @@ -4181,13 +4248,21 @@ }, "Test-Suites" : { "DNSSECOperations" : { - "Description" : "This test suite verifies the ability of an RSP to carry out standard\nDNSSEC operational procedures while maintaining a chain of trust to the\nparent zone.\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", + "Description" : "This test suite verifies the ability of an RSP to carry out standard DNSSEC\noperational procedures while maintaining a chain of trust to the parent\nzone.\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", + "Errors" : [ + "DNSSEC_OPS_XFR_FAILED" + ], + "Input-Parameters" : [ + "dnssecOps.nameservers", + "dnssecOps.primaryServer", + "dnssecOps.tsigKey" + ], "Name" : "DNSSEC Operations", "Order" : "8", "Test-Cases" : "^dnssecOps" }, "MinimumRPMs" : { - "Description" : "This test suite verifies an RSP's support for the minimum Rights\nProtection Mechanisms (RPMs), and the Launch Extension (RFC 8334).\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", + "Description" : "This test suite verifies an RSP's support for the minimum Rights Protection\nMechanisms (RPMs), and the Launch Extension (RFC 8334).\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" : [ "epp.hostName", "epp.serverIssuedClientCertificate01", @@ -4225,7 +4300,7 @@ "Test-Cases" : "^dnssec-" }, "StandardEPP" : { - "Description" : "The EPP test suite validates the EPP service of the TLD or RSP. It\nverifies that the EPP server properly implements the query and transform\ncommands specified for domain names (and optionally host and contact\nobjects) and the mandatory extensions.\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", + "Description" : "The EPP test suite validates the EPP service of the TLD or RSP. It verifies\nthat the EPP server properly implements the query and transform commands\nspecified for domain names (and optionally host and contact objects) and the\nmandatory extensions.\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", "Errors" : [ "EPP_DNS_RESOLUTION_ERROR", "EPP_SERVICE_PORT_UNREACHABLE", @@ -4285,7 +4360,7 @@ "Test-Cases" : "^idn-" }, "StandardIntegrationTest" : { - "Description" : "This test suite verifies that the critical registry services of the TLD\nare properly integrated and functioning within the requirements of the\nService Level 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", + "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", "Name" : "Standard Integration Test", "Order" : "10", "Test-Cases" : "^integration-" @@ -4316,7 +4391,7 @@ "Test-Cases" : "^rde-" }, "StandardSRSGateway" : { - "Description" : "The SRS Gateway test suite validates the conformance of the Gateway\nregistry infrastructure of a TLD or RSP, and the synchronisation between\nprimary and gateway systems.\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", + "Description" : "The SRS Gateway test suite validates the conformance of the Gateway registry\ninfrastructure of a TLD or RSP, and the synchronisation between primary and\ngateway systems.\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", "Errors" : [ "EPP_DNS_RESOLUTION_ERROR", "EPP_SERVICE_PORT_UNREACHABLE", @@ -4369,5 +4444,5 @@ "Test-Cases" : "^srsgw-" } }, - "Version" : "3.0.244" + "Version" : "3.0.253" } diff --git a/rst-test-specs.yaml b/rst-test-specs.yaml index 55e13ff..01aac80 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.244 +Version: 3.0.253 Last-Updated: 2024-01-11 Contact: Name: GDS Technical Services @@ -209,18 +209,21 @@ Preamble: | interfaces are defined in [draft-lozano-icann-registry-interfaces](https://datatracker.ietf.org/doc/html/draft-lozano-icann-registry-interfaces). Test-Plans: + + + StandardPreDelegationTest: Order: 1 Name: Pre-Delegation Test Description: | The purpose of the Pre-Delegation Test is to verify that the applicant has met its commitment to establish registry operations in accordance with the - technical and operational criteria described in the gTLD Applicant - Guidebook (AGB). Each applicant will be required to complete PDT as a - prerequisite to delegation into the root zone. + technical and operational criteria described in the gTLD Applicant Guidebook + (AGB). Each applicant will be required to complete PDT as a prerequisite to + delegation into the root zone. - The Pre-Delegation Test covers all critical registry services and IDNs, - and therefore uses all test suites. + The Pre-Delegation Test covers all critical registry services and IDNs, and + therefore uses all standard test suites. **Note on test environment:** this is a "business as usual" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment. @@ -247,7 +250,7 @@ Test-Plans: requirements of the Registry Agreement. The RSP Change Test covers all critical registry services and IDNs, and - therefore uses all test suites. + therefore uses all test standard suites. **Note on test environment:** this is a "business as usual" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment. @@ -312,7 +315,7 @@ Test-Plans: Name: IDN Test (RSP Evaluation) Description: | This test plan is identical to the Standard IDN Test, but is intended - solely for use by the RSP evaluation program. + solely for use in the RSP evaluation program. **Note on test environment:** this is a "business as usual" test, designed to test a soon-to-be or already delegated TLD. Therefore, all input parameters provided **MUST** relate to the production registry environment. @@ -326,17 +329,17 @@ Test-Plans: Order: 6 Name: SRS Gateway Test Description: | - An SRS Gateway service is a Shared Registry System implementation that - acts as a proxy between a subset of Registrars and the Registry. It uses - a local cache to speed up EPP query commands, but forwards all EPP - transform commands to the primary registry system. TLD registries need to - deploy a proxy setup in order to operate in certain markets worldwide. + An SRS Gateway service is a Shared Registry System implementation that acts + as a proxy between a subset of Registrars and the Registry. It uses a local + cache to speed up EPP query commands, but forwards all EPP transform + commands to the primary registry system. TLD registries need to deploy a + proxy setup in order to operate in certain markets worldwide. - The purpose of an SRS Gateway Test is to verify that the Registry - Operator’s proxy setup operates in accordance with the technical and - operational criteria for EPP systems described in the gTLD Applicant - Guidebook (AGB). Furthermore, it **MUST** keep its own database - synchronized with that of the TLD registry. + The purpose of an SRS Gateway Test is to verify that the Registry Operator’s + proxy setup operates in accordance with the technical and operational + criteria for EPP systems described in the gTLD Applicant Guidebook (AGB). + Furthermore, it **MUST** keep its own database synchronized with that of the + TLD registry. The SRS Gateway Test Change Test uses the SRS gateway test suite only. @@ -353,9 +356,9 @@ Test-Plans: Order: 7 Name: Main RSP Evaluation Test Description: | - The Main RSP is responsible for the creation and maintenance of domain - name registrations in a Shared Registration System (SRS). This encompasses - the lifecycle of a domain name registration using domain registrars and + The Main RSP is responsible for the creation and maintenance of domain name + registrations in a Shared Registration System (SRS). This encompasses the + lifecycle of a domain name registration using domain registrars and protocols such as the Extensible Provisioning Protocol (EPP) and adherence to policies regarding the use and transparency domain name registrations through reporting, the Registration Data Access Protocol (RDAP), and other @@ -376,11 +379,11 @@ Test-Plans: Order: 8 Name: DNS RSP Evaluation Test Description: | - DNS RSPs provide primary or secondary authoritative DNS services. - Therefore, this test plan only covers the DNS area. + DNS RSPs provide primary or secondary authoritative DNS services. Therefore, + this test plan only covers the DNS area. - RSPs wishing to offer DNSSEC services in addition to authoritative DNS - will also be evaluated using the DNSSEC RSP Evaluation Test below. + RSPs wishing to offer DNSSEC services in addition to authoritative DNS will + also be evaluated using the DNSSEC RSP Evaluation Test below. **Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment. @@ -397,8 +400,8 @@ Test-Plans: DNSSEC RSPs provide signing of TLD zone files as a service. They do not provide primary or secondary authoritative DNS services. - RSPs wishing to offer DNSSEC services in addition to authoritative DNS - will also be evaluated using the DNSSEC RSP Evaluation Test below. + RSPs wishing to offer DNSSEC services in addition to authoritative DNS will + also be evaluated using the DNSSEC RSP Evaluation Test below. **Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment. @@ -412,18 +415,19 @@ Test-Plans: Name: SRS Gateway RSP Evaluation Test Description: | SRS Gateway RSPs provide a proxy between a subset of Registrars and the - Registry. It uses a local cache to speed up EPP query commands, but - forwards all EPP transform commands to the primary registry system. TLD - registries need to deploy a proxy setup in order to operate in certain - markets worldwide. - - The [SRS Gateway test suite](#Test-Suite-StandardSRSGateway) requires - access to a primary registry system that is logically independent of the - SRS Gateway system, and details of the primary registry system are - required as input parameters. RSPs wishing to offer SRS gateway services - **MUST** identify such a primary registry system, which **MUST** be - independent of the SRS gateway system, and MAY be operated by a third - party. + Registry. It uses a local cache to speed up EPP query commands, but forwards + all EPP transform commands to the primary registry system. TLD registries + need to deploy a proxy setup in order to operate in certain markets + worldwide. + + The [SRS Gateway test suite](#Test-Suite-StandardSRSGateway) requires access + to a primary registry system that is logically independent of the SRS + Gateway system, and details of the primary registry system are required as + input parameters. + + RSPs wishing to offer SRS gateway services **MUST** identify such a primary + registry system, which **MUST** be independent of the SRS gateway system, + and **MAY** be operated by a third party. **Note on test environment:** this test is designed to be used as part of the RSP evaluation program. Therefore, input parameters **MAY** be provided the relate to a test, staging or OT&E environment. @@ -435,6 +439,9 @@ Test-Plans: Test-Suites: + + + StandardDNS: Order: 1 Name: Authoritative DNS Service @@ -517,10 +524,10 @@ Test-Suites: Order: 4 Name: Extensible Provisioning Protocol (EPP) Description: | - The EPP test suite validates the EPP service of the TLD or RSP. It - verifies that the EPP server properly implements the query and transform - commands specified for domain names (and optionally host and contact - objects) and the mandatory extensions. + The EPP test suite validates the EPP service of the TLD or RSP. It verifies + that the EPP server properly implements the query and transform commands + specified for domain names (and optionally host and contact objects) and the + mandatory extensions. # Pass/fail criteria @@ -604,9 +611,9 @@ Test-Suites: Order: 7 Name: SRS Gateway Description: | - The SRS Gateway test suite validates the conformance of the Gateway - registry infrastructure of a TLD or RSP, and the synchronisation between - primary and gateway systems. + The SRS Gateway test suite validates the conformance of the Gateway registry + infrastructure of a TLD or RSP, and the synchronisation between primary and + gateway systems. # Pass/fail criteria @@ -661,21 +668,27 @@ Test-Suites: Order: 8 Name: DNSSEC Operations Description: | - This test suite verifies the ability of an RSP to carry out standard - DNSSEC operational procedures while maintaining a chain of trust to the - parent zone. + This test suite verifies the ability of an RSP to carry out standard DNSSEC + operational procedures while maintaining a chain of trust to the parent + zone. # Pass/fail criteria 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: ^dnssecOps + Input-Parameters: + - dnssecOps.nameservers + - dnssecOps.primaryServer + - dnssecOps.tsigKey + Errors: + - DNSSEC_OPS_XFR_FAILED MinimumRPMs: Order: 9 Name: Minimum Rights Protection Mechanisms (RPMs) Description: | - This test suite verifies an RSP's support for the minimum Rights - Protection Mechanisms (RPMs), and the Launch Extension (RFC 8334). + This test suite verifies an RSP's support for the minimum Rights Protection + Mechanisms (RPMs), and the Launch Extension (RFC 8334). # Pass/fail criteria @@ -697,9 +710,9 @@ Test-Suites: Order: 10 Name: Standard Integration Test Description: | - This test suite verifies that the critical registry services of the TLD - are properly integrated and functioning within the requirements of the - Service Level Agreement. + This test suite verifies that the critical registry services of the TLD are + properly integrated and functioning within the requirements of the Service + Level Agreement. # Pass/fail criteria @@ -3940,19 +3953,30 @@ Test-Cases: If the value of the `dnssecOps.csk` input parameter is `true`, then this test will be skipped. - The system will monitor the SOA record in the domain name specified in the - `dnssec.zskRolloverZone` input parameter. The domain may be present - anywhere in the DNS hierarchy (that is, it does not need to be a TLD), but - **MUST** have a secure chain of trust up to the root zone, so that it can - be validated using the root zone trust anchor. + The system will monitor the zone specified in the `dnssec.zskRolloverZone` + input parameter. The domain may be present anywhere in the DNS hierarchy + (that is, it does not need to be a TLD), but **MUST** have a secure chain of + trust up to the root zone, so that it can be validated using the root zone + trust anchor. + + The zone **MUST** contain at least 10,000 delegations, where a delegation is + considered to be one or more `NS` records with owner names that are below + the zone's origin. If NSEC3 is used for secure denial of existence, the + opt-out flag `MUST NOT` be set *(that is, an `RRSIG` record should be + present for all `NS` rrsets, irrespective of whether a corresponding `DS` + record is published)*. + + Monitoring will be carried out using `SOA` queries sent to multiple + validating DNS resolvers, and by validating the result of a a zone transfer + from the server specified in the `dnssecOps.primaryServer` input parameter. - During the test period (currently defined as 24 hours) the operator + During the test period (currently defined as 48 hours) the operator **MUST** successfully carry out a ZSK rollover for the domain, where the Zone Signing Key is replaced, without disrupting the chain of trust. - To simplify testing, applicants may wish to provision domain that is - configured with short TTLs and a short ZSK lifetime, so that a ZSK - rollover is guaranteed to occur within the 24 test period. + To simplify testing, applicants may wish to provision the zone such that it + is configured with short TTLs and a short ZSK lifetime, so that a ZSK + rollover is guaranteed to occur within the 48 test period. Input-Parameters: - dnssecOps.csk - dnssecOps.zskRolloverZone @@ -3968,13 +3992,24 @@ Test-Cases: RFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.2) for a zone. - The system will monitor the SOA record in the domain name specified in the - `dnssec.kskRolloverZone` input parameter. The domain may be present - anywhere in the DNS hierarchy (that is, it does not need to be a TLD), but - **MUST** have a secure chain of trust up to the root zone, so that it can - be validated using the root zone trust anchor. + The system will monitor the zone specified in the `dnssec.zskRolloverZone` + input parameter. The domain may be present anywhere in the DNS hierarchy + (that is, it does not need to be a TLD), but **MUST** have a secure chain of + trust up to the root zone, so that it can be validated using the root zone + trust anchor. - During the test period (currently defined as 24 hours) the operator + The zone **MUST** contain at least 10,000 delegations, where a delegation is + considered to be one or more `NS` records with owner names that are below + the zone's origin. If NSEC3 is used for secure denial of existence, the + opt-out flag `MUST NOT` be set *(that is, an `RRSIG` record should be + present for all `NS` rrsets, irrespective of whether a corresponding `DS` + record is published)*. + + Monitoring will be carried out using `SOA` queries sent to multiple + validating DNS resolvers, and by validating the result of a a zone transfer + from the server specified in the `dnssecOps.primaryServer` input parameter. + + During the test period (currently defined as 48 hours) the operator **MUST** successfully carry out a KSK rollover for the domain, where the Key Signing Key is replaced, and the DS record in the parent zone is updated, without disrupting the chain of trust. @@ -3992,13 +4027,24 @@ Test-Cases: RFC 6781](https://datatracker.ietf.org/doc/html/rfc6781#section-4.1.2) for a zone. - The system will monitor the SOA record in the domain name specified in the - `dnssec.algorithmRolloverZone` input parameter. The domain may be present - anywhere in the DNS hierarchy (that is, it does not need to be a TLD), but - **MUST** have a secure chain of trust up to the root zone, so that it can - be validated using the root zone trust anchor. + The system will monitor the zone specified in the `dnssec.zskRolloverZone` + input parameter. The domain may be present anywhere in the DNS hierarchy + (that is, it does not need to be a TLD), but **MUST** have a secure chain of + trust up to the root zone, so that it can be validated using the root zone + trust anchor. + + The zone **MUST** contain at least 10,000 delegations, where a delegation is + considered to be one or more `NS` records with owner names that are below + the zone's origin. If NSEC3 is used for secure denial of existence, the + opt-out flag `MUST NOT` be set *(that is, an `RRSIG` record should be + present for all `NS` rrsets, irrespective of whether a corresponding `DS` + record is published)*. - During the test period (currently defined as 72 hours) the operator + Monitoring will be carried out using `SOA` queries sent to multiple + validating DNS resolvers, and by validating the result of a a zone transfer + from the server specified in the `dnssecOps.primaryServer` input parameter. + + During the test period (currently defined as 48 hours) the operator **MUST** successfully carry out an algorithm rollover for the domain (including an update to the DS record in the parent zone), where the algorithm used to secure the domain is changed, without disrupting the @@ -4015,6 +4061,7 @@ Test-Cases: Errors: - DNSSEC_OPS_ALGORITHM_ROLLOVER_CHAIN_OF_TRUST_BROKEN - DNSSEC_OPS_ALGORITHM_ROLLOVER_NOT_COMPLETED + - DNSSEC_OPS_INVALID_ALGORITHM rde-01: Summary: validate deposit filename format Maturity: BETA @@ -4594,7 +4641,7 @@ Test-Cases: Summary: contact command test (if applicable for the registry type) Description: | This test will perform `` commands on the objects created during - `epp-24` and will confirm that the server accepts the `` command + `epp-22` and will confirm that the server accepts the `` command with a `1xxx` response code. If the `general.minimalPublicDataSet` input parameter is `true`, this @@ -4694,12 +4741,6 @@ Test-Cases: - EPP_HOST_UPDATE_INFO_RESPONSE_OBJECT_DOES_NOT_EXIST - EPP_HOST_UPDATE_INFO_RESPONSE_MISSING_OBJECT_PROPERTIES epp-14: - Summary: intentionally omitted - Description: intentionally omitted - epp-15: - Summary: intentionally omitted - Description: intentionally omitted - epp-16: Summary: domain command test Description: | This test performs a series domain `` commands, using pseudo- @@ -4773,7 +4814,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-17: + epp-15: Summary: Registry object integrity test Description: | This test confirms that the EPP server will refuse a request to delete a @@ -4784,18 +4825,18 @@ Test-Cases: will be skipped. The client will submit `` commands for any contact and host - objects created during `epp-16`. The server **MUST** respond with a `2305` + objects created during `epp-14`. The server **MUST** respond with a `2305` "Object association prohibits operation" error. Dependencies: - - epp-16 + - epp-14 Errors: - EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_CONTACT_OBJECT - EPP_INTEGRITY_SERVER_ACCEPTS_DELETE_FOR_LINKED_HOST_OBJECT - epp-18: + epp-16: 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-16`, including: + 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) @@ -4811,7 +4852,7 @@ Test-Cases: stored by the server. Input-Parameters: Dependencies: - - epp-16 + - epp-14 Errors: - EPP_DOMAIN_UPDATE_INFO_RESPONSE_UNEXPECTED_STATUS_CODE - EPP_DOMAIN_UPDATE_INFO_RESPONSE_MISSING_STATUS_CODE @@ -4823,12 +4864,12 @@ 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-18: + epp-16: 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 - `epp-16`. + `epp-14`. * Following a succesful `` command, the expiry date of the domain **MUST** have been increased by the period specified by the client; @@ -4840,21 +4881,21 @@ Test-Cases: commands to ensure that the expiry date and RGP status of the domain are set correctly. Dependencies: - - epp-16 + - epp-14 Errors: - EPP_RENEW_SERVER_ACCEPTS_INVALID_PERIOD - EPP_RENEW_SERVER_ACCEPTS_INVALID_CURRENT_EXPIRY_DATE - EPP_RENEW_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE - EPP_RENEW_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS - epp-19: + epp-17: Summary: domain command test Description: | This test will confirm that the client is able to initiate a domain transfer. The client will perform an `` command to set the authInfo code for - the test domain (taken from the set created in `epp-16`) to a + the test domain (taken from the set created in `epp-14`) to a randomly-determined value. If the server implements RFC 9154, it **MUST** reject the `` command if the authInfo code is insufficently secure. @@ -4890,7 +4931,7 @@ Test-Cases: This message **MUST** be received within 120 seconds of the transfer approval. Dependencies: - - epp-16 + - epp-14 Errors: - EPP_TRANSFER_SERVER_ACCEPTS_INSECURE_AUTHINFO - EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO @@ -4902,26 +4943,26 @@ Test-Cases: - EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS - EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET - epp-20: + epp-18: 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-19`, but the transfer request will + The 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. Dependencies: - - epp-16 + - epp-14 Errors: - EPP_TRANSFER_SERVER_PROCESSED_REJECTED_TRANSFER - epp-21: + epp-19: Summary: domain command test Description: | This test will perform `` commands on the objects created during - `epp-16` and will confirm that the server accepts the `` command + `epp-14` and will confirm that the server accepts the `` command with a `1xxx` response code. Once the `` commands have been processed, the client will perform @@ -4933,17 +4974,17 @@ Test-Cases: response, then the domain has the `pendingDelete` status and the `redemptionPeriod` RGP status. Dependencies: - - epp-16 + - epp-14 Errors: - EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS - EPP_DOMAIN_DELETE_INFO_RESPONSE_OBJECT_NOT_PENDING_DELETE - EPP_DOMAIN_DELETE_INFO_RESPONSE_RGP_STATUS_NOT_PENDING_DELETE - epp-22: + epp-20: Summary: domain restore test 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 + during `epp-19`, 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 @@ -4952,11 +4993,11 @@ Test-Cases: Input-Parameters: - epp.restoreReportRequired Dependencies: - - epp-21 + - epp-19 Errors: - EPP_RESTORE_DOMAIN_STILL_PENDINGDELETE - epp-23: + epp-21: Summary: host rename test (if applicable) Description: | This tests verifies the server's support for host rename operations. @@ -4978,14 +5019,14 @@ Test-Cases: by another registrar is rejected. The domain name(s) provided in the `epp.registeredNames` parameter will be used for this test. * an `` command which places the object within a domain sponsored - by the test client is accepted. A domain created during the `epp-16` + by the test client is accepted. A domain created during the `epp-14` test case will be used as the new parent domain. The client will then perform `` commands on the objects successfully updated, to confirm that the server has correctly stored the updated values. Dependencies: - - epp-16 + - epp-14 - epp-11 Errors: - EPP_HOST_RENAME_SERVER_ACCEPTS_INVALID_HOSTNAME @@ -4994,7 +5035,7 @@ Test-Cases: - EPP_HOST_RENAME_SERVER_ACCEPTS_RENAME_TO_ANOTHER_REGISTRARS_DOMAIN - EPP_HOST_RENAME_SERVER_UNEXPECTEDLY_REJECTS_RENAME - epp-24: + epp-22: Summary: host command test (if applicable) Description: | This test will perform `` commands on the objects created during @@ -5008,7 +5049,7 @@ Test-Cases: received from the server, the client will perform `` and `` commands to confirm that the objects have been deleted. Dependencies: - - epp-23 + - epp-21 Errors: - EPP_HOST_DELETE_INFO_RESPONSE_OBJECT_STILL_EXISTS rdap-01-domainCaseFoldingValidation: @@ -5016,163 +5057,190 @@ Test-Cases: Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-02-domainNameValidation: Summary: Domain Name validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-03-ipv4Validation: Summary: IPv4 address validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-04-ipv6Validation: Summary: IPv6 address validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-05-stdRdapAsEventActorValidation: Summary: asEventActor Validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-06-stdRdapConformanceValidation: Summary: RDAP Conformance validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-07-stdRdapDomainLookupValidation: Summary: Domain Lookup Validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-08-stdRdapEntitiesValidation: Summary: Entities validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-09-stdRdapEntityLookupValidation: Summary: Entity lookup validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-10-stdRdapErrorResponseBodyValidation: Summary: Error Response Body Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-11-stdRdapEventsValidation: Summary: Events Validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-12-stdRdapHelpValidation: Summary: Help validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-13-stdRdapIpAddressesValidation: Summary: IP Addresses Validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-14-stdRdapLanguageIdentifierValidation: Summary: Language Identifier Validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-15-stdRdapLdhNameValidation: Summary: LDH name Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-16-stdRdapLinksValidation: Summary: Links validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-17-stdRdapNameserverLookupValidation: Summary: Nameserver lookup validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-18-stdRdapNameserversSearchValidation: - Summary: RFC7159RDAP_RFCsNameservers search validation + Summary: Nameservers search validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-19-stdRdapNoticesRemarksValidation: Summary: Notices and Remarks Validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-20-stdRdapPort43WhoisServerValidation: Summary: Port 43 WHOIS Server Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-21-stdRdapPublicIdsValidation: Summary: Public IDs validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-22-stdRdapRolesValidation: Summary: Roles validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-23-stdRdapSecureDnsValidation: Summary: Secure DNS validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-24-stdRdapStatusValidation: Summary: Status validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-25-stdRdapUnicodeNameValidation: - Summary: RFC7159RDAP_RFCsIDNA_RFCsUnicode name + Summary: Unicode name Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-26-stdRdapVariantsValidation: Summary: Variants validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + rdap-27-webUriValidation: Summary: Web URI validation Maturity: GAMMA Description: | This test case comes from the RDAP Conformance Tool. For more information, see - . + . + minimumRPMs-01: Summary: Claims command test Description: | @@ -5722,14 +5790,14 @@ Test-Cases: the SLA. The test system will perform RDAP queries to confirm that the RDAP server - provides responses for the domains created in `epp-16`, and host objects + 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. Input-Parameters: - epp.hostModel - rdap.baseURLs Dependencies: - - epp-16 + - epp-14 - epp-11 Errors: - INTEGRATION_RDAP_REQUEST_FAILED @@ -5744,13 +5812,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-16`. All DNS + 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. Input-Parameters: - dns.nameservers Dependencies: - - epp-16 + - epp-14 Errors: - INTEGRATION_DNS_QUERY_FAILED - INTEGRATION_DOMAIN_NOT_PRESENT_IN_DNS @@ -5772,7 +5840,7 @@ 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-16` and `epp-11` (if applicable) tests + 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. @@ -5796,7 +5864,7 @@ Test-Cases: - integration.rdeSFTPUsername - integration.rriACL Dependencies: - - epp-16 + - epp-14 - epp-11 Errors: - INTEGRATION_RDE_SFTP_SERVER_UNREACHABLE @@ -5816,7 +5884,7 @@ Input-Parameters: Description: | The set of nameservers that will be authoritative for the TLD(s). - This input parameter is an array where the object properties are the + This input parameter is an object where the object properties are the TLD names, and the values are objects. For these objects, the properties are the nameserver names, and the values are arrays of IPv4 and IPv6 addresses. @@ -5846,6 +5914,52 @@ Input-Parameters: be at least one DS record for each TLD. Type: object Example: {"example":[{"keyTag":12345,"alg":8,"digestType":2,"digest":"E2D3...5766"}]} + dnssecOps.nameservers: + Description: | + The set of nameservers that will be authoritative for the zones used in the + DNSSEC operations test suite. + + This input parameter is an object where the object properties are the + zone names, and the values are objects. For these objects, the properties + are the nameserver names, and the values are arrays of IPv4 and IPv6 + addresses. + Type: object + Example: {"example":{"ns1.example.com":["192.168.53.1","2001:DB8::53:1"],"ns2.example.com":["192.168.53.2","2001:DB8::53:2"]}} + Schema: + type: object + patternProperties: + ^[a-z]+[a-z0-9\.]*[a-z]\$: + type: array + items: + type: string + format: + - ipv4 + - ipv6 + + dnssecOps.primaryServer: + Description: The primary nameserver from which zones can be transferred. + Type: string + Example: 192.168.53.1 + Schema: + type: string + format: + - ipv4 + - ipv6 + + dnssecOps.tsigKey: + Description: The TSIG key which should be used to perform zone transfers. + Type: object + Example: {"name": "rst-tsig-01", "algorithm": "hmac-sha256", "secret": "NQO...xQ="} + Schema: + type: object + properties: + name: + type: string + algorithm: + type: string + secret: + type: string + dnssecOps.csk: Description: | A boolean indicating whether the RSP uses a Combined Signing Key (CSK, @@ -5853,18 +5967,21 @@ Input-Parameters: KSK/ZSK configuration. Type: boolean Example: false + dnssecOps.zskRolloverZone: Description: | The domain name which will be monitored for the occurrence of a ZSK rollover. Type: string Example: example.com + dnssecOps.kskRolloverZone: Description: | The domain name which will be monitored for the occurrence of a KSK rollover. Type: string Example: example.com + dnssecOps.algorithmRolloverZone: Description: | The domain name which will be monitored for the occurrence of an algorithm @@ -7305,6 +7422,14 @@ Errors: DNSSEC_OPS_ZSK_ROLLOVER_NOT_COMPLETED: Severity: ERROR Description: TBA. + + DNSSEC_OPS_INVALID_ALGORITHM: + Severity: ERROR + Description: TBA. + + DNSSEC_OPS_XFR_FAILED: + Severity: ERROR + Description: TBA. RDE_CONTACT_HAS_INVALID_CC: Severity: ERROR Description: TBA.