Hi, Luis: Thank for your proposed new draft on service function handling (https://datatracker.ietf.org/doc/draft-lcsr-alto-service-functions/), I believe it is related to service function invocation use case. Thanks for that. ALTO Path vector seems a good basis for your requested protocol extension. One thing I am not very clear is 1.who will be the client to consume ALTO information combining network topo info and service function information? Should it be cross domain service orchestration system, or ingress node or headend? 2.How does such client consume these information?
-Qin
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
