Talk:Trivial File Transfer Protocol: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
No edit summary
m (Text replacement - "locality of networks" to "locality of networks")
 
Line 8: Line 8:
It's sometimes very hard to understand what background assumptions, if any, I can make about someone writing about (in the broadest sense) about networking. There is something significant, although I can't quite categorize it, when someone calls the development framework for an Ajax system a "backbone".
It's sometimes very hard to understand what background assumptions, if any, I can make about someone writing about (in the broadest sense) about networking. There is something significant, although I can't quite categorize it, when someone calls the development framework for an Ajax system a "backbone".


I'd welcome comments on what is a far-reaching article, [[locality of networks]], which I realized was needed when I found it was rather hard to write an encyclopedic-quality article defining LANs. I have now done something on that, and also started [[Ethernet]] -- troubling, because "Ethernet" is overloaded in so many ways. One of my all-time favorite cringes was when a colleague explained that something was "Ethernet" because it used an RJ45, with 802.3 pin assignments, to connect to a 4000 kilometer point-to-point optical link intended for oceanic cables.
I'd welcome comments on what is a far-reaching article, locality of networks, which I realized was needed when I found it was rather hard to write an encyclopedic-quality article defining LANs. I have now done something on that, and also started [[Ethernet]] -- troubling, because "Ethernet" is overloaded in so many ways. One of my all-time favorite cringes was when a colleague explained that something was "Ethernet" because it used an RJ45, with 802.3 pin assignments, to connect to a 4000 kilometer point-to-point optical link intended for oceanic cables.


<center>'''''So many protocols, so little time'''''</center>
<center>'''''So many protocols, so little time'''''</center>


[[User:Howard C. Berkowitz|Howard C. Berkowitz]] 13:26, 23 August 2008 (CDT)
[[User:Howard C. Berkowitz|Howard C. Berkowitz]] 13:26, 23 August 2008 (CDT)

Latest revision as of 08:21, 24 June 2024

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
To learn how to update the categories for this article, see here. To update categories, edit the metadata template.
 Definition A protocol that has the absolutely minimal set of functions needed for a computer, with no local storage for executable code, to get its basic operating system from a trusted server on a trusted network [d] [e]
Checklist and Archives
 Workgroup category Computers [Categories OK]
 Talk Archive none  English language variant American English

nice start!

Thanks for starting this; very good beginning!Pat Palmer 13:05, 23 August 2008 (CDT)

Very roundabout creation

After seeing the article on TCP spoofing and making some suggestions, I realized I needed to go back and fill in more under Transmission Control Protocol. In turn, that made me think about writing some more about tradeoffs in error control, which made me think of TFTP.

It's sometimes very hard to understand what background assumptions, if any, I can make about someone writing about (in the broadest sense) about networking. There is something significant, although I can't quite categorize it, when someone calls the development framework for an Ajax system a "backbone".

I'd welcome comments on what is a far-reaching article, locality of networks, which I realized was needed when I found it was rather hard to write an encyclopedic-quality article defining LANs. I have now done something on that, and also started Ethernet -- troubling, because "Ethernet" is overloaded in so many ways. One of my all-time favorite cringes was when a colleague explained that something was "Ethernet" because it used an RJ45, with 802.3 pin assignments, to connect to a 4000 kilometer point-to-point optical link intended for oceanic cables.

So many protocols, so little time

Howard C. Berkowitz 13:26, 23 August 2008 (CDT)