[CDNi] Éric Vyncke's No Objection on draft-ietf-cdni-request-routing-extensions-07: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 14 October 2019 07:47 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: cdni@ietf.org
Delivered-To: cdni@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D4112010C; Mon, 14 Oct 2019 00:47:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-cdni-request-routing-extensions@ietf.org, Kevin Ma <kevin.j.ma.ietf@gmail.com>, cdni-chairs@ietf.org, kevin.j.ma.ietf@gmail.com, cdni@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <157103923374.24668.472430642187497462.idtracker@ietfa.amsl.com>
Date: Mon, 14 Oct 2019 00:47:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/YJPnnFfTbx5w1BJVQ4QB_0c_u7U>
Subject: [CDNi] Éric Vyncke's No Objection on draft-ietf-cdni-request-routing-extensions-07: (with COMMENT)
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2019 07:47:14 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-cdni-request-routing-extensions-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-cdni-request-routing-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document. I have a couple of comments and
nits.

Regards,

-éric

== COMMENTS ==

One generic suggestion (no need to act on a COMMENT): add the definition of
"router" in this document as it is not the typical IP-layer router as in most
IETF documents.

-- Section 2.3 --
It is unclear to me whether the 3xx redirection (cfr last example) can switch
from HTTP to HTTPS or vice-versa? Should the 'httptarget' include the
scheme/protocol to be used ? In any case, the text should be clear whether the
scheme is kept between original request and the scheme in the redirected
location. Or is it specify in the OpenCache spec ?

== NITS ==

-- Abstract --
Please expand FCI at first use.

-- Requirements language --
Unusual place in the document. It will be fixed by the RFC Editor probably
later in the process.

-- Section 2 --
s/defintion/definition/, I will stop looking for typos, easier to use a spell
checker ;)