Loop Detection in Content Delivery Networks
RFC 8586, “Loop Detection in Content Delivery Networks”, is a Proposed Standard document published in April 2019 by S. Ludin, M. Nottingham, N. Sullivan. The canonical text is published by the RFC Editor.
Abstract
This document defines the CDN-Loop request header field for HTTP. CDN-Loop addresses an operational need that occurs when an HTTP request is intentionally forwarded between Content Delivery Networks (CDNs), but is then accidentally or maliciously re-routed back into the original CDN causing a non-terminating loop. The new header field can be used to identify the error and terminate the loop.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8586 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8585 Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a- Service
- RFC 8587 NFS Version 4.0 Trunking Update
- RFC 8584 Framework for Ethernet VPN Designated Forwarder Election Extensibility
- RFC 8588 Personal Assertion Token Extension for Signature-based Handling of Asserted information using toKENs
- RFC 8583 Diameter Load Information Conveyance
- RFC 8589 The 'leaptofrogans' URI Scheme
- RFC 8582 Diameter Overload Rate Control
- RFC 8590 Change Poll Extension for the Extensible Provisioning Protocol