User Datagram Protocol

<h2 id="attributes">Attributes</h2>
UDP is a simple message-oriented <a href="/facts/Transport_layer/UmIGUCeK">transport layer</a> protocol that is documented in RFC <a href="https://datatracker.ietf.org/doc/html/rfc768">768</a>. Although UDP provides integrity verification (via <a href="/facts/Checksum/AqxQ0I8g">checksum</a>) of the header and payload,<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a> it provides no guarantees to the <a href="/facts/Upper_layer_protocol/xttAQnu0">upper layer protocol</a> for message delivery and the UDP layer retains no state of UDP messages once sent. For this reason, UDP sometimes is referred to as <a href="/facts/Reliability_(computer_networking)/v3kGvfvs">Unreliable</a> Datagram Protocol.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a> If transmission reliability is desired, it must be implemented in the user's application.
A number of UDP's attributes make it especially suited for certain applications.

<ul><li>It is transaction-oriented, suitable for simple query-response protocols such as the <a href="/facts/Domain_Name_System/rfxdWFsj">Domain Name System</a> or the <a href="/facts/Network_Time_Protocol/vS21KqT5">Network Time Protocol</a>.</li>
<li>It provides <a href="/facts/Datagram/TMHVctMz">datagrams</a>, suitable for modeling other protocols such as <a href="/facts/IP_tunneling/GW7aeJyI">IP tunneling</a> or <a href="/facts/Remote_procedure_call/uMMb9CQw">remote procedure call</a> and the <a href="/facts/Network_File_System/jWRRALVo">Network File System</a>.</li>
<li>It is simple, suitable for <a href="/facts/Bootstrapping/6dkM4EQv">bootstrapping</a> or other purposes without a full <a href="/facts/Protocol_stack/Btj9FtwJ">protocol stack</a>, such as the <a href="/facts/DHCP/lpASHnhz">DHCP</a> and <a href="/facts/Trivial_File_Transfer_Protocol/TslBlcvJ">Trivial File Transfer Protocol</a>.</li>
<li>It is stateless, suitable for very large numbers of clients, such as in <a href="/facts/Streaming_media/4rPhSq0Y">streaming media</a> applications like <a href="/facts/IPTV/tHqsXX6h">IPTV</a>.</li>
<li>The lack of retransmission delays makes it suitable for real-time applications such as <a href="/facts/Voice_over_IP/5QGBbXYg">Voice over IP</a>, <a href="/facts/Online_games/UH6ItLnW">online games</a>, and many protocols using <a href="/facts/Real_Time_Streaming_Protocol/he6ChB16">Real Time Streaming Protocol</a>.</li>
<li>Because it supports <a href="/facts/Multicast/D9IspSfl">multicast</a>, it is suitable for broadcast information such as in many kinds of <a href="/facts/Service_discovery/ffYBWapn">service discovery</a> and shared information such as <a href="/facts/Precision_Time_Protocol/N5u5HVqx">Precision Time Protocol</a> and <a href="/facts/Routing_Information_Protocol/xGeIuGk6">Routing Information Protocol</a>.</li></ul>
<h2 id="ports">Ports</h2>
Applications can use <a href="/facts/Datagram_socket/r1ldfkb5">datagram sockets</a> to establish host-to-host communications. An application binds a socket to its endpoint of data transmission, which is a combination of an <a href="/facts/IP_address/z9V22Sw9">IP address</a> and a <a href="/facts/Port_(computer_networking)/ygoHVKNC">port</a>. In this way, UDP provides application <a href="/facts/Multiplexing/YE7hK8cw">multiplexing</a>. A port is a software structure that is identified by the <a href="/facts/Port_number/ygoHVKNC">port number</a>, a 16-bit integer value, allowing for port numbers between 0 and 65535. Port 0 is reserved but is a permissible source port value if the sending process does not expect messages in response.
The <a href="/facts/Internet_Assigned_Numbers_Authority/b6MlP6zQ">Internet Assigned Numbers Authority</a> (IANA) has divided port numbers into three ranges.<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a> Port numbers 0 through 1023 are used for common, well-known services. On <a href="/facts/Unix/0pNL2seI">Unix</a>-like <a href="/facts/Operating_system/8XTuvMh2">operating systems</a>, using one of these ports requires <a href="/facts/Superuser/0Brr6ol7">superuser</a> operating permission. Port numbers 1024 through 49151 are the <a href="/facts/Registered_port/o8mnzK0h">registered ports</a> used for IANA-registered services. Ports 49152 through 65535 are dynamic ports that are not officially designated for any specific service and may be used for any purpose. These may also be used as <a href="/facts/Ephemeral_port/Tls92nHS">ephemeral ports</a>, which software running on the host may use to dynamically create communications endpoints as needed.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a>

<h2 id="udp-datagram-structure">UDP datagram structure</h2>
A UDP datagram consists of a datagram header followed by a data section (the payload data for the application). The UDP datagram header consists of 4 fields, each of which is 2 bytes (16 bits):<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>

UDP header format<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a><table><tbody><tr><th>Offset</th><th><a href="/facts/Octet_(computing)/dqCHsuUF">Octet</a></th><th colspan="8">0</th><th colspan="8">1</th><th colspan="8">2</th><th colspan="8">3</th></tr><tr><th>Octet</th><th><a href="/facts/Bit/S972NSaD">Bit</a></th><th>0</th><th>1</th><th>2</th><th>3</th><th>4</th><th>5</th><th>6</th><th>7</th><th>8</th><th>9</th><th>10</th><th>11</th><th>12</th><th>13</th><th>14</th><th>15</th><th>16</th><th>17</th><th>18</th><th>19</th><th>20</th><th>21</th><th>22</th><th>23</th><th>24</th><th>25</th><th>26</th><th>27</th><th>28</th><th>29</th><th>30</th><th>31</th></tr><tr><th>0</th><th>0</th><td colspan="16">Source Port</td><td colspan="16">Destination Port</td></tr><tr><th>4</th><th>32</th><td colspan="16">Length</td><td colspan="16">Checksum</td></tr><tr><th>8</th><th>64</th><td colspan="32" rowspan="3">Data</td></tr><tr><th>12</th><th>96</th></tr><tr><th>⋮</th><th>⋮</th></tr></tbody></table>
The use of the Checksum and Source Port fields is optional in IPv4 (light purple background in table). In IPv6 only the Source Port field is optional. If not used, these fields should be set to zero.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a>

Source Port: 16 bits
This field identifies the sender's port, when used, and should be assumed to be the port to reply to if needed. If the source host is the client, the port number is likely to be an ephemeral port. If the source host is the server, the port number is likely to be a <a href="/facts/Well-known_port/c30Xg4d4">well-known port</a> number from 0 to 1023.<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a>
Destination Port: 16 bits
This field identifies the receiver's port and is required. Similar to source port number, if the client is the destination host then the port number will likely be an ephemeral port number and if the destination host is the server then the port number will likely be a well-known port number.<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a>
Length: 16 bits
This field specifies the length in bytes of the UDP datagram (the header fields and Data field) in <a href="/facts/Octet_(computing)/dqCHsuUF">octets</a>. The minimum length is 8 bytes, the length of the header. The field size sets a theoretical limit of 65,535 bytes (8-byte header + 65,527 bytes of data) for a UDP datagram. However, the actual limit for the data length, which is imposed by the underlying <a href="/facts/IPv4/bnQ5MEqm">IPv4</a> protocol, is 65,507 bytes (65,535 bytes − 8-byte UDP header − 20-byte <a href="/facts/IPv4_header/bnQ5MEqm">IP header</a>).<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>
Using IPv6 <a href="/facts/Jumbogram/xMtqGUth">jumbograms</a> it is possible to have UDP datagrams of size greater than 65,535 bytes. The length field is set to zero if the length of the UDP header plus UDP data is greater than 65,535.<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a>
<a href="/facts/Internet_checksum/3Em2ejgB">Checksum</a>: 16 bits
The checksum field may be used for error-checking of the header and data. This field is optional in IPv4, and mandatory in most cases in IPv6.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a>
Data: Variable
The payload of the UDP packet.
<h2 id="checksum-computation">Checksum computation</h2>
The method used to compute the checksum is defined in RFC <a href="https://datatracker.ietf.org/doc/html/rfc768">768</a>, and efficient calculation is discussed in RFC <a href="https://datatracker.ietf.org/doc/html/rfc1071">1071</a>:

Checksum is the 16-bit <a href="/facts/Ones%27_complement/Wl2PcLtg">ones' complement</a> of the ones' complement sum of a pseudo header of information from the IP header, the UDP header, and the data, padded with zero octets at the end (if necessary) to make a multiple of two octets.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>
In other words, all 16-bit words are summed using ones' complement arithmetic. Add the 16-bit values up. On each addition, if a carry-out (17th bit) is produced, swing that 17th carry bit around and add it to the least significant bit of the running total.<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a> Finally, the sum is then ones' complemented to yield the value of the UDP checksum field.
If the checksum calculation results in the value zero (all 16 bits 0) it should be sent as the ones' complement (all 1s) as a zero-value checksum indicates no checksum has been calculated.<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a> In this case, any specific processing is not required at the receiver, because all 0s and all 1s are equal to zero in 1's complement arithmetic.
The differences between <a href="/facts/IPv4/bnQ5MEqm">IPv4</a> and <a href="/facts/IPv6/d4dg7kIL">IPv6</a> are in the pseudo header used to compute the checksum, and that the checksum is not optional in IPv6.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a> Under specific conditions, a UDP application using IPv6 is allowed to use a zero UDP zero-checksum mode with a tunnel protocol.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a>

<h3>IPv4 pseudo header</h3>
When UDP runs over IPv4, the checksum is computed using a pseudo header that contains some of the same information from the real <a href="/facts/IPv4_header/bnQ5MEqm">IPv4 header</a>.<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>: 2  The pseudo header is not the real IPv4 header used to send an IP packet, it is used only for the checksum calculation.
UDP checksum computation is optional for IPv4. If a checksum is not used it should be set to the value zero.

UDP pseudo-header for checksum computation (IPv4)<table><tbody><tr><th>Offset</th><th><a href="/facts/Octet_(computing)/dqCHsuUF">Octet</a></th><th colspan="8">0</th><th colspan="8">1</th><th colspan="8">2</th><th colspan="8">3</th></tr><tr><th>Octet</th><th><a href="/facts/Bit/S972NSaD">Bit</a></th><th>0</th><th>1</th><th>2</th><th>3</th><th>4</th><th>5</th><th>6</th><th>7</th><th>8</th><th>9</th><th>10</th><th>11</th><th>12</th><th>13</th><th>14</th><th>15</th><th>16</th><th>17</th><th>18</th><th>19</th><th>20</th><th>21</th><th>22</th><th>23</th><th>24</th><th>25</th><th>26</th><th>27</th><th>28</th><th>29</th><th>30</th><th>31</th></tr><tr><th>0</th><th>0</th><td colspan="32">Source Address</td></tr><tr><th>4</th><th>32</th><td colspan="32">Destination Address</td></tr><tr><th>8</th><th>64</th><td colspan="8">Zeroes</td><td colspan="8">Protocol</td><td colspan="16">UDP Length</td></tr><tr><th>12</th><th>96</th><td colspan="16">Source Port</td><td colspan="16">Destination Port</td></tr><tr><th>16</th><th>128</th><td colspan="16">Length</td><td colspan="16">Checksum</td></tr><tr><th>20</th><th>160</th><td colspan="32" rowspan="3">Data</td></tr><tr><th>24</th><th>192</th></tr><tr><th>⋮</th><th>⋮</th></tr></tbody></table>
The checksum is calculated over the following fields:

Source Address: 32 bits
The source address from the IPv4 header.
Destination Address: 32 bits
The destination address from the IPv4 header.
Zeroes: 8 bits; Zeroes == 0
All zeroes.
Protocol: 8 bits
The <a href="/facts/List_of_IP_protocol_numbers/lf9S6JCk">protocol value</a> for UDP: 17 (or 0x11).
UDP length: 16 bits
The length of the UDP header and data (measured in octets).

<h3>IPv6 pseudo header</h3>
As IPv6 has larger addresses and a different header layout, the method used to compute the checksum is changed accordingly:<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a>: §8.1 

Any transport or other upper-layer protocol that includes the addresses from the IP header in its checksum computation must be modified for use over IPv6, to include the 128-bit IPv6 addresses instead of 32-bit IPv4 addresses.
When computing the checksum, again a pseudo header is used that mimics the real <a href="/facts/IPv6_header/afCKKH3o">IPv6 header</a>:

UDP pseudo-header for checksum computation (IPv6)<table><tbody><tr><th>Offset</th><th><a href="/facts/Octet_(computing)/dqCHsuUF">Octet</a></th><th colspan="8">0</th><th colspan="8">1</th><th colspan="8">2</th><th colspan="8">3</th></tr><tr><th>Octet</th><th><a href="/facts/Bit/S972NSaD">Bit</a></th><th>0</th><th>1</th><th>2</th><th>3</th><th>4</th><th>5</th><th>6</th><th>7</th><th>8</th><th>9</th><th>10</th><th>11</th><th>12</th><th>13</th><th>14</th><th>15</th><th>16</th><th>17</th><th>18</th><th>19</th><th>20</th><th>21</th><th>22</th><th>23</th><th>24</th><th>25</th><th>26</th><th>27</th><th>28</th><th>29</th><th>30</th><th>31</th></tr><tr><th>0</th><th>0</th><td colspan="32" rowspan="4">Source address</td></tr><tr><th>4</th><th>32</th></tr><tr><th>8</th><th>64</th></tr><tr><th>12</th><th>96</th></tr><tr><th>16</th><th>128</th><td colspan="32" rowspan="4">Destination address</td></tr><tr><th>20</th><th>160</th></tr><tr><th>24</th><th>192</th></tr><tr><th>28</th><th>224</th></tr><tr><th>32</th><th>256</th><td colspan="32">UDP length</td></tr><tr><th>36</th><th>288</th><td colspan="24">Zeroes (0)</td><td colspan="8">Next Header (17)</td></tr><tr><th>40</th><th>320</th><td colspan="16">Source port</td><td colspan="16">Destination port</td></tr><tr><th>44</th><th>352</th><td colspan="16">Length</td><td colspan="16">Checksum</td></tr><tr><th>48</th><th>384</th><td colspan="32" rowspan="3">Data</td></tr><tr><th>52</th><th>416</th></tr><tr><th>⋮</th><th>⋮</th></tr></tbody></table>
The checksum is computed over the following fields:

Source address: 128 bits
The address in the IPv6 header.
Destination address: 128 bits
The final destination; if the IPv6 packet does not contain a Routing header, TCP uses the destination address in the IPv6 header, otherwise, at the originating node, it uses the address in the last element of the Routing header, and, at the receiving node, it uses the destination address in the IPv6 header.
UDP length: 32 bits
The length of the UDP header and data (measured in octets).
Zeroes: 24 bits; Zeroes == 0
All zeroes.
Next Header: 8 bits
The <a href="/facts/Transport_layer/UmIGUCeK">transport layer</a> protocol value for UDP: 17.
<h2 id="reliability-and-congestion-control">Reliability and congestion control</h2>
Lacking reliability, UDP applications may encounter some packet loss, reordering, errors or duplication. If using UDP, the end-user applications must provide any necessary handshaking such as real-time confirmation that the message has been received. Applications, such as <a href="/facts/TFTP/TslBlcvJ">TFTP</a>, may add rudimentary reliability mechanisms into the application layer as needed.<a class="footnote-ref" id="fnref:23" href="#fn:23">23</a> If an application requires a high degree of reliability, a protocol such as the <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">Transmission Control Protocol</a> may be used instead.
Most often, UDP applications do not employ reliability mechanisms and may even be hindered by them. <a href="/facts/Streaming_media/4rPhSq0Y">Streaming media</a>, real-time multiplayer games and <a href="/facts/Voice_over_IP/5QGBbXYg">voice over IP</a> (VoIP) are examples of applications that often use UDP. In these particular applications, loss of packets is not usually a fatal problem. In VoIP, for example, latency and jitter are the primary concerns. The use of TCP would cause jitter if any packets were lost as TCP does not provide subsequent data to the application while it is requesting a re-send of the missing data.

<h2 id="applications">Applications</h2>
Numerous key Internet applications use UDP, including: the <a href="/facts/Domain_Name_System/rfxdWFsj">Domain Name System</a> (DNS), the <a href="/facts/Simple_Network_Management_Protocol/UNYPVA1C">Simple Network Management Protocol</a> (SNMP), the <a href="/facts/Routing_Information_Protocol/xGeIuGk6">Routing Information Protocol</a> (RIP)<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a> and the <a href="/facts/Dynamic_Host_Configuration_Protocol/lpASHnhz">Dynamic Host Configuration Protocol</a> (DHCP).
Voice and video traffic is generally transmitted using UDP. Real-time video and <a href="/facts/Audio_over_IP/v8ygS9Yu">audio streaming protocols</a> are designed to handle occasional lost packets, so only slight degradation in quality occurs, rather than large delays if lost packets were retransmitted. Because both TCP and UDP run over the same network, in the mid-2000s a few businesses found that an increase in UDP traffic from these real-time applications slightly hindered the performance of applications using TCP such as <a href="/facts/Point_of_sale/DwUHVn2v">point of sale</a>, <a href="/facts/Accounting_software/MHASg2lH">accounting</a>, and <a href="/facts/Database_management_system/VYcpkevb">database</a> systems (when TCP detects packet loss, it will throttle back its data rate usage).<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a>
Some <a href="/facts/VPN/HX1WUQ3E">VPN</a> systems such as <a href="/facts/OpenVPN/p8qllSrP">OpenVPN</a> may use UDP and perform error checking at the application level while implementing reliable connections. <a href="/facts/WireGuard/zSJv87LA">WireGuard</a> uses UDP and performs error checking, but does not provide any reliability guarantees, leaving it for the encapsulated protocols to deal with.
<a href="/facts/QUIC/nQt0oLRW">QUIC</a> is a transport protocol built on top of UDP. QUIC provides a reliable and secure connection. <a href="/facts/HTTP/3/SUASQpzB">HTTP/3</a> uses QUIC as opposed to earlier versions of <a href="/facts/HTTPS/MSWYz4zo">HTTPS</a> which use a combination of <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">TCP</a> and <a href="/facts/Transport_Layer_Security/pGy16TnA">TLS</a> to ensure reliability and security respectively. This means that HTTP/3 uses a single handshake to set up a connection, rather than having two separate handshakes for TCP and TLS, meaning the overall time to establish a connection is reduced.<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a>

<h2 id="comparison-of-udp-and-tcp">Comparison of UDP and TCP</h2>
See also: <a href="/facts/Transport_layer/UmIGUCeK">Transport layer</a>
<a href="/facts/Transmission_Control_Protocol/WW4sPrt9">Transmission Control Protocol</a> is a connection-oriented protocol and requires handshaking to set up end-to-end communications. Once a connection is set up, user data may be sent bi-directionally over the connection.

<ul><li>Reliable – TCP manages message acknowledgment, retransmission and timeouts. Multiple attempts to deliver the message are made. If data gets lost along the way, data will be re-sent. In TCP, there's either no missing data, or, in case of multiple timeouts, the connection is dropped.</li>
<li>Ordered – If two messages are sent over a connection in sequence, the first message will reach the receiving application first. When data segments arrive in the wrong order, TCP buffers the out-of-order data until all data can be properly re-ordered and delivered to the application.</li>
<li>Heavyweight – TCP requires three packets to set up a socket connection before any user data can be sent. TCP handles reliability and <a href="/facts/Congestion_control/9ohkRMso">congestion control</a>.</li>
<li>Streaming – Data is read as a <a href="/facts/Byte/BNHUp9Qq">byte</a> stream, no distinguishing indications are transmitted to signal message (segment) boundaries.</li></ul>
User Datagram Protocol is a simpler message-based <a href="/facts/Connectionless_protocol/MfMys8t7">connectionless protocol</a>. Connectionless protocols do not set up a dedicated end-to-end connection. Communication is achieved by transmitting information in one direction from source to destination without verifying the readiness or state of the receiver.

<ul><li>Unreliable – When a UDP message is sent, it cannot be known if it will reach its destination; it could get lost along the way. There is no concept of acknowledgment, retransmission, or timeout.</li>
<li>Not ordered – If two messages are sent to the same recipient, the order in which they arrive cannot be guaranteed.</li>
<li>Lightweight – There is no ordering of messages, no tracking connections, etc. It is a very simple transport layer designed on top of IP.</li>
<li>Datagrams – Packets are sent individually and are checked for integrity on arrival. Packets have definite boundaries which are honored upon receipt; a read operation at the receiver socket will yield an entire message as it was originally sent.</li>
<li>No congestion control – UDP itself does not avoid congestion. Congestion control measures must be implemented at the application level or in the network.</li>
<li>Broadcasts – being connectionless, UDP can broadcast - sent packets can be addressed to be receivable by all devices on the subnet.</li>
<li>Multicast – a multicast mode of operation is supported whereby a single datagram packet can be automatically routed without duplication to a group of subscribers.</li></ul>
<h2 id="standards">Standards</h2>
<ul><li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc768">768</a> – User Datagram Protocol</li>
<li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc2460">2460</a> – Internet Protocol, Version 6 (IPv6) Specification</li>
<li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc2675">2675</a> – IPv6 Jumbograms</li>
<li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc4113">4113</a> – Management Information Base for the UDP</li>
<li>RFC <a href="https://datatracker.ietf.org/doc/html/rfc8085">8085</a> – UDP Usage Guidelines</li></ul>
<h2 id="see-also">See also</h2>

<ul><li><a href="/facts/Comparison_of_transport_layer_protocols/UmIGUCeK">Comparison of transport layer protocols</a></li>
<li><a href="/facts/Datagram_Transport_Layer_Security/WxzxdITB">Datagram Transport Layer Security</a> (DTLS)</li>
<li><a href="/facts/List_of_TCP_and_UDP_port_numbers/c30Xg4d4">List of TCP and UDP port numbers</a></li>
<li><a href="/facts/Micro_Transport_Protocol/JjDMRI5n">Micro Transport Protocol</a> (μTP)</li>
<li><a href="/facts/Reliable_Data_Protocol/B5ewkGAN">Reliable Data Protocol</a> (RDP)</li>
<li><a href="/facts/Reliable_User_Datagram_Protocol/zL2uXFyW">Reliable User Datagram Protocol</a> (RUDP)</li>
<li><a href="/facts/UDP-based_Data_Transfer_Protocol/bqLw0sKC">UDP-based Data Transfer Protocol</a></li>
<li><a href="/facts/UDP_flood_attack/69CHcRWK">UDP flood attack</a></li>
<li><a href="/facts/UDP_Helper_Address/tYzuqabE">UDP Helper Address</a></li>
<li><a href="/facts/UDP_hole_punching/fAcm3XkF">UDP hole punching</a></li>
<li><a href="/facts/UDP-Lite/Bn3YqjzG">UDP-Lite</a> – a variant that delivers packets even if they are malformed</li></ul>

<h2 id="external-links">External links</h2>

Wikiversity has learning resources about User Datagram Protocol

<ul><li><a href="https://www.iana.org/assignments/port-numbers">IANA Port Assignments</a></li>
<li><a href="http://condor.depaul.edu/~jkristof/papers/udpscanning.pdf">The Trouble with UDP Scanning (PDF)</a></li>
<li><a href="http://www.networksorcery.com/enp/protocol/udp.htm">Breakdown of UDP frame</a></li>
<li><a href="http://msdn.microsoft.com/en-us/magazine/cc163648.aspx">UDP on MSDN Magazine Sockets and WCF</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">Castelli, Matthew J. (2003). Network Sales and Services Handbook. Cisco Press. ISBN 9781587050909. <a href="9781587050909" target="_blank">9781587050909</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Stanek, William (2015). Windows Command Line: The Personal Trainer for Windows 8.1 Windows Server 2012 and Windows Server 2012 R2. Stanek & Associates. ISBN 9781627164139. <a href="9781627164139" target="_blank">9781627164139</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Kurose, J. F.; Ross, K. W. (2010). Computer Networking: A Top-Down Approach (5th ed.). Boston, MA: Pearson Education. ISBN 978-0-13-136548-3. <a href="978-0-13-136548-3" target="_blank">978-0-13-136548-3</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Clark, M.P. (2003). Data Networks IP and the Internet, 1st ed. West Sussex, England: John Wiley & Sons Ltd. <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">content@ipv6.com (15 August 2006). "UDP Protocol Overview". Ipv6.com. Retrieved 17 August 2011.{{cite web}}: CS1 maint: numeric names: authors list (link) <a href="http://ipv6.com/articles/general/User-Datagram-Protocol.htm" target="_blank">http://ipv6.com/articles/general/User-Datagram-Protocol.htm</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Forouzan, B.A. (2000). TCP/IP: Protocol Suite, 1st ed. New Delhi, India: Tata McGraw-Hill Publishing Company Limited. <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Forouzan, B.A. (2000). TCP/IP: Protocol Suite, 1st ed. New Delhi, India: Tata McGraw-Hill Publishing Company Limited. <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Kurose, J. F.; Ross, K. W. (2010). Computer Networking: A Top-Down Approach (5th ed.). Boston, MA: Pearson Education. ISBN 978-0-13-136548-3. <a href="978-0-13-136548-3" target="_blank">978-0-13-136548-3</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">J. Postel, ed. (28 August 1980). User Datagram Protocol. IETF. doi:10.17487/RFC0768. STD 6. RFC 768. Internet Standard 6.
 <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">J. Postel, ed. (28 August 1980). User Datagram Protocol. IETF. doi:10.17487/RFC0768. STD 6. RFC 768. Internet Standard 6.
 <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">Forouzan, B.A. (2000). TCP/IP: Protocol Suite, 1st ed. New Delhi, India: Tata McGraw-Hill Publishing Company Limited. <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">Forouzan, B.A. (2000). TCP/IP: Protocol Suite, 1st ed. New Delhi, India: Tata McGraw-Hill Publishing Company Limited. <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Stevens, W. Richard (1994). TCP/IP Illustrated: The protocols. Vol. 1 (2 ed.). Addison-Wesley. ISBN 978-0-20-163346-7. <a href="978-0-20-163346-7" target="_blank">978-0-20-163346-7</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">D. Borman; S. Deering; R. Hinden (August 1999). IPv6 Jumbograms. Network Working Group. doi:10.17487/RFC2675. RFC 2675. Proposed Standard. Obsoletes RFC 2147.
 <a href="/wiki/Steve_Deering" target="_blank">/wiki/Steve_Deering</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">S. Deering; R. Hinden (July 2017). Internet Protocol, Version 6 (IPv6) Specification. Internet Engineering Task Force. doi:10.17487/RFC8200. STD 86. RFC 8200. Internet Standard 86. Obsoletes RFC 2460.
 <a href="/wiki/Steve_Deering" target="_blank">/wiki/Steve_Deering</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">J. Postel, ed. (28 August 1980). User Datagram Protocol. IETF. doi:10.17487/RFC0768. STD 6. RFC 768. Internet Standard 6.
 <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">"Compute 16-bit Ones' Complement Sum". mathforum.org. John. 20 March 2002. Archived from the original (email) on 17 November 2020. Retrieved 5 November 2014. <a href="https://web.archive.org/web/20201117162031/http://mathforum.org/library/drmath/view/54379.html" target="_blank">https://web.archive.org/web/20201117162031/http://mathforum.org/library/drmath/view/54379.html</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">J. Postel, ed. (28 August 1980). User Datagram Protocol. IETF. doi:10.17487/RFC0768. STD 6. RFC 768. Internet Standard 6.
 <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Internet Protocol, Version 6 (IPv6) Specification. p. 27-28. doi:10.17487/RFC8200. RFC 8200. <a href="https://datatracker.ietf.org/doc/html/rfc8200#page-27-28" target="_blank">https://datatracker.ietf.org/doc/html/rfc8200#page-27-28</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">Internet Protocol, Version 6 (IPv6) Specification. p. 23. doi:10.17487/RFC8085. RFC 8085. <a href="https://datatracker.ietf.org/doc/html/rfc8085#page-23" target="_blank">https://datatracker.ietf.org/doc/html/rfc8085#page-23</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">J. Postel, ed. (28 August 1980). User Datagram Protocol. IETF. doi:10.17487/RFC0768. STD 6. RFC 768. Internet Standard 6.
 <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">S. Deering; R. Hinden (July 2017). Internet Protocol, Version 6 (IPv6) Specification. Internet Engineering Task Force. doi:10.17487/RFC8200. STD 86. RFC 8200. Internet Standard 86. Obsoletes RFC 2460.
 <a href="/wiki/Steve_Deering" target="_blank">/wiki/Steve_Deering</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">Forouzan, B.A. (2000). TCP/IP: Protocol Suite, 1st ed. New Delhi, India: Tata McGraw-Hill Publishing Company Limited. <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">Kurose, J. F.; Ross, K. W. (2010). Computer Networking: A Top-Down Approach (5th ed.). Boston, MA: Pearson Education. ISBN 978-0-13-136548-3. <a href="978-0-13-136548-3" target="_blank">978-0-13-136548-3</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">"The impact of UDP on Data Applications". Networkperformancedaily.com. Archived from the original on 31 July 2007. Retrieved 17 August 2011. <a href="https://archive.today/20070731124008/http://www.networkperformancedaily.com/2007/08/whiteboard_series_nice_guys_fi.html" target="_blank">https://archive.today/20070731124008/http://www.networkperformancedaily.com/2007/08/whiteboard_series_nice_guys_fi.html</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">"QUIC, a multiplexed stream transport over UDP". chromium.org. Retrieved 17 February 2021. <a href="https://www.chromium.org/quic" target="_blank">https://www.chromium.org/quic</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
</ol>

User Datagram Protocol open-in-new

User Datagram Protocol