RFC 8586 on Loop Detection in Content Delivery Networks (CDNs)
rfc-editor@rfc-editor.org Wed, 24 April 2019 16:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A611201E5 for <ietf-announce@ietfa.amsl.com>; Wed, 24 Apr 2019 09:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QELS5e-gGfft for <ietf-announce@ietfa.amsl.com>; Wed, 24 Apr 2019 09:13:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9390D12001B for <ietf-announce@ietf.org>; Wed, 24 Apr 2019 09:13:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D615B80E49; Wed, 24 Apr 2019 09:13:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8586 on Loop Detection in Content Delivery Networks (CDNs)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190424161303.0D615B80E49@rfc-editor.org>
Date: Wed, 24 Apr 2019 09:13:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/WbQX0QGY3hJVXtDxSykhOYLLuJk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 16:13:12 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8586 Title: Loop Detection in Content Delivery Networks (CDNs) Author: S. Ludin, M. Nottingham, N. Sullivan Status: Standards Track Stream: IETF Date: April 2019 Mailbox: sludin@akamai.com, mnot@fastly.com, nick@cloudflare.com Pages: 6 Characters: 12560 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-httpbis-cdn-loop-02.txt URL: https://www.rfc-editor.org/info/rfc8586 DOI: 10.17487/RFC8586 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. This document is a product of the Hypertext Transfer Protocol Bis Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC