Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-09.txt

Kai GAO <godrickk@gmail.com> Wed, 09 October 2019 13:02 UTC

Return-Path: <godrickk@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 32A77120105 for <alto@ietfa.amsl.com>; Wed, 9 Oct 2019 06:02:51 -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_HELO_NONE=0.001, SPF_PASS=-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 MwlRkk4VoK9U for <alto@ietfa.amsl.com>; Wed, 9 Oct 2019 06:02:48 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 EB5071200FB for <alto@ietf.org>; Wed, 9 Oct 2019 06:02:47 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id m15so3291292qtq.2 for <alto@ietf.org>; Wed, 09 Oct 2019 06:02:47 -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=viXeyrOr1Nan/8c9/THSKd8aJkU/rbhjVyeHOcOCGCQ=; b=UyN82n4vim/L/YkIE9yB+tl3t5nhdgOnZnW8/o11vEKhupSjLtcnX6KlNgt/jpDZ7T v26n/28oqS/D1NblsHv67EV8lB35gHvFA66NNoihEas28GG+epuMkNiSnL8E/2YHLkCc 3xHVfLAcVOpEb3OTsP6qvBDhJm5A6KYi41u0m/GZhakkWC+Y9pcyMsiP8siFmPWnB1es K5fycWROu54+QlXLpC5Om5qknPBu6jW4pE22iy2rREqW+L2MJSSNbcKRHjIBSCQZ4sNf Xb3NM3bcTOgNYaBkdYF+xJFDqSrgqz8nVjuPycC0Qh8I97ML1FI8W1f0JaxCfBT8IaHA W9sw==
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=viXeyrOr1Nan/8c9/THSKd8aJkU/rbhjVyeHOcOCGCQ=; b=pHj8dhanyH2xvuwuuD0c4OOTLkkKXHwqeKGUF1UYIgQHulmlzM1s9bwSTcmC9hfAGH qGsl2QiC3xEKVWr1nnazl5zVWJs20f2fQYrNP8xtmQI/GQ+e6IuGl/a6qjNzgXwXBbdo d8yHgsY8FYvCF+6kjhVDNbElC/gruQkN7dxL03WVyD+mS2k3fPekfrItl2AtUw5U1F+T gxaSkYrlSLAnqXWwZ9vJljDURb+fNY6/yIP/CUy2Pq4l8vhAtO3HxG6hvYEe6GpV8gxC KtWW9xWz5erapqW/VbBS9+0hKlZ9PlkQXS29HmwGw0si6Ac/P/9qpemoktHbVe1WYbq5 bEOA==
X-Gm-Message-State: APjAAAUTFbPxKDx5TeqV36tQUS4t+6OWXfEEPsg1deNJ4DQoFj9hh0Cs /nKrj3eTtTwHvP3CgVdE7VqgcM8/nXAiUxWPasU=
X-Google-Smtp-Source: APXvYqzbZmiKJ9S5K+RzZe4JtVizG5+FpksBAN3fLtoycWP0LIuBce0Tcr81EtRkeRYGMSRXgtbm4FKs16UgTrNo2Wc=
X-Received: by 2002:a0c:c10d:: with SMTP id f13mr3538420qvh.88.1570626166911; Wed, 09 Oct 2019 06:02:46 -0700 (PDT)
MIME-Version: 1.0
References: <156760442278.22833.16544634733937720759@ietfa.amsl.com> <CAEDarXLD+eJVM4rQg94FmmnJhUwXCROdNzen34nuJcwSwb=ihw@mail.gmail.com> <PR1PR07MB5100C260E33E211D02A5AEBF95840@PR1PR07MB5100.eurprd07.prod.outlook.com> <CAEDarXLkZ30hA1m5Y9x7N8z5TcYEyh2r-FuXkfAsWhGV4Cm7EA@mail.gmail.com> <CAAbpuypFVJrQ2WrNPvjCBOrxM4-Ny6_jx3JSkXR789UMwpVX=A@mail.gmail.com>
In-Reply-To: <CAAbpuypFVJrQ2WrNPvjCBOrxM4-Ny6_jx3JSkXR789UMwpVX=A@mail.gmail.com>
From: Kai GAO <godrickk@gmail.com>
Date: Wed, 9 Oct 2019 21:02:33 +0800
Message-ID: <CAOELiNM=cHR0V_W2UAZZd2bvDjGe-VSSvrDd59R--_Ea4KQ8NA@mail.gmail.com>
To: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Cc: Danny Alex Lachos Perez <dlachosper@gmail.com>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c0f93f059479e696"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/H7061L7CIabeVjvsV8cAcbWJzL4>
Subject: Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-09.txt
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: Wed, 09 Oct 2019 13:02:51 -0000

Hi Jensen and all,

I'm looking at the -10 version and find it quite odd to have 2.5.4
Resource-specific Entity Property as a subsection of 2.4 Entity Domain.

My suggestion is to move 2.5.4 to 2.2 instead. Another potential
improvement is to move 2.4 Information Resource before 2.2.

Best,
Kai



On Fri, Sep 27, 2019 at 5:28 AM Jensen Zhang <jingxuan.n.zhang@gmail.com>;
wrote:

> Hi Danny,
>
> Thanks for your review and comments. Sabine and I are working on the next
> revision. We will address all the issues in the next revision.
>
> And for your additional comment, actually, the "ip-pid-property-map"
> resource in IRD is an example of Aggregated Entity Domain. Sec 9.7 should
> illustrate it. But you are right, the current example in Sec 9.7 does not
> show the benefit of Aggregated Entity Domain. I will also revise this
> example in the next revision.
>
> Looking forward to your further comments.
>
> Thanks,
> Jensen
>
>
> On Wed, Sep 25, 2019 at 9:50 AM Danny Alex Lachos Perez <
> dlachosper@gmail.com>; wrote:
>
>> Hi Sabine,
>>
>> I have a quick additional comment:
>>
>> I believe that an example (sec. 9) of Aggregated Entity Domain is missing.
>> Perhaps you could re-use (or extend) the IRD example [0] and try to add a
>> couple of sentences to indicate equivalent entity property mappings (see
>> slide 17, 18 in [1]).
>>
>> Best regards,
>>
>> Danny Lachos
>> [0]
>> https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-09#page-28
>> [1]
>> https://datatracker.ietf.org/meeting/105/materials/slides-105-alto-unified-properties-for-the-alto-protocol-02.pdf
>>
>> On Tue, Sep 24, 2019 at 10:42 AM Randriamasy, Sabine (Nokia -
>> FR/Paris-Saclay) <sabine.randriamasy@nokia-bell-labs.com>; wrote:
>>
>>> Hi Danny,
>>>
>>>
>>>
>>> Many thanks for your review. I saw your last comment is in Section 9.7.
>>>
>>> Should we consider that until section 9.7 your review is complete or
>>> will you have more questions?
>>>
>>> We look forward to your other comments,
>>>
>>> Best regards,
>>>
>>> Sabine
>>>
>>>
>>>
>>>
>>>
>>> *From:* alto <alto-bounces@ietf.org>; *On Behalf Of *Danny Alex Lachos
>>> Perez
>>> *Sent:* Tuesday, September 17, 2019 8:28 PM
>>> *To:* IETF ALTO <alto@ietf.org>;
>>> *Cc:* i-d-announce@ietf.org
>>> *Subject:* Re: [alto] I-D Action:
>>> draft-ietf-alto-unified-props-new-09...txt
>>>
>>>
>>>
>>> Dear authors,
>>>
>>>
>>>
>>> I started to read the “*Unified Properties for the ALTO Protocol*” draft
>>> (-09).
>>>
>>>
>>>
>>> Please, see my first comments in the attached file (search for
>>> '[DANNY]').
>>>
>>> Many of them are suggestions about clarity and format issues .
>>>
>>>
>>>
>>> I will continue the review and send additional comments in a short time.
>>>
>>>
>>> Best regards,
>>>
>>>
>>>
>>> Danny Lachos
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Sep 4, 2019 at 10:41 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           : Unified Properties for the ALTO Protocol
>>>         Authors         : Wendy Roome
>>>                           Sabine Randriamasy
>>>                           Y. Richard Yang
>>>                           Jingxuan Jensen Zhang
>>>                           Kai Gao
>>>         Filename        : draft-ietf-alto-unified-props-new-09.txt
>>>         Pages           : 43
>>>         Date            : 2019-09-04
>>>
>>> Abstract:
>>>    This document extends the Application-Layer Traffic Optimization
>>>    (ALTO) Protocol [RFC7285] by generalizing the concept of "endpoint
>>>    properties" to generic types of entities, and by presenting those
>>>    properties as maps, similar to the network and cost maps in
>>>    [RFC7285].
>>>
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-09
>>>
>>> https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-09
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-09
>>>
>>>
>>> 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/
>>> <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
>>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>