[alto] ALTO Recharter: Operation Automation for ALTO

Jensen Zhang <jingxuan.n.zhang@gmail.com> Tue, 17 November 2020 13:11 UTC

Return-Path: <jingxuan.n.zhang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 56A823A1053 for <alto@ietfa.amsl.com>; Tue, 17 Nov 2020 05:11:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3YlNAgbPKnNn for <alto@ietfa.amsl.com>; Tue, 17 Nov 2020 05:11:48 -0800 (PST)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 CF3AD3A102B for <alto@ietf.org>; Tue, 17 Nov 2020 05:11:47 -0800 (PST)
Received: by mail-yb1-xb33.google.com with SMTP id v92so18891099ybi.4 for <alto@ietf.org>; Tue, 17 Nov 2020 05:11:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=PUIUzcSM6JKOgT+PJHNAr/Nu4L7y80ySrlhKasGzn2Y=; b=WqtIcLv3H93+YWwmckL2WpS1q0gXd7d2uHg3nuD/u2omQEGbgnjMrzPusNJpxkrBBq vGYNVJv8svJmwL/sEDBW35Odh3BPwUAbVXcvmA+9i3slff/LFx87knddjBoQhaAAehOD 13YJ+NKjx2KVgYiNDnv1lCz0tRhRqCxvU3n8HzDSRxPDj2tkTcQ0HcnhH3hwD3QJx2vV piKUVVydTo+5OsBvmbDE/vuVfYKgkVybCl4lPRPhCV6IQIUW/ntQOotepSpUYoM3c2j3 16d0W8d+ZctuGbFL3ec+nlHQHtPH41b3tBN7OGWNthYYehIYl2MiicYJRnEQpEvw/ESI fDnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PUIUzcSM6JKOgT+PJHNAr/Nu4L7y80ySrlhKasGzn2Y=; b=nXtzdsZUroE9NAJK0njXI+IpZcK6pnIEf0ht57RIT+kzWt/NiwMcnD0b1XJUXtXWlm gNaG1oUDOYSU37Oy8hpTBeKpusyQPewBrw81N7EXkYHlAyZLjCcebDnsxXbXRHDnIx52 uTxy0Ns9HT3mmWP0sXtJF7ejlBNXJizDDhePPAWpJatdHl4tuWj6ODR0sKCb/Se9huqJ xgoCDgjaBJjvb4b2D3o8To2aKMF6uS7Br6c5G4MYt0SfbwPY1Ea9DIw8F3iPFgogeAcB TRQWOovpzT6fWJTXHztPeAN2bcu41PsoCNvTdmYw0ZD+JCMv8Bq9Bc35OOuLmsdRD0Lp bKVg==
X-Gm-Message-State: AOAM531uoOSHpAYj1V/etxCUVW21X+4BOdlTY/PKvM+xzCB4I3MmIqzX wfATpyl+IwIM3i+8I34Pm/m0R6jXhUW6hI+RXxgU1zyeVZ0lig==
X-Google-Smtp-Source: ABdhPJxRJys1gSD4buAJndLep6FXWrojsLvBG0j8n8q5yqFT6LuqtvyIAfeetELLLEPq7T2kQmPeq0oq4xv+3MV1s3Q=
X-Received: by 2002:a25:d804:: with SMTP id p4mr27675364ybg.7.1605618706622; Tue, 17 Nov 2020 05:11:46 -0800 (PST)
MIME-Version: 1.0
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Tue, 17 Nov 2020 21:11:31 +0800
Message-ID: <CAAbpuyrS-+BiUF19eqTp7Md+SG-beDwtgzKA9g20CvLn2dEv3g@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a72b2b05b44d3c7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/1Zixzjz62Sh6MSvv6gzKIRl4254>
Subject: [alto] ALTO Recharter: Operation Automation for ALTO
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: Tue, 17 Nov 2020 13:11:49 -0000

Dear all,

Please find below a WG item proposal for “Operation Automation for ALTO”,
on which your feedback and suggestions will be more than welcome.



Operation Automation for ALTO

## Proposed paragraph

Best practice documentation and extension of ALTO for operation automation.
Operating an ALTO server can be complex, and the automation of the
of the ALTO services can be highly valuable. The operations of an ALTO
includes decisions on the set of information resources (e.g., what metrics,
how they are divided into multiple entries) exposed in the information
resource directory (IRD), population (may be proactive and reactive) of the
content of the services (e.g., pull the backend, or trigger just-in-time
measurements), and aggregation/processing of the collected information to
give clients the proper response. Because of the dynamicity of network
and application demands, the automation of the ALTO server operations
requires more inputs from applications. The working group will (1)
investigate the best practices in ALTO operations automation, including
interop/interfaces/protocols with routing systems and measurement tools; (2)
propose the new protocol extension for more application-aware information to
enable reactive measurement and computation.

## Basic Issue

- New complexity of operations
  - Practical operations of an ALTO server includes the complex workflow
  - New ALTO protocol extensions (e.g., the incremental update mechanism,
    calendar, unified properties, and path vector) introduce more
complexity to
- Inefficient measurement and computation
  - ALTO information resource may be populated reactively, which requests
    more communications with applications to predict/decide which low-level
    information (e.g., INT) should be collected/measured, and which
    information (e.g., end-to-end path cache) should be precomputed

## Potential solution(s)

- Investigate best practices (extending RFC7971) including:
  - Automatic IRD generation
  - ALTO information resources population from information collected by
existing routing
    systems and measurement tools (e.g., TEDB, LSPDB, SNMP)
  - Reactive ALTO information resources update
  - Aggregation of different information sources
  - Considerations about intermediate abstraction (e.g., history, path
- Define the new interface (service) between application and server to allow
  the application to subscribe demand and enable reactive measurement and
  - Interested E2E flows
  - Constraints for flows

## Remaining issues to be addressed

- How to reactively populate on-demand ALTO information resources (e.g.,
  vectors) based on client queries
- Flows that applications are interested in may change because of dynamic
  network state
  - e.g., applications are only interested in the endpoints attached to the
    specific PoP (Point of Presence)
- Constraints for interested flows may be correlated
  - e.g., filter all sources whose total upload bandwidth are higher than

## Who will work on it

- Luis/Jensen/Kai
- Any other interested people

## Potential milestones (1-2 years)

- IETF 109: problem statement
- IETF 110: initial draft for protocol extension
- IETF 112: best practice documentation