http://blog.ipspace.net/2016/12/response-on-death-of-openflow.html
Programmable traffic tapping
Flexible endpoint (host) authentication
Per-user packet filters installed into edge devices
Interesting load balancing scenarios of long-lived elephant flows
really hard to:
- Detect non-trivial link failures in milliseconds (that’s why we have BFD);
- Respond to real-time events in reasonable timeframe;
- Respond to control-plane requests (ARP/ND) from a very large number of hosts;
- Run chatty edge protocols (LLCP, LACP, STP …) on a large number of ports.
extensions to OpenFlow,but lost interoperability
fancy programmable patch panel
<厲害 , 命名專家>
not require control-plane protocols,
not time-sensitive
no real-time response to failures
No control-plane protocols;
No real-time response to topology change events;
No real-time response to link failures. You’d either use a single uplink or a pre-computed backup path.
programmable ACL/PBR”
<厲害 , 命名專家>
Comments