Toerless Eckert <[email protected]> wrote: > But in general: i would like for this (informational!) draft to just motivate > the concept and not specify the solution: MPTCP would be a simple way to > make "TCP" applications automatically "upgrade" from ACP to a data-plane path > and switch back when data-plane fails... because MP-TCP can signal the > additional data-plane addresses, establish transparently another subflow and switch > traffic between the subflows - all by using the right shim-library+API or > in-MP-TCP address/subflow policies - and the ability to establish subflows > across two VRFs.
Perhaps we need some examples to motivate why the ACP wouldn't be enough.
Some obvious ones to me are:
a) firmware updates
b) transfering VM images onto the
target equipment --- the ASA is a priviledged domain in a hypervisor
system.
c) things like mirror port/captures that need to be offloaded quickly
as they can not be stored.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
