Dear Vijay, Jan and Qin
The new version 15 below fully addresses the review comments and now includes a
"navigation table" listing the new features and the section describing them.
This table stressed the need to change some section titles for more coherency.
Additionally, upon discussions with Qin, Wendy and co-authors, the document
title has now been changed to "ALTO extension: Entity Property Maps".
The document section titles and text have been updated to harmonize with the
document title.
Other minor updates have been added to further address the need for
clarification reflected in the reviews.
The updates done on v14 to produce v15 are listed in the attached text file
"v15-updates-2611.txt".
We feel the document is now ready for WG chair review and look forward to
getting review feedback.
Thanks,
Sabine, Jensen, Richard, Kai
-----Original Message-----
From: alto <[email protected]> On Behalf Of [email protected]
Sent: Thursday, November 26, 2020 8:15 PM
To: [email protected]
Cc: [email protected]
Subject: [alto] I-D Action: draft-ietf-alto-unified-props-new-15.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-15.txt
Pages : 57
Date : 2020-11-26
Abstract:
This document extends the base Application-Layer Traffic Optimization
(ALTO) Protocol 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 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-15
https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-15
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-15
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
[email protected]
https://www.ietf.org/mailman/listinfo/alto
-------------------------------------------
UPDATES
-------------------------------------------
---------- Document title: changed
ALTO extension: Entity Property Maps
Can also be ALTO Entity Property Maps for more simplicity
Harmonized Section titles and text with new document title.
---------- Terminology
Section 2. Terminology
added: This document uses the following terms and abbreviations, that will be
further defined in the document.
While this document introduces the feature "entity property map", it will use
both the term "property map"
and "entity property map" to refer to this feature.
added: EPM
---------- "feature navigation table" and related text
3. Basic Features of the Unified Property Extension
has a new last paragraph mentioning the section (Annex A) providing the
navigation table (4)
The Entity Property Maps extension described in this document
introduces a number of features that are summarized in
<xref target="features-introduced-with-epm-extension"/>, where
<xref target="TableUPFeatures"/> lists the features and references
the sections in this document that give a high-level and normative
description thereof.
Annex A: table is as follows (with real xrefs)
<texttable anchor="TableUPFeatures" align="center" title="Features introduced
with ALTO Entity Property Maps">
Entity 3.1 5.1.3
Entity domain (ED) 3.2
ED type 3.2.1 5.1.1
ED name 3.2.2 5.1.2
Entity property (EP) type 3.3 5.2, 5.2.1, 5.2.2, 5.2.3,
Entity property map 3.4 7, 8
resource-specific ED name 4.2 5.1.2, 5.1.2.1
resource-specific EP value 4.3 5.2.3
defining information resource 4.6, 12.2.2,
4.7 12.3
---------- Errors and warnings
Abstract: removed [references] and replaced by text
Added text of e-mail sent to Wendy, Qin and list regarding the document title.
---------- Coherent section titles
4.6. Defining Information Resource
NEW
4.6 Defining Information Resource for Resource-Specific Entity Domains
4.6.1 Defining Information Resource and Media Type
NEW
4.6.1. Media Type of Defining Information Resource
4.6.2. Examples of specific resources media-types
NEW
4.6.2. Examples of defining information resources media-types
To harmonize terminology: 6.1.1, 6.1.2, 6.2 and (new section) 8.7.1
Example:
OLD
IPv4 Domain
NEW
"Entity Domain Type: IPv4"
---------- re-wording & format
3.3. Entity Property Type
- rewording on examples for more accuracy
- added example for common property and domain name
Section 8.3: finally opted for phrasing:
OLD
"The input parameters for a filtered property map request are
supplied in the entity body of the POST request."
NEW
The input parameters for a filtered property map request are
supplied in the body of the POST request.
8.7.1: new section to better formalize the text on the new entity property type
introduced by this document.
---------- JSON examples
Corrected #5 (added/removed ",")
---------- IANA tables
12.3. ALTO Entity Property Type Registry:
added item "Media type of defining information resource:"
Added column Media Type of Defining Resource
in Tables 2 (section 12.2) and Table 3 (section 12.3) of IANA section
PROBLEM: revising the "width" of columns in table 3 has no effect...
dom-reg-process
---------- REFERENCES
put RFC8008 in comments because not used_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
