From nobody Tue Nov 17 05:58:58 2020 Return-Path: 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 78A6D3A132C for ; Tue, 17 Nov 2020 05:58:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QW5plYUAPyoN for ; Tue, 17 Nov 2020 05:58:51 -0800 (PST) Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 91DDC3A132F for ; Tue, 17 Nov 2020 05:58:51 -0800 (PST) Received: by mail-yb1-xb2a.google.com with SMTP id o144so10131764ybg.7 for ; Tue, 17 Nov 2020 05:58:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RuHTJNA/NtkIgemnzeaWBF85ztSmVXq56hRAnPW2f5Q=; b=crQcJ5jpIOvOFNTfs1PJOqY5pUaiyXHtRPywEuDZttb+1LpBF2kk+JWnmHoaUMGnVp MPSsWg5O645LUYWzzmBuApvB9YBU46lbbpE5eW5xpmeRm1FqnIaPiJgY8QtH05z0P7dz fqCiHvZ+8zbskWp5Rjp29lxX+f5+q8ivqJ8TdIpwg1qzXxsohlM4X2CCmGHZUDrtsi55 WIAOBgsnifq41M970dx8/4x1LdbPxCvMI4E0gy+UnUxLbSIa31ZjwLb9k/PKbcA23RH8 OGej6AIbMudG6avZD5wQx44gzg6gSVe7zOASYbww+QTPlaZ0f4E8eKcs4n84sAyxnOr0 j2QA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RuHTJNA/NtkIgemnzeaWBF85ztSmVXq56hRAnPW2f5Q=; b=Eieu2aUYeeuA7UQ3Vsr6+UPJnBL86sAKq2eYQ28OtGZIA8m+kOI9DSgu3wPEpj23dn rDYApbljHs2rFlfIjM2tfXuz/mKAoWp/f4JmoBlKkOkxr5HmPBikU2mRFjV361qpmiIe do91Dd9SGFJDVrbpO+oDAPaVyUYTgjoASlayCTL718pi2wgQq/yGqxSnWYGU1bSVzDeu DBzQB32XBUil2yiMw4jDxpFVZiQPhIJWUSQH6IhYR8Bl1Bt0XA/Ol33mkN41M0Q7nNNy fIJbd9zWDC7qrO87zz0H0oKul77RhIyVMnOuY3+Ylez+4rBSzoKhpwRgZ8S/WMSV9OpU U03A== X-Gm-Message-State: AOAM532Wr4bzwpqmD1eAYibQZ1gwOjEmtyguTE14o/3TTb2/hQUn2MaI s/vWlULjKeijIejVZ2QbF+WTzuAbfMSsZN5UnPY= X-Google-Smtp-Source: ABdhPJxcCHs7hLLEMAPntFi5bCm4gau2wLteLfH2eNFlnK76cJotYQMQj+gxI7w+onEa6loucyHLdNjSm/xjBpQX6UI= X-Received: by 2002:a25:d3cf:: with SMTP id e198mr22474696ybf.292.1605621530531; Tue, 17 Nov 2020 05:58:50 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jensen Zhang Date: Tue, 17 Nov 2020 21:58:35 +0800 Message-ID: To: Qin Wu Cc: "kaigao@scu.edu.cn" , "alto@ietf.org" , "alto-weekly-meeting@googlegroups.com" Content-Type: multipart/alternative; boundary="000000000000f89b7e05b44de4fd" Archived-At: Subject: Re: [alto] Meeting info for Nov 17, 2020 X-BeenThere: alto@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2020 13:58:55 -0000 --000000000000f89b7e05b44de4fd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Qin, Glad to see your feedback. On Mon, Nov 16, 2020 at 10:14 PM Qin Wu wrote: > Regarding the topic 3, I think investigating the configuration, > management, and > > operation of ALTO systems is interesting, I am wondering how network > topology model in RFC8345 > > and TE topology model in RFC8795 can be translated into network map, > property map, cost map? > Actually, how to automatically translate data collected by southbound into ALTO information resources (network map, cost map) is not a fully new topic= . RFC7971 has already discussed the related considerations. The newer southbound interfaces (like what you mentioned, the I2RS topology model and TE topology model) indeed make it easier. But to generate specific ALTO information resources, a single data source is usually not enough. I don't think either the I2RS topology or the TE topology can be directly translated into the cost map. The generation of property map can be more complex. It depends on the use case. e.g., like the use case of the property map proposed in the path vector document, the property map can be generated dynamically based on the client query. > > > Or use pub/sub mechanism to subscribe specific data source and publish th= e > event notification to the ALTO server automatically, > > Or translated TEDB and LSPDB directly into Network map or Cost map? > Whether using pub/sub to pull the specific data source may depend on the type of data source. For LSPDB, usually, we can pull the complete database. But for some measurement information, like INT, deciding which states to be measured will be very important. > > > Luis=E2=80=99s draft provide a good use case for this, i.e., automaticall= y derived > ALTO information from southbound interface. > > https://tools.ietf.org/html/draft-contreras-alto-service-edge-02 > > which also specify additional ALTO protocol extension for computing > capability exposure and selection. > I agree. Luis's draft is a good use case. This topic is more like an extension to RFC7971. Because of the evolution of both the application-aware network and ALTO, we need to reconsider the best practices and potential protocol extension for operations. To better clarify the scope of this item, we post a proposal to the mailing list [1]. Looking forward to seeing your further feedback. [1] https://mailarchive.ietf.org/arch/msg/alto/1Zixzjz62Sh6MSvv6gzKIRl4254/ Thanks, Jensen > > > -Qin > > *=E5=8F=91=E4=BB=B6=E4=BA=BA:* alto [mailto:alto-bounces@ietf.org] *=E4= =BB=A3=E8=A1=A8 *kaigao@scu.edu.cn > *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2020=E5=B9=B411=E6=9C=8816=E6=97= =A5 21:18 > *=E6=94=B6=E4=BB=B6=E4=BA=BA:* alto@ietf.org; alto-weekly-meeting@googleg= roups.com > *=E4=B8=BB=E9=A2=98:* [alto] Meeting info for Nov 17, 2020 > > > > Dear all, > > > > We will have the last meeting before the IETF 109 ALTO session at 9:00 am > US EST (3 pm CET, 10 pm Beijing Time). > > > > The purpose is to go over and finalize the recharter items. Given that > some topics were not presented in the last meeting, I suggest we follow t= he > order below: > > > > 1. General extensions > > 2. New transport > > 3. Operation automation > > 4. First hop > > 5. Multi-domain > > > > Bridge: https://yale.zoom.us/my/yryang > > > > Best, > > Kai > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto > --000000000000f89b7e05b44de4fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Qin,

Glad to see yo= ur feedback.


On Mon, Nov 16, 2020 at 10:14 PM Qin Wu &l= t;bill.wu@huawei.com> wrote:

Regarding the topic 3= , I think investigating the configuration, management, and

operation of ALTO systems i= s interesting, I am wondering how network topology model in RFC8345<= u>

and TE topology model in RF= C8795 can be translated into network map, property map, cost map?


Actually, how to automaticall= y translate data collected by southbound into ALTO information resources (n= etwork map, cost map) is not a fully new topic.
RFC7971 has alrea= dy discussed the related considerations. The newer southbound interfaces (l= ike what you mentioned, the I2RS topology model and TE topology model) inde= ed make it easier. But to generate specific ALTO information resources, a s= ingle data source is usually not enough. I don't think either=C2=A0the = I2RS topology or the TE topology can be directly translated into the cost m= ap. The generation of property map can be more complex. It depends on the u= se case. e.g., like the use case of=C2=A0 the property map proposed in the path vector document, the property map can be generated dy= namically based on the client query.
=C2=A0

=C2=A0=

Or use pub/sub mechanism to= subscribe specific data source and publish the event notification to the A= LTO server automatically,

Or translated TEDB and LSPD= B directly into Network map or Cost map?


Whether using pub/sub to pull the specific data s= ource may depend on the type of data source. For LSPDB, usually, we can pul= l the complete database. But for some measurement information, like INT, de= ciding which states to be measured will be very important.
= =C2=A0

=C2=A0=

Luis=E2=80=99s draft provid= e a good use case for this, i.e., automatically derived ALTO information fr= om southbound interface.

https:/= /tools.ietf.org/html/draft-contreras-alto-service-edge-02=

which also specify addition= al ALTO protocol extension for computing capability exposure and selection.=


I agree. Luis's= draft is a good use case. This topic is more like an extension to RFC7971.= Because of the evolution of both the application-aware network and ALTO, w= e need to reconsider the best practices and potential protocol extension fo= r operations.

To better clarify the scope of this = item, we post a proposal to the mailing list [1]. Looking forward to seeing= your further feedback.


Thanks,
Jensen
=C2=A0

=C2=A0=

-Qin

=E5=8F=91=E4=BB=B6=E4=BA=BA: alto [ma= ilto:alto-bounce= s@ietf.org] =E4=BB=A3=E8=A1=A8 kaigao@scu.edu.cn
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2020=E5=B9=B411=E6=9C=8816=E6=97=A5 21:18
=E6=94=B6=E4=BB=B6=E4=BA=BA: alto@ie= tf.org; alto-weekly-meeting@googlegroups.com
=E4=B8=BB=E9=A2=98: [alto] Meeting info for Nov 17, 2020

=C2=A0

Dear all,

=C2=A0

We will have the last meeting before the IETF 109 A= LTO session at 9:00 am US EST (3 pm CET, 10 pm Beijing Time).

=C2=A0

The purpose is to go over and finalize the recharte= r items. Given that some topics were not presented in the last meeting, I s= uggest we follow the order below:

=C2=A0

1. General extensions

2. New transport

3. Operation automation

4. First hop

5. Multi-domain

=C2=A0

Bridge: https://yale.zoom.us/my/yryang

=C2=A0

Best,

Kai

_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
--000000000000f89b7e05b44de4fd--