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?
Or use pub/sub mechanism to subscribe specific data source and publish the event notification to the ALTO server automatically, Or translated TEDB and LSPDB directly into Network map or Cost map? Luis’s draft provide a good use case for this, i.e., automatically 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. -Qin 发件人: alto [mailto:[email protected]] 代表 [email protected] 发送时间: 2020年11月16日 21:18 收件人: [email protected]; [email protected] 主题: [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 the 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 [email protected] https://www.ietf.org/mailman/listinfo/alto
