{"id":302,"date":"2020-08-18T19:23:47","date_gmt":"2020-08-18T20:23:47","guid":{"rendered":"http:\/\/www.linux-tutorial.info\/?page_id=77"},"modified":"2020-08-22T19:26:17","modified_gmt":"2020-08-22T20:26:17","slug":"this-is-the-page-title-toplevel-137","status":"publish","type":"page","link":"http:\/\/www.linux-tutorial.info\/?page_id=302","title":{"rendered":"Network Standards"},"content":{"rendered":"\nNetwork Standards<\/title>\n<p>\nHere we need to side step a little. We need to first talk about what goes into making a\nstandard. Without standards, it makes communication between computers of different type very\ndifficult. Just like you have <glossary>bus<\/glossary>\nstandards like <glossary>ISA<\/glossary>\nand <glossary>PCI<\/glossary> so hardware can communicate with the\nCPU, you need some kind of standard.\n<\/p>\n<question id=\"276\" text=\"Networking standards are usually found in what documents?\" \/>\n<question id=\"\" type=\"mc\" text=\"What is an RFC?\" \/>\n<p>\nIn the Internet community, standards are both suggested and established through Request for Comments or\nRFCs. To some extent this is the “law”. If one product claims to comply with a\nparticular <glossary>RFC<\/glossary>, you know that any other application that\ndoes so should be able to communicate with it. However, RFCs include other\nthings such as lists of previous RFCs and basic introductions to things like\n<glossary>TCP<\/glossary>.\n<\/p>\n<p>\nBecoming a standard is a three step process.\nUsually, the first few paragraphs of an <glossary>RFC<\/glossary>\nwill tell you to what stage it applies. Assuming of\ncourse, that the <glossary>RFC<\/glossary>\nis part of a standards proposal. At the first stage, the standard is proposed.\nOrganizations then decide to implement the proposed standard. It requires three separate\nimplementations before the proposal becomes a standard. (Finally, it becomes a standard. This is an\noversimplication of the process, since there will also be a lot of discussion about the proposed\nstandard.)<\/p>\n<p>\nIf you need information about a specific <glossary>network<\/glossary>\nstandard, the first place to look\nis the most current <glossary>RFC<\/glossary>\nindex, which is also published as an RFC. Not only does this list all the\nRFCs, but will also tell you if one <glossary>RFC<\/glossary>\nhas been replaced and by which one.\n<\/p>\n<p>\nOriginally I had\nplanned to include a list of the more commonly used and significant RFCs. I eventually realized that\nthis was an unending task. When I started this, there were just over 1800 RFCs. The last time I\nchecked before I originally completed this section, there are well over 2000. Instead I will simply tell you where\nto get them.\n<\/p><p>\nThe first place is from the “central repository.” These are obtainable using ftp\nfrom <i>ftp.ds.internic.net<\/i>. There is an rfc directory, which contains the RFCs in <glossary>ASCII<\/glossary>\nas well\nas many in postscript format. If you know what <glossary>RFC<\/glossary>\nyou want, this can be obtained by sending an\nemail message to mailserv@ds.internic.net. List each <glossary>RFC<\/glossary>\nyou want in the format:<\/p>\n<p>\ndocument-by-name rfc<b>XXXX<\/b>\n<\/p>\n<p>\nwhere <b>XXXX<\/b> is the number of the <glossary>RFC<\/glossary>. You\ncan obtain the index by including the entry:<\/p>\n<p>\ndocument-by-name rfc-index\n<\/p>\n<p>\nIn addition, the\nRFCS are available from archives all over the Internet. However, rather than tying up the Internet\nbandwidth with a lot of copy of files you may not need.\n<\/p>\n<question id=\"277\" text=\"Ethernet uses what method to access the pyhysical connection?\" \/>\n<question id=\"\" type=\"mc\" text=\"When was Ethernet first developed\" \/>\n<question id=\"\" type=\"mc\" text=\"What is the primary Ethernet standard?\" \/>\n<p>\nFor Linux systems running TCP\/IP one of the most important\nstandards deals with <glossary>Ethernet<\/glossary>.\n The <glossary>encapsulation<\/glossary>\n(packaging) of <glossary>IP<\/glossary>\ndatagrams is defined for Ethernet\nin <glossary>RFC<\/glossary>\n894. Developed in 1982 by Digital Equipment Corporation (DEC), Intel and Xerox. Ethernet\n(spelled with a capital) is a standard, rather than a physical entity. Several years later, the 802\nCommittee of the Institute of Electrical and Electronic Engineers (IEEE or I-triple E), published\nstandards of its own that differed in many ways from the original <glossary>Ethernet<\/glossary>\nstandard. Collectively,\nthese are referred to as the 802 IEEE standards. The 802.3 standard covers networks similar to\nEthernet. The IEEE 802 <glossary>encapsulation<\/glossary>\nwas defined in <glossary>RFC<\/glossary>\n1042. Both of these use an access method\ncalled Carrier Sense Multiple Access with Collision Detection or CSMA\/CD.\n<\/p>\n<p>\nBoth of these\nframing types (RFC 894 and <glossary>RFC<\/glossary>\n1042) use a 48-bit addressing scheme. These are generally referred to\nas the MAC or hardware <glossary>address<\/glossary>.\n The six bytes of both the destination and source machine are\nincluded in the <glossary>header<\/glossary>\nof both framing types. however, the remainder of the frame is different. As\nwe talked about earlier, this layer is responsible for sending and receiving the <glossary>IP<\/glossary>\ndatagrams. It is\nalso responsible for sending and receiving other kinds of packets as well. These are packets from\nthe Address Resolution Protocol (ARP) and the Reverse Address Resolution Protocol (RARP). We’ll\ntalk about both later on.\n<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Network Standards Here we need to side step a little. We need to first talk about what goes into making a standard. Without standards, it makes communication between computers of different type very difficult. Just like you have bus standards … <a href=\"http:\/\/www.linux-tutorial.info\/?page_id=302\">Continue reading <span class=\"meta-nav\">→<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-302","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/302","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=302"}],"version-history":[{"count":1,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/302\/revisions"}],"predecessor-version":[{"id":640,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/302\/revisions\/640"}],"wp:attachment":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}