Re: [alto] I-D Action: draft-ietf-alto-path-vector-04.txt

Danny Alex Lachos Perez <dlachosper@gmail.com> Tue, 10 July 2018 21:39 UTC

Return-Path: <dlachosper@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 2F898131057; Tue, 10 Jul 2018 14:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_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 Ltj6GLrjTw0O; Tue, 10 Jul 2018 14:39:41 -0700 (PDT)
Received: from mail-pl0-x244.google.com (mail-pl0-x244.google.com [IPv6:2607:f8b0:400e:c01::244]) (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 1DDCC12872C; Tue, 10 Jul 2018 14:39:41 -0700 (PDT)
Received: by mail-pl0-x244.google.com with SMTP id z9-v6so8175190plo.1; Tue, 10 Jul 2018 14:39:41 -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=TK0R/y+2vuH+bppEva8GaCVkKBUP6nyISqWQcAwaZaE=; b=OhsoHh8tUkHqM3RrQW/ffrYZI2Hi2rWV5t8pqNqDZCq2PNwlDAhG+IPtouhRywGgc5 CDbKO6BGypO3FUzswBKCbRcgCOMA1fJRc27QzXx6dLzd9S6ui+X6MovR5NGQ8zohMl58 Dfv9vMMuNjuJJsSGPnGzZJUrTzqjz2GoVtYuxf+IK5X6/O+lnhCct8Kks8VvQuawqA+h lH+PBmuJnWhFgirrh8Fyba7EdRlP8jqsDGchQcQwr0ymF8aWM0lknXI+bbOJ9ANqoQqd qwVkhpId5RP5XUFx3K7hqq/W7A39DnYSoFLl7TEnwYUfGytZL0PnIUeAbTsVUR4wTrKZ CTYQ==
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=TK0R/y+2vuH+bppEva8GaCVkKBUP6nyISqWQcAwaZaE=; b=F0zNhB/3TfmiQANTPPiBn6KUtkp0KrqWxa7ykWkNji+pLNk/h7Hai9cv9bMzoahWTp +CjNNJ8drCLOOIE/pL9bN6Aul/yHMxTr6QdKDRipuBSPqZ3k/CA1O0B/3lEtBDHNt+9Z zZenvQiB1c7hofjdJV3b9kqfTy5nQwSJ/jkSV9OKb7lLJ/hIX3X6VB3f16IuqsObg+aP cFveMVbHE6x+avFOQo6wj7aqwnbdA/bCDGYLIixaBs7tIaIlZOCn1D/jgZQG2sthqq9c lfXmZaJcdHU1lgCLf9j8mW5V1lz1uHraPTFduv3LBpcd+cyupF5Lg5JH6Oa4nKDyERBi +BTw==
X-Gm-Message-State: APt69E2+Stl14yO7pNVqS2+23dj0A8cTEw6gZEp/TBqOAJnPbU1E9u15 k22AdF+B33HYfSbAPnbmCqtEmqK6S9copt3cmMaQ3w==
X-Google-Smtp-Source: AAOMgpdjJWWFQ+kaXjv4sCr6twbc95p6D/3VhI0optZwk4QsnsTiRuWtxC18HNcTJwUZSXnE6kmkln5VAlP0Da88f3U=
X-Received: by 2002:a17:902:aa8f:: with SMTP id d15-v6mr25924621plr.262.1531258780689; Tue, 10 Jul 2018 14:39:40 -0700 (PDT)
MIME-Version: 1.0
References: <153056076382.16100.4380161360915504373@ietfa.amsl.com> <CAAbpuyre_LqPZOZRzmMt_TniSreLZ_UjnNvcpnsqv34vVooW1A@mail.gmail.com>
In-Reply-To: <CAAbpuyre_LqPZOZRzmMt_TniSreLZ_UjnNvcpnsqv34vVooW1A@mail.gmail.com>
From: Danny Alex Lachos Perez <dlachosper@gmail.com>
Date: Tue, 10 Jul 2018 18:39:28 -0300
Message-ID: <CAEDarXKvc_jyT-GWfrRSRgAKPk3mQPUVJ7QfQU3kMEaV8P=WRg@mail.gmail.com>
To: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Cc: internet-drafts@ietf.org, IETF ALTO <alto@ietf.org>, i-d-announce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000aea88c0570abf7ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/HSGkZ2o4JvneiiYiVSGcCZjDVSQ>
Subject: Re: [alto] I-D Action: draft-ietf-alto-path-vector-04.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 10 Jul 2018 21:39:45 -0000

Hi Jensen and WG

I started to review the draft. I have one technical comment that I would
like to share:

In section 5.1 (Cost Mode :  Array):
*"This document extends the CostMode defined in Section 10.5 of [RFC7285]
with a new cost mode: "array".  This cost mode indicates that every cost
value in a cost map represents an array rather than a simple value.  The
values are arrays of JSONValue."*

It seems that the current path-vector draft can not support
multi-paths between source/destination points. What if an ALTO client wants
to know the different paths (or all paths) for a pair of endpoints or
PIDs?. For example, in the Broker-assisted architecture, a filtered cost
map could provide an array of arrays of values to provide all possible
paths for each source and destination node.

Let me know your thoughts about that.

Ss

Danny Lachos


On Mon, Jul 2, 2018 at 5:08 PM Jensen Zhang <jingxuan.n.zhang@gmail.com>;
wrote:

> Hi all,
>
> In this revision -04, we do the following changes:
>
> - The major change is to decouple the multipart query service from the
> path vector.
>     - Instead, A capability called "allow-compound-response" is introduced
> to make the property map inline.
>     - The multipart query service is moved to a new document and defined
> for the general cases.
> - The examples section is revised to better explain the usage of the path
> vector extension.
> - The compatibility of the path vector extension is better clarified.
> - Some general discussions are raised.
>
> Looking forward to receiving your feedback.
>
> Thanks,
> Jensen
>
> On Tue, Jul 3, 2018 at 3:46 AM <internet-drafts@ietf.org>; wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Application-Layer Traffic Optimization
>> WG of the IETF.
>>
>>         Title           : ALTO Extension: Path Vector Cost Type
>>         Authors         : Greg Bernstein
>>                           Shiwei Dawn Chen
>>                           Kai Gao
>>                           Young Lee
>>                           Wendy Roome
>>                           Michael Scharf
>>                           Y. Richard Yang
>>                           Jingxuan Jensen Zhang
>>         Filename        : draft-ietf-alto-path-vector-04.txt
>>         Pages           : 29
>>         Date            : 2018-07-02
>>
>> Abstract:
>>    The Application-Layer Traffic Optimization (ALTO) protocol [RFC7285]
>>    has defined cost maps and endpoint cost maps to provide basic network
>>    information.  However, they provide only scalar (numerical or
>>    ordinal) cost mode values, which are insufficient to satisfy the
>>    demands of solving more complex network optimization problems.  This
>>    document introduces an extension to the base ALTO protocol, namely
>>    the path-vector extension, which allows ALTO clients to query
>>    information such as capacity regions for a given set of flows.  A
>>    non-normative example called multi-flow scheduling is presented to
>>    illustrate the limitations of existing ALTO endpoint cost maps..
>>    After that, details of the extension are defined.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-alto-path-vector-04
>> https://datatracker.ietf.org/doc/html/draft-ietf-alto-path-vector-04
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-04
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>