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

Vijay Gurbani <vijay.gurbani@gmail.com> Sat, 17 April 2021 15:42 UTC

Return-Path: <vijay.gurbani@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 582BB3A26ED for <alto@ietfa.amsl.com>; Sat, 17 Apr 2021 08:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 QT3GKSsQrE42 for <alto@ietfa.amsl.com>; Sat, 17 Apr 2021 08:42:15 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 87CD93A26E2 for <alto@ietf.org>; Sat, 17 Apr 2021 08:42:15 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id z1so33526338ybf.6 for <alto@ietf.org>; Sat, 17 Apr 2021 08:42:15 -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=zH+YDPrkQ8EA3EC3iFx3HW9ik2rVitv6yuz9P4umOIU=; b=FgXjWivFnIRBjNdBOErsCwWt3K14XtZpZL1pIksLMrK9djay/Gi+IIl6lwzDlm7fo/ yfG5Rvg7Km+41S/g2rNiSEJvYMzd9CC8D1+/IqmX2amC4ZSnYsHnvvhS2+AaGsm+r8Ix qyV1iqPreQ3L3ZLLv0eylCnhnYqCwiCh/GvEQApl/cbfIZ47OGcAuvsmUmV/I3qEwxav 5VfQjzTvlzz7x5M6IuLAeKra3UhNzfEgK4JqJIBWEBjHdM/INae3MzSRq6GJ3PTdWVhT Z6Avmf9ZkplS+nZplTun4GrDQIdCvM0wldWmrEF1oCsQIVpkY9HNOHOkN+8pjNOj1WoH HU4Q==
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=zH+YDPrkQ8EA3EC3iFx3HW9ik2rVitv6yuz9P4umOIU=; b=WZcEetdkpkd9k4WmZknDSlRth8ALnpVzpnexGCIbZ6H1tNOjec/4e3IFXjgDfcjy8G GZJzk9XVrJ/UyLxq6XHBdkjCIMzZsOnpDFQSBTZa7FvSwJNdYxuIXY5+3/43eFvJM2oq gNiATyT1s1l7yIszQ2q2uVd6RtQxGVM/5e9K7p+KotzQCZxzdJod9MMN0qR0IbqN1kns khHeJduTV0EleZ9XtqgZSg4ZGOx7hi6B9rMxZJg356Rg56X/JdJv7R1Y2BsteAYpWXUp y/CY63Q//6F23lX98L2mq5Uq8yZ8MvxQRpMOpk2WT3/fC5guj8ejRHtdohzcKXF9Ur2z AlQg==
X-Gm-Message-State: AOAM533nlK8ZzogTaGGa6+PifLXw8+wArxivZrNpvTwHXNlcmKKioCRz AlclcErZEGPDkH9hMYNxkz4IurL9V3wA7wlnMnWcJ8nCSEE=
X-Google-Smtp-Source: ABdhPJwdYXlL5sD3RtoLTwez5rZFsevkc8TYsB7GVhh3JaJLtS888OiPoF1Ed90UAf+b3YtefJgZLdEMNzoDVdka7Ys=
X-Received: by 2002:a25:830f:: with SMTP id s15mr6335456ybk.50.1618674133748; Sat, 17 Apr 2021 08:42:13 -0700 (PDT)
MIME-Version: 1.0
References: <161859924228.22138.7638537623807052073@ietfa.amsl.com> <PR3PR07MB7018BA6742966FD6E904781B954C9@PR3PR07MB7018.eurprd07.prod.outlook.com>
In-Reply-To: <PR3PR07MB7018BA6742966FD6E904781B954C9@PR3PR07MB7018.eurprd07.prod.outlook.com>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Sat, 17 Apr 2021 10:42:01 -0500
Message-ID: <CAMMTW_KXW4aQyTmXJVPvenMscDu6okioF38ByYnpiFJJtMMieA@mail.gmail.com>
To: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bfd0ea05c02cf009"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ZkddhIXdIt0xU2-5Ip4nJAu2E74>
Subject: Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-17.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: Sat, 17 Apr 2021 15:42:20 -0000

Dear Sabine: Excellent. I will start to wrap up the post-chair review
process next week on this and path-vector so they can be sent to IESG.

Have a nice weekend.

On Fri, Apr 16, 2021, 2:05 PM Randriamasy, Sabine (Nokia - FR/Paris-Saclay)
<sabine.randriamasy@nokia-bell-labs.com> wrote:

> Dear Vijay,
>
> A new version 17 of the "ALTO Extension: Entity Property Maps" has been
> uploaded and hopefully addresses the pending review comments.
> It can be found at the link below, by clicking on the number "16" on the
> ALTO status pages.
> https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-17
> Below is a digest of the updates and we look forward to having your
> feedback.
> A detailed "diff" can be sent if you wish.
>
> Best regards,
> Sabine & co-authors
> =========================
> updates in draft-ietf-alto-unified-props-new-17
> =========================
> Previous V16 was submitted to address Vijay's review of v15
> This V17 addresses remaining issues on V15 review
>
> Main update is the addition of a substantial Section 11. Security
> Considerations.
> The other updates are as follows:
>
> - Defined terminology nomenclature used in 4.4.  Entity Hierarchy and
> Property Inheritance
> --- related (small) edits in subsections
>
> - In Section 4.7 Defining Information Resource for Resource-Specific
> Property Values
> text was clarified and moved back from 4.6.1 to 4.7. Section 4.7.1 (of
> V15) with examples was merged with 4.7
>
> - Clarified text on defining information resources in sections 4.6 and
> 4.7, as review reflects it was unclear
> --- added example in 4.6.2 of entity domain types that do  not have a
> defining resource
> --- Clarified text in related IANA sections 12.2.2 and 12.3
>
> - Added normative "MUST" wherever needed
> --- section 4.3.  Resource-Specific Entity Property Value
> --- 4.6.1.  Defining Information Resource and its Media Type
> --- sections 12.2.2 and 12.3 on item "Media type of defining information
> resource"
> - Replaced lower case "must" with other words where convenient
>
> - Rewording
> ---  Clarified sentence distinguishes domain name and domain type in 3.2.1
> --- Added introduction sentence in Section 4 Advanced Features...
> - Typos and nits in sections  5.1.2, 8.6
>
> - Added normative and informative references
>
> >-----Original Message-----
> >From: alto <alto-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
> >Sent: Friday, April 16, 2021 8:54 PM
> >To: i-d-announce@ietf.org
> >Cc: alto@ietf.org
> >Subject: [alto] I-D Action: draft-ietf-alto-unified-props-new-17.txt
> >
> >
> >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: Entity Property Maps
> >        Authors         : Wendy Roome
> >                          Sabine Randriamasy
> >                          Y. Richard Yang
> >                          Jingxuan Jensen Zhang
> >                          Kai Gao
> >       Filename        : draft-ietf-alto-unified-props-new-17.txt
> >       Pages           : 59
> >       Date            : 2021-04-16
> >
> >Abstract:
> >   This document extends the base Application-Layer Traffic Optimization
> >   (ALTO) Protocol by generalizing the concept of "endpoint properties"
> >   as applied to endpoints as defined by IP addresses to endpoints
> >   defined by a wider set of objects.  Further, these properties are
> >   presented as maps, similar to the network and cost maps in the base
> >   ALTO protocol.  The protocol is extended in two major directions.
> >   First, from endpoints restricted to IP addresses to entities covering
> >   a wider and extensible set of objects; second, from properties on
> >   specific endpoints to entire entity property maps.  These extensions
> >   introduce additional features allowing entities and property values
> >   to be specific to a given information resource.  This is made
> >   possible by a generic and flexible design of entity and property
> >   types.
> >
> >
> >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-17
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-17
> >
> >A diff from the previous version is available at:
> >https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-17
> >
> >
> >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
>