What a fantastic article. Thanks!
Network protocols for anyone who knows a programming language
11–20 of 72 posts
Re: Network protocols for anyone who knows a programming language
#12> An interpacket gap of 96 bits (12 bytes) where the line is left idle. Presumably, this is to let the devices rest because they are tired.
Kind of! They allow systems with slightly different clock rates to adjust. A system sending data nominally at 10 Gb/s can actually run slightly faster to a system running slightly slower b/c their timing bases (crystals) oscillate at slight different frequencies.
Is it also to allow other nodes on the network to communicate, especially if they're on the same collision domain?
Re: Network protocols for anyone who knows a programming language
#13With the current state of generally terrible technical writing and my ever decreasing attention span it's bloody refreshing to read a concise and well written explanation of a highly technical subject! I'll definitely have to check out the rest of their 'compendium': https://www.destroyallsoftware.com/compendium
What do you see as an issue in technical writing, if anything past not concise or well written?
I suppose it boils down to why the Feynman lectures are generally considered a gold standard in technical presentations.
His explanations focus on the most important bits (which he has skillfully prioritized based on his expert knowledge) and avoid highly domain specific nomenclature i.e. he gives a thorough-yet-concise explanation in a way that a reasonably intelligent lay person can understand.
Does that make sense?
Re: Network protocols for anyone who knows a programming language
#14With the current state of generally terrible technical writing and my ever decreasing attention span it's bloody refreshing to read a concise and well written explanation of a highly technical subject! I'll definitely have to check out the rest of their 'compendium': https://www.destroyallsoftware.com/compendium
Agree, and love that guys domain name.
Re: Network protocols for anyone who knows a programming language
#15> An interpacket gap of 96 bits (12 bytes) where the line is left idle. Presumably, this is to let the devices rest because they are tired.
Kind of! They allow systems with slightly different clock rates to adjust. A system sending data nominally at 10 Gb/s can actually run slightly faster to a system running slightly slower b/c their timing bases (crystals) oscillate at slight different frequencies.
>"They allow systems with slightly different clock rates to adjust."
Adjust to what? Ethernet is not synchronous its asynchronous. There is no shared clock.
The interframe gap goes back to the days of CSMA/CD. The interframe gap was the period during which end stations would contend for the shared medium. Without this an end station could continuously stream and monopolize the network.
Re: Network protocols for anyone who knows a programming language
#16Earlier quoted context omitted.
Kind of! They allow systems with slightly different clock rates to adjust. A system sending data nominally at 10 Gb/s can actually run slightly faster to a system running slightly slower b/c their timing bases (crystals) oscillate at slight different frequencies.
Is it also to allow other nodes on the network to communicate, especially if they're on the same collision domain?
No. Wired ethernet hasn't used collison-based protocols in a long time. It's point-to-point now, not shared.
Re: Network protocols for anyone who knows a programming language
#17With the current state of generally terrible technical writing and my ever decreasing attention span it's bloody refreshing to read a concise and well written explanation of a highly technical subject! I'll definitely have to check out the rest of their 'compendium': https://www.destroyallsoftware.com/compendium
When I was doing my CCNA the cisco press books where well written and went from first principals.
Re: Network protocols for anyone who knows a programming language
#18Earlier quoted context omitted.
What do you see as an issue in technical writing, if anything past not concise or well written?
I suppose it boils down to why the Feynman lectures are generally considered a gold standard in technical presentations. His explanations focus on the most important bits (which he has skillfully prioritized based on his expert knowledge) and avoid highly domain specific nomenclature i.e. he gives a thorough-yet-concise explanation in a way that a reasonably intelligent lay person can understand. Does that make sense…
Agreed. This is also why I adore the SICP lectures from the 1980s [1] (and the book in general).
It broke programming down to its most fundamental and important building blocks without all the baggage of machine/operating system/application/dependency/etc specific stuff.
[1] https://www.youtube.com/watch?v=2Op3QLzMgSY&list=PL8FE88AA54...
Re: Network protocols for anyone who knows a programming language
#19Earlier quoted context omitted.
Kind of! They allow systems with slightly different clock rates to adjust. A system sending data nominally at 10 Gb/s can actually run slightly faster to a system running slightly slower b/c their timing bases (crystals) oscillate at slight different frequencies.
>"They allow systems with slightly different clock rates to adjust." Adjust to what? Ethernet is not synchronous its asynchronous. There is no shared clock. The interframe gap goes back to the days of CSMA/CD. The interframe gap was the period during which end stations would contend for the shared medium. Without this an end station could continuously stream and monopolize the network.
No, that was the preamble.
Re: Network protocols for anyone who knows a programming language
#20With the current state of generally terrible technical writing and my ever decreasing attention span it's bloody refreshing to read a concise and well written explanation of a highly technical subject! I'll definitely have to check out the rest of their 'compendium': https://www.destroyallsoftware.com/compendium
Agree, and love that guys domain name.
I love it too. Sadly, not to long ago he considered changing it because it makes their materials a hard sell to enterprises.