Default-free zone: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
No edit summary
imported>Howard C. Berkowitz
(Internet transit provider)
Line 2: Line 2:
A [[router]] in the '''default zone (DFZ)''' has only explicit routes in its [[routing information base]]; it gets all routing information from local configuration and dynamic [[routing protocol]]s. Its tables contain no default routes.
A [[router]] in the '''default zone (DFZ)''' has only explicit routes in its [[routing information base]]; it gets all routing information from local configuration and dynamic [[routing protocol]]s. Its tables contain no default routes.


[[Internet Service Provider]] (ISP) interprovider routers are normally in the DFZ.  Large enterprise edge routers that connect to multiple ISPs may be in the DFZ. Any production DFZ router will run the [[Border Gateway Protocol]] as its major means of acquiring routing information.
[[Internet transit provider]]s' interprovider routers connect to the DFZ.  Large enterprise edge routers that connect to multiple ISPs may be in the DFZ. Any production DFZ router will run the [[Border Gateway Protocol]] as its major means of acquiring routing information.

Revision as of 05:23, 17 August 2008

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.

A router in the default zone (DFZ) has only explicit routes in its routing information base; it gets all routing information from local configuration and dynamic routing protocols. Its tables contain no default routes.

Internet transit providers' interprovider routers connect to the DFZ. Large enterprise edge routers that connect to multiple ISPs may be in the DFZ. Any production DFZ router will run the Border Gateway Protocol as its major means of acquiring routing information.