avoid using the message queue in epp-19

Author: gbicann

ChangeLog.yaml

@@ -1,3 +1,8 @@
+2024-12-11:
+  - |
+    Updated [epp-19](#Test-Case-epp-19) to avoid the use of the EPP message
+    queue.
+
 2024-12-04:
   - Updated the format for test TLDs for RSP evaluation.
   - Fixed an issue with the HTML generator which resulted in boolean values

inc/epp/cases.yaml

@@ -894,25 +894,17 @@ epp-19:
     * the server accepts a `<transfer>` command with a valid authInfo code
       and period.
 
-    The client will use an `<info>` command to ensure that the
-    `pendingTransfer` status code is added to the domain after a successul
+    The client will use `<info>` commands to ensure that the `pendingTransfer`
+    status code is added to the domain within 120 seconds of a successul
     transfer request.
 
-    Once the transfer request has been accepted, the sponsoring client will
-    wait for a message to be received on the server's message queue, and will
-    then approve the transfer. This message **MUST** be received within 120
-    seconds of the transfer request.
+    The client will also use `<info>` commands to confirm that, within 120
+    seconds of a transfer being approved by the losing registrar:
 
-    Once the gaining registrar has also received a message on the queue, the
-    client will use an `<info>` command to confirm that:
-
-    * the domain is now under the sponsorship of the gaining registrar;
+    * the domain is under the sponsorship of the gaining registrar;
     * the authInfo code has been reset by the server (if the server supports
       [RFC 9154](https://www.rfc-editor.org/rfc/rfc9154.html));
     * the domain has the `transferPeriod` RGP status.
-
-    This message **MUST** be received within 120 seconds of the transfer
-    approval.
   Errors:
     - EPP_DNS_RESOLUTION_ERROR
     - EPP_SERVICE_PORT_UNREACHABLE
@@ -926,8 +918,6 @@ epp-19:
     - EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO
     - EPP_TRANSFER_SERVER_ACCEPTS_INVALID_PERIOD
     - EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_STATUS_CODE
-    - EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED
-    - EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED
     - EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE
     - EPP_TRANSFER_INFO_RESPONSE_MISSING_OR_INVALID_RGP_STATUS
     - EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET

inc/epp/errors.yaml

@@ -871,13 +871,6 @@ EPP_SERVICE_PORT_NOT_CONSISTENT:
     One or more `<info>` commands sent to the advertised EPP service ports
     resulted in inconsistent responses.
 
-EPP_TRANSFER_GAINING_REGISTRAR_NO_MESSAGE_RECEIVED:
-  Severity: ERROR
-  Description: |
-    Following a successful `<transfer op="approve">` command submitted by the
-    losing registrar of a transfer, the gaining registrar did not receive a
-    message on the EPP message queue within the deadline (120 seconds).
-
 EPP_TRANSFER_INFO_RESPONSE_AUTHINFO_NOT_RESET:
   Severity: ERROR
   Description: |
@@ -902,13 +895,6 @@ EPP_TRANSFER_INFO_RESPONSE_UNEXPECTED_EXPIRY_DATE:
     Following a successful domain transfer, a subsequent `<info>` response did
     not include the expected value of the `<exDate>` element.
 
-EPP_TRANSFER_LOSING_REGISTRAR_NO_MESSAGE_RECEIVED:
-  Severity: ERROR
-  Description: |
-    Following a successful `<transfer op="request">` command submitted by the
-    gaining registrar of a transfer, the losinng registrar did not receive a
-    message on the EPP message queue within the deadline (120 seconds).
-
 EPP_TRANSFER_SERVER_ACCEPTS_INCORRECT_AUTHINFO:
   Severity: ERROR
   Description: |