Editing Handshake (computing) (section)

== Example ==

=== TCP three-way handshake ===
[[File:Three-way-handshake-example.gif|thumbnail|right|500px|Example of three way handshaking]]
Establishing a normal [[Transmission Control Protocol#Connection establishment|TCP]] connection requires three separate steps:
:# The first host (Alice) sends the second host (Bob) a "synchronize" (SYN) message with its own sequence number <math>x</math>, which Bob receives.
:# Bob replies with a synchronize-acknowledgment ([[SYN-ACK]]) message with its own sequence number <math>y</math> and acknowledgement number <math>x + 1</math>, which Alice receives.
:# Alice replies with an acknowledgment (ACK) message with acknowledgement number <math>y + 1</math>, which Bob receives and to which he doesn't need to reply.
: In this setup, the synchronize messages act as service requests from one server to the other, while the acknowledgement messages return to the requesting server to let it know the message was received.

The reason for the client and server not using a default sequence number such as 0 for establishing the connection is to protect against two incarnations of the same connection reusing the same sequence number too soon, which means a segment from an earlier incarnation of a connection might interfere with a later incarnation of the connection.

=== SMTP === 
 
The [[Simple Mail Transfer Protocol]] (SMTP) is the key Internet standard for email transmission. It [[Simple Mail Transfer Protocol#SMTP transport example|includes handshaking]] to negotiate authentication, encryption and maximum message size. 

=== TLS handshake ===
{{Main|Transport Layer Security#TLS handshake}}
When a [[Transport Layer Security]] (SSL or TLS) connection starts, the record encapsulates a "control" protocol—the handshake messaging protocol  (content type 22). This protocol is used to exchange all the information required by both sides for the exchange of the actual application data by TLS. It defines the messages formatting or containing this information and the order of their exchange. These may vary according to the demands of the client and server—i.e., there are several possible procedures to set up the connection. This initial exchange results in a successful TLS connection (both parties ready to transfer application data with TLS) or an alert message (as specified below).

The protocol is used to negotiate the secure attributes of a session. (RFC 5246, p.&nbsp;37)<ref>{{cite IETF |rfc=5246 |title=The Transport Layer Security (TLS) Protocol, version 1.2 |publisher=[[IETF]] |date=August 2008 }}</ref>

=== WPA2 wireless ===
The [[Wi-Fi Protected Access#WPA2|WPA2 standard for wireless]] uses a four-way handshake defined in [[IEEE 802.11i-2004]].

=== Dial-up access modems ===
One classic example of handshaking is that of [[dial-up modem]]s, which typically negotiate communication parameters for a brief period when a connection is first established, and there after use those parameters to provide optimal information transfer over the channel as a function of its quality and capacity. The "squealing" (which is actually a sound that changes in pitch 100 times every second) noises made by some modems with speaker output immediately after a connection is established are in fact the sounds of modems at both ends engaging in a handshaking procedure; once the procedure is completed, the speaker might be silenced, depending on the settings of operating system or the application controlling the modem.

=== Serial "Hardware Handshaking" ===

This frequently used term describes the use of RTS and CTS signals over a serial interconnection.  It is, however, not quite correct;{{cn|date=February 2021}} it's not a true form of handshaking, and is better described as [[RS-232|flow control]].

=== Mobile device charging ===
In mobile device chargers offering special quick-charge abilities to supported devices, the charging process will switch up to a higher output voltage for increased power transfer. But this could cause serious damage to an unsupported device or even result in a fire. It is therefore very important for the device and charger to first perform a handshake to "agree" on mutually supported charge parameters. If such a charger can't identify the connected device or determine its compatibility, it will default to normal but much slower charge parameters within the USB standard.