Default-free zone: Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz (Internet transit provider) |
imported>Howard C. Berkowitz No edit summary |
||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
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)''' of an internet 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 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. | [[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 17:42, 26 May 2009
A router in the default zone (DFZ) of an internet 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.