Routing: Difference between revisions
imported>Pat Palmer (Rewording of this very nice beginning to have more "flow") |
imported>Pat Palmer mNo edit summary |
||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
In computer networking, '''routing''' is the process of receiving a [[packet]] on one interface of a [[router]], validating the packet, and (assuming the router knows that a particular outbound interface will move the packet one [[hop]] closer to its final destination) forwards it out that interface. Routing may be compared to a destination along a set of highways. Each exit sign informs the driver of a set of destinations reachable through that exit. The driver will decide to take the exit if it goes toward the destination, or will continue looking for a better exit. | In computer networking, '''routing''' is the process of receiving a [[packet]] on one interface of a [[router]], validating the packet, and (assuming the router knows that a particular outbound interface will move the packet one [[hop]] closer to its final destination) forwards it out that interface. Routing may be compared to driving to a destination along a set of highways. Each exit sign informs the driver of a set of destinations reachable through that exit. The driver will decide to take the exit if it goes toward the destination, or will continue looking for a better exit. | ||
The process that draws the "map" of the network, or, in the highway analogy, puts the list of destinations on the exit sign, is the [[control plane]] of the router. The process that actually moves the packet from input to output is the [[forwarding plane]].<ref name=FORCES>{{citation | The process that draws the "map" of the network, or, in the highway analogy, puts the list of destinations on the exit sign, is the [[control plane]] of the router. The process that actually moves the packet from input to output is the [[forwarding plane]].<ref name=FORCES>{{citation | ||
| Line 18: | Line 18: | ||
| date = June 1995 | | date = June 1995 | ||
}}</ref> Physically, a router is usually a special-purpose computer, although it is possible to program a personal computer to route. | }}</ref> Physically, a router is usually a special-purpose computer, although it is possible to program a personal computer to route. | ||
==Forwarding plane== | ==Forwarding plane== | ||
Both in [[Internet Protocol version 4]] and [[Internet Protocol version 6]], the most basic principle of routing is "longest prefix match." Every Internet Protocol address has a certain number of bits, from the left, which form its '''prefix''' or '''locator''', describing the target network or group of networks in which it resides. Unless other factors override, routing forwards a packet towards its best knowledge of the most precise specification of that destination. That knowledge is in a [[forwarding information base]], created by the router's [[control plane]]. If, for example, there are two [[routing information base]] entries, one matching the first 8 bits of the address and the second matching the first 16 bits, the second entry will prescribe the next hop for the routing operation. | Both in [[Internet Protocol version 4]] and [[Internet Protocol version 6]], the most basic principle of routing is "longest prefix match." Every Internet Protocol address has a certain number of bits, from the left, which form its '''prefix''' or '''locator''', describing the target network or group of networks in which it resides. Unless other factors override, routing forwards a packet towards its best knowledge of the most precise specification of that destination. That knowledge is in a [[forwarding information base]], created by the router's [[control plane]]. If, for example, there are two [[routing information base]] entries, one matching the first 8 bits of the address and the second matching the first 16 bits, the second entry will prescribe the next hop for the routing operation. | ||
Revision as of 08:39, 24 December 2010
In computer networking, routing is the process of receiving a packet on one interface of a router, validating the packet, and (assuming the router knows that a particular outbound interface will move the packet one hop closer to its final destination) forwards it out that interface. Routing may be compared to driving to a destination along a set of highways. Each exit sign informs the driver of a set of destinations reachable through that exit. The driver will decide to take the exit if it goes toward the destination, or will continue looking for a better exit.
The process that draws the "map" of the network, or, in the highway analogy, puts the list of destinations on the exit sign, is the control plane of the router. The process that actually moves the packet from input to output is the forwarding plane.[1]
The device that performs these functions is called a router.[2] Physically, a router is usually a special-purpose computer, although it is possible to program a personal computer to route.
Forwarding plane
Both in Internet Protocol version 4 and Internet Protocol version 6, the most basic principle of routing is "longest prefix match." Every Internet Protocol address has a certain number of bits, from the left, which form its prefix or locator, describing the target network or group of networks in which it resides. Unless other factors override, routing forwards a packet towards its best knowledge of the most precise specification of that destination. That knowledge is in a forwarding information base, created by the router's control plane. If, for example, there are two routing information base entries, one matching the first 8 bits of the address and the second matching the first 16 bits, the second entry will prescribe the next hop for the routing operation.
Control plane
The control plane learns the connectivity and reachability of the router, stores it in a routing information base from which it generates the forwarding information base.
References
- ↑ Khosravi, H. & T. Anderson (November 2003), Requirements for Separation of IP Control and Forwarding], Internet Engineering Task Force, RFC3654
- ↑ Baker, F. (June 1995), Requirements for IPv4 routers, Internet Engineering Task Force, RFC1812