Intradomain routing protocols: Difference between revisions
Jump to navigation
Jump to search
imported>Meg Taylor m (spelling: contol -> control) |
Pat Palmer (talk | contribs) mNo edit summary |
||
Line 5: | Line 5: | ||
*[[Routing Information Protocol]] (RIP) | *[[Routing Information Protocol]] (RIP) | ||
*[[Open Shortest Path First]] (OSPF) | *[[Open Shortest Path First]] (OSPF) | ||
*[[Intermediate System | *[[Intermediate System-Intermediate System]] (IS-IS) | ||
*[[Enhanced Interior Gateway Routing Protocol]] (EIGRP) | *[[Enhanced Interior Gateway Routing Protocol]] (EIGRP) | ||
Of these protocols, the first three are open standards from the [[Internet Engineering Task Force]], while EIGRP is a proprietary protocol of [[Cisco Systems]]. | Of these protocols, the first three are open standards from the [[Internet Engineering Task Force]], while EIGRP is a proprietary protocol of [[Cisco Systems]]. |
Latest revision as of 08:34, 9 September 2024
Intradomain routing protocols support one of the two planses, control and forwarding, are needed to deliver IP packets over a network. Intradomain routing protocols provide information to the control plane, which determines and chooses the path to a destination based on metrics such as number of hops, delay, and bandwidth. The forwarding process does the actual insertion of the IP packet into a frame and forwards the frame to the next hop.
The major intradomain routing protocols in current use are:
- Routing Information Protocol (RIP)
- Open Shortest Path First (OSPF)
- Intermediate System-Intermediate System (IS-IS)
- Enhanced Interior Gateway Routing Protocol (EIGRP)
Of these protocols, the first three are open standards from the Internet Engineering Task Force, while EIGRP is a proprietary protocol of Cisco Systems.