GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: remove excessive formatting in dgram.md · nodejs/node@b62d9b4

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • doc/api
    • dgram.md
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/api/dgram.md‎

Copy file name to clipboardExpand all lines: doc/api/dgram.md
+9-9Lines changed: 9 additions & 9 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -520,25 +520,25 @@ client.connect(41234, 'localhost', (err) => {
520520

521521
#### Note about UDP datagram size
522522

523-
The maximum size of an `IPv4/v6` datagram depends on the `MTU`
524-
(_Maximum Transmission Unit_) and on the `Payload Length` field size.
523+
The maximum size of an IPv4/v6 datagram depends on the `MTU`
524+
(Maximum Transmission Unit) and on the `Payload Length` field size.
525525

526-
* The `Payload Length` field is `16 bits` wide, which means that a normal
527-
payload cannot exceed 64K octets _including_ the internet header and data
526+
* The `Payload Length` field is 16 bits wide, which means that a normal
527+
payload cannot exceed 64K octets including the internet header and data
528528
(65,507 bytes = 65,535 − 8 bytes UDP header − 20 bytes IP header);
529529
this is generally true for loopback interfaces, but such long datagram
530530
messages are impractical for most hosts and networks.
531531

532532
* The `MTU` is the largest size a given link layer technology can support for
533-
datagram messages. For any link, `IPv4` mandates a minimum `MTU` of `68`
534-
octets, while the recommended `MTU` for IPv4 is `576` (typically recommended
533+
datagram messages. For any link, IPv4 mandates a minimum `MTU` of 68
534+
octets, while the recommended `MTU` for IPv4 is 576 (typically recommended
535535
as the `MTU` for dial-up type applications), whether they arrive whole or in
536536
fragments.
537537

538-
For `IPv6`, the minimum `MTU` is `1280` octets, however, the mandatory minimum
539-
fragment reassembly buffer size is `1500` octets. The value of `68` octets is
538+
For IPv6, the minimum `MTU` is 1280 octets. However, the mandatory minimum
539+
fragment reassembly buffer size is 1500 octets. The value of 68 octets is
540540
very small, since most current link layer technologies, like Ethernet, have a
541-
minimum `MTU` of `1500`.
541+
minimum `MTU` of 1500.
542542

543543
It is impossible to know in advance the MTU of each link through which
544544
a packet might travel. Sending a datagram greater than the receiver `MTU` will

0 commit comments

Comments
0 (0)
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.