[alto] Re: RFC 9569 on The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)

"Y. Richard Yang" <yang.r.yang@yale.edu> Wed, 11 September 2024 13:11 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 CE029C16942F for <alto@ietfa.amsl.com>; Wed, 11 Sep 2024 06:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.755
X-Spam-Level:
X-Spam-Status: No, score=-1.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 ggAoQPOtE4ra for <alto@ietfa.amsl.com>; Wed, 11 Sep 2024 06:11:23 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479A3C14CF09 for <alto@ietf.org>; Wed, 11 Sep 2024 06:11:23 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id 38308e7fff4ca-2f75aa08a96so22640491fa.1 for <alto@ietf.org>; Wed, 11 Sep 2024 06:11:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; t=1726060282; x=1726665082; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7/ZRIKUcjrhEY3rPLIxu8emFOWkYbZlQdyJl6Kp27uM=; b=C6wvMuaqyDv0Sww8IPHEw9ecEH54Imv0Vp7PVOMNui2n0exEp/SNr+Bdbw9sql8wBS uYc6YfUYRy3hHV2B+KQU1tLVZ+Q9ezRCBdo42F0qn++VnQdRopAiqachMSNQit8XIQZj +VIQbITm63ZoP6iHqlUsdoA9RMjUT9uqBkhhw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726060282; x=1726665082; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7/ZRIKUcjrhEY3rPLIxu8emFOWkYbZlQdyJl6Kp27uM=; b=ofKjUYRAvN+Wg7Sfqq2WTeryxnjiJ9JrtAcZdchquYsPnZAWQFs3oR4kRdJR4z6nNc hYK5EOaD75ZCoKjeIaG9LlIi3MBbNzdWIWBU1CuDNxEq9CMt/AWRGeqeFqjhwmBNJkct bCp5fMbDCDITXWuY2msAJB9pOeTjrp+qHuR3BgRtym8+MqIWYBQBw4gxcLbod0cxS1mv Co5lAyHH9E+xjKZ5Np2jmdDOfpdNrA9i6MvGjta7SU4TXAaY4cn8h7KCx3LxwJI9oty/ ChCPBpELcfg7foT6reQeKvRt3ljraRLXvZZpDjX6HfUoqe6ndj6QMAS5A9ViNOLA7OzQ i0Ug==
X-Forwarded-Encrypted: i=1; AJvYcCUN9+e9eX3zUM2UE4PV3kWvYx68SFY6L1NDaNNjEvHFe+6k2pJa0Rd8X2iJwsyvxt4EGurJ@ietf.org
X-Gm-Message-State: AOJu0YyhwY6uqI7TTgeCSoeJKVjrkShRJtS1cP1RkM7vHLtCsqcExTrq 3ge29gHHYau4rDmlVOMfuR7YPHY+uqahldgle1cQXGNKavna1ShdoNuOkozyV2s78ITtptehMxB 9y6Jo4aYkme4NwXDKi9HcO2RhSqw=
X-Google-Smtp-Source: AGHT+IGBiaWyQNRNhZmh/SN8+6MB36cd10i4g0KdhSuNEvrn5uaNCpFsYJC7bZOtcXjRhwDF/UFU1NwXLLB1Zylq9FM=
X-Received: by 2002:a2e:611:0:b0:2f5:1fa7:ac3a with SMTP id 38308e7fff4ca-2f77b7fa89bmr13986411fa.28.1726060280543; Wed, 11 Sep 2024 06:11:20 -0700 (PDT)
MIME-Version: 1.0
References: <37f7a2a245b34e7cb184c26922a2175e@huawei.com> <6d900dae.ff32.191e1289d41.Coremail.kaigao@scu.edu.cn>
In-Reply-To: <6d900dae.ff32.191e1289d41.Coremail.kaigao@scu.edu.cn>
From: "Y. Richard Yang" <yang.r.yang@yale.edu>
Date: Wed, 11 Sep 2024 09:11:08 -0400
Message-ID: <CANUuoLpUTLczk1=19VBdvCt01z6=bio+XE8Q02qXxSmXg_8M7g@mail.gmail.com>
To: kaigao@scu.edu.cn
Content-Type: multipart/alternative; boundary="000000000000e2093c0621d7b968"
Message-ID-Hash: 7TQGJR4M3UGWFS7IRF6CB2OYY4AZHAR2
X-Message-ID-Hash: 7TQGJR4M3UGWFS7IRF6CB2OYY4AZHAR2
X-MailFrom: yang.r.yang@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alto.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Qin Wu <bill.wu=40huawei.com@dmarc.ietf.org>, "alto@ietf.org" <alto@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [alto] Re: RFC 9569 on The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)
List-Id: "Application-Layer Traffic Optimization (alto) WG mailing list" <alto.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/NOn5-lN_4jtJRUclmdtQuAWBTFI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Owner: <mailto:alto-owner@ietf.org>
List-Post: <mailto:alto@ietf.org>
List-Subscribe: <mailto:alto-join@ietf.org>
List-Unsubscribe: <mailto:alto-leave@ietf.org>

This is good progress indeed. Echo Kai, great thanks to Qin and Med for the
great guidance! Great thanks to all those help from this good group of
collaborators!

Richard


On Wed, Sep 11, 2024 at 8:57 AM <kaigao@scu.edu.cn> wrote:

> Thanks, Qin! Congratulations to my co-authors and big thanks to everyone
> who helps to review/edit the document!
>
> I believe the next milestone wouldn't take long :)
>
> Best,
> Kai
>
>
> > -----Original Messages-----
> > From: "Qin Wu" <bill.wu=40huawei.com@dmarc.ietf.org>
> > Send time:Wednesday, 09/11/2024 18:27:39
> > To: "'alto@ietf.org'" <alto@ietf.org>
> > Subject: [alto] Re: RFC 9569 on The Application-Layer Traffic
> Optimization (ALTO) Transport Information Publication Service (TIPS)
> >
> > Congratulation to authors who complete one of last two milestones.
> >
> > -Qin
> > -----邮件原件-----
> > 发件人: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> > 发送时间: 2024年9月11日 13:32
> > 收件人: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> > 抄送: rfc-editor@rfc-editor.org; drafts-update-ref@iana.org; alto@ietf.org
> > 主题: [alto] RFC 9569 on The Application-Layer Traffic Optimization (ALTO)
> Transport Information Publication Service (TIPS)
> >
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >         RFC 9569
> >
> >         Title:      The Application-Layer Traffic Optimization (ALTO)
> >                     Transport Information Publication Service (TIPS)
> >         Author:     K. Gao,
> >                     R. Schott,
> >                     Y. R. Yang,
> >                     L. Delwiche,
> >                     L. Keller
> >         Status:     Standards Track
> >         Stream:     IETF
> >         Date:       September 2024
> >         Mailbox:    kaigao@scu.edu.cn,
> >                     Roland.Schott@telekom.de,
> >                     yry@cs.yale.edu,
> >                     lauren.delwiche@yale.edu,
> >                     lachlan.keller@aya.yale.edu
> >         Pages:      40
> >         Updates/Obsoletes/SeeAlso:   None
> >
> >         I-D Tag:    draft-ietf-alto-new-transport-22.txt
> >
> >         URL:        https://www.rfc-editor.org/info/rfc9569
> >
> >         DOI:        10.17487/RFC9569
> >
> > "Application-Layer Traffic Optimization (ALTO) Protocol" (RFC 7285)
> leverages HTTP/1.1 and is designed for the simple, sequential request-reply
> use case, in which an ALTO client requests a sequence of information
> resources and the server responds with the complete content of each
> resource, one at a time.
> >
> > RFC 8895, which describes ALTO incremental updates using Server-Sent
> Events (SSE), defines a multiplexing protocol on top of HTTP/1.x, so that
> an ALTO server can incrementally push resource updates to clients whenever
> monitored network information resources change, allowing the clients to
> monitor multiple resources at the same time.
> > However, HTTP/2 and later versions already support concurrent,
> non-blocking transport of multiple streams in the same HTTP connection.
> >
> > To take advantage of newer HTTP features, this document introduces the
> ALTO Transport Information Publication Service (TIPS). TIPS uses an
> incremental RESTful design to give an ALTO client the new capability to
> explicitly and concurrently (in a non-blocking manner) request (or pull)
> specific incremental updates using HTTP/2 or HTTP/3, while still
> functioning for HTTP/1.1.
> >
> > This document is a product of the Application-Layer Traffic Optimization
> Working Group of the IETF.
> >
> > This is now a Proposed Standard.
> >
> > STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions for improvements.  Please refer to the current edition of the
> Official Internet Protocol Standards (https://www.rfc-editor.org/standards)
> for the standardization state and status of this protocol.  Distribution of
> this memo is unlimited.
> >
> > This announcement is sent to the IETF-Announce and rfc-dist lists.
> > To subscribe or unsubscribe, see
> >   https://www.ietf.org/mailman/listinfo/ietf-announce
> >   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> >
> > For searching the RFC series, see https://www.rfc-editor.org/search For
> downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> >
> > Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for unlimited
> distribution.
> >
> >
> > The RFC Editor Team
> > Association Management Solutions, LLC
> >
> > _______________________________________________
> > alto mailing list -- alto@ietf.org
> > To unsubscribe send an email to alto-leave@ietf.org
> > _______________________________________________
> > alto mailing list -- alto@ietf.org
> > To unsubscribe send an email to alto-leave@ietf.org
> _______________________________________________
> alto mailing list -- alto@ietf.org
> To unsubscribe send an email to alto-leave@ietf.org
>