IPV4 (Internet Protocol version 4)

MAC header IP header Data :::

0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Version IHL TOS Total length

Identification Flags Fragment offset

TTL Protocol Header checksum

Source IP address

Destination IP address

Options and padding :::

IPV4 (Internet Protocol
version 4)
 Version. 4 bits.
 IHL, Internet Header Length. 4 bits.
Specifies the length of the IP packet header
in 32 bit words. The minimum value for a
valid header is 5.
 ToS, Type of Service. 8 bits.
Specifies the parameters for the type of
service requested. The parameters may be
utilized by networks to define the handling of
the datagram during transport. The M bit was
added to this field in RFC 1349.
 IPV4 (Internet Protocol
version 4)

00 01 02 03 04 05 06 07

Precedence D T R M 0

Total length. 16 bits.

Contains the length of the datagram.
IPV4 (Internet Protocol
version 4)
 Total length. 16 bits.
Contains the length of the datagram.
 Identification. 16 bits.
Used to identify the fragments of one datagram from
those of another. The originating protocol module of
an internet datagram sets the identification field to a
value that must be unique for that source-destination
pair and protocol for the time the datagram will be
active in the internet system. The originating protocol
module of a complete datagram clears the MF bit to
zero and the Fragment Offset field to zero
 IPV4 (Internet Protocol
version 4)
 Flags. 3 bits.
00 01 02

R DF MF

•R, Reserved. 1 bit.

Should be set to 0.
•DF, Don't fragment. 1 bit.
Controls the fragmentation of the datagram.
Value Description
0 Fragment if necessary.
1 Do not fragment.
 IPV4 (Internet Protocol
version 4)
•MF, More fragments. 1 bit.
Indicates if the datagram contains additional
fragments.

Value Description
0 This is the last fragment.
1 More fragments follow this fragment.
IPV4 (Internet Protocol
version 4)
 Fragment Offset. 13 bits.
Used to direct the reassembly of a
fragmented datagram.
 TTL, Time to Live. 8 bits.
A timer field used to track the lifetime of the
datagram. When the TTL field is decremented
down to zero, the datagram is discarded.
 Protocol. 8 bits.
This field specifies the next encapsulated
protocol.
 Options. Variable length.
 TCP (Transmission Control
Protocol )
MAC header IP header TCP header Data :::

0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0
Source Port Destination Port
Sequence Number
Acknowledgment Number
Data Offset reserved ECN Control Bits Window
Checksum Urgent Pointer
Options and padding :::
Data :::
TCP
 Source Port. 16 bits.
 Destination Port. 16 bits.
 Sequence Number. 32 bits.
The sequence number of the first data byte in this
segment. If the SYN bit is set, the sequence number
is the initial sequence number and the first data byte
is initial sequence number + 1.
 Acknowledgment Number. 32 bits.
If the ACK bit is set, this field contains the value of
the next sequence number the sender of the
segment is expecting to receive. Once a connection is
established this is always sent.
TCP
 Data Offset. 4 bits.
The number of 32-bit words in the TCP
header. This indicates where the data begins.
The length of the TCP header is always a
multiple of 32 bits.
 reserved. 4 bits.
Must be set to zero.
 ECN, Explicit Congestion Notification. 2
bits.
Added in RFC 3168.
TCP
 Checksum. 16 bits.
This is computed as the 16-bit one's
complement of the one's complement sum of
a pseudo header of information from the IP
header, the TCP header, and the data,
padded as needed with zero bytes at the end
to make a multiple of two bytes
 Data. Variable length.
TCP

Control Bits. 6 bits.

00 01 02 03 04 05
U A P R S F
TCP
 ACK
 Value showing the acknowledgement number of segment
 PSH
 Push the data
 RST
 Value showing the connection is resetting
 SYN
 Synchronize sequence number during convention
 FIN
 Terminate the connection
 UDP (User Datagram Protocol )

MAC header IP header UDP header Data :::

0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0

Source Port Destination Port

Length Checksum

Data :::
UDP
 Source Port. 16 bits.
This is an optional field. If it is not used, it is cleared to zero.
Otherwise, it specifies the port of the sender.
 Destination Port. 16 bits.
The port this packet is addressed to.
 Length. 16 bits.
The length in bytes of the UDP header and the encapsulated data. The
minimum value for this field is 8.
 Checksum. 16 bits.
This is computed as the 16-bit one's complement of the one's
complement sum of a pseudo header of information from the IP
header, the UDP header, and the data, padded as needed with zero
bytes at the end to make a multiple of two bytes. If the checksum is
 set to zero, then checksuming is disabled. If the computed checksum is
zero, then this field must be set to 0xFFFF
 Data. Variable length.
PPP (Point to Point Protocol)

Addre Contr Protocol Informat FCS

ss ol ion

1 byte 1 byte 2 bytes Variable 2 bytes

PPP header structure

PPP
 Address
HDLC broadcast address. PPP does not assign individual station
addresses. The value of this field is always set to FF Hex.
 Control
HDLC command for Unnumbered Information (UI) with the Poll/Final
bit set to zero. The value of this field is always set to 03 Hex. Frames
containing any other value in this field are discarded.
 Protocol
identifies the encapsulated protocol within the Information field of the
frame.
 Information
Higher-level protocol data.
 FCS
Value of the frame checksum calculation. PPP verifies the contents of
the FCS field upon receipt of the packet
 RSVP (Resource Reservation Protocol )

MAC header IP header RSVP header Data :::

0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0
Version Flags Message type RSVP checksum
TTL reserved RSVP length
Data :::
RSVP
 Version. 4 bits.
RSVP version number.
 Flags. 4 bits.
 Message type. 8 bits.
 RSVP checksum. 16 bits.
The one's complement of the one's
complement sum of the message, with the
checksum field replaced by zero for the
purpose of computing the checksum. An all-
zero value means that no checksum was
transmitted.
RSVP
 TTL, Time to Live. 8 bits.
The IP TTL value with which the message
was sent.
 reserved. 8 bits.
 RSVP length. 16 bits.
The total length of this RSVP message in
bytes, including the common header and the
variable length objects that follow.
 Data. Variable length.
 Real Time Protocol RFC1889

V
E
Payload
4 bytes CC M Sequence Number
R Type

4 bytes RTP Timestamp

4 bytes Synchronization Source (SSRC) ID
Real Time Protocol RFC1889
 Ver, Version. 2 bits.
RTP version number. Always set to 2.
 P, Padding. 1 bit.
If set, this packet contains one or more additional
padding bytes at the end which are not part of the
payload. The last byte of the padding contains a
count of how many padding bytes should be ignored.
Padding may be needed by some encryption
algorithms with fixed block sizes or for carrying
several RTP packets in a lower-layer protocol data
unit.
Real Time Protocol RFC1889
 X, Extension. 1 bit.
If set, the fixed header is followed by exactly
one header extension.
 CC, CSRC count. 4 bits.
The number of CSRC identifiers that follow
the fixed header.
 M=bit is an application-specific marker bit
 Payload Type=tells which encoding algorithm
is used
(Uncompressed 8-bit audio,MP3,etc…)
 Real Time Protocol RFC1889
 Sequence Number=Incremented on every RTP
packet.
 Timestamps=produced by the stream’s source to
note when the first sample in packet is made.it is
helpful to reduce jitter at receiver by decoupling of
the play back from the arrival time.
 Synchronization Source Identifier tells which stream
the packet belongs to.it is the method used to
multiplex and demultiplex multiple data streams onto
a single stream of UDP packets
 RTCP (RTP Control Protocol)
MAC header IP header UDP header RTCP header Data :::

0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0

Ver P Count Type Length

sion

Data :::
RTCP (RTP Control Protocol)
 Version. 2 bits.
The version of RTP which is the same in RTCP
packets as in RTP data packets.
 P, Padding. 1 bit.
If set, this RTCP packet contains some additional
padding bytes at the end which are not part of the
control information. The last byte of the padding is a
count of how many padding bytes should be ignored.
Padding may be needed by some encryption
algorithms with fixed block sizes. In a compound
RTCP packet, padding should only be required on the
last individual packet because the compound packet
is encrypted as a whole.
RTCP (RTP Control Protocol)
 Count. 5 bits. 0 to 31.
The number of reception report blocks contained in
this packet.
 Type. 8 bits.
RTCP packet type.
 Length. 16 bits.
The length of this RTCP packet in 32 bit words minus
one, including the header and any padding. The
offset of one makes zero a valid length and avoids a
possible infinite loop in scanning a compound RTCP
packet, while counting 32 bit words avoids a validity
check for a multiple of 4.