Added blueprint EP038 - Githubissues

Alopalao commented 1 year ago

Related to coloring issue #45

Blueprint detailing vulnerabilities that coloring presents and how to solve them.

viniarck commented 1 year ago

@Alopalao let me know when you need another review, the updated text look good, looks like these points are still open though:

Do we really need to manage the general dl_src actions drop? Since flows will be matched with in_port too on NNIs? Maybe we don't even need to manage extra drop flows and let the switch itself drop. Unless for sanity sake we'd like to make that explicitly. I'll leave that up to you and @italovalcy to discuss if you really want this to be explicit.
How flows will be migrated? Are you going to provide a script?
Partly related: coloring is also exposing the COLOR_FIELD='dl_src' to be configurable, since that flow is never persisted, if it changes it might also leave flows behind, which probably wouldn't impact but still leftovers, maybe it might be worth documenting in the README if it changes then network operators are supposed to delete the old flows?

Alopalao commented 6 months ago

This implementation will be on hold for some time until:

MAC address needs to be changed. Start using addresses reserved from IETF/IANA (00-00-5E-00-53-00 - 00-00-5E-00-53-FF)
Attribute in config file to determine range of assigned MAC addresses
coloring needs a counter to keep track of links.

kytos-ng / kytos