Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 1018e52

Browse filesBrowse files
Trottaddaleax
authored andcommitted
doc: remove excessive formatting in dgram.md
PR-URL: #35234 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
1 parent e026ce9 commit 1018e52
Copy full SHA for 1018e52

File tree

Expand file treeCollapse file tree

1 file changed

+9
-9
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+9
-9
lines changed
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
@@ -516,25 +516,25 @@ client.connect(41234, 'localhost', (err) => {
516516

517517
#### Note about UDP datagram size
518518

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

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

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

534-
For `IPv6`, the minimum `MTU` is `1280` octets, however, the mandatory minimum
535-
fragment reassembly buffer size is `1500` octets. The value of `68` octets is
534+
For IPv6, the minimum `MTU` is 1280 octets. However, the mandatory minimum
535+
fragment reassembly buffer size is 1500 octets. The value of 68 octets is
536536
very small, since most current link layer technologies, like Ethernet, have a
537-
minimum `MTU` of `1500`.
537+
minimum `MTU` of 1500.
538538

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

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.