[CDNi] Roman Danyliw's No Objection on draft-ietf-cdni-additional-footprint-types-07: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Fri, 30 December 2022 22:03 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 F28DEC1516E2; Fri, 30 Dec 2022 14:03:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-cdni-additional-footprint-types@ietf.org, cdni-chairs@ietf.org, cdni@ietf.org, kevin.j.ma.ietf@gmail.com, kevin.j.ma.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <167243781398.15862.2641090676647478462@ietfa.amsl.com>
Date: Fri, 30 Dec 2022 14:03:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/cuVZjYLW2bfyzCaWL6Hi1rDu6ZQ>
Subject: [CDNi] Roman Danyliw's No Objection on draft-ietf-cdni-additional-footprint-types-07: (with COMMENT)
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 30 Dec 2022 22:03:34 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-cdni-additional-footprint-types-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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-cdni-additional-footprint-types/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Daniel Migault for the SECDIR review. ** Section 2.1.1.1. Editorial. An [ISO3166-2] code in lowercase. Each code consists of two parts separated by a hyphen. The first part is the [ISO3166-1] code of the country. The second part is a string of up to three alphanumeric characters. ISO3166-2 already defines the format. To make that clear, consider s/The first part is/Per [ISO3166-2], the first part is/ ** Section 2.2. Typo. “syntextual restrication”. I’m not sure what to replace both of these words with. Is it “syntactic restriction”? ** Section 5. Editorial. More specifically, the use of "subdivisioncode" footprint type, introduces a higher level of granularity into the published dCDN Footprint. Therefore, to meet confidentiality requirements ... It does not follow for my why a more specific sub-division code (sentence one) suggests confidentiality requirements (sentence two). ** Section 5. In describing the CDNI Metadata Objective Model, Section 3 of RFC8006 hints at the uCDN expressing geo-blocking rules. In addition to the intended use cases suggested in Section 1 of this document, is this higher resolution geographic metadata going to provide primitives that can express more selective filtering of content in the boundaries of a country? While this dual use may not avoidable, should this be acknowledged?
- [CDNi] Roman Danyliw's No Objection on draft-ietf… Roman Danyliw via Datatracker
- Re: [CDNi] Roman Danyliw's No Objection on draft-… Nir Sopher