Hi, I’m assessing feasibility before implementing a small macOS HTTPS snapshot client.
The requirement is strict: every request-bearing byte must cross the final controlled network-egress boundary before an absolute deadline. A byte crossing at or after the deadline fails. For context, the intended deadline is 07:41:00 Europe/London on a specified date, converted to UTC.
This concerns request transmission, not response completion. An application precheck or a deadline to begin sending would not satisfy it.
Is there a supported macOS API or mechanism with a documented guarantee covering this requirement?
Specifically:
- Where is the enforcement boundary? Does expiry cover request bytes already queued in TLS/TCP, kernel, driver or NIC buffers, partially transmitted requests, and retransmitted request payload?
- Does enforcement remain fail-closed if the client or enforcement process is suspended, hangs or crashes, or the Mac sleeps and wakes? Can queued bytes resume transmission after expiry?
- What clock and deadline semantics apply, including equality, uncertainty, clock steps/regression and unavailable or unreliable time?
- Can connection reuse or buffering bypass expiry? Application retries, redirects and additional requests would be prohibited.
- How could an implementation observe and qualify the actual controlled egress boundary, rather than an earlier callback or queue?
I have reviewed documentation for:
- NWConnection.ContentContext.expirationMilliseconds, which describes expiry for beginning transmission;
- NWConnection.SendCompletion.contentProcessed;
- Network Extension packet filtering, delayed-packet verdicts and provider lifecycle;
- TN3134 and TN3165.
I have not found a documented end-to-end guarantee covering the cases above. I am not assuming that filters, cancellation, timers or socket timeouts provide it.
Could an Apple engineer point to the applicable supported contract and platform restrictions, or clarify that this strict guarantee is not provided? If a mechanism is applicable, please identify supported macOS versions, required entitlements and any relevant interface or hardware limitations.
This is a documentation/feasibility question only. No external service, account, credentials or capture is involved. An authoritative reference—or an explicit statement of unsupported cases—would be helpful. Many thanks in advance.