16
Several Design Issues at Network layer Implementation of Connectionless Services Implementation of Connection oriented Services Comparison of datagram subnet and virtual-circuit subnet Ashish Dubey(9) Hansel Gonsalves(12) Kashyap Davariya(7)

Final several design issues at network layer

Embed Size (px)

Citation preview

Page 1: Final several design issues at network layer

Several Design Issues at Network layer

Implementation of Connectionless ServicesImplementation of Connection oriented Services Comparison of datagram subnet and virtual-

circuit subnet

Ashish Dubey(9)Hansel Gonsalves(12)Kashyap Davariya(7)

Page 2: Final several design issues at network layer

Implementation of Connectionless Services

• In Connectionless Service, no need to establish connection

• In this packets are injected into subnet and routed independently of each other.

• No advance set up is needed• In this context the packets are frequently

called datagram and subnet is called datagram subnet.

Page 3: Final several design issues at network layer

Routing within a datagram subnet

Page 4: Final several design issues at network layer

• Let see the working of datagram subnet.• Suppose process p1 has long message for process

p2.• It hands message with instructions to transport

layer to deliver it to process 2 on host 2.• The transport layer code runs on H1,within an OS.• It prepends a transport header to the front of

message and hands the result to the network layer.

Page 5: Final several design issues at network layer

• Assume that message is four times longer than maximum packet size.

• The Network layer breaks it into four packets 1, 2 ,3 and 4 and sends all to router A using point-to-point protocol.

• At this point carrier takes over.• Every router has an internal table that tells

where to send packets for each possible destinations.

Page 6: Final several design issues at network layer

• Each table entry is a pair consisting of a destination and the outgoing line to use for that destination.

• Only directly connected lines can be used.• For eg: A has only two outgoing lines - to B

and C - so every incoming packet must be sent to one of these routers, even if ultimate destination is some other router.

Page 7: Final several design issues at network layer

• As packets arrived at A, packets 1, 2 and 3 were stored briefly(to verify their checksums).

• Then each was forwarded to C according to A’s table .

• Packet 1 was then forwarded to C according to A’s table.

• Packet 1 was then forwarded to E and then to F and at F it was encapsulated in datalink layer frame and sent to H2 over the LAN.

Page 8: Final several design issues at network layer

• Packet 2 and 3 follow the same route.• However packet 4 was routed at different

router(i.e at B) for some reason.• Perhaps it learned of traffic jam somewhere

along the ACE path and updated its router table as “later”.

• The algorithm that manages the tables and makes the routing decisions is called Routing Algorithm.

Page 9: Final several design issues at network layer

Implementation of Connection Oriented Services

• In this a connection is established.• A path from source to the destination router

must be established before any packets can be sent.

• This connection is virtual circuit with physical circuit set up by the telephone system

• Subnet is called virtual circuit subnet.• The particular route choosen is used for all

traffic flowing over the connection.

Page 10: Final several design issues at network layer

• With connection oriented service , each packet carries an identifier telling which virtual circuit it belongs.

Page 11: Final several design issues at network layer

Routing within a virtual-circuit subnet.

Page 12: Final several design issues at network layer

• Here , host H1 has established a connection 1 with host H2.

• It is remembered as the first entry in each of the routing tables.

• The first lines of A’s table says that if a packet bearing connection identifier 1 comes from H1, it to be sent to router C and given a connection identifier 1.

• Similarly, the first entry at C routes the packet to E, also with connection identifier 1.

Page 13: Final several design issues at network layer

• Now let consider what happens if H3 also wants to establish a connection to H2.

• It chooses identifier 1(because it is initiating the connection and this is its only connection) and tells the subnet to establish the virtual circuit.

• This leads to the second row in the tables.• Note that we have a conflict here because although

A can easily distinguish connection 1 packets from H1 from connection 1 packets from H3 , C cannot do this.

Page 14: Final several design issues at network layer

• For this reason, A assigns a different connection identifier to the outgoing traffic for the second connection.

• Avoiding conflicts of this kind is why routers need the ability to replace connection identifiers in outgoing packets.

• In some contexts, this is called label swithing.

Page 15: Final several design issues at network layer

Comparison of datagram subnet and virtual-circuit subnet

Issue Datagram Subnets Virtual-Circuit Subnet

Circuit set up Not required Required

Addressing Each packet contains the source as well as destination address

Each packet contains a short VC number

State information Subnet does not hold state information

A table is needed to hold the state information

Routing Each packet is routed independently

Route chosen when VC is setup; all packet follow this route

Page 16: Final several design issues at network layer

Comparison of datagram subnet and virtual-circuit subnet

Issue Datagram Subnets Virtual-Circuit Subnet

Effect of router failure No other effect except for the packets lost at the time of crash

All VCs which passed through failed router are terminated.

Quality of service Easy if enough resources can be allocated in advance for each VC.

Difficult

Congestion control Easy if enough resources can be allocated in advance for each VC.

Difficult