Potato routing

From Citizendium
Revision as of 22:13, 15 July 2008 by imported>Howard C. Berkowitz (Origin of the term. See discussion page whether some of my own work is appropriate.)
Jump to navigation Jump to search
This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

In Internet routing, two paradigms, informally called hot potato and cold potato, exemplify the operational principles used in developing routing policy. When a routing domain or autonomous system receives a packet, under hot potato, it gets rid of it as quickly as possible. Hot potato is also called closest exit routing, and does minimize the workload required to route the information.

The term comes from a 1964 Rand Corporation paper by Sharla Boehm and Paul Baran.[1]

Network reliability and potatoes

Potatoes and controlling quality of service

Cold potato, also called best exit routing, involves having the routing domain or autonomous system keep control of the packet as long as it can route it over links of known performance and traffic, so it can control the per-hop behavior encountered by the packet. The exit point from the current routing domain will also be selected to have the best available external path to the destination.

Regulatory and economic considerations

The alternatives have different regulatory and economic aspects.[2]

References