Hi Sabine, Minor comments that aren't blocking last call:
(7) Eliminate the commas around "for the Client" (8.3) Isn't " The client wants all properties values on all the entities," the use case for the (unfiltered) property map? (8.3) s/Sever/Server On Thu, Aug 12, 2021 at 8:38 AM Randriamasy, Sabine (Nokia - FR/Paris-Saclay) <sabine.randriam...@nokia-bell-labs.com> wrote: > Hello Martin and ALTO WG, > > Thanks again Martin for your thorough review and discussions that allowed > to improve the document and enrich the capabilities of this extension. > > This new version addresses the comments in the AD review and is available > at > https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-18 > You may check the diffs here > https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-18 > > The main updates: > - remove unused and unclear terms and clarifies text in many places, > - Filtered Property Map (FPM) queries now allow empty lists of entities > and properties. Empty lists are interpreted as representing the full set of > entities and properties. > - put tables and text in coherency in IANA sections 12.2 and 12.3. Though > due to lack of space, only added a column "mapping to ALTO address type" in > Table 2. Some text on the security issue item referring to relevant > sections was added in the introduction of section 12.2 and 12.3 > > The key updates were added in section 8 "Filtered Property Map". (FPM) > They address the question on: how a Client can obtain the list of > entityIDs that can be used as input to a FPM without having to download a > full property map. The FPM query input format and response have been > updated accordingly. > - In Section 8: a paragraph explains why this is useful for a Client > - In section 8.3 Accept Input Parameters: the format of query object > ReqFilteredPropertyMap is revised and explained to support this. The > property member is optional. > - In section 8.6 Filtered Property Map Response: > --- an error case is added when input member "entities" is absent > --- text explains how, when the "property" member is absent in the query, > the Server returns an empty value for the queried entities. > > We hope the updates are meeting the review expectations. > Thanks, > Sabine and authors > > >-----Original Message----- > >From: alto <alto-boun...@ietf.org> On Behalf Of internet-dra...@ietf.org > >Sent: Thursday, August 12, 2021 4:45 PM > >To: i-d-annou...@ietf.org > >Cc: alto@ietf.org > >Subject: [alto] I-D Action: draft-ietf-alto-unified-props-new-18.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-18.txt > > Pages : 60 > > Date : 2021-08-12 > > > >Abstract: > > This document extends the base Application-Layer Traffic Optimization > > (ALTO) Protocol by generalizing the concept of "endpoint properties" > > to entities defined by a wide set of objects, instead of only IP > > addresses. 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 is also an htmlized version available at: > > > https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-18 > > > >A diff from the previous version is available at: > >https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-18 > > > > > >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 >
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
