(as an aside) Some of this timed & controlled distribution (by the content originator) should be possible using IETF Content Delivery Network Interconnection (CDNI) standards - see https://datatracker.ietf.org/wg/cdni/documents/. The initial RFC 6707 provides some background - https://www.rfc-editor.org/rfc/rfc6707. But I think folks are correct that the issue may be more that a given gaming device was turned off at night (though no reason that device could not pre-cache the content from the source). In any case, there should be a better way to address this. The Internet will see more and more of these downloads and smoothing the impact out seems prudent for all involved. Jason On 2/12/20, 11:59 AM, "NANOG on behalf of Chris Adams" <nanog-bounces@nanog.org on behalf of cma@cmadams.net> wrote: I think security is probably the sticking point for this. Content owners don't want anybody having direct access to their files, and as more content is distributed over HTTPS, content distributors don't wany anbody having access to their certificates. -- Chris Adams <cma@cmadams.net>