1.1.2 - Concept of Network and TCP_IP Model (2).pptx
1. Concept of Network and TCP/IP Model
Broadband Faculty
Advanced Level Telecom Training Centre (ALTTC)
Bharat Sanchar Nigam Limited (BSNL)
2. Concept of Network and TCP/IP Model 2
Agenda
ā¢ Internet
ā¢ Comparison of TCP/IP & OSI
ā¢ Data Encapsulation
ā¢ TCP-IP Protocol Suite
ā¢ TCP/IP Protocol Documents
ā¢ TCP-IP Protocol Suite (IPv4 vs IPv6)
3. Concept of Network and TCP/IP Model 3
What is Internet?
ā¢ Internet is network of networks, with different
hardware/software technologies
ā¢ Also known by the name TCP/IP Internet
ā¢ Name TCP/IP is taken from the names of the one of
the transport layer protocols (Transport Control
Protocol) and the network layer protocol (Internet
Protocol)
ā¢ TCP/IP is backbone of the Internet
4. Concept of Network and TCP/IP Model 4
TCP/IP and OSI
ā¢ OSI is made of seven layers.
ā¢ TCP/IP protocol is made of five layers.
PHYSICAL
DATA LINK
NETWORK
TRANSPORT
APPLICATION
PHYSICAL
DATA LINK
NETWORK
TRANSPORT
SESSION
PRESENTATION
APPLICATION
OSI Model TCP/IP Model
5. Frame Head Trailer
Frame
Concept of Network and TCP/IP Model 5
Data Encapsulation
Data
Data
Data
TCP Header
TCP Segment
UDP Header
UDP Message
TCP-UDP Data
IP Header
IP Datagram
IP Header TCP-UDP Data
Application
TPT Layer
NW Layer
Data Link
6. D
P
N
T
A
Concept of Network and TCP/IP Model 6
TCP/IP Protocol Suite..
ICMP IGMP
RARP
ARP
FTP
SMTP
TELNET
HTTP
TFTP
NFS
SNMP
DNS
TCP UDP
IP
Protocols defined by the underlying networks
7. Concept of Network and TCP/IP Model 7
Applications using TCP
ā¢ File Transfer Protocol (FTP)
ā Provides the ability to upload and download files between hosts
on the network.
ā¢ Simple Mail Transport Protocol (SMTP)
ā Provides the ability to send mail between users on the network.
ā¢ TELNET
ā Provides the ability to login into a remote host and administer
the machine.
ā¢ Hyper Text Transfer Protocol (HTTP)
ā Provides the ability to supply web pages between a browser and
the server.
8. Concept of Network and TCP/IP Model 8
Applications using UDP
ā¢ Trivial File Transfer Protocol (TFTP)
ā Provides simplex file transfer for network booting of devices.
ā¢ Network File System (NFS)
ā Provides the ability for sharing directories between hosts on the
network.
ā¢ Simple N/w Management Protocol (SNMP)
ā Provides the ability to supply network management services on
the network.
ā¢ Domain Name Service (DNS)
ā Provides mapping between domain name and IP address and
vice versa.
9. Concept of Network and TCP/IP Model 9
TCP Details
ā¢ Provides application programs access to the network
using a reliable connection-oriented transport layer
service
ā¢ TCP sends and receives data reliably using sequence
numbers and acknowledgements
ā¢ TCP is a byte oriented protocol i.e. every byte in each
packet is assigned a sequence number
ā¢ Data stream handed over to TCP is called an unstructured
stream
ā¢ TCP divides this data stream into segments for
transmission to remote network
10. TCP Header..
Octet +0 Octet +1 Octet +2 Octet +3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
SOURCE PORT DESTINATION PORT
SEQUENCE NUMBER
ACKNOWLEDGEMENT NUMBER
HELEN
U
R
G
A
C
K
P
S
H
R
S
T
S
Y
N
F
I
N
WINDOW SIZE
CHECKSUM URGENT POINTER
OPTIONS AND PADDING
10
Concept of Network and TCP/IP Model
11. Concept of Network and TCP/IP Model 11
TCP Headerā¦
ā¢ Source & Destination Port (16 Bits)
ā Can run number of applications using same transport by multiplexing through port
numbers
ā Port numbers are used to identify a unique application in a machine
ā 65536 (0-65535) port numbers can be defined
ā Theoretically it is possible to run 65535 simultaneous applications in a host
ā The first 1024 ports, port numbers 0-1023 known as well known port numbers, are
assigned and are reserved for standard applications and are controlled by IANA
ā The remaining ports, 1024-65535, are dynamic and can be used freely by
applications
ā Source port is randomly generated by the source machine
12. Concept of Network and TCP/IP Model 12
Well known port numbers
PORT DESCRIPTION
20 File Transfer-Data
21 File Transfer-Control
23 Telnet
25 SMTP
53 Domain Name Server
69 Trivial File Transfer
80 WWW
123 Network Time Protocol
179 Border Gateway Protocol
13. Concept of Network and TCP/IP Model 13
TCP Headerā¦
ā¢ Sequence Number (32 Bits)
ā Helps in establishing TCP connections, along with SYN bit, called as Three
Way Handshake
ā Helps in maintaining account of amount of data being transferred
ā Identifies where the encapsulated data fits within a data stream from the
sender
ā Sequence number is incremented, in the system, every 4 microsecond
ā¢ Acknowledgement Number (32 Bits)
ā Helps in maintaining account of amount of data being transferred
ā Identifies the sequence number expected from the other end of data
transmission unit
14. Concept of Network and TCP/IP Model 14
Seq/Ack numbers relation
ā¢ During TCP Connection Establishment / Three way
handshake
ā Acknowledgement Number Sent = Sequence Number Received+1
ā¢ During Data Transfer
ā Acknowledgement Number Sent = Sequence Number Received + Data
Received in Bytes
17. Closing a TCP Connection
Receiver
Sender
6-Finish; 0- Closed
0 0
6
SN - 95880
AN -17334
0B
1
1
0 SN - 17334
AN - 95881
0B
0
1
0
WAIT
SN - 17334
AN - 95881
0 B
1
1
0
6
SN - 95881
AN -17334
0B
0
1
0
17
Concept of Network and TCP/IP Model
18. Concept of Network and TCP/IP Model 18
TCP Headerā¦.
ā¢ Header Length (4 Bits)
ā Sometimes called Data Offset
ā Indicates the length of header in 32-bit words
ā Identifies the beginning of data
ā Typical value is 5 unless there are options
ā¢ Flags (6 Bits)
ā Urgent (URG)
ā Acknowledgement (ACK)
ā Push (PSH)
ā Reset (RST)
ā Synchronisation (SYN)
ā Finish (FIN)
19. Concept of Network and TCP/IP Model 19
TCP Headerā¦..
ā¢ Window Size (16 Bits)
ā Indicates the size of the sliding window
ā Specifies the number of octets, starting with the octet
indicated by the acknowledgement number, that the
sender of the segment will accept from its peer at the
other end of the connection before the peer must
stop transmitting and wait for an acknowledgement
ā A default window size is 4096 bytes
ā Used for flow control by using Sliding window
mechanism
20. Concept of Network and TCP/IP Model 20
Flow Control
ā¢ Sender retains a copy of transmitted data until it receives an
acknowledgment from the remote network.
ā¢ If no acknowledgment is received, within a specified time, the data
is retransmitted by using adaptive retransmission algorithm.
ā TCP records the time of the transmission and sequence number of the
segment.
ā TCP again records the time of the acknowledgement received.
ā Using this delta, TCP builds a sample round-trip delay time and uses this to
build an average time for a packet to be sent and to receive an
acknowledgement
ā¢ TCP will time out after a number of unsuccessful retransmissions
21. Concept of Network and TCP/IP Model 21
Sliding Window-Flow Control
Moves to right when
ack is received.
Moves to right when
data is sent.
Moves to right or left to fix
the size of the window.
Window Size
Sent and ack
Sent but not ack
Can be sent
Canāt be sent
22. Concept of Network and TCP/IP Model 22
TCP Headerā¦..
ā¢ Checksum(16 Bits)
ā Used for error detection
ā Covers both header and the encapsulated data
ā¢ Urgent Pointer(16 Bits)
ā Used only when urgent flag is set
ā Points to the last octet of urgent data
ā¢ Options
ā One of the important options is MSS (Maximum Segment
Size)
ā¢ Informs the receiver of the largest segment the sender is willing to
accept, without causing fragmentation
23. Concept of Network and TCP/IP Model 23
TCP Headerā¦ā¦
ā¢ Padding
ā Consists of 1-3 octets, each equal to zero, to force
the length of TCP header to be in multiples of four
octets.
24. Concept of Network and TCP/IP Model 24
User Datagram Protocol
ā¢ Provides unreliable connectionless service
ā¢ Transfers data without establishing a session
ā¢ Used for services that have an inbuilt reliability
ā¢ Does not use end to end error checking and correction
ā¢ Does not order the packets; may loose or duplicate a
packet
ā¢ Runs faster than TCP due to less overheads
26. Concept of Network and TCP/IP Model 26
UDP Header...
ā¢ Source Port (16 Bits)
ā Identifies the sending process.
ā¢ Destination Port (16 Bits)
ā Identifies the receiving process.
ā Some fixed, pre-assigned port numbers used for services on the Internet.
ā¢ 7 for UDP; 69 for TFTP
ā¢ Message length (16 Bits)
ā Indicates the size of the UDP header and its data in bytes.
ā Minimum size is 8, if carries no data.
ā¢ Checksum (16 Bits)
ā Covers the UDP header and UDP data.
ā Optional; If not used, set to all zeros.
27. Concept of Network and TCP/IP Model 27
Internet Protocol.
ā¢ Provides best-effort or connectionless delivery service.
ā¢ No error checking or tracking
ā¢ If reliability is important, IP must be paired with a reliable
protocol like TCP
ā¢ Transmits blocks of data called datagrams each of which
is transported separately
ā¢ Responsible for IP addressing
ā¢ Datagrams may travel along different routes and may
arrive out of sequence or duplicated.
28. IP Header..
Octet +0 Octet +1 Octet +2 Octet +3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
VER HLEN TOS TOTAL LENGTH
IDENTIFICATION D
F
M
F FRAGMENT OFFSET
TIME TO LIVE PROTOCOL HEADER CHECKSUM
SOURCE ADDRESS OF HOST
DESTINATION ADDRESS OF HOST
OPTIONS PADDING
28
Concept of Network and TCP/IP Model
29. Concept of Network and TCP/IP Model 29
IP Headerā¦
ā¢ Version (4 Bits)
ā Identifies the IP version to which the packet belongs
ā¢ Header Length (4 Bits)
ā Indicates the length of IP header in 32 bit words.
ā Minimum length is 20 octets.
ā Options may increase the size up to a maximum of 24 octets.
ā¢ Type of Service (8 Bits)
ā Used for specifying special handling of packet.
ā Has two sub-fields:
ā¢ Precedence
ā¢ TOS
30. Concept of Network and TCP/IP Model 30
IP Headerā¦.
0
C
R
T
D
P
P
P
Reliability
0-Normal
1-Maximise
Precedence
000-Routine
001-Priority
010-Immediate
011-Flash
100-Flash Override
101-CRITIC/ECP
110-Internetwork Control
111-Network Control
Delay
0-Normal
1-Minimise
Throughput
0-Normal
1-Maximise
Cost
0-Normal
1-Minimise
Reserved:
Always set to ā0ā
0 = No TOS
0
0
0
0
0
0
0
31. Concept of Network and TCP/IP Model 31
IP Headerā¦..
ā¢ Total Length (16 Bits)
ā Specifies total length of the packet, including header, in octets
ā Largest decimal number =216= 65535, the maximum possible
size of an IP packet is 65535 octets
ā Total length - header length = Packetās data payload
ā¢ Identification (16 Bits)
ā Each datagram is identified by a identification number set by the
source.
ā Normally incremented by 1 for each datagram sent.
32. Concept of Network and TCP/IP Model 32
IP Headerā¦ā¦
ā¢ Flags (3 Bits)
ā First bit is not used.
ā Second bit is Donāt Fragment (DF) bit
ā Third bit if More Fragment (MF) bit
ā¢ Maximum Transmit Unit (MTU) is the size of the largest packet,
including IP Header, that can be transmitted or received through a
data link
ā¢ Default MTU is 576 bytes, which can be handled by any network
without fragmentation
33. Concept of Network and TCP/IP Model 33
IP Headerā¦ā¦
ā¢ Fragment Offset (13 Bits)
ā The fragmentation occurs at the routers, if the original packet
length exceeds the MTU of a data link
ā Used only in the cases when a datagram is fragmented on its
way
ā Specifies the offset, in units of eight octets, from the beginning
of header to the beginning of the fragment
ā Each fragment is marked, by router, with the same identifier
number
34. Concept of Network and TCP/IP Model 34
Fragmentation..
172.16.2.0 172.16.3.0
MTU-1500 MTU-1500
MTU-576
Data
TCP
IP
1500 B
Data
TCP
IP
512 B
Data
512 B
Data
476 B
Data
TCP
IP Data Data
Data
TCP
IP
IP IP IP
DF=0; MF=1; Offset=0 DF=0; MF=1; Offset=64 DF=0; MF=0; Offset=128
35. Concept of Network and TCP/IP Model 35
Fragmentation
ā¢ Only the receiver host reassembles the datagram
ā¢ The destination machine starts a reassembly timer
for about 60-120 seconds.
ā¢ If not all fragments were received, then hosts discard
the packets and sends a time exceeded ICMP
message to the source machine
ā¢ If a single fragment is lost during a transmission, the
entire packet must be resent
36. Concept of Network and TCP/IP Model 36
IP Headerā¦ā¦
ā¢ Time to live-TTL (8 Bits)
ā Assigns a life to an IP datagram
ā¢ Protocol (8 Bits)
ā Specifies the protocol that runs on the top of IP.
ā TCP-6; EGP-8; UDP-17; OSPF-89
ā¢ Header Checksum (16 Bits)
ā Error detection field for IP header
ā As each router decrements the TTL, the checksum is
calculated by each router
37. Concept of Network and TCP/IP Model 37
IP Headerā¦ā¦.
ā¢ Source Address of Host (32 Bits)
ā IP Address of the Originating Machine
ā¢ Destination Address of Host (32 Bits)
ā IP Address of the Destination Machine
ā¢ Options
ā Security:
ā¢ Specifies how secret the datagram is
ā Strict Source Routing(SSR):
ā¢ Gives the complete path to be followed
ā Loose Source Routing(LSR):
ā¢ Gives the list of routers not to be missed
38. Concept of Network and TCP/IP Model 38
IP Headerā¦ā¦..
ā Record Route:
ā¢ Makes each router to append its IP address.
ā Time Stamp:
ā¢ Makes each router to append its IP address and time
stamp.
ā¢ Padding
ā Ensures that the header ends on a 32 bit
boundary by adding zeros after the option field.
39. Concept of Network and TCP/IP Model 39
Underlying Networks Protocols
ā¢ Ethernet
ā¢ Token Ring
ā¢ FDDI
ā Fiber Distributed Data Interface
ā¢ HDLC
ā High-level Data Link Control
ā¢ Frame Relay
ā¢ PPP
ā Point-to-Point Protocol
ā¢ ATM
ā Asynchronous Transfer Mode
40. Concept of Network and TCP/IP Model 40
Socket Connection..
ā¢ Ports along with an IP address, known as socket
connection, allow any application in any machine on
an internet to be uniquely defined.
ā¢ Multiple applications can run simultaneously on a
host by making use of separate socket connection for
each application.
41. Concept of Network and TCP/IP Model 41
Socket Connection-Multiplexing
DATA
DATA
3753-53
2764-21
DATA
DATA
DATA 3753-53
2764-21
DATA
A.B.C.D-E.F.G.H
A.B.C.D-E.F.G.H
A.B.C.D-E.F.G.H
DATA 3753-53
2764-21
DATA A.B.C.D-E.F.G.H
TRAILER
TRAILER HEADER
HEADER
D
P
N
T
DNS
FTP
2764 3753
TCP UDP
IP
A.B.C.D
DNS
FTP
21 53
TCP UDP
E.F.G.H
1. A.B.C.D(2764) ā E.F.G.H(21) 2. A.B.C.D(3753) ā E.F.G.H(53)
42. Concept of Network and TCP/IP Model 42
Socket Connection-Demultiplexing
D
P
N
T
DNS
FTP
2764 3753
TCP UDP
IP
A.B.C.D
DNS
FTP
21 53
TCP UDP
E.F.G.H
53- 3753
21- 2764
DATA
DATA
DATA 53- 3753
21- 2764
DATA
E.F.G.H-A.B.C.D
E.F.G.H-A.B.C.D
DATA
DATA
E.F.G.H-A.B.C.D
DATA 53- 3753
21- 2764
DATA E.F.G.H-A.B.C.D
TRAILER
TRAILER HEADER
HEADER
1. A.B.C.D(2764) ā E.F.G.H(21) 2. A.B.C.D(3753) ā E.F.G.H(53)
43. Concept of Network and TCP/IP Model 43
Internet Control Message Protocol
ā¢ Internet Control Message Protocol is a mechanism used
by hosts and routers to send notification of datagram
problems back to the sender.
ā¢ Sends error messages only to the source and not to
intermediate routers.
ā¢ Sole function is to report problems, not to correct them.
ā¢ An important use of ICMP is echo/reply to test whether a
destination is reachable and responding.
44. Concept of Network and TCP/IP Model 44
Internet Control Message Protocol
ā¢ Echo request/reply (PING; Packet INternet Gropher)
ā Destination unreachable
0-Network unreachable
1-Host unreachable
2-Protocol unreachable
3-Port unreachable
4-Fragment needed but DF bit is set
5-Source route failed
6-Destination network unknown
45. Concept of Network and TCP/IP Model 45
Internet Control Message Protocol
7-Destination host unknown
8-Source host isolated
9-Communication with destination network administratively
prohibited
10-Communication with destination host administratively prohibited
11-Network unreachable for type of service
12-Host unreachable for type of service
ā Time exceeded message format
ā¢ 0-TTL exceeded
ā¢ 1-Fragment reassembly time exceeded
46. Concept of Network and TCP/IP Model 46
Internet Group Message Protocol
ā¢ Internet Group Message Protocol provides allows for
multicast to operate on an internetwork.
ā Multicast is one-to-many communication.
ā A message sent can be simultaneously received by
a group of hosts.
ā¢ Special type of Class-D IP addresses, starting with
1110, are reserved as multicast addresses.
47. Concept of Network and TCP/IP Model 47
Address Resolution Protocol
ā¢ Address Resolution Protocol is used to translate 32
bits IP addresses to 48 bits Ethernet addresses.
ā¢ A hostās physical address is determined by
broadcasting its IP address to all machines.
ā¢ The machine with matching IP address, in broadcast
message, sends its hardware address to the machine
originating broadcast.
48. Concept of Network and TCP/IP Model 48
ARP Operation
Request
Ignored
Request
Ignored
ARP
Response
Accepted
Give me MAC address of 129.1.1.4
Thatās
Me
Here is my MAC address
129.1.1.1 129.1.1.4
129.1.1.2 129.1.1.3
08-00-39-00-2F-C3
08-00-10-99-AC-54
08-00-5A-21-A7-22
08-00-39-00-2F-AB
49. Concept of Network and TCP/IP Model 49
Reverse Address Resolution Protocol
ā¢ Reverse Address Resolution Protocol is used to get
the 32 bits Source IP address, knowing the 48 bits
Hardware address.
ā¢ It is reverse of ARP, hence named Reverse Address
Resolution Protocol.
ā¢ A diskless workstation broadcasts RARP-Request to
find its IP Address at the time of boot up.
50. Concept of Network and TCP/IP Model 50
RARP Operation
Give me my IP address RARP Response
Diskless
work
station
RARP
Server
08-00-39-00-2F-C3 08-00-10-99-AC-54
08-00-5A-21-A7-22
223.1.2.1
223.1.2.2
223.1.2.3
08-00-39-00-2F-AB
51. Concept of Network and TCP/IP Model 51
IPv4 vs IPv6
ā¢ Some independent protocols of version 4 are part of
ICMPv6.
ā RARP protocol is dropped from the suite.
ā ARP and IGMP are combined with ICMPv6.
ICMP IGMP
RARP
ARP
IPv4
ICMP
IPv6
52. IPv6 Base Header
Octet +0 Octet +1 Octet +2 Octet +3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
VER PRI FLOW LABEL
PAYLOAD LENGTH NEXT HEADER HOP LIMIT
SOURCE ADDRESS
(128 Bits)
DESTINATION ADDRESS
(128 Bits)
PAYLOAD (0-65535 Bytes)
(EXTENSION HEADERS + DATA PACKETS FROM UPPER LAYERS)
52
Concept of Network and TCP/IP Model
53. Concept of Network and TCP/IP Model 53
TCP/IP Protocol Documents
ā¢ TCP/IP technical documents are known as Request
For Comments (RFCs).
ā¢ Once issued, RFC do not change.
ā Updated by new RFCs.
ā RFCs can be obsoleted but their numbers are
never used again.
ā¢ A major source for RFCs is the Internet Engineering
Task Force and are accessible on site www.ietf.org