Re: [alto] ALTO pipeline discussions

[Qiao Xiang <[e-mail]>]

Dear WG members,

As posted in Richard's earlier email, we want to discuss items that are not
working group documents but are of interests to the WG. This email is to
share my preliminary thoughts on two items: (1) How should ALTO information
be integrated/utilize in orchestration; and (2) Use mathematical
programming representation abstraction as unified resource representation.

The motivation for me to look into these items are (1) How to represent
resource sharing of flows with on-demand routing? and (2) How to represent
shared risk link group (SRLG) information of flows? Both these motivating
questions are raised during our earlier discussion with people from LNBL
and ESNet, one of the major use cases of ALTO. They are highly interested
in the linear inequality abstraction introduced in the ALTO path vector
draft.

My first design proposal is to use "generalized disjunctive programming"
(GDP) as the abstraction. GDP is an optimization modeling technique that
can encode not only linear/integer constraints, but logical propositions. I
believe it is a good candidate for unified resource representation in ALTO
because it is highly expressive and easy to interpret. I prepare a few
simple slides to illustrate the basic idea of my design, and will write
down the specs in a draft before the cut-off date. Meanwhile, it will be
greatly appreciated if you could share your comments or thoughts on this
design,

Thank you very much.


Best
Qiao

On Thu, Jun 21, 2018 at 9:58 PM Y. Richard Yang <[e-mail]> wrote:

> Dear all,
>
> It is 24 days to the scheduled ALTO session, on July 16. After this
> weekend, it will be only 3 weeks. During the last couple of months, to
> better prepare for the coming IETF, some of us (Danny, Dawn, Lyle, Jensen,
> Sabine, Shawn, Qiao, Christian) looked at both the current state and the
> pipeline of ALTO.
>
> For the current-state part, Dawn/Danny/Shawn are doing a wonderful review
> of ALTO, on ALTO implementations, ALTO in related work. They will continue
> to lead the efforts.
>
> The objective of this email is to start a thread to discuss the pipeline
> aspect. We want to discuss items that are not working group documents but
> have interests. We may or may not have a chance to work on these items, but
> will definitely help to get the discussion started.
>
> At a high, rough level, we can classify ALTO pipeline into three
> categories, and in each category, we can identify several potential working
> items. At the end of this email is a list. We are hoping that we can have a
> good discussion on this before and during the coming IETF.
>
> Cheers,
> Richard, on behalf of Danny, Dawn, Lyle, Jensen, Sabine, Shawn, Qiao,
> Christian
>
>
>
>
>
>
>
>
>
>
>
> * - App use cases/requirements/architecture 1. A systematic study of how
> ALTO info be integrated/utilize in orchestration 1. One aspect ALTO + PCE,
> ABNO, Path-based, 2. Extension to new architectures (e.g., cellular, 5G)
> endpoint types 3. Extension to new settings such as multi-domain (ALTO is
> traditional design for App-Net, i.e., north-south interface, interdomain is
> more EW interface), SFC, NFV,  edge clouds - API/base protocol 1. A general
> multipart service, SSE -> HTTP/2 2. Flow cost service, extensible query
> schema for a set of flows, may including unicast and multicast, multipath,
> ... 3. Calendar for endpoint entity properties [Sabine] 4. Unified resource
> representation (e.g., mathematical programming representation abstraction,
> linear inq) - Backend/infrastructure 1. Smart/on-demand measurements (query
> miss trigger, start and collect measurements, formalize the protocol,
> connect to IPPM, accuracy/freshness, what kind of info to be provided) 2.
> Proxy architecture, for scale, interdomain, for fault tolerance, for
> security/privacy -- Qiao Xiang Postdoctoral Fellow, Department of Computer
> Science,Yale University*
>