Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81801 - 81820 из 81894.
Упорядочить по:
URL
|
дате изменения
81801. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1063.txt
... OPTION FORMATS Probe MTU Option (Number 11) Format +--------+--------+--------+--------+ |00001011|00000100| 2 octet value | ... When a datagram containing the Probe MTU option is received, the option must be passed up to the receiving transport layer, which should then acknowledge the Probe with a Reply MTU option in the next return datagram. ... Whenever an IP datagram is sent, the IP layer checks in the routing cache to see if a Probe or Reply MTU option needs to be inserted in the datagram. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1063.txt -- 26.9 Кб -- 27.07.1988
Похожие документы
Похожие документы
81802. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1059.txt
Network Working Group D. Mills Request for Comments: 1059 University of Delaware July 1988 Network Time Protocol (Version 1) Specification and Implementation Status of this Memo This memo describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1059.txt -- 135.4 Кб -- 27.07.1988
Похожие документы
Похожие документы
81803. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1058.txt
Network Working Group C. Hedrick Request for Comments: 1058 Rutgers University June 1988 Routing Information Protocol Status of this Memo This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. ... Thus, we mark the route as invalid. ... for the direct link from C to D, which |/ has cost 10 D |<=== target network Hedrick [Page 12] RFC 1058 Routing Information Protocol June 1988 Each gateway will have a table showing a route to each network. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1058.txt -- 90.3 Кб -- 30.06.1988
Похожие документы
Похожие документы
81804. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1057.txt
... Request For Comments: 1057 June 1988 Obsoletes: RFC 1050 RPC: Remote Procedure Call Protocol Specification Version 2 STATUS OF THIS MEMO This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. ... TERMINOLOGY This document discusses clients, calls, servers, replies, services, programs, procedures, and versions. ... 7.4 Other Uses of the RPC Protocol The intended use of this protocol is for calling remote procedures. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1057.txt -- 50.9 Кб -- 24.06.1988
Похожие документы
Похожие документы
81805. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1056.txt
... Reset-mailbox" causes the repository to place all of the messages in a named mailbox onto the current client's update list. ... Responses by number 100 Pcmail repository version XXX; following are supported 200 Command OK 220 Client list name status follows: 221 Client out of date by 1 week 230 Mailbox list name high UID #msgs #new follows: 240 Subscription list follows: 250 Descriptor list follows: 251 Message follows: 260 Address list follows: 350 enter ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1056.txt -- 82.3 Кб -- 16.06.1988
Похожие документы
Похожие документы
81806. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1055.txt
... PROTOCOL The SLIP protocol defines two special characters: END and ESC. ... To send a packet, a SLIP host simply starts sending the data in the packet. ... SLIP special character codes */ #define END 0300 /* indicates end of packet */ #define ESC 0333 /* indicates byte stuffing */ #define ESC _ END 0334 /* ESC ESC _ END means END data byte */ #define ESC _ ESC 0335 /* ESC ESC _ ESC means ESC data byte */ /* SEND _ PACKET : sends a ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1055.txt -- 13.3 Кб -- 15.06.1988
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std47.txt -- 13.3 Кб -- 15.06.1988
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std47.txt -- 13.3 Кб -- 15.06.1988
Похожие документы
81807. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1054.txt
Network Working Group S. Deering Request for Comments: 1054 Stanford University Obsoletes: RFC 988 May 1988 Host Extensions for IP Multicasting 1. ... INTRODUCTION IP multicasting is defined as the transmission of an IP datagram to a "host group", a set of zero or more hosts identified by a single IP destination address. ... A host transmits an IP multicast datagram as a local network multicast which reaches all immediately-neighboring members of the destination host group. ... Group Address | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1054.txt -- 44.4 Кб -- 13.05.1988
Похожие документы
Похожие документы
81808. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1029.txt
Network Working Group G. Parr Request For Comments: 1029 University of Ulster May 1988 A MORE FAULT TOLERANT APPROACH TO ADDRESS RESOLUTION FOR A MULTI-LAN SYSTEM OF ETHERNETS STATUS OF THIS MEMO This memo discusses an extension to a Bridge Protocol to detect and disclose changes in neighbouring host address parameters in a Multi- LAN system of Ethernets. ... To actually transmit the Ethernet packet, a 48 bit Ethernet/hardware address must be generated. ... Let the Ethernet type of Internet be ET(IP). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1029.txt -- 43.0 Кб -- 09.05.1988
Похожие документы
Похожие документы
81809. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1053.txt
... Code 0 -- 110 bps Code 10 -- 50 bps Code 1 -- 134.5 bps Code 11 -- 75 bps in, 1200 out Code 2 -- 300 bps Code 12 -- 2400 bps Code 3 -- 1200 bps Code 13 -- 4800 bps Code 4 -- 600 bps Code 14 -- 9600 bps Code 5 -- 75 bps Code 15 -- 19200 bps Code 6 -- 150 bps Code 16 -- 48000 bps Code 7 -- 1800 bps Code 17 -- 56000 bps Code 8 -- 200 bps Code 18 -- 64000 bps Code 9 -- 100 bps Levy & Jacobson [Page 11] RFC 1053 Telnet X.3 PAD Option April 1988 Parameter 12 -- Flow control of host-to-user data. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1053.txt -- 47.7 Кб -- 15.04.1988
Похожие документы
Похожие документы
81810. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1052.txt
Network Working Group V. Cerf Request for Comments: 1052 NRI April 1988 IAB Recommendations for the Development of Internet Network Management Standards Status of this Memo This memo is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. ... 4) Lee LaBarre, "Network Layer Management Information: IP", DRAFT-NNNN, February 1988. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1052.txt -- 30.1 Кб -- 12.04.1988
Похожие документы
Похожие документы
81811. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1050.txt
... Request for Comments: 1050 April 1988 RPC: Remote Procedure Call Protocol Specification STATUS OF THIS MEMO This RFC describes a standard that Sun Microsystems and others are using and is one we wish to propose for the Internet's consideration. ... Network clients are pieces of software that initiate remote procedure calls to services. ... 7.1 RPC Programs and Procedures The RPC call message has three unsigned fields: remote program number, remote program version number, and remote procedure number....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1050.txt -- 50.0 Кб -- 08.04.1988
Похожие документы
Похожие документы
81812. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1051.txt
Network Working Group P. Prindeville Request for Comments: 1051 McGill University March 1988 A Standard for the Transmission of IP Datagrams and ARP Packets over ARCNET Networks Status of this Memo This RFC specifies a standard protocol for the Internet community. ... The ARP hardware address type for ARCNET is 7 [9]. ... Prindeville [Page 3] RFC 1051 IP and ARP on ARCNET March 1988 References [1] Postel, J., "Internet Protocol", RFC-791, Network Information Center, SRI, September 1981. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1051.txt -- 8.4 Кб -- 24.03.1988
Похожие документы
Похожие документы
81813. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1777-tests2.txt
- Can the IUT interpret a bad option and a good option? - Action: Send a datagram to the IP Implementation Under Test whose option field contains a security option with an invalid security level and a stream ID option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. -
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1777-tests2.txt -- 341.1 Кб -- 10.03.1988
Похожие документы
Похожие документы
81814. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1780-tests.txt
DCEC PROTOCOL LABORATORY FILE TRANSFER PROTOCOL (FTP) MIL-STD-1780 CERTIFICATION TESTS INDEX This Certification Tests Index provides information on the derivation, organization, and function of tests specified for FTP within the DCEC Protocol Laboratory. ... Test 1 Establish Connection Issue USER, PASS, and ACCT Commands Test 2 Issue QUIT Command ------------------------------------------------------- Test 1 - Can the implementation under test (IUT) establish a connection to the reference (REF)? ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1780-tests.txt -- 60.3 Кб -- 10.03.1988
Похожие документы
Похожие документы
81815. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1782-tests.txt
... Command or Primitive Option User Test Number -------------------- ------ -------------------- Open connection 0 Network Virtual Terminal Go Ahead status 0 Network Virtual Terminal Echo status 0 Response to DO option request Remote echo 1 GoAhead 2 Binary 3 Timing Mark 4 Extended Options 5 Status 6 Response to DO option request for enabled option Remote echo 1 GoAhead 2 Binary 3 Timing Mark 4 Extended Options 5 Status 6 Response to DON'T ... Action: Send a data string REF to the IUT. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1782-tests.txt -- 54.4 Кб -- 10.03.1988
Похожие документы
Похожие документы
81816. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1778-tests.txt
... TEST NUMBER PURPOSE ---- ------ ------ 1 Unspecified Passive Open Request 2 Active Open Request 3 Basic Data Transfer 4 Remote Driver Interpretation of command LCN 5 Determine IUT Standard Send Buffer 6 Closing Handshake - IUT initiates close 7 Closing Handshake - IUT peer initiates close 8 Ability to reconnect Remote Driver command channel 9 Fully Specified Passive Open Request 10 Illegal Fully Specified Passive ... Action: The Laboratory Slave Driver (LSD) sends data to the IUT....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1778-tests.txt -- 98.7 Кб -- 10.03.1988
Похожие документы
Похожие документы
81817. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1777-tests1.txt
DCEC PROTOCOL LABORATORY INTERNET PROTOCOL MIL-STD-1777 CERTIFICATION TESTS INDEX This Certification Tests Index provides information on the derivation, organization, and function of tests specified for Internet Protocol (IP) within the DCEC Protocol Laboratory. This document is divided into five sections: IP TRACEABILITY INDEX; IP TESTS INDEX; IP CODES INDEX; IP TEST SCENARIOS INDEX; and IP SCENARIOS AND TESTS DESCRIPTIONS. -------- IP TRACEABILITY INDEX: IP TEST NUMBERS versus IP MIL-STD-1777
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/mil-std-tests/mstd-1777-tests1.txt -- 376.8 Кб -- 10.03.1988
Похожие документы
Похожие документы
81818. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1048.txt
Network Working Group P. Prindeville Request for Comments: 1048 McGill University February 1988 BOOTP Vendor Information Extensions Status of this Memo This memo proposes an addition to the Bootstrap Protocol (BOOTP). ... The protocol included provisions for vendor-defined resource information. ... Prindeville [Page 3] RFC 1048 BOOTP Extensions February 1988 Cookie/Quote Server Field (Tag: 8, Data: N address bytes) Specifies the IP addresses of N/4 Quote of the Day servers [RFC-865]. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1048.txt -- 15.7 Кб -- 26.02.1988
Похожие документы
Похожие документы
81819. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1047.txt
Network Working Group Craig Partridge Request for Comments: 1047 CIC at BBN Labs February 1988 DUPLICATE MESSAGES AND SMTP STATUS OF THIS MEMO An examination of a synchronization problem in the Simple Mail Transfer Protocol (SMTP) is presented. ... A method for avoiding this problem is suggested. ... There is a point in the process of delivering a message where the receiving mailer knows it has accepted the message but the sending mailer is still not sure the message has been reliably delivered. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1047.txt -- 6.6 Кб -- 26.02.1988
Похожие документы
Похожие документы
81820. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1046.txt
... Introduction The Type-of-Service (TOS) field in IP headers allows one to chose from none to all the following service types; low delay, high throughput, and high reliability. It also has a portion allowing a priority selection from 0-7. ... The low delay class of service should have the ability to pass data through the net faster than regular data. ... The datagrams responding to low delay traffic (i.e., Acking the data) might be sent with a high reliability class of service, but not low delay. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1046.txt -- 29.8 Кб -- 25.02.1988
Похожие документы
Похожие документы