Chapter 4 Flashcards
1
Q
Link-State Routing Protocols and Areas
A
- Link-state routing protocols like OSPF and IS-IS partition routing domains into areas.
- Areas are groups of routers that exchange link-state information.
- There is a special area known as the backbone area (Area 0), which connects all other areas.
- Example: Routers R1, R2, and R3 can be members of both the backbone area and nonbackbone areas (e.g., Area 1, Area 2).
- A router that is a member of both the backbone area and a nonbackbone area is called an Area Border Router (ABR).
2
Q
Routing Within and Between Areas
A
- Within an area, all routers exchange link-state advertisements to develop a complete map of the area.
- Link-state advertisements from non-ABR routers do not leave the area, which improves scalability.
- To route between nonbackbone areas, packets travel through the backbone area (Area 0).
- Area border routers summarize routing information from one area and advertise it into the backbone area.
- Routers in the backbone area then summarize and advertise this information into nonbackbone areas.
3
Q
Tradeoff Between Scalability and Routing Optimality
A
- Dividing a domain into areas trades off routing optimality for scalability.
- All packets between nonbackbone areas must travel through the backbone area, even if a shorter path exists.
- This design decision ensures scalability by limiting the number of routers that need to exchange routing information.
- Example: Even if R4 and R5 are directly connected, packets cannot flow between them if they are in different nonbackbone areas.
4
Q
Virtual Links and Routing Flexibility
A
- Virtual links allow network administrators to connect routers not directly connected to the backbone to routers in Area 0.
- Example: A virtual link can connect R8 in Area 1 to R1 in Area 0, making R8 part of the backbone.
- Virtual links improve routing optimality by allowing non-ABR routers to participate in backbone routing.
- The cost of the virtual link is determined by routing information exchanged in the respective nonbackbone area.
5
Q
Autonomous Systems (AS) and Routing
A
- Autonomous systems (AS) provide hierarchical aggregation of routing information in large networks like the Internet.
- Routing in AS is divided into:
- Intradomain routing (within an AS)
- Interdomain routing (between ASs or routing domains)
- AS model allows each AS to use its own intradomain routing protocols and policies independently.
- Interdomain routing involves sharing reachability information between ASs.
6
Q
Challenges in Interdomain Routing
A
- Interdomain routing requires each AS to define its own routing policies.
- Example: Policies might prefer one path (AS X) over another (AS Y), avoid carrying traffic between specific AS pairs, and prioritize certain providers over others.
- Complex policies need to be supported without relying on other ASs, due to competitive and confidential reasons.
- Interdomain routing protocols must handle misconfigurations and malicious behaviors from other ASs.
7
Q
History and Evolution of Interdomain Routing Protocols
A
- Exterior Gateway Protocol (EGP) was the first interdomain routing protocol but had limitations with the Internet’s evolving topology.
- Border Gateway Protocol (BGP), specifically BGP-4, replaced EGP and supports a graph model for interconnecting ASs.
- BGP can accommodate non-tree-structured internetworks, such as multiprovider networks.
- Today’s Internet is a complex network of interconnected ASs, mainly operated by private ISPs.
8
Q
Types of Autonomous Systems (AS)
A
- Stub AS: Connects to only one other AS and carries local traffic only.
- Multihomed AS: Connects to multiple ASs but refuses to carry transit traffic.
- Transit AS: Connects to multiple ASs and carries both transit and local traffic.
- AS types influence routing decisions and policies within the network.
9
Q
Goals and Challenges in Interdomain Routing
A
- Interdomain routing aims to find loop-free paths compliant with AS policies.
- Challenges include scale (handling 700,000+ prefixes), diverse routing policies, and trust between ASs.
- Interdomain routing focuses on reachability rather than optimizing path costs across multiple ASs.
- The autonomous nature of ASs complicates path cost calculations due to varying metrics and policies.
10
Q
Basics of BGP
A
- Each AS has one or more border routers responsible for forwarding packets between autonomous systems (AS).
- Border routers may also function as BGP speakers, which communicate routing information with other BGP speakers in different ASs.
- BGP is not a distance-vector or link-state protocol; it advertises complete paths as enumerated AS sequences to reach specific networks.
- This path-vector approach is crucial for making policy decisions and preventing routing loops in complex AS networks.
11
Q
BGP Path Advertisement
A
- BGP speakers advertise reachability information for networks assigned to their customers.
- Example: AS 2 advertises networks 128.96, 192.4.153, 192.4.32, and 192.4.3 as reachable directly from AS 2.
- Backbone networks then advertise paths to these networks, indicating the sequence of ASs to reach them, such as (AS 1, AS 2) and (AS 1, AS 3).
- BGP’s path enumeration prevents routing loops by detecting and avoiding paths that lead back to the originating AS.
12
Q
AS Numbers and Loop Prevention
A
- AS numbers in BGP must be unique to prevent routing loops.
- AS numbers are 32 bits long and centrally assigned to ensure uniqueness.
- Unique AS numbers are critical for BGP speakers to correctly identify and avoid routing loops in the AS path advertisements.
13
Q
BGP Route Selection and Advertisement
A
- A BGP speaker selects the best route to a destination based on its local policies.
- BGP speakers are not obliged to advertise all routes; they can choose not to advertise routes to certain prefixes, implementing policies such as not providing transit.
- Route cancellations in BGP are achieved through withdrawn route messages, a form of negative advertisement.
14
Q
BGP Communication and Reliability
A
- BGP runs over TCP for reliable communication.
- TCP ensures that once information is sent from one BGP speaker to another, it does not need to be retransmitted unless changes occur.
- BGP speakers exchange keepalive messages to confirm connectivity and the validity of routes; absence of keepalives indicates route invalidity.
15
Q
Common AS Relationships and Policies
A
- Autonomous Systems (ASs) have different relationships reflecting common connectivity needs and business models.
- Three primary relationships are:
- Provider-Customer
- Customer-Provider
- Peer
- These policies ensure that traffic is routed efficiently and economically, aligning with the business interests of each AS.