Intra-Domain Vs Inter-Domain Routing
Duration: 4 min
This video lesson is available to enrolled students.
AI Summary
An AI-generated summary of this video lecture.
This lecture introduces the architecture of large-scale internet routing, explaining why the internet is divided into Autonomous Systems (AS) due to the limitations of single routing protocols. The instructor defines AS as a group of networks under a single administration and distinguishes between intra-domain routing (inside an AS) and inter-domain routing (between AS). The session concludes by classifying routing protocols into Intradomain (Distance Vector, Link State) and Interdomain (Path Vector) categories, providing examples like RIP, OSPF, and BGP.
Chapters
0:00 – 2:00 00:00-02:00
The instructor begins by explaining the necessity of dividing the internet into Autonomous Systems (AS). The slide text states, 'Today, an internet can be so large that one routing protocol cannot handle the task of updating the routing tables of all routers.' He defines an AS as 'a group of networks and routers under the authority of a single administration.' The diagram illustrates three distinct clouds labeled AS A, AS B, and AS C, connected by routers. The instructor underlines the phrase 'autonomous systems' and 'single administration' to emphasize that routing within an AS is called intra-domain routing, while the diagram shows links connecting these separate administrative domains.
2:00 – 4:25 02:00-04:25
The lecture transitions to a hierarchical diagram classifying 'Routing protocols' into 'Intradomain' and 'Interdomain'. Under Intradomain, the slide lists 'Distance vector' (with RIP as an example) and 'Link state' (with OSPF as an example). Under Interdomain, it lists 'Path vector' (with BGP as an example). The instructor uses red checkmarks to validate these classifications. He further explains metrics, noting that simple protocols like RIP treat all networks as equal with a cost of one hop count. In contrast, protocols like OSPF allow administrators to assign costs based on service requirements, meaning a route can have different metrics depending on the network type.
The video effectively bridges the gap between high-level network architecture and specific protocol implementation. By first establishing the concept of Autonomous Systems to manage scale, the instructor sets the stage for understanding why different routing protocols are needed for different scopes. The classification of protocols into Distance Vector, Link State, and Path Vector provides a clear framework for students to categorize routing algorithms based on their operational domain and metric calculation methods.