Re: New Version Notification for draft-cdn-loop-prevention-00.txt

Thanks Mark.

 

Should this specification be specifically named and emphasised on CDNs exclusively? I would think that many web services with more than 1 tier of load balancing/traffic routing have also shot themselves in the foot at least once with traffic looping.

 

From: Mark Nottingham <mnot@mnot.net>
Date: Monday, 2 July 2018 at 08:04
To: HTTP Working Group <ietf-http-wg@w3.org>
Cc: "Ludin, Stephen" <sludin@akamai.com>, Nick Sullivan <nick@cloudflare.com>
Subject: Fwd: New Version Notification for draft-cdn-loop-prevention-00.txt
Resent-From: <ietf-http-wg@w3.org>
Resent-Date: Mon, 02 Jul 2018 07:00:48 +0000

 

(Co-author hat on)

 

For interest / discussion. This is a proposal for a minimal mechanism to avoid loop attacks and misconfigurations against CDNs. Feedback appreciated.

 

Cheers,

 



Begin forwarded message:

 

From: internet-drafts@ietf.org

Subject: New Version Notification for draft-cdn-loop-prevention-00.txt

Date: 27 June 2018 at 2:12:46 pm AEST

To: "Stephen Ludin" <sludin@akamai.com>, "Mark Nottingham" <mnot@fastly.com>, "Nick Sullivan" <nick@cloudflare.com>

 


A new version of I-D, draft-cdn-loop-prevention-00.txt
has been successfully submitted by Mark Nottingham and posted to the
IETF repository.

Name:                  draft-cdn-loop-prevention
Revision:              00
Title:                      CDN Loop Prevention
Document date:               2018-06-27
Group:                  Individual Submission
Pages:                   5
URL:            https://www.ietf.org/internet-drafts/draft-cdn-loop-prevention-00.txt
Status:         https://datatracker.ietf.org/doc/draft-cdn-loop-prevention/
Htmlized:       https://tools.ietf.org/html/draft-cdn-loop-prevention-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-cdn-loop-prevention


Abstract:
  This specification defines the CDN-Loop request header field for
  HTTP.

 

--
Mark Nottingham   https://www.mnot.net/