XWare Поиск по информационным ресурсам МГУ English Russian
       
       Точная форма слов   О проекте   Сайты   Помощь
Поиск по:mirror.msu.net   - Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81321 - 81340 из 81894.

В начало ] Пред. | 4063 | 4064 | 4065 | 4066 | 4067 | 4068 | 4069 | 4070 | 4071 | 4072 | След.В конец ]

Упорядочить по: URL  |  дате изменения
81321. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc841.txt
RFC 841 FIPS Pub 98 SPECIFICATION FOR MESSAGE FORMAT FOR COMPUTER BASED MESSAGE SYSTEMS 27 January 1983 National Bureau of Standards This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accesible to the ARPA research community. This RFC does not specify a standard for the ARPA Internet. TABLE OF CONTENTS Page EXECUTIVE SUMMARY 5 1. INTRODUCTION 7 1.1 Guide to Reading This Document 7 1.2 Vendor-Defined Extensions to the Specification 8 1.3 The Scope of the Message
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc841.txt -- 227.4 Кб -- 23.09.1992
Похожие документы

81322. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc840.txt
Network Working Group J. Postel Request for Comments: 840 ISI April 1983 Official Protocols This RFC identifies the documents specifying the official protocols used in the Internet. ... In each entry there are notes on status, specification, comments, other references, dependencies, and contact. ... OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Postel@USC-ISIF NICNAME Protocol STATUS: Elective SPECIFICATION: RFC 812 (in IPTW) COMMENTS: Accesses the ARPANET Directory database. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc840.txt -- 33.7 Кб -- 23.09.1992
Похожие документы

81323. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc839.txt
... Dead, refused, and unreachable hosts were retried 26-Jan-83 from ~8:00 am to ~6:10 pm PST. ... 323 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- d e a d ada-vax 10.0.0.52 ---- accepted accepted accepted aerospace 10.2.0.65 T--- accepted accepted accepted afgl 10.1.0.66 ---- accepted accepted afsc-ad 10.0.0.53 T--- accepted accepted afsc-dev 10.2.0.53 ---- accepted ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc839.txt -- 45.1 Кб -- 23.09.1992
Похожие документы

81324. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc838.txt
Network Working Group D. Smallberg Request for Comments: 838 January 1983 Who Talks TCP? ... 323 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- d e a d ada-vax 10.0.0.52 ---- accepted accepted accepted aerospace 10.2.0.65 T--- accepted accepted accepted afgl 10.1.0.66 ---- accepted accepted afsc-ad 10.0.0.53 T--- accepted accepted afsc-dev 10.2.0.53 ---- accepted accepted ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc838.txt -- 45.0 Кб -- 23.09.1992
Похожие документы

81325. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc837.txt
... Dead, refused, and unreachable hosts were retried 12-Jan-83 from ~8:00 am to ~4:30 pm PST. ... 323 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- d e a d ada-vax 10.0.0.52 ---- accepted accepted accepted aerospace 10.2.0.65 T--- accepted accepted accepted afgl 10.1.0.66 ---- accepted accepted afsc-ad 10.0.0.53 T--- accepted accepted afsc-dev 10.2.0.53 ---- accepted ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc837.txt -- 44.8 Кб -- 23.09.1992
Похожие документы

81326. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc836.txt
... Dead, refused, and unreachable hosts were retried 5-Jan-83 from ~8:00 am to ~4:15 pm PST. ... 315 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- ada-vax 10.0.0.52 ---- accepted accepted accepted aerospace 10.2.0.65 T--- accepted accepted accepted afgl 10.1.0.66 ---- accepted accepted afsc-ad 10.0.0.53 T--- accepted accepted afsc-dev 10.2.0.53 ---- accepted ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc836.txt -- 43.6 Кб -- 23.09.1992
Похожие документы

81327. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc835.txt
... Dead, refused, and unreachable hosts were retried 29-Dec-82 from ~8:00 am to ~7:40 pm PST. ... 314 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- ada-vax 10.0.0.52 ---- aerospace 10.2.0.65 T--- d e a d afgl 10.1.0.66 ---- afsc-ad 10.0.0.53 T--- afsc-dev 10.2.0.53 ---- accepted accepted afsc-hq 10.0.0.67 ---- afsc-sd 10.0.0.65 ---- afwl 10.0.0.48 ---- alta-coma 3.1.0.50 T--- ames-11 10.3.0.16 ---- ames-67 10.0.0 ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc835.txt -- 43.0 Кб -- 23.09.1992
Похожие документы

81328. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc834.txt
... Dead, refused, and unreachable hosts were retried 24-Dec-82 from ~3:50 pm to ~5:15 pm PST. ... 314 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- ada-vax 10.0.0.52 ---- aerospace 10.2.0.65 T--- d e a d afgl 10.1.0.66 ---- afsc-ad 10.0.0.53 T--- afsc-dev 10.2.0.53 ---- accepted accepted afsc-hq 10.0.0.67 ---- afsc-sd 10.0.0.65 ---- afwl 10.0.0.48 ---- alta-coma 3.1.0.50 T--- ames-11 10.3.0.16 ---- ames-67 10.0.0 ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc834.txt -- 42.8 Кб -- 23.09.1992
Похожие документы

81329. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc833.txt
Network Working Group D. Smallberg Request for Comments: 833 December 1982 Who Talks TCP? ... 314 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- ada-vax 10.0.0.52 ---- refused refused accepted aerospace 10.2.0.65 T--- afgl 10.1.0.66 ---- d e a d afsc-ad 10.0.0.53 T--- accepted accepted afsc-dev 10.2.0.53 ---- afsc-hq 10.0.0.67 ---- afsc-sd 10.0.0.65 ---- afwl 10.0.0.48 ---- alta-coma 3.1.0.50 T--- ames-11 10.3.0 ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc833.txt -- 43.0 Кб -- 23.09.1992
Похожие документы

81330. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc832.txt
... 130 l +-----------+-------------+---------+------+------------+ a tcp | ... 315 Results in alphabetical order: Name Address Claims Telnet FTP SMTP ---- ------- ------ ------ --- ---- acc 10.2.0.54 ---- ada-vax 10.0.0.52 ---- aerospace 10.2.0.65 T--- accepted accepted accepted afgl 10.1.0.66 ---- afsc-ad 10.0.0.53 T--- afsc-dev 10.2.0.53 ---- accepted accepted afsc-hq 10.0.0.67 ---- afsc-sd 10.0.0.65 ---- afwl 10.0.0.48 ---- alta-coma 3.1.0.50 T--- ames-11 10.3.0.16 ---- ames-67 10.0...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc832.txt -- 42.7 Кб -- 23.09.1992
Похожие документы

81331. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc831.txt
Network Working Group R. Braden Request for Comments: 831 University College London December 1982 Backup Access to the European Side of SATNET Robert Braden DISCUSSION The purpose of this RFC is to focus discussion on a particular Internet problem: a backup path for software maintenance of the European sector of the Internet, for use when SATNET is partitioned. We propose a mechanism, based upon the Source Routing option of IP, to reach European Internet sites via the VAN Gateway and UCL. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc831.txt -- 12.5 Кб -- 23.09.1992
Похожие документы

81332. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc830.txt
... Internet Name Service provides a network service for name resolution and resource negotiation for the establishment of direct communication between a pair of source and destination application processes. ... It logically consists of two parts: the domain name service and the application interface (Figure 1). ... Example: 1 3 1 9 F.ISI.USC 1 9 F.ISI.USC 9 18 Resolution Failure 13 RFC 830 October 1982 4.2.4 DNS/DNS Communication The domain name service is an application independent network service. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc830.txt -- 31.9 Кб -- 23.09.1992
Похожие документы

81333. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc819.txt
Network Working Group Zaw-Sing Su (SRI) Request for Comments: 819 Jon Postel (ISI) August 1982 The Domain Naming Convention for Internet User Applications 1. ... This note is an attempt to clarify this generalized naming convention, the Internet Naming Convention, and to explore the implications of its adoption for Internet name service and user applications. ... This Internet naming convention allows distributed name service and naming authority functions at each domain. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc819.txt -- 35.5 Кб -- 23.09.1992
Похожие документы

81334. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc818.txt
Network Working Group J. Postel Request for Comments: 818 ISI November 1982 The Remote User Telnet Service This RFC is the specification of an application protocol. ... The Telnet Protocol is to be used on the connection from the originating user to the server. ... A user TC-Telnet application provides an interface to allow the user to use the network to connect to a host, Postel [Page 1] RFC 818 November 1982 Remote User Telnet Service providing a network virtual terminal. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc818.txt -- 4.6 Кб -- 23.09.1992
Похожие документы

81335. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc817.txt
... Assume that data is being sent from one machine to another in packets of 576 bytes, the maximum generally acceptable internet packet size. ... RFC 813, "Window and Acknowledgement Strategy in TCP", discusses one aspect of reducing the number of packets sent per useful data byte. ... The protocol can be in a process that is provided by the operating system, or it can be part of the kernel of the operating system itself, or it can be put in a separate communications processor or front end machine. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc817.txt -- 45.9 Кб -- 23.09.1992
Похожие документы

81336. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc816.txt
... Introduction Occasionally, a network or a gateway will go down, and the sequence of hops which the packet takes from source to destination must change. ... When a host sends a datagram to some distant net, the host should be prepared to receive back either of two advisory messages which the gateway may send. ... This works, but, since the message must be sent fairly often to detect a fault in a reasonable time, it can imply an unbearable overhead on the host itself, the network, and the gateway. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc816.txt -- 20.6 Кб -- 23.09.1992
Похожие документы

81337. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc815.txt
RFC: 815 IP DATAGRAM REASSEMBLY ALGORITHMS David D. Clark MIT Laboratory for Computer Science Computer Systems and Communications Group July, 1982 1. ... Under certain circumstances, a datagram originally transmitted as a single unit will arrive at its final destination broken into several fragments. ... This pair of numbers we will call the "hole descriptor", and we will assume that all of the hole descriptors for a particular datagram are gathered together in the "hole descriptor list". ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc815.txt -- 15.2 Кб -- 23.09.1992
Похожие документы

81338. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc814.txt
RFC: 814 NAME, ADDRESSES, PORTS, AND ROUTES David D. Clark MIT Laboratory for Computer Science Computer Systems and Communications Group July, 1982 1. ... Routes show up explicitly in the form of the internet routing options, and also implicitly in the address to route translation tables which all hosts and gateways maintain. ... In particular, when a datagram is being sent out from a host, the IP layer must decide where to send it on the immediately connected network, based on the internet address. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc814.txt -- 25.1 Кб -- 23.09.1992
Похожие документы

81339. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc813.txt
... This algorithm at the sender end is very simple. ... When the receiver window algorithm and the receiver acknowledgement algorithm are used together, it will be seen that sending an acknowledgement will be triggered by one of the following events. ... In fact, the receiver algorithm is designed to be more robust than this, for transmission of an acknowledgment is triggered by two events, either a cessation of data or a reduction in the amount of offered window to 50 percent of the actual value. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc813.txt -- 38.2 Кб -- 23.09.1992
Похожие документы

81340. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc812.txt
Ken Harrenstien RFC-812 Vic White 1 March 1982 Network Information Center SRI International NICNAME/WHOIS INTRODUCTION The NICNAME/WHOIS Server is an NCP/TCP transaction based query/response server, running on the SRI-NIC machine, that provides netwide directory service to ARPANET users. ... To access the server: Connect to the service host (SRI-NIC) TCP: service port 43 decimal NCP: ICP to socket 43 decimal, establishing two 8-bit connections Send a single "command line", ending with <CRLF>. ...
[ Сохраненная копия ]  Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc812.txt -- 6.3 Кб -- 23.09.1992
Похожие документы

Rambler's Top100 RFBR Яндекс цитирования