Intradomain routing protocols: Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz No edit summary |
imported>Meg Taylor m (spelling: contol -> control) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
'''Intradomain routing protocols''' | '''Intradomain routing protocols''' support one of the two planses, [[control plane|control]] and [[forwarding plane|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: | The major intradomain routing protocols in current use are: | ||
Latest revision as of 22:12, 6 February 2010
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 to 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.