The client sets the window size for the session.
The client sends an ISN to the server to start the 3-way handshake.
The client randomly selects a source port number.
The client sends a synchronization segment to begin the session.
The client randomly selects a source port number.
UDP ACK flag
TCP 3-way handshake
UDP sequence number
TCP port number
TCP 3-way handshake
0 to 255
0 to 1023
256 – 1023
1024 – 49151
0 to 1023
the combination of the source and destination IP address and source and destination Ethernet address
the combination of a source IP address and port number or a destination IP address and port number
the combination of the source and destination sequence and acknowledgment numbers
the combination of the source and destination sequence numbers and port numbers
the combination of a source IP address and port number or a destination IP address and port number
1 segment
10 segments
100 segments
1000 segments
10 segments
Explanation: With a window of 1000 bytes, the destination host accepts segments until all 1000 bytes of data have been received. Then the destination host sends an acknowledgment.
the amount of data the destination can process at one time
Explanation: Window is the number of bytes that the sender will send prior to expecting an acknowledgement from the destination device. The initial window is agreed upon during the session startup via the three-way handshake between source and destination. It is determined by how much data the destination device of a TCP session is able to accept and process at one time.
It just sends the datagrams.
It queries the server to see if it is ready to receive data.
It sends a simplified three-way handshake to the server.
It sends to the server a segment with the SYN flag set to synchronize the conversation.
It just sends the datagrams.
Explanation: When a client has UDP datagrams to send, it just sends the datagrams.
Window Size
Length
Source Port
Acknowledgment Number
Checksum
Sequence Number
Length
Source Port
Checksum
Explanation: A UDP header consists of only the Source Port, Destination Port, Length, and Checksum fields. Sequence Number, Acknowledgment Number, and Window Size are TCP header fields.
identifying the proper application for each communication stream
tracking the individual communication between applications on the source and destination hosts
providing frame delimiting to identify bits making up a frame
performing a cyclic redundancy check on the frame for errors
providing the interface between applications and the underlying network over which messages are transmitted
identifying the proper application for each communication stream
tracking the individual communication between applications on the source and destination hosts
Explanation: The transport layer has several responsibilities. The primary responsibilities include the following:
Tracking the individual communication streams between applications on the source and destination hosts
Segmenting data at the source and reassembling the data at the destination
Identifying the proper application for each communication stream through the use of port numbers
port numbers
sequence numbers
acknowledgment numbers
fragment numbers
sequence numbers
Explanation: At the transport layer, TCP uses the sequence numbers in the header of each TCP segment to reassemble the segments into the correct order.
destination and source port numbers
Destination devices receive traffic with minimal delay.
Transmitted data segments are tracked.
Destination devices reassemble messages and pass them to an application.
Received data is unacknowledged.
Unacknowledged data packets are retransmitted.
Destination devices receive traffic with minimal delay.
Received data is unacknowledged.
Explanation:
TCP:
Provides tracking of transmitted data segments
Destination devices will acknowledge received data.
Source devices will retransmit unacknowledged data.
UDP
Destination devices will not acknowledge received data
Headers use very little overhead and cause minimal delay.
VER IMAGEM
Explanation: In order to terminate a TCP session, the client sends to the server a segment with the FIN flag set. The server acknowledges the client by sending a segment with the ACK flag set. The server sends a FIN to the client to terminate the server to client session. The client acknowledges the termination by sending a segment with the ACK flag set.
FIN
ACK
SYN
RST
ACK
Explanation: In a TCP session, when a device has no more data to send, it will send a segment with the FIN flag set. The connected device that receives the segment will respond with an ACK to acknowledge that segment. The device that sent the ACK will then send a FIN message to close the connection it has with the other device. The sending of the FIN should be followed with the receipt of an ACK from the other device.
DNS
Explanation: Some applications may use both TCP and UDP. DNS uses UDP when clients send requests to a DNS server, and TCP when two DNS serves directly communicate.
UDP datagrams take the same path and arrive in the correct order at the destination.
Applications that use UDP are always considered unreliable.
UDP reassembles the received datagrams in the order they were received.
UDP only passes data to the network when the destination is ready to receive the data.
UDP reassembles the received datagrams in the order they were received.
Explanation: UDP has no way to reorder the datagrams into their transmission order, so UDP simply reassembles the data in the order it was received and forwards it to the application.
registered port
private port
dynamic port
source port
registered port
Explanation: Registered ports (numbers 1024 to 49151) are assigned by IANA to a requesting entity to use with specific processes or applications. These processes are primarily individual applications that a user has chosen to install, rather than common applications that would receive a well-known port number. For example, Cisco has registered port 1985 for its Hot Standby Routing Protocol (HSRP) process.
SMTP
FTP
SNMP
HTTP
TFTP
DHCP
SMTP
FTP
HTTP
Explanation: Some protocols require the reliable data transport that is provided by TCP. In addition, these protocols do not have real time communication requirements and can tolerate some data loss while minimizing protocol overhead. Examples of these protocols are SMTP, FTP, and HTTP.
UDP provides basic connectionless transport layer functions.
UDP provides connection-oriented, fast transport of data at Layer 3.
UDP relies on application layer protocols for error detection.
UDP is a low overhead protocol that does not provide sequencing or flow control mechanisms.
UDP relies on IP for error detection and recovery.
UDP provides sophisticated flow control mechanisms.
UDP provides basic connectionless transport layer functions.
UDP relies on application layer protocols for error detection.
UDP is a low overhead protocol that does not provide sequencing or flow control mechanisms.
Explanation: UDP is a simple protocol that provides the basic transport layer functions. It has much lower overhead than TCP because it is not connection-oriented and does not offer the sophisticated retransmission, sequencing, and flow control mechanisms that provide reliability.
window
checksum
source port
destination port
sequence number
window
sequence number
Explanation: The sequence number and window fields are included in the TCP header but not in the UDP header.
window
reserved
checksum
control bits
control bits
Explanation: The value in the control bits field of theTCP header indicates the progress and status of the connection.
to ensure the fastest possible download speed
because HTTP is a best-effort protocol
because transmission errors can be tolerated easily
because HTTP requires reliable delivery
because HTTP requires reliable delivery
Explanation: When a host requests a web page, transmission reliability and completeness must be guaranteed. Therefore, HTTP uses TCP as its transport layer protocol.
applications that need data flow control
applications that require reliable delivery
applications that handle reliability themselves
applications that need the reordering of segments
applications that can tolerate some data loss, but require little or no delay
applications that handle reliability themselves
applications that can tolerate some data loss, but require little or no delay
Explanation: Applications that can tolerate some data loss, require a simple request and reply, and handle reliability themselves are best suited for UDP. UDP has low overhead and no requirement of reliability. TCP provides services for reliability, controlling data flow, and the reordering of segments.
Source port numbers and destination port numbers are not necessary when UDP is the transport layer protocol being used for the communication.
Source port and destination port numbers are randomly generated.
If multiple conversations occur that are using the same service, the source port number is used to track the separate conversations.
Destination port numbers are assigned automatically and cannot be changed.
If multiple conversations occur that are using the same service, the source port number is used to track the separate conversations.
Explanation: Both UDP and TCP use port numbers to provide a unique identifier for each conversation. Source port numbers are randomly generated and are used to track different conversations. Destination port numbers identify specific services by using either a default port number for the service or a port number that is assigned manually by a system administrator.