[alto] open alto development update

"Y. Richard Yang" <yry@cs.yale.edu> Tue, 13 September 2022 03:44 UTC

Return-Path: <yang.r.yang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA7CC15270F for <alto@ietfa.amsl.com>; Mon, 12 Sep 2022 20:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.409
X-Spam-Level:
X-Spam-Status: No, score=-1.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFr9HaKuBByj for <alto@ietfa.amsl.com>; Mon, 12 Sep 2022 20:44:15 -0700 (PDT)
Received: from mail-ot1-f48.google.com (mail-ot1-f48.google.com [209.85.210.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D05FFC15257B for <alto@ietf.org>; Mon, 12 Sep 2022 20:44:15 -0700 (PDT)
Received: by mail-ot1-f48.google.com with SMTP id v2-20020a056830090200b006397457afecso7220720ott.13 for <alto@ietf.org>; Mon, 12 Sep 2022 20:44:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=ipcSricVb+PWcA2G0ap/AFv/2Zld/nY4CjUiF8cn7/Y=; b=dF89TbYnY633uEA2pHeIiwBz5AM2ZPAQNba3X295efZcEk4xKmQHw3wHJFrrCnzaj5 VwBJk92xB0Sss38mxe7AFlJIDA23Q+n6+iUSUsInGvE2ZXPBlp7p4q+EBZtL8gk9s9dJ 2QZyP63P+/hk3un0sLfvzCuZSMRdkc/2RXl+QxSxdFWfT3C9mX6ZtedAf+mv6mHdNGcb 937sn4KJFPzuLm0u0EVR3fC2dgZhKu3hxoSq1lb2SyRXOeufPoX3bu/4U3KpkjWJ8/G/ RNZj0cuYOEbRu7vrt89IrlsMoQBGoLw9ABcSe+bDexqzlfAN1BhPj2fqtcFs3oANFs5S 0HCg==
X-Gm-Message-State: ACgBeo1MyunGUUa/C/n+WvDjPUPPm9AchfPifVQK4GePztUEGt+aHhoJ khOCIatqth7L6nbXOXbtzstdUvmToH6uNuVwJdf+kvJw
X-Google-Smtp-Source: AA6agR7+sMNgr10LQ1251ZBOmBcBf5SsqvV3y+kwG47gMhHtfHBSSgHWpMbrwPnWlDHcvY/8torOLJeTFxTh+8g/+CQ=
X-Received: by 2002:a05:6830:631c:b0:638:c121:463a with SMTP id cg28-20020a056830631c00b00638c121463amr11751167otb.39.1663040654760; Mon, 12 Sep 2022 20:44:14 -0700 (PDT)
MIME-Version: 1.0
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 12 Sep 2022 23:44:04 -0400
Message-ID: <CANUuoLp4rnJPm6oLiVdNsHbKxjJp-KsWTk0uHXZk1qP_Ah=i0g@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000079603105e886d3c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/sPeTcZ0Qysk_fMn78XJBWSwobEs>
Subject: [alto] open alto development update
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.39
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, 13 Sep 2022 03:44:20 -0000

Hi all,

Sorry to spam the mailing list with a second email message.

During the weekly meeting last week, we also discussed about the progress
and planning for the testing and deployment of TCN, which uses alto and is
based on our past progress. It was suggested that we post the planning (in
reverse chronological order) to engage the WG broadly.

- IETF 115 hackathon (11/2022): The main target is the partial deployment
(a parallel controller domain) that integrates alto into FTS to realize the
resource control

- LHCOPN/LHCONE meeting (10/25/2022): This will serve as a checkpoint, to
seek feedback from the broad CERN community to refine the current design

- GRP meeting (10/12/2022): This is the checkpoint to realize the first
running CERN infrastructure.

We will be happy to provide more details and feel free to get in touch.

Richard, Jordi on behalf of the team

-- 
Richard