Re: [CDNi] Opsdir last call review of draft-ietf-cdni-request-routing-extensions-05
Ori Finkelman <orifinkelman@gmail.com> Thu, 22 August 2019 09:40 UTC
Return-Path: <orifinkelman@gmail.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAF91200B7; Thu, 22 Aug 2019 02:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6IgPAX5eifm2; Thu, 22 Aug 2019 02:40:04 -0700 (PDT)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ECFB1200B2; Thu, 22 Aug 2019 02:40:04 -0700 (PDT)
Received: by mail-ua1-x92f.google.com with SMTP id m23so1761202uaq.11; Thu, 22 Aug 2019 02:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ErSS8Uz+AnGdrK0+Cgx/g+iiS3VRLyrk9b5yaq+5jEU=; b=RGfegXxuYr6n9NRF8u4jGqqMHIZ3JvQ2quv+D8GycvHehx8fDqCjWDcoDS2RznFlWa zf+1veF6z44h1B8PT3DDFv5/fE6X/gVwqmdKWakkMYHpM5TNFpOPGk4gEn/nWMoNw7qy Vm3JNkceEnnK0kN4OPMeZvwE6RWupAr0WmXs8yjasjUoQL2tEfRpzf0WC2cpM0Mt8yyi S3Wj2Gp0xct61LKbUxhyOJ+HaWJrPY1zvGoH1mldfxI/98WftPHTMMvBy3pvhVwLS1b1 eELceFTf6LoyKy+v+x08b4Vgh0PkMlCuTyS+rcs27OO+lEZSpC/l5MfGIwdlWmv+Pq+H b3AA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ErSS8Uz+AnGdrK0+Cgx/g+iiS3VRLyrk9b5yaq+5jEU=; b=NqN2p+0X9JChX4C0yHeOuyJirb7r99AVRjX+GAxClP8rTX0AqC1itSjOCeZ0WKCOZF weztFF1agnslv+k9lwhnNXwRUMfn670LXiijgCgl2x2u9LOHYQ+YscLE6nZ0XpRPPhXY nWBKXP14Nr6uuLZR0t5edzkDYyCO01coZ+zC8uv2Sql7haNT16hUW20Hnf2M/fUgus0F 1xwVh3/vbs2G9pS1cD8VVC+p1v95U5K2eeLQzafJ8zsCb7Er3igMquizrrhrINkPV2AD S0ExmePyom7V2quMAKVuc0t2sOVTBNUWLgrTHyLwdzauRIWA0gMR6BEzhPJBbdmat4C6 7WhA==
X-Gm-Message-State: APjAAAX7zYBcL/I3f9MdJ8D2XsfERxXjn2xLTMfN/gof3JauLPeoMv2g +SV8d70hZHSbLifwvr0n07rbWxNnL3VHbt/8tuk=
X-Google-Smtp-Source: APXvYqzTnSdS3G1f5GJYY3YYQ1R5s5W0sXatmDz0ahcGEwNIJx7iUj51WWgUtYlLVxcXxUBv9cpBWmxdbjuzYIIcw68=
X-Received: by 2002:ab0:6883:: with SMTP id t3mr5329890uar.104.1566466802977; Thu, 22 Aug 2019 02:40:02 -0700 (PDT)
MIME-Version: 1.0
References: <156628451754.370.12072038967357761358@ietfa.amsl.com>
In-Reply-To: <156628451754.370.12072038967357761358@ietfa.amsl.com>
From: Ori Finkelman <orifinkelman@gmail.com>
Date: Thu, 22 Aug 2019 12:39:50 +0300
Message-ID: <CAM8emGW1P7NS91rj_-t+s6R3kuNdu0DzZPh6ZzcCsg4yqb3dsw@mail.gmail.com>
To: Zitao Wang <wangzitao@huawei.com>
Cc: ops-dir@ietf.org, draft-ietf-cdni-request-routing-extensions.all@ietf.org, ietf@ietf.org, cdni@ietf.org
Content-Type: multipart/alternative; boundary="000000000000580ff50590b17987"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/lLtHQgvpOzmw1V1t6_INLWpUweA>
Subject: Re: [CDNi] Opsdir last call review of draft-ietf-cdni-request-routing-extensions-05
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Thu, 22 Aug 2019 09:40:07 -0000
Hi, Thanks a lot for your time and for the comments. I will fix them for the next revision. Best regards, Ori On Tue, Aug 20, 2019, 10:02 Zitao Wang via Datatracker <noreply@ietf.org> wrote: > Reviewer: Zitao Wang > Review result: Has Issues > > I have reviewed this document as part of the Operational directorate’s > ongoing > effort to review all IETF documents being processed by the IESG. These > comments were written with the intent of improving the operational aspects > of > the IETF drafts. Comments that are not addressed in last call may be > included > in AD reviews during the IESG review. Document editors and WG chairs > should > treat these comments just like any other last call comments. > > Summary: > The Open Caching working group of the Streaming Video Alliance is focused > on > the delegation of video delivery requests from commercial CDNs to a caching > layer at the ISP. In that aspect, Open Caching is a specific use case of > CDNI, > where the commercial CDN is the upstream CDN (uCDN) and the ISP caching > layer > is the downstream CDN (dCDN). The extensions specified in this document to > the > CDNI Metadata and FCI interfaces are derived from requirements raised by > Open > Caching but are applicable to CDNI use cases in general. > > The document is well written, easy to read, and technically I have no > issues. > However, as shown below, I do have some questions for clarifications. > > Major issues: None > > Minor issues: > #1: There are a lot of abbreviations that are not provided with > explanations or > citations, such as uCDN, dCDN, CFI, etc. > > #2: The example of of a Redirect Target capability object serialization, > is it > encoded as json? Please present its encoding format. > > #3: In section 2.1, the "Mandatory-to-Specify" attributes of dns-target and > http-target, it describes that "No, but at least one of dns-target or > http-target MUST be present and non-empty." I wonder whether there should > be a > detection mechanism. For example, if the requirements are not met, an error > message will be returned. And if there are existing mechanisms, please > briefly > introduce them. > > Best Regards! > -Michael > >
- [CDNi] Opsdir last call review of draft-ietf-cdni… Zitao Wang via Datatracker
- Re: [CDNi] Opsdir last call review of draft-ietf-… Ori Finkelman