Routing: Difference between revisions
imported>Howard C. Berkowitz (Consistency exits) |
imported>Howard C. Berkowitz (Introduction to routing) |
||
| Line 4: | Line 4: | ||
Routing is not terribly difficult than 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. | Routing is not terribly difficult than 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 | 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 | ||
| url = http://www.ietf.org/rfc/rfc3654.txt | |||
| title = Requirements for Separation of IP Control and Forwarding] | |||
| id=RFC3654 | |||
| first1 = H. |last1= Khosravi | first2= T. | last2= Anderson | |||
| date = November 2003 | |||
| publisher = Internet Engineering Task Force}}</ref> | |||
The device that performs these functions is called a [[router]]. Physically, a router is usually a special-purpose computer, although it is possible to program a personal computer to route. | The device that performs these functions is called a [[router]].<ref name=RFC1812>{{citation | ||
|title = Requirements for IPv4 routers | |||
|author = Baker, F. | |||
| id = RFC1812 | |||
|url=http://www.ietf.org/rfc/rfc1812.txt | |||
| publisher = Internet Engineering Task Force | |||
| date = June 1995 | |||
}}</ref> Physically, a router is usually a special-purpose computer, although it is possible to program a personal computer to route. | |||
==References== | |||
{{reflist}} | |||
Revision as of 21:21, 6 May 2008
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 is not terribly difficult than 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.
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