📄 ch06.htm
字号:
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT"><B>ANSI</B></TD>
<TD ALIGN="LEFT"></TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.4</TD>
<TD ALIGN="LEFT">Information interchange code</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.15</TD>
<TD ALIGN="LEFT">Bit sequencing for X3.4 in serial data streams</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.16</TD>
<TD ALIGN="LEFT">Character and parity structure for X.34 transmissions</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.28</TD>
<TD ALIGN="LEFT">Standard for the use of communication control characters</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.41</TD>
<TD ALIGN="LEFT">Code extensions for the 7-bit V3.4 interchange code</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.66</TD>
<TD ALIGN="LEFT">Advanced Data Communication Control Procedures (ADCCP)</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">X3.92</TD>
<TD ALIGN="LEFT">Data Encryption Algorithm</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT"><B>IEEE</B></TD>
<TD ALIGN="LEFT"></TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.2</TD>
<TD ALIGN="LEFT">Data Link Layer</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.3</TD>
<TD ALIGN="LEFT">CSMA/CD</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.4</TD>
<TD ALIGN="LEFT">Token Bus</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.5</TD>
<TD ALIGN="LEFT">Token Ring</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.6</TD>
<TD ALIGN="LEFT">Metropolitan area networks</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.7</TD>
<TD ALIGN="LEFT">Broadband local area networks</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.9/802.10</TD>
<TD ALIGN="LEFT">Integrated LAN/MAN networks</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.11</TD>
<TD ALIGN="LEFT">Wireless LAN Medium Access Control and Physical Layer specification</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">802.12</TD>
<TD ALIGN="LEFT">100 Mbps (Fast Ethernet)</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1003</TD>
<TD ALIGN="LEFT">Portable operating systems (POSIX)</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1394</TD>
<TD ALIGN="LEFT">High Performance Serial Bus ("Firewire")</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT"><B>EIA</B></TD>
<TD ALIGN="LEFT"></TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">RS-232C</TD>
<TD ALIGN="LEFT">Interfacing DTE and DCE devices via serial exchange</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">RS-449</TD>
<TD ALIGN="LEFT">37- and 9-pin DTE interfaces for serial exchange</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT"><B>FTSC</B></TD>
<TD ALIGN="LEFT"></TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1003</TD>
<TD ALIGN="LEFT">Synchronous data link control procedures (ADCCP)</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1005</TD>
<TD ALIGN="LEFT">Coding and modulation requirements for 2400-bps modems</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1006</TD>
<TD ALIGN="LEFT">Coding and modulation requirements for 4800-bps modems</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1007</TD>
<TD ALIGN="LEFT">Coding and modulation requirements for 9600-bps modems</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1008</TD>
<TD ALIGN="LEFT">Coding and modulation for 600/1200-bps modems</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1010</TD>
<TD ALIGN="LEFT">Bit sequencing of ANSI X3.4 for serial transmissions</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1011</TD>
<TD ALIGN="LEFT">Character/parity structure for ANSI X3.4 transmissions</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1015</TD>
<TD ALIGN="LEFT">Analog to digital conversion of voice by 2400 bps linear predictive coding</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1016</TD>
<TD ALIGN="LEFT">Analog to digital conversion of radio voice by 4800bps code excited linear prediction
(CELP)</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1026</TD>
<TD ALIGN="LEFT">Interoperability and security requirements for use of the Data Encyrption Standard
in the physical layer of data communications</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1027</TD>
<TD ALIGN="LEFT">Security requirements for equipment using the data encryption standard</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1028</TD>
<TD ALIGN="LEFT">Interoperability and security requirements for use of the Data Encryption Standard
with CCITT Group 3 facsimile equipment</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1045</TD>
<TD ALIGN="LEFT">High frequency radio automatic link establishment</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1046</TD>
<TD ALIGN="LEFT">Radio Automatic Networking</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1047</TD>
<TD ALIGN="LEFT">Radio automatic message delivery</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1048</TD>
<TD ALIGN="LEFT">Radio automatic networking to multiple-media</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1049</TD>
<TD ALIGN="LEFT">Radio automatic operation in stressed environment</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1052</TD>
<TD ALIGN="LEFT">Radio modems</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1101-1108</TD>
<TD ALIGN="LEFT">Land mobile radio</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT"><B>FIPS</B></TD>
<TD ALIGN="LEFT"></TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">1-1</TD>
<TD ALIGN="LEFT">Code for information interchange</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">7</TD>
<TD ALIGN="LEFT">Implementation of FIPS 1-1 and related standards</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">15</TD>
<TD ALIGN="LEFT">Subsets of the 1-1 code for information interchange</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">16-1</TD>
<TD ALIGN="LEFT">Bit sequencing of the 1-1 code for serial transmissions</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">17-1</TD>
<TD ALIGN="LEFT">Character and parity structure for FIPS 1-1transmissions</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">35</TD>
<TD ALIGN="LEFT">Code extension techniques using 7 or 8 bits</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">71</TD>
<TD ALIGN="LEFT">Advanced Data Communication Control Procedures (ADCCP)</TD>
</TR>
<TR ALIGN="LEFT" VALIGN="TOP">
<TD ALIGN="LEFT">81</TD>
<TD ALIGN="LEFT">Data Encryption Standard (DES) Modes of Operation</TD>
</TR>
</TABLE>
</P>
<P>Dramatic differences in standards were much more prevalent in the days before
the OSI Reference Model. In today's world, each organization dances around the same
OSI maypole, hoping to create a universal set of multifaceted standards. The fact
that a given standard at a given layer was created by one organization or another
becomes, for the most part, irrelevant--the ISO stamp of approval is the great equalizer.
<H2><A NAME="Heading10"></A><FONT COLOR="#000077">Emerging Standards</FONT></H2>
<P>New standards, and indeed, even new standards organizations are being created
at an accelerated pace. In addition, there is a growing trend among companies to
make informal alliances to create a de facto standard. Formalized or not, however,
a new standard must prove its vitality in an ever-changing marketplace before being
accepted by the user community.
<H3><A NAME="Heading11"></A><FONT COLOR="#000077">Salutation Architecture</FONT></H3>
<P>The Salutation Consortium, Inc.--whose members include IBM, Novell, and HP--is
planning to release a specification that will let devices identify and communicate
with each other. The consortium's middleware, Salutation Architecture, creates a
handshake between several different types of devices, such as faxes, printers, and
PCs. The consortium will release the specification to the developer community without
royalty or fees. The middleware fits within the operating system and defines a set
of APIs that applications are able to understand. It has discovery capability, so
it can identify devices, determine their capabilities, and communicate. The middleware
is similar in nature to Microsoft's Microsoft At Work, a project designed to connect
office equipment to PCs. Salutation Architecture is more network-oriented, however,
and At Work never took off.
<H3><A NAME="Heading12"></A><FONT COLOR="#000077">SONET (synchronous optical network)</FONT></H3>
<P>SONET is a high-speed transmission standard initially developed for fiber-optic
systems. It has since been adapted for microwave radio systems, for use in areas
where physical cabling is difficult.
<H3><A NAME="Heading13"></A><FONT COLOR="#000077">Plug and Play Standard (Microsoft)</FONT></H3>
<P>The Plug and Play standard is Microsoft's approach to multivendor compatibility.
Although it enables users to easily integrate peripherals from many vendors, it is
limited by its proprietary nature. However, the standard is supported by many vendors,
and is likely to become a de facto standard. Plug and Play has been built into the
Windows 95 operating system and enables PCs and peripherals from different vendors
to work together under the Microsoft environment. Under this paradigm, if a PC user
attaches a new peripheral, it can start working immediately. A Plug and Play hardware
device automatically sends information to the host about its basic services, what
it requires to operate, and which drivers it needs. The operating system software
will then automatically configure the device. The catch is, the peripheral must be
specifically designed for the standard.
<H3><A NAME="Heading14"></A><FONT COLOR="#000077">Firewire (IEEE 1394)</FONT></H3>
<P>This standard was designed to speed up LAN communications over high-speed serial
ports. It can function as a local device interface for ATM or Fast Ethernet, enabling
ATM to be routed to individual devices inexpensively. The standard might ultimately
provide the framework necessary for multimedia LAN applications, and is designed
to transport data at rates of up to 400 Mbps.
<H3><A NAME="Heading15"></A><FONT COLOR="#000077">Common Desktop Environment (CDE)</FONT></H3>
<P>There have been many attempts to unify a fractured U N I X market,
but only the Common Desktop Environment (CDE) has succeeded. Part of the Common Operating
System Environment (COSE) agreement, CDE establishes several common features across
all major U N I X implementations. CDE does not actually implement
any new technology; rather, it is a composite of bits and pieces of various U N I Xs
from HP, Sun Microsystems, and IBM.</P>
<CENTER>
<P>
<HR>
<A HREF="ch05.htm" tppabs="http://docs.rinet.ru:8080/MuNet/ch05/ch05.htm"><IMG SRC="previous.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/previous.gif" WIDTH="128" HEIGHT="28"
ALIGN="BOTTOM" ALT="Previous chapter" BORDER="0"></A><A HREF="ch07.htm" tppabs="http://docs.rinet.ru:8080/MuNet/ch07/ch07.htm"><IMG
SRC="next.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/next.gif" WIDTH="128" HEIGHT="28" ALIGN="BOTTOM" ALT="Next chapter"
BORDER="0"></A><A HREF="index-2.htm" tppabs="http://docs.rinet.ru:8080/MuNet/index.htm"><IMG SRC="contents.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/contents.gif" WIDTH="128"
HEIGHT="28" ALIGN="BOTTOM" ALT="Contents" BORDER="0"></A> <BR>
<BR>
<BR>
<P>© <A HREF="javascript:if(confirm('http://docs.rinet.ru:8080/MuNet/copy.htm \n\nThis file was not retrieved by Teleport Pro, because it was deleted using Teleport Pro\'s Delete command. \n\nDo you want to open it from the server?'))window.location='http://docs.rinet.ru:8080/MuNet/copy.htm'" tppabs="http://docs.rinet.ru:8080/MuNet/copy.htm">Copyright</A>, Macmillan Computer Publishing. All
rights reserved.
</CENTER>
</BODY>
</HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -