Re: [alto] [E] [CDNi] WGLC for draft-ietf-alto-cdni-request-routing-alto-09

"Y. Richard Yang" <yry@cs.yale.edu> Mon, 24 February 2020 05:58 UTC

Return-Path: <yang.r.yang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 006B53A08D9; Sun, 23 Feb 2020 21:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 RhjkDqwABlsA; Sun, 23 Feb 2020 21:58:37 -0800 (PST)
Received: from mail-ua1-f52.google.com (mail-ua1-f52.google.com [209.85.222.52]) (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 041C73A08D7; Sun, 23 Feb 2020 21:58:36 -0800 (PST)
Received: by mail-ua1-f52.google.com with SMTP id g13so2811941uab.7; Sun, 23 Feb 2020 21:58:36 -0800 (PST)
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=H4pc0TLCSrYi3jjkk6VY+Aoq+e+1BhvGaAQHNlzigrA=; b=HQJs44D7JIYLD1WOgnE4U/71CKU6Sl/Juk4iaCnzsx14BXoEA/Qlf6DX5CSQno6ddD uuBOiah9cj70KLihdeEWzoZe2NLR9F+/hajTt6egw8CZBavajfsw9Ji4fH0qyTNGN6At dRXobRYtfeU5eAKjnn5FIGtqElchqcMv866KELdlXWr7fOWQC7DxnrApZytxLjMyFlbH evDisnLHdbTrjO4EyxqzbOgUm2S+UDpRJJ2mcT0+YYzC9dsfW70nxWTIzr0lpbTF3xqx oqTApvEkVxfrNhArQRPbIdAmGG+xPc+Pl1dnHcHVIwyafN+X9L0wy1R468xxVdxrDPYo MYZQ==
X-Gm-Message-State: APjAAAV8WD0q0SRjooINh/xuqDQ1r7uiVtbMfPkp0gIkDw4iKlTExIUK BKbLwoSW90GXy5Yk4R7U2ZhHU37Au3ff1sB6ZpnG/g==
X-Google-Smtp-Source: APXvYqwOkrTKmJhqYy26NR+5FpMqmIFxyQW2n3mTkHWwzMZG0O08UPw8tX2VHRnWDx07u0RKccFw/FZPd3ywzAHxTw4=
X-Received: by 2002:a9f:23ca:: with SMTP id 68mr23555496uao.128.1582523915793; Sun, 23 Feb 2020 21:58:35 -0800 (PST)
MIME-Version: 1.0
References: <CAMMTW_Li0KE-vBUUy0fULxyCVfpjU=UugPzqbgvzva59j_2Pgg@mail.gmail.com> <6a9f3fdc0d774acdb7f0e0ad60806fab@tbwexch02apd.uswin.ad.vzwcorp.com>
In-Reply-To: <6a9f3fdc0d774acdb7f0e0ad60806fab@tbwexch02apd.uswin.ad.vzwcorp.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 24 Feb 2020 00:58:25 -0500
Message-ID: <CANUuoLpY6CFEHtue5U1DmW51LiLiUyLfB1ZrgTSGozAd5vD4BA@mail.gmail.com>
To: sanjay.mishra=40verizon.com@dmarc.ietf.org
Cc: IETF ALTO <alto@ietf.org>, "cdni@ietf.org" <cdni@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d97d7a059f4c0f60"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/MR5Ae_cIwtZYFEE6qdzQ2yjmlOo>
Subject: Re: [alto] [E] [CDNi] WGLC for draft-ietf-alto-cdni-request-routing-alto-09
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2020 05:58:39 -0000

Dear Sanjay,

Thank you so much for the careful review! We will follow the suggestions
and take a pass. In particular, we will enumerate a few examples of error
handling as suggested. We will post a new version by Tuesday.

Richard

On Wed, Feb 19, 2020 at 6:12 PM <sanjay.mishra=40verizon.com@dmarc.ietf.org>
wrote:

> I have review draft-ietf-alto-cdni-request-routing-alto-09 and don’t have
> any issues except some minor suggestions and nits.
>
>
>
> *Sec 1 Introduction:*
>
> 1.       If by using “functionalities” below is meant to reference the
> two RFC (RFC 7975 & RFC 8008), semantically, it may be better to state that
> the request routing interface is covered in two separate RFCs and reference
> the two RFC by name and number.
>
> a.       Correspondingly, the request routing interface is broadly
> divided into two functionalities: (1) CDNI Footprint & Capabilities
> Advertisement interface (FCI), and (2) CDNI Request Routing Redirection
> interface (RI).
>
>
>
> 2.       (replace is -> are)
>
> a.       A protocol to transport and update such objects between a uCDN
> and a dCDN, however, is not defined
>
> 3.       (delete “some”)
>
> b.      In this way, a uCDN can effectively fetch capabilities of some
> footprints in which it is interested
>
> 4.       (add “as defined” instead of “defined” in two places in the
> sentence starting as below)
>
> c.       Throughout this document, we use the terminologies for CDNI
> defined…
>
>
>
> *Section 2.1:*
>
> 5.       (replace “For a detailed discussions” with “For detailed
> information…” )
>
> d.      For a detailed discussion, the reader is referred to the RFCs.
>
> 6.       Remove extra sub bullet at the end of section 2.1 since there is
> no text (check the document for other instances of bullet but no text).
>
>
>
> *Section 2.2:*
>
> 7.       Remove reference to I-D.jenkins-alto-cdn-use-cases
>
> 8.       Replace (“Identifications -> Identification): Security:
> Identifications between uCDNs and dCDNs are extremely important
>
> 9.       Can an example be added of what unexpected cases authors
> envision?
>
> a.       Error-handling: The ALTO protocol has undergone extensive
> revisions in order to provide sophisticated error-handling, in particular
> regarding unexpected cases
>
> *Section 6:*
>
> 10.   Re-word (“First, we describe how to represent”)
>
> a.       We firstly describe how to represent
>
> 11.   Replace (“And then” with “Second”)
>
>
>
> *Section 8:*
>
> 12.   Add a colon  after follows
>
> a.       included as follows.
>
> 13.   Needs some rewording for the sentence below:
>
> a.       For availability of ALTO services, an attacker may get the
> potential huge full CDNI
>
>
>
> Thanks
>
> Sanjay
>
>
>
> *From:* CDNi [mailto:cdni-bounces@ietf.org] *On Behalf Of *Vijay Gurbani
> *Sent:* Monday, February 3, 2020 10:08 AM
> *To:* IETF ALTO <alto@ietf.org>rg>; cdni@ietf.org
> *Subject:* [E] [CDNi] WGLC for
> draft-ietf-alto-cdni-request-routing-alto-09
>
>
>
> All: Jan and I will like to start WGLC for
> draft-ietf-cdni-request-routing-alto-09.  The WGLC period will run from
> Mon,
> Feb 3 2020 to Wed, Feb 19 2020.
>
> This email is also being cross-posted to the CDNI working group.
>
> We will like to have one WG list member from ALTO and one WG list member
> from
>
> CDNI review this draft in depth.  Please send Jan and me an email if you
> are willing
>
> review the draft as part of WGLC.
>
>
>
> In addition, we will like general reviews of the draft from both ALTO and
> CDNI WGs.
>
>
>
> Thank you.
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
-- 
Richard