Subject: [alto] Some thinkings about “ALTO Contextual Cost Values”

From: xin wang <[email-masked]>
Date: Thu, 29 Jun 2017 01:45:54 +0000

Dear authors of “ALTO Contextual Cost Values”,

There are already several reviews for your draft, and my thinking would be the potential collaboration with Flow Cost Service (fcs) (https://datatracker.ietf.org/doc/draft-gao-alto-fcs/) which aims to extend ALTO query with OpenFlow format. The flow concept in fcs goes beyond source, destination endpoints/PIDs, which makes fine-grained query service available. Your draft, from my perspective, also extends original ALTO query by adding context parameters, such as “RFcost”. Data transmissions with different context parameters would be treated differently in networks. For example, flows with different network environments (e.g., wifi or cell) would have different delays; flows with different timing would have different limitations. However, these constraints are missing in OpenFlow format. By merging the flow in fcs and the context in your draft, "context available” flow-based cost query should be a generic solution. The "context available” flow extends original flow in OpenFlow by adding context, such as environments, user-side limitations, and makes it more flexible to express requirements in different situations.

draft-gao-alto-fcs-01 - ALTO Extension: Flow-based Cost Query<https://datatracker.ietf.org/doc/draft-gao-alto-fcs/>
datatracker.ietf.org
ALTO Extension: Flow-based Cost Query (Internet-Draft, 2017)

Also there are some typos you may fix:

Page 4: “advatageously” -> “ advantageously”;

Page 5: “aforementionned” -> “ aforementioned”;

Page 6: “unpredictible” -> “unpredictable”, “patrameters” -> “parameters”, “explicitely” -> “explicitly”;

Page 7: “a an” -> “an”, “the the” -> “the”, “specfied” -> “specified”;

Page 15: add space in “local”ALTO;

Best,

Xin