Re: [alto] A new draft draft-liu-alto-can-usecase-00 for discussion and comments

Peng Liu <> Sun, 25 July 2021 03:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 061CA3A1278 for <>; Sat, 24 Jul 2021 20:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.001, HDRS_MISSP=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SzOiflDB_pHe for <>; Sat, 24 Jul 2021 20:45:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 27ED83A127D for <>; Sat, 24 Jul 2021 20:45:54 -0700 (PDT)
Received: from (unknown[]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec60fcde5275c-78ed6; Sun, 25 Jul 2021 11:45:22 +0800 (CST)
X-RM-TRANSID: 2eec60fcde5275c-78ed6
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-LP (unknown[]) by rmsmtp-syy-appsvr08-12008 (RichMail) with SMTP id 2ee860fcde5013d-4da86; Sun, 25 Jul 2021 11:45:21 +0800 (CST)
X-RM-TRANSID: 2ee860fcde5013d-4da86
MIME-Version: 1.0
x-PcFlag: c0417622-4b7e-47c1-958d-db7d794d4b6b_5_23998
X-Mailer: PC_RICHMAIL 2.8.5
Date: 25 Jul 2021 11:46:24 +0800
From: =?utf-8?B?UGVuZyBMaXU=?=<>
To: =?utf-8?B?UWluIFd1?=<>
Cc: =?utf-8?B?TFVJUyBNSUdVRUwgQ09OVFJFUkFTIE1VUklMTE8=?=<>, alto<>
Message-ID: <>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart143096287_=----"
Archived-At: <>
Subject: Re: [alto] A new draft draft-liu-alto-can-usecase-00 for discussion and comments
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: Sun, 25 Jul 2021 03:46:01 -0000

Hi Qin,

Thanks. These issues really deserve further consideration. Please see inline.



Peng Liu | 刘鹏

China Mobile | 移动研究院

mobile phone:13810146105



发件人: Qin Wu

时间: 2021/07/23(星期五)21:31


主题: RE: [alto] A new draft draft-liu-alto-can-usecase-00 for discussion and comments 


Hi Peng, 


Thanks for sharing. Looking at the figure of the CAN framework I can see depicted multiple  components interacting with the ALTO server: Service Orchestration, Computing OAM, Routing Management and Resource Management. This brings to my mind a number of questions: 


 -          Do you foresee an individual interaction per component with the ALTO Server? If so, what would be the specific interaction per component  and to what extend such interaction would imply some extension? 

[Qin Wu] Good question, let me ask authors in a different angle 

 1.       Can we have one single protocol to collect both network information and compute information 

[PL] Yes, extending BGP may be an option, or the network probe packet carrys computing information. Both require the service node to expose the corresponding information to the gateway. 

 2.       or we still use different protocol to collect network information and compute information but, we could use one single protocol e.g.,  ALTO protocol to expose both network information and compute information to the application? 

The problem, how we can make sure the network information and compute information are synchronized if these  information change over time?

[PL] If the network and computing information are colleted to Alto through different protocols, it is difficult to maintain absolute synchronization unless time stamps and other information are added, but this may require time synchronization of all the network nodes and the service nodes, which will cause some additional expenses. The accuracy of synchronization will affect the quality of service, and the demands of applications should also be considered. 

 -          Would not be more practical to consider a single ALTO Client as part of the Computing and Network Management Layer aggregating all the  requests towards the ALTO Server? This also could decouple the solution from a specific CAN architecture 

 -          In the scheduling section, you mention the possibility of retrieving real time information. How far the information could be “real-time”?  I mean, in the way ALTO works (i.e., collecting information from protocols such BGP with certain timers) the notion of “real-time” could be relative. Would the aging of that information sufficient to ensure the “real-time” needs? Would it be needed any other  mechanisms to shorten the period of information refreshment? 


Best regards 






De: alto <> En nombre de Peng Liu
 Enviado el: miércoles, 21 de julio de 2021 5:39
 Para: alto <>
 Asunto: [alto] A new draft draft-liu-alto-can-usecase-00 for discussion and comments   




 Hi All, 


 A new draft draft-liu-alto-can-usecase-00 has been submitted( 

 Since some work of computing related service deployment and routing have been proposed in IETF and ITU, this draft describes a new network scenario and architecture considering computing-related  properties, and assumes that Alto could be used to help realize the deployment of services, and to assist in the selection of service nodes. 

 Any comments are welcome. 








 Peng Liu | 刘鹏  


 China Mobile | 移动研究院  


 mobile phone:13810146105  





 Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la  lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
 The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination,  distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
 Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a  leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição