Hi Qin,
Thanks. These issues really deserve further consideration. Please see inline.
Regards,
Peng
Peng Liu | 刘鹏
China Mobile | 移动研究院
mobile phone：13810146105
email: liupeng...@chinamobile.com
发件人: Qin Wu
时间: 2021/07/23(星期五)21:31
收件人: LUIS MIGUEL CONTRERAS MURILLO;Peng Liu;alto;
主题: 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
Luis
De: alto <alto-boun...@ietf.org> En nombre de Peng Liu
Enviado el: miércoles, 21 de julio de 2021 5:39
Para: alto <alto@ietf.org>
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（https://www.ietf.org/archive/id/draft-liu-alto-can-usecase-00.txt）
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.
Regards,
peng
Peng Liu | 刘鹏
China Mobile | 移动研究院
mobile phone：13810146105
email: liupeng...@chinamobile.com
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_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
