The de facto standard Application Program Interface (API) for TCP/IP applications is the “sockets” interface. Although this API was developed for （71） in the early 1960s it has also been implemented on a wide variety of no-Unix systems. TCP/IP （72） Written using the sockets API have in the past enjoyed a high degree of portability and we would like the same （73） with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 （74） ,new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features requited by TCP and UDP applications, including multicasting, while introducing a minimums of change into the system and providing complete （75） for existing IPv4 applications.A.WindowsB.LinuxC.UnixD.DOS
The de facto standard Application Program Interface (API) for TCP/IP applications is the “sockets” interface. Although this API was developed for （71） in the early 1960s it has also been implemented on a wide variety of no-Unix systems. TCP/IP （72） Written using the sockets API have in the past enjoyed a high degree of portability and we would like the same （73） with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 （74） ,new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features requited by TCP and UDP applications, including multicasting, while introducing a minimums of change into the system and providing complete （75） for existing IPv4 applications.
A.Windows
B.Linux
C.Unix
D.DOS
相关考题：
● A glue that holds the whole Internet together is the network layer protocol,(71). Unlike most older network layer protocols, it was designed from the beginning with internetworking in mind. Its job is to provide a -(72) way to transport datagrams from source to destination, without regard to whether these machines are on the same network or whether there are other networks in between them.Communication in the Internet works as follows. The (73)layer takes data streams and breaks them up into datagrams. Each datagram is transmitted through the Internet, possibly being fragmented into smaller units as it goes. When all the pieces finally get to the destination machine, they are reassembled by the(74) layer into the original datagram. This datagram is then handed to the transport layer, which inserts it into the receiving process' input stream.An IP datagram consists of a header part and a text part. The header has a (75) part and a variable length optional part.(71) A. IP (Internet Protocol)B. IP (Interworking Protocol)C. TCP (Transport Control Protocol)D. TCP (Transfer Communication Protocol)(72) A. best-qualityB. quality-guaranteedC. connection-orientedD. best-efforts(73) A. data linkB. transportC. networkD. application(74) A. data linkB. transportC. networkD. application(75) A. 40-byte fixedB. 64-byte fixedC. 20~64 bytes variableD. 20-byte fixed
《民用航空器加油规范》中提出，飞机加油胶管应符合( )的C类标准。A.API/IP1564B.API/IP1581C.API/IP1529或BS3158(EN1361)D.API/IP1583
Thedefacto standard Application Program Interface （API） for TCP/IP applications is the “sockets” interface. Although this API was developed for __（71）__ in the early 1980s it has also been implemented on a wide variety ofnon-Unix systems。 TCP/IP __（72）__ written using the sockets API have in the past enjoyed a high degreeof portability and we would like the same __（73）__ with IPv6 applications。 But changes are requiredto the sockets API to support IPv6 and this memo describes these changes。These include a new socket address structure to carry IPv6 __（74）__，new address conversion functions，and some new socket options。These extensions aredesigned to provide access to the basic IPv6 features required by TCP and UDPapplications，including multicasting， while introducing aminimum of change into the system and providing complete __（75）__ for existing IPv4 applications。A.WindowsB.LinuxC.UnixD.DOS@@@SXB@@@A.applicationsB.networksC.protocolsD.systems@@@SXB@@@A.portabilityB.availabilityC.capabilityD.reliability@@@SXB@@@A.connectionsB.protocolsC.networksD.addresses@@@SXB@@@A.availabilityB.compatibilityC.capabilityD.reliability
The defacto standard Application Program Interface （API） for TCP/IP applications is the “sockets” interface. Although this API was developed for __（71）__ in the early 1980s it has also been implemented on a wide variety of non-Unix systems。 TCP/IP __（72）__ written using the sockets API have in the past enjoyed a high degree of portability and we would like the same __（73）__ with IPv6 applications。 But changes are required to the sockets API to support IPv6 and this memo describes these changes。These include a new socket address structure to carry IPv6 __（74）__，new address conversion functions，and some new socket options。These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications，including multicasting， while introducing a minimum of change into the system and providing complete __（75）__ for existing IPv4 applications。A.WindowsB.LinuxC.UnixD.DOS
TCP/IP （ ）layer protocols provide services to the application（ ）running on a computer. The application layer does not define the application itself, but rather it defines（ ）that applications need--like the ability to transfer a file in the case of HTTP. In short, the application layer provides an（请作答此空）between software running on a computer and the network itself. The TCP/IP application layer includes a relatively large number of protocols, with HTTP being only one of those. The TCP/IP（ ）layer consists of two main protocol options--the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP).A.iterationB.objectC.interface]D.activity