689 | | The server just derives the destination's attachment point in terms of domain, and replies with a !PacketOut. Domains, to keep it simple, will have an identifier that can be aliased to an attachment point as describable in a !PacketOut. |
690 | | |
| 689 | The server just derives the destination's attachment point in terms of domain, and replies with a !PacketOut or !FlowMod. Domains, to keep it simple, will have an identifier that can be aliased to an attachment point as describable in a !PacketOut. |
| 690 | |
| 691 | Current infrastructure contains modules that can find routes (topology) within switches and islands(strongly connected switches) under control of the same controller, but not of different ones. We will call this group of switches/islands a domain. If determined to be out of the domain, current forwarding will flood the message. The route is pulled up by the routing engine(class implementing IRoutingService, which is currently !TopologyManager). |