Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81241 - 81260 из 81894.
[ В начало ] Пред. | 4059 |
4060 |
4061 |
4062 |
4063
|
4064 |
4065 |
4066 |
4067 |
4068 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
81241. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc683.txt
RFC 683, NIC 32251 FTPSRV - TENEX FTP EXTENSIONS FOR PAGED FILES R. Clements - BBN - 3 April 75 1 Introduction In response to a long-known need for the ability to transfer TENEX paged files over the net via FTP, the TENEX FTP implementation has been extended. ... TYPE XTP is only implemented for STRU F, BYTE 36, and MODE S. Information of TYPE XTP is transfered in chunks (I intentionally avoid the words RECORD and BLOCK) which consist of a header and some data. ... Word 4: Page number. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc683.txt -- 9.6 Кб -- 15.10.1992
Похожие документы
Похожие документы
81242. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc678.txt
Network Working Group J. Postel Request for Comments: 678 (SRI-ARC) NIC: 31524 19 December 1974 Standard File Formats Introduction In an attempt to provide online documents to the network community we have had many problems with the physical format of the final documents. ... This results in the typical physical page having a maximum capacity of 66 lines and 85 characters per line. ... A typical logical page is 60 lines high and 72 characters wide. ... Page Length 60 lines. ... Page Length 60 Lines. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc678.txt -- 13.1 Кб -- 15.10.1992
Похожие документы
Похожие документы
81243. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc672.txt
Network Working Group Richard Schantz (BBN-TENEX) Request for Comments: 672 Dec 1974 NIC #31440 A Multi-Site Data Collection Facility Preface: This RFC reproduces most of a working document prepared during the design and implementation of the protocols for the TIP-TENEX integrated system for handling TIP accounting. ... Total time=2N+P+O]. ... From time to time the TIP will transmit intermediate accounting data to Accounting Server (ACTSER) processes scattered throughout the network. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc672.txt -- 26.1 Кб -- 15.10.1992
Похожие документы
Похожие документы
81244. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc674.txt
GJOURNAL 31484. NLS ;1, 12-DEC-74 04:32 XXX ;;;; Title: Author(s): Jonathan B. Postel/JBP; Distribution: /NAG( [ ACTION ] ) NLG( [ ACTION ] ) NSW ( [ ACTION ] ) PI( [ ACTION ] ) ; Sub-Collections: NIC NWG SRI-ARC NAG NLG NSW PI; RFC# 674; Clerk: JAKE; Origin: NETINFO, RFC674. NLS ;2, , 11-DEC-74 17:58 JAKE ;;;;####; NWG/RFC# 674 JBP 11-DEC-74 18:04 31484 Procedure Call Protocol Documents Request for Comments 674 Jon Postel NIC 31484 Jim White ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc674.txt -- 12.9 Кб -- 15.10.1992
Похожие документы
Похожие документы
81245. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc662.txt
... 1974 PERFORMANCE IMPROVEMENT IN ARPANET FILE TRANSFERS FROM MULTICS With the growth of Multics usage in the ARPA Network community, users often need to transfer large amounts of data from Multics to other systems. ... Recently the Cambridge Information Systems Laboratory (CISL) development Multics system was connected to the ARPA Network. ... At currently realizable data transfer rates, transmission of a typical MST, (approximately 12 million bits), takes about half an hour. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc662.txt -- 9.7 Кб -- 15.10.1992
Похожие документы
Похожие документы
81246. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc658.txt
... 25, 1974) Online file: [ISI]<DCROCKER>NAOLFD.TXT TELNET OUTPUT LINEFEED DISPOSITION 1. ... IAC DO NAOLFD The data sender requests or agrees to negotiate about output linefeed disposition with the data receiver. ... IAC WILL NAOLFD The data receiver requests or agrees to negotiate about output linefeed disposition with the sender. ... IAC SB NAOLFD DS <8-bit value> IAC SE The data sender specifies, with the 8-bit value, which party should handle output linefeeds and what their disposition should be. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc658.txt -- 7.3 Кб -- 15.10.1992
Похожие документы
Похожие документы
81247. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc660.txt
... These changes come in four areas: a) decoupling of the message number sequences of Hosts; b) Host/Host access control; c) expansion of the message number window from four to eight; and d) provision for messages outside the normal message number mechanism. ... The pool will be sufficiently large to seldom interfere with a pair of Hosts wishing to communicate. ... If the pair of Hosts is not allowed to communicate, a special type of Destination Dead Message (sub-code 3) is returned to the source Host....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc660.txt -- 5.9 Кб -- 15.10.1992
Похожие документы
Похожие документы
81248. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc657.txt
... 25, 1974) Online file: [ISI]<DCROCKER>NAOVTD.TXT TELNET OUTPUT VERTICAL TAB DISPOSITION OPTION 1. ... IAC DO NAOVTD The data sender requests or agrees to negotiate about output vertical tab character disposition with the data receiver. ... IAC SB NAOVTD DS <8-bit value> IAC SE The data sender specifies, with the 8-bit value, which party should handle output vertical tab characters and what their disposition should be. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc657.txt -- 6.6 Кб -- 15.10.1992
Похожие документы
Похожие документы
81249. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc655.txt
... IAC DO NAOFFD The data sender requests or agrees to negotiate about output formfeed disposition with the data receiver. ... Description of the Option The data sender and the data receiver use the 8-bit value along with the DS and DR SB commands as follows: 8-bit value Meaning 0 Command sender suggests that he alone will handle formfeeds, for the connection. 1 to 250 Command sender suggests that the other party alone should handle formfeeds, but suggests that the indicated value be used. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc655.txt -- 6.9 Кб -- 15.10.1992
Похожие документы
Похожие документы
81250. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc656.txt
TELNET OUTPUT VERTICAL TABSTOPS OPTION RFC 656, NIC 31159 (Oct. ... Command name and code NAOVTS 14 (Negotiate About Vertcial Tabstops) 2. ... IAC DO NAOVTS The data sender requests or agrees to negotiate about output vertical tabstops with the data receiver. ... IAC SB NAOVTS DS <8-bit value> ... <8-bit value> IAC SE The data sender specifies, with the 8-bit value(s), which party should handle output vertical tabstop considerations and what the stops should be. ... Default DON'T NAOVTS/WON'T NAOVTS. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc656.txt -- 5.7 Кб -- 15.10.1992
Похожие документы
Похожие документы
81251. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc654.txt
TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION RFC 654, NIC 31157 (Oct. ... Command name and code NAOHTD 12 (Negotiate About Output Horizontal Tab Disposition) 2. ... IAC DO NAOHTD The data sender requests or agrees to negotiate about output horizontal tab character disposition with the data receiver. ... IAC SB NAOHTD DS <8-bit value> IAC SE The data sender specifies, with the 8-bit value, which party should handle output horizontal tab characters and what their disposition should be. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc654.txt -- 7.0 Кб -- 15.10.1992
Похожие документы
Похожие документы
81252. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc652.txt
... 74 NIC #31155 Online file: [ISI]<DCROCKER>NAOCRD.TXT Telnet Output Carriage-Return Disposition Option 1. ... IAC DO NAOCRD The data sender requests or agrees to negotiate about output carriage-return character disposition with the data receiver. ... Telnet NAOCRD Option Page 3 254 Command sender suggests that the other party alone should handle carriage-returns but suggests waiting for a character to be transmitted (on the other simplex connection) before sending more data. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc652.txt -- 7.8 Кб -- 15.10.1992
Похожие документы
Похожие документы
81253. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc653.txt
TELNET OUTPUT HORIZONTAL TABSTOPS OPTION RFC 653, NIC 31156 (Oct. ... Command name and code NAOHTS 11 (Negotiate About Output Horizontal Tabstops) 2. ... IAC DO NAOHTS The data sender requests or agrees to negotiate about output horizontal tabstops with the data receiver. ... IAC SB NAOHTS DS <8-bit value> ... <8-bit value> IAC SE The data sender specifies, with the 8-bit value(s), which party should handle output horizontal tabstop considerations and what the stops should be. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc653.txt -- 5.6 Кб -- 15.10.1992
Похожие документы
Похожие документы
81254. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc644.txt
Network Working Group Bob Thomas Request for Comments: 644 BBN-TENEX Jul 1974 On the Problem of Signature Authentication for Network Mail This note describes the problem of signature authentication for network mail, presents a general approach to the problem and proposes a specific implementation of that approach. ... We shall discuss our approach using the following simple model for network mail: To send net mail a user invokes a mail sending process (SP) on his local host (SH). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc644.txt -- 10.3 Кб -- 15.10.1992
Похожие документы
Похожие документы
81255. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc643.txt
... See description of asynchronous replies below). ... The PDP-11 should reply DEPOSITED (Process, Address, Count) if successful or CAN'T DEPOSIT (Process, Address, Count) Page 3 if the deposit doesn't succeed, or the remote host isn't debugging the process. ... The PDP-11 should reply CONTENTS (Process, Address, Count, Byte String) if it can supply the bytes, or CAN'T EXAMINE (Process, Address, Count) if all the bytes don't exist in the address space, or the remote host isn't debugging the process. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc643.txt -- 13.3 Кб -- 15.10.1992
Похожие документы
Похожие документы
81256. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc640.txt
... The replies show the existence of an intermediate state if all preceding commands have been successful. ... 13 ICP 13a 120 13a1 220 13a1a 220 13a2 421 13a3 NWG/RFC# 640 JBP NJN 5-JUN-74 16:07 30843 Neigus FTP Reply Codes [8] Logon 13b USER 13b1 230 13b1a 530 13b1b 500 , 501 , 421 13b1c 331, 332 13b1d PASS 13b2 230 13b2a 202 13b2b 530 13b2c 500 , 501 , 503, 421 13b2d 332 13b2e ACCT 13b3 230 13b3a 202 13b3b 530 13b3c 500 , 501 , 503, 421 13b3d Logoff 13c QUIT 13c1 221 13c1a ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc640.txt -- 39.7 Кб -- 15.10.1992
Похожие документы
Похожие документы
81257. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc636.txt
NWG/RFC# 636 JDB BPC RST DCW3 MLK 23-OCT-75 22:27 30490 TIP / TENEX Reliability Improvements RFC 636 J. Burchfiel - BBN- TENEX B. Cosell - BBN-NET NIC 30490 R. Tomlinson - BBN- TENEX D. Walden - BBN-NET 10 June 1974 TIP / TENEX Reliability Improvements During the past months we have felt strong pressure to improve the reliability of TIP / TENEX network connection as improvement in the ... When a TIP user attempts to open a connection to any Host, the Host may be down. ... link ! ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc636.txt -- 20.4 Кб -- 15.10.1992
Похожие документы
Похожие документы
81258. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc624.txt
... Once a server has been set to the state where he is "passive" with regard to establishment of data connections, there is no convenient way for the user to make him "active" again. ... ACTV" is to have the same reply codes as "PASV". ... Design of an FTP server or user would be simpler if all command verbs were the same length. ... It is undesirable for ah FTP user to be required to keep a list of reply codes for each command, all of which mean "command accepted, continue". ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc624.txt -- 10.9 Кб -- 15.10.1992
Похожие документы
Похожие документы
81259. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc626.txt
Network Working Group L. Kleinrock (UCLA-NMC) Request for Comments: 626 H. Opderbeck (UCLA-NMC) NIC #22161 Mar 1974 "On a Possible Lockup Condition in the IMP Subnet Due to Message Sequencing" Lockup or deadlock conditions are one of the most serious system malfunctions that can occur in a computer system or network. ... A deadlock condition can occur if IMP B and IMP C also send a single-packet message in their stream of 8-packet measures which cannot be serviced for the same reason. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc626.txt -- 13.8 Кб -- 15.10.1992
Похожие документы
Похожие документы
81260. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc620.txt
Network Working Group Bill Ferguson (SRI-ARC) Request for Comments: 620 Mar 1974 NIC # 21993 Request for Monitor Host Table Updates The ARC/NIC group has successfully been running OFFICE-1 for several weeks now. Our NIC users have been transferred to that site, and are receiving all their computation from TYMSHARE. ... To effect this change, each TENEX site's monitor host table should be updated in the following manner. ... 253,TYMSHARE-TIP,USER!TIP) CC.( ... 2,ARC,NICKNAME!SERVER!USER!TENEX) CC.( ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc620.txt -- 2.9 Кб -- 15.10.1992
Похожие документы
Похожие документы