Re: [alto] Some questions for alto-cdni-request-routing

Shenshen Chen <shenshen.chen.tj@gmail.com> Sun, 03 December 2017 10:13 UTC

Return-Path: <shenshen.chen.tj@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 7044D1250B8; Sun, 3 Dec 2017 02:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 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, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_MIME_MALF=0.01] 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 C29_llkndi0O; Sun, 3 Dec 2017 02:13:53 -0800 (PST)
Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (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 49374124207; Sun, 3 Dec 2017 02:13:52 -0800 (PST)
Received: by mail-lf0-x243.google.com with SMTP id r143so15995750lfe.13; Sun, 03 Dec 2017 02:13:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nCcYo8d1C4OAZ0xwXZ4NIbzck8WH04YhZmGVV66vJeU=; b=EIs4ARuNCP47Rol5R2NSODUwTDRNJk0XrP321RJsHLNQ/xAMwyw7S5xdQN4dM29i9C 91bK2eXeKrvoup54yAb+Pao9X9nkciT+UZmSJW93vVBTkNYpmyCjgf828B6nNB9Mhxnt iHdOyXCW49MqacLlBMexTj1137QZ3sau2W1ldiYzDGWnOiDxJoWcbYHW2N2RETvcBXQU 6N1a8ECWE2/NAY+qhX2frM02ISJ+vV+FQEfBKQiRNYQi02NAbGQ2YDzZH6cxYK7JURqN l1yD9+iIKYQzyeNjPE7C4E4FM0Uw/zUCcy0/3LMDuHxNnq/yThUAmlUkd3Ek6SExVW2u xBbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nCcYo8d1C4OAZ0xwXZ4NIbzck8WH04YhZmGVV66vJeU=; b=PUU2lAfG8/X0yKcoTxJElTc2jbz+nI4UcLaMPPFySKVR+KKzwPP8sw4HvvCF2vGq2B HHrY9exRgPoQvpDZkYnO1KSr1xLC+VjXSK+78Tmnmf5+uT4CoSqTjT90lmHmcvSjey6V 6AEKLbajR0bYzpNSlcj1Od68KQO2KZBtCTC7mNAnx2NjbLwJ3rmzJmIbabQJSDdfVSxy ljGtHfoET6ZerWBA1A9DNNLuU0Fkd4tXSfyvEDyPeSP3uVnxs7SWjciyzGIuacJIJHL3 zsNrUuDSJNklm03uJu54iDYfeKQUC2gGCrACeEUKMUQhukto2WkWRzczO9io01oWppMK qoVQ==
X-Gm-Message-State: AJaThX4cUpRz0Jds8si6MNPwWm3EUFsZPW3etpzeKmrX3mKaDY2xTUl7 CEepSLW2SgPVHYE4lgfTLsj+oqP/a7Dz5MPQKWhK6Si7
X-Google-Smtp-Source: AGs4zMYtFUl7qgDHEg9zCch5CjkuLhycg1f6tEddCX4IO+Max0/XNngSrso81GOrrmmKuAfAEn53jxscC/00lQ/iptM=
X-Received: by 10.46.43.65 with SMTP id q62mr7487000lje.56.1512296030325; Sun, 03 Dec 2017 02:13:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.201.19 with HTTP; Sun, 3 Dec 2017 02:13:49 -0800 (PST)
In-Reply-To: <CA+oaSDrNSEWbRF0s5T_M19fFGwPUFTif_iZxa0tpETrnd6yqyA@mail.gmail.com>
References: <CA+oaSDrNSEWbRF0s5T_M19fFGwPUFTif_iZxa0tpETrnd6yqyA@mail.gmail.com>
From: Shenshen Chen <shenshen.chen.tj@gmail.com>
Date: Sun, 3 Dec 2017 18:13:49 +0800
Message-ID: <CAJzLMpMwxLKm30eJmXxy=k4cf=dTCmwAAa3iBqgqxOoUxBwsug@mail.gmail.com>
To: draft-ietf-alto-cdni-request-routing-alto.authors@ietf.org
Cc: IETF ALTO <alto@ietf.org>, Shawn Lin <x.shawn.lin@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c0da636aeceac055f6cdb32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/4kIG6XO0ghgOvs0p8sFYRr5T4jU>
Subject: Re: [alto] Some questions for alto-cdni-request-routing
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 03 Dec 2017 10:13:55 -0000

Dear ALTO working group,

Here is my review of draft-ietf-alto-cdni-request-routing-alto-00.  Most of
them are minor issues.
Your feedback and comments are highly appreciated.

1. IANA consideration is missing.

2. In page 3, para "The main purpose ..."

   I prefer to define uCDN by appending "(uCDN)" to "Upstream CDN" since
the uCDN (and dCDN) are used without definition in para "CDNI FCI: ...".
Also, the "upstream CDN" appears in the following content several times,
which should be unified into "uCDN".

3. In page 6, para "Originally, ..."

   In the last quote, I prefer to use "actual algorithm ..." following the
original text in [RFC6707].

4. In page 6, para "Security: ..."

   A period is missing in the end.

5. In page 8, sec "3.1.3. Data Information"

   "a JSON object defined by [RFC8008]" seems obscure.  I guess it refers
to "a Capability Advertisement Object".

6. In page 8, sec "3.1.2", "3.1.3", "3.2"

   "[RFC7285] (Section 10.3.)" should be changed into "Section 10.3 of
[RFC7285]", otherwise this link doesn't work.  "(Section 8.4.)", "(Section
8.5.)" have the same problem.

Regards,
Shenshen

On Sat, Dec 2, 2017 at 11:27 AM, Shawn Lin <x.shawn.lin@gmail.com> wrote:

> Dear authors of  draft-ietf-alto-cdni-request-routing-alto-00 and ALTOers,
>
>
> Using ALTO to provide guidelines on the FCI protocol is really a good
> idea since ATLO can provide resources information of network as well as
> endpoints by an elegant way.
>
>
> 1. I found that there are *two sections (3.3.2 and 3.3.3) left blank *in
> this draft, have they be solved yet?
>
> 2. It seems that *how to use ALTO network map* is not described in this
> draft.
>
>
> I posted one example and its source for each of them, and hope we can refresh
> the current progress and try to move it forward.
>
>
> *3.3.2.  Incremental FCI Update Example*
>
> source: https://datatracker.ietf.org/meeting/99/materials/slides-
> 99-alto-cdni-footprint-and-capabilities-advertisements-using-alto/
>
>
> POST /updates/fci HTTP/1.1
>
> Host: fcialtoupdate.example.com
>
> Accept: text/event-stream,application/alto-error+json Content-Type:
> application/alto-updatestreamparams+json Content-Length: ###
>
> { "add": {
>
>     "my-fci-stream": {
>
>         "resource-id": "my-fci-map"
>
>     }
>
> }
>
>
> HTTP/1.1 200 OK
>
> Connection: keep-alive
>
> Content-Type: text/event-stream
>
> event: application/alto-updatestreamcontrol+json
>
> data: {"control-uri": "http://fcialtocu.example.com/
> updates/streams/3141592653589"}
>
>
> event: application/cdni,my-fci-stream
>
> data: { ... full cdni message ... }
>
>
> event: application/merge-patch+json,my-fci-stream
>
> data: { ... Merge patch update of cdni objects ... }
>
>
> event: application/json-patch+json,my-fci-stream
>
> data: { ... JSON patch update of cdni objects, e.g., footprints entries
> ... }
>
>
> *3.3.3.  FCI Using ALTO Network Map Example*
>
> source: https://tools.ietf.org/html/draft-ma-cdni-capabilities-09#
> section-5
>
>
> networkmap:
>
>     GET /networkmap HTTP/1.1
>
>     Host: http://alto.example.com/fcifootprint001
>
>     Accept: application/alto-networkmap+json,application/alto-error+json
>
>
>     HTTP/1.1 200 OK
>
>     Content-Length: 319
>
>     Content-Type: application/alto-networkmap+json
>
>
>     {
>
>       "meta" : {
>
>         "vtag": [
>
>           {"resource-id": "my-eu-netmap",
>
>            "tag": "1266506139"
>
>           }
>
>         ]
>
>       },
>
>       "network-map" : {
>
>         "south-france" : {
>
>           "ipv4" : [ "192.0.2.0/24", "198.51.100.0/25" ]
>
>         },
>
>         "germany" : {
>
>           "ipv4" : [ "192.0.3.0/24"]
>
>         }
>
>       }
>
>     }
>
>
> fcimap:
>
>       GET /fcimap HTTP/1.1
>
>       Host: alto.example.com
>
>       Accept: application/alto-fcimap+json,application/alto-error+json
>
>
>       HTTP/1.1 200 OK
>
>       Content-Length: 618
>
>       Content-Type: application/alto-fcimap+json
>
>
>       {
>
>         "meta" : {
>
>         },
>
>         "fcimap": {
>
>           "capabilities": [
>
>             { "capability-type": "FCI.DeliveryProtocol",
>
>               "capability-value": [
>
>                 "http1.1"
>
>               ]
>
>             },
>
>             { "capability-type": "FCI.DeliveryProtocol",
>
>               "capability-value": [
>
>               "values": [
>
>                 "https1.1"
>
>               ],
>
>               "footprints": [
>
>                 { "footprint-type": "altonetworkmap",
>
>                   "footprint-value": [
>
> *                    "http://alto.example.com/fcifootprint001
> <http://alto.example.com/fcifootprint001>",*
>
> *                    "germany",*
>
> *                    "south-france"*
>
>                   ]
>
>                 }
>
>               ]
>
>             }
>
>           ]
>
>         }
>
>       }
>
>
> One suggestion about the "footprint-value": although the meaning of each
> element in "footprint-value" list is described in
> draft-ma-cdni-capabilities-09, it may be better to use objects in
> "footprint-value" list in some circumstances. For example, this may be more
> human readable.
>
> "footprint-value": [
>
>   {"uri": *"http://alto.example.com/fcifootprint001
> <http://alto.example.com/fcifootprint001>*"},
>
>   {"country":"*germany*"},
>
>   {"coutry":"*south-france*"}
>
> ]
>
>
> Bests,
>
> X. Shawn Lin
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>