> "In a routing network, the routing system is responsible for > determining how data packets should be forwarded and communicating > that to the relevant forwarding or data plane. The dispersal of both > the relevant information for this determination and the resulting > routes or paths is part of the routing system. The relevant > forwarding or data plane need not be co-located with the portion of > the routing system that determines the routes. However, a routing > system is frequently co-located in a network element with a forwarding > or data plane that contains one or more interface over which data > traffic is forwarded. Thus, the routing system includes control plane > protocols that compute routes and paths for data packets."
I would propose putting this in a bulleted list, rather than in paragraph form --it would make for easier reading. == In a routed network, the routing system: - Distributes topology and other state (network metadata) - Uses this network metadata to determine the best path to each given reachable destination attached to the network - Communicates these decisions to the forwarding plane of each forwarding device in the network While processes participating in the routing system are often colocated with the with local forwarding elements, this isn't a necessary condition. Thus, the routing system includes control plane protocols that compute routes and paths for data packets, wherever the processes implementing those protocols may be running. == Does this help clarify any? > While the type of interface is, I think, clear and beaten to death, I'd > like to jump further on it > by suggesting adding "protocol-based" to the list of possible > descriptors. That would make it: Hmmm... Are you trying to further the distance between forwarding and control interfaces here? > "The I2RS working group works to develop a framework and architecture > that will enable specific use cases, and lead to an understanding of > theinformational models and requirements for encodings and protocols of the > control and management protocol-based interfaces." This does help connect the charter to the work at hand better... :-) Russ -- <>< [email protected] [email protected] _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
