VKCW.NET

An RRI proposal for the specification of a 72-hour expiration time for routine messages, after which the routine message must be delivered or serviced back, is in agreement with a similar policy already mooted at CWB and thus is to be adopted henceforth.

Any (R)outine message that is not delivered after 48 hours (2 days) should have a final delivery attempt, and if failing, by latest 72 hours (3 days) a SVC MSG should be sent back to the originating station notifying of non-delivery of the QTC.

(B)ulk messages should not be serviced back but simply left undelivered and no further attempts should be made for delivery after 72 hours from time of origin.

Discussions were held regarding international QTC as to whether the same time limit should apply.
The consensus is that yes, unless specified otherwise in the message or PBL, for example with an HXB designator (see HX Handling Codes) which we can modify from hours to days or weeks e.g. HXB 10D would mean 10 days, HXB 2W would mean 2 weeks), then the same 2-3 day expiration time will apply.
For the purpose of testing CW circuits that are once weekly, messages may be held for longer, if it is clear the message is intended to be used for the testing of that circuit, or if an extended HXB code is present.
Otherwise, messages intended for insertion in a CW net that is once weekly (e.g. currently the AUS-USA CWB-RRI CW Circuit), should be originated not long before the net, to be within the 2-3 day expiry limit.
In all other cases and under normal circumstances, the delivery of QTC by ANY means should occur without delay, and according to Precedence priority indicator. For example, insertion into Email, Winlink, or DTN as appropriate or as determined by the forwarding station. It should normally be possible to have a QTC arrive around the world within 2 days without being restricted to a particular mode, or method of delivery.