[Tsv-art] Tsvart last call review of draft-ietf-httpbis-cdn-loop-01

Colin Perkins <csp@csperkins.org> Thu, 06 December 2018 14:50 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
To: tsv-art@ietf.org
Cc: draft-ietf-httpbis-cdn-loop.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154410785082.3495.12752667499926726690@ietfa.amsl.com>
Date: Thu, 06 Dec 2018 06:50:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/V6mauomiEEa6FRPc7jBcQXqDXlU>
Subject: [Tsv-art] Tsvart last call review of draft-ietf-httpbis-cdn-loop-01

Reviewer: Colin Perkins
Review result: Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

I have reviewed draft-ietf-httpbis-cdn-loop-01. It defines a new HTTP header
that can be used to detect CDN forwarding loops. There are no apparent
transport issues. 

Editorial: The terminology 'The CDN-Loop Request Header' can easily be
misread to suggest that the CDN is being requested to loop traffic. Using
instead 'The "CDN-Loop" Request Header' might make this clearer.

Colin

[Tsv-art] Tsvart last call review of draft-ietf-h… Colin Perkins