You could, of course, buy a copy of the ISO standard and start implementing: https://www.iso.org/obp/ui/#iso:std:iso-iec:7498:-1:ed-1:v2:en
It's only 178 CHF, plus shipping. ANSI sells a version as a PDF: https://webstore.ansi.org/Standards/ISO/ISOIEC74981994 That's only $209 and you could avoid the shipping charges. I'm sure you would learn a lot. On Sat, Aug 10, 2019 at 12:01 PM Russell Senior <[email protected]> wrote: > > > On Sat, Aug 10, 2019 at 8:55 AM Richard Owlett <[email protected]> > wrote: > >> I have read more and made some progress ;} >> I am using Debian 9.8 {Stretch} with MATE desktop on two Lenovo laptops. >> As I used Networkmanager to create the ad-hoc network, I only have WEP >> *NOT* WPA at the moment [but have info on doing WPA]. >> [see >> >> https://wiki.debian.org/WiFi/HowToUse#WiFi_can_scan.2C_but_not_connect_using_NetworkManager_.28Debian_9_Stretch.29 >> on how to overcome a connection problem.] >> >> My stated goal is file sharing on a peer-to-peer network with exactly >> two nodes. The unstated purpose of chosen method is understanding >> networks. Traveling down memory lane to early 60's, I can see this as a >> Sophomore/Junior E.E. lab {Cornell's B.S.E.E. program was 5 years at the >> time ;] >> > > Nothing on wireless involves two nodes. Each station broadcasts. It's only > happenstance if only two stations are receiving, it could easily be more. > > Did you see this? > > https://wiki.debian.org/WiFi/AdHoc > > >> >> Since I last posted, I've discovered "Open Systems .Interconnection >> (OSI) Model". >> >> > Did you see this part? > > https://en.wikipedia.org/wiki/OSI_model#Comparison_with_TCP/IP_model > > "The OSI protocol suite <https://en.wikipedia.org/wiki/OSI_protocols> > that was specified as part of the OSI project was considered by many as too > complicated and inefficient, and to a large extent unimplementable.[21] > <https://en.wikipedia.org/wiki/OSI_model#cite_note-Tanenbaum-21> Taking > the "forklift upgrade" approach to networking, it specified eliminating all > existing networking protocols and replacing them at all layers of the > stack. This made implementation difficult, and was resisted by many vendors > and users with significant investments in other network technologies. In > addition, the protocols included so many optional features that many > vendors' implementations were not interoperable.[21] > <https://en.wikipedia.org/wiki/OSI_model#cite_note-Tanenbaum-21> > > Although the OSI model is often still referenced, the Internet protocol > suite <https://en.wikipedia.org/wiki/Internet_protocol_suite> has become > the standard for networking. TCP/IP's pragmatic approach to computer > networking and to independent implementations of simplified protocols made > it a practical methodology.[21] > <https://en.wikipedia.org/wiki/OSI_model#cite_note-Tanenbaum-21> Some > protocols and specifications in the OSI stack remain in use, one example > being IS-IS <https://en.wikipedia.org/wiki/IS-IS>, which was specified > for OSI as ISO/IEC 10589:2002 and adapted for Internet use with TCP/IP as > RFC <https://en.wikipedia.org/wiki/Request_for_Comments_(identifier)> 1142 > <https://tools.ietf.org/html/rfc1142>." > > >> I would like to be pointed to material on creating an appropriate P2P >> network with a preference to sources tied to OSI. >> {References to servers/clients, switches, routers, un-listed hardware, >> etc are _*VERBOTEN*_!} >> >> TIA >> >> >> >> >> _______________________________________________ >> PLUG mailing list >> [email protected] >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
