Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81281 - 81300 из 81894.
[ В начало ] Пред. | 4061 |
4062 |
4063 |
4064 |
4065
|
4066 |
4067 |
4068 |
4069 |
4070 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
81281. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc892.txt
Network Working Group ISO Request for Comments: 892 December 1983 ISO Transport Protocol Specification This document is distributed as an RFC for information only. It does not specify a standard for the ARPA Internet. Note: This document appeared in: ISO/TC97/SC16/WG6. Information Processing Systems - Open Systems Interconnection - Transport Protocol Specification. Computer Communication Review 12, 3-4 (July/October 1982), pp. 24-67. and differs from it only in format. Table of Contents 0. Introduction 1.
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc892.txt -- 155.4 Кб -- 23.09.1992
Похожие документы
Похожие документы
81282. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc890.txt
... The Future Situation In the future, as it is currently envisioned, there will be a number of co-equal autonomous systems of gateways. ... Some gateways of each autonomous system will exchange routing informations with some gateways of other autonomous systems via an Exterior Gateway Protocol (EGP) [2]. ... Some gateway of each autonomous system must exchange routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc890.txt -- 6.8 Кб -- 23.09.1992
Похожие документы
Похожие документы
81283. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc889.txt
Network Working Group D.L. Mills Request for Comments: 889 December 1983 Internet Delay Experiments This memo reports on some measurement experiments and suggests some possible improvements to the TCP retransmission timeout calculation. ... One series of experiments was designed to determine the network delays with respect to packet length, while the other was designed to assess the effectiveness of the TCP retransmission-timeout algorithm specified in the standards documents. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc889.txt -- 27.5 Кб -- 23.09.1992
Похожие документы
Похожие документы
81284. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc888.txt
RFC 888 "STUB" EXTERIOR GATEWAY PROTOCOL Linda J. Seamonson Eric C. Rosen BBN Communications January 1984 This note describes the Exterior Gateway Protocol used to connect Stub Gateways to an Autonomous System of core Gateways. ... 5 - RFC 888 JANUARY 1984 The Exterior Gateway Protocol has three parts: (a) Neighbor Acquisition Protocol, (b) Neighbor Reachability Protocol, and (c) Network Reachability determination. ... The gateway should maintain one sequence number per neighbor. ... EGP Version # ! ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc888.txt -- 53.0 Кб -- 23.09.1992
Похожие документы
Похожие документы
81285. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc887.txt
Network Working Group M. Accetta Request for Comments: 887 Carnegie-Mellon University December 1983 RESOURCE LOCATION PROTOCOL This note describes a resource location protocol for use in the ARPA Internet. ... Protocol Summary The Resource Location Protocol is a simple request/reply procedure. ... Each receiving host examines the list of resources named in the request packet, determines which of the resources it provides, and returns a reply message to the querying host in confirmation. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc887.txt -- 36.9 Кб -- 23.09.1992
Похожие документы
Похожие документы
81286. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc886.txt
Request For Comments: 886 Proposed Standard for Message Header Munging Thu Dec 15 03:37:52 1983 Marshall T. Rose Department of Information and Computer Science University of California, Irvine Irvine, CA 92717 MRose.UCI@Rand-Relay This memo proposes a standard for the ARPA Internet community. ... Page 15 Request For Comments: 886 M. Rose Proposed Standard for Message Header Munging UCI Appendices Minimal Canonical Forms This memo defines the minimal canonical forms for the 822 standard. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc886.txt -- 30.8 Кб -- 23.09.1992
Похожие документы
Похожие документы
81287. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc885.txt
... Command Meanings IAC WILL END-OF-RECORD The sender of this command requests permission to begin transmission of the Telnet END-OF-RECORD (EOR) code when transmitting data characters, or the sender of this command confirms it will now begin transmission of EORs with transmitted data characters. IAC WON'T END-OF-RECORD The sender of this command demands to stop transmitting, or to refuses to begin transmitting, the EOR code when transmitting data characters. ... The code for EOR is 239 (decimal). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc885.txt -- 4.2 Кб -- 23.09.1992
Похожие документы
Похожие документы
81288. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc884.txt
... Command Meanings IAC WILL TERMINAL-TYPE Sender is willing to send terminal type information in a subsequent sub-negotiation IAC DO TERMINAL-TYPE Sender is willing to receive terminal type information in a subsequent sub-negotiation IAC DON'T TERMINAL-TYPE Sender refuses to accept terminal type information IAC WON'T TERMINAL-TYPE Sender refuses to send terminal type information IAC SB TERMINAL-TYPE SEND IAC SE Sender requests receiver to transmit his (the receiver's) terminal type. ... IAC SE command...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc884.txt -- 8.7 Кб -- 23.09.1992
Похожие документы
Похожие документы
81289. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc883.txt
Network Working Group P. Mockapetris Request for Comments: 883 ISI November 1983 DOMAIN NAMES - IMPLEMENTATION and SPECIFICATION +-----------------------------------------------------+ | | | This memo discusses the implementation of domain | | name servers and resolvers, specifies the format of | | transactions, and discusses the use of domain names | | in the context of existing mail systems and other | | network software. | | | | This memo assumes that the reader is familiar with | | RFC 882, "Domain
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc883.txt -- 172.0 Кб -- 23.09.1992
Похожие документы
Похожие документы
81290. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc882.txt
... From a name server's point of view, the domain system consists of separate sets of local information called zones. ... Queries Queries to a name server must include a domain name which identifies the target resource set (QNAME), and the type and class of desired resource records. ... When presented with a query for a domain name over which it has authority, a name server returns the desired resource information or an indication that the query refers to a domain name or resource that does not exist. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc882.txt -- 78.9 Кб -- 23.09.1992
Похожие документы
Похожие документы
81291. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc881.txt
Network Working Group J. Postel Request for Comments: 881 ISI November 1983 The Domain Names Plan and Schedule This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA Internet community. ... The most likely case is for a computer mail message sent from an ARPA community user on a host know to name servers but not in the central table to a user on a DDN community host that relies on a local copy of the central table. ... HOSTS.TXT is updated. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc881.txt -- 23.9 Кб -- 23.09.1992
Похожие документы
Похожие документы
81292. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc880.txt
Network Working Group J. Reynolds Request for Comments: 880 J. Postel ISI Obsoletes: RFC 840 October 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: RFC 822 - Mail Header Format Standards This has been revised since the IPTW, it is in the "Internet Mail Protocols" volume of November 1982. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc880.txt -- 37.5 Кб -- 23.09.1992
Похожие документы
Похожие документы
81293. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc879.txt
Network Working Group J. Postel Request for Comments: 879 ISI November 1983 The TCP Maximum Segment Size and Related Topics This memo discusses the TCP Maximum Segment Size Option and related topics. ... Introduction This memo discusses the TCP Maximum Segment Size and its relation to the IP Maximum Datagram Size. ... This Maximum Segment Size (MSS) announcement (often mistakenly called a negotiation) is sent from the data receiver to the data sender and says "I can accept TCP segments up to size X". ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc879.txt -- 22.5 Кб -- 23.09.1992
Похожие документы
Похожие документы
81294. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc878.txt
Request for Comments: 878 Obsoletes RFCs: 851, 802 The ARPANET 1822L Host Access Protocol RFC 878 Andrew G. Malis ARPANET Mail: malis@bbn-unix BBN Communications Corp. ... If an 1822L name is being used to specify the destination - 13 - 1822L Host Access Protocol December 1983 RFC 878 host, and the name maps to only one authorized host port, then a type 7 message will also be sent to the source host. ... 36 - 1822L Host Access Protocol December 1983 RFC 878 Type 8: Error in Data - See 1822(3.4). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc878.txt -- 74.0 Кб -- 23.09.1992
Похожие документы
Похожие документы
81295. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc877.txt
Network Working Group J. T. Korb Request for Comments: 877 Purdue University September 1983 A Standard for the Transmission of IP Datagrams Over Public Data Networks This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks. An X.25 virtual circuit is opened on demand when a datagram arrives at the network interface for transmission. ... 1.4 Either site may close a virtual circuit. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc877.txt -- 4.2 Кб -- 23.09.1992
Похожие документы
Похожие документы
81296. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc876.txt
... See sections 4.2 and 4.3 of RFC 821.) ... There are six result entries for each host : Claim SMTP + = the host table lists this host as supporting SMTP ; - = such support is not listed Arpanet + = a connection could be opened from ISI-VAXA - = no such connection could be opened ISI- Net + = a connection could be opened from ISI-MOE - = no such connection could be opened VRFY Post + = the command VRFY postmaster evoked a positive reply - = it did not RCPT ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc876.txt -- 37.9 Кб -- 23.09.1992
Похожие документы
Похожие документы
81297. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc875.txt
... Some protocol sets have such severe functionality mismatches that proper T/ MG's cannot be generated for them; all attempts to mesh heterogeneous suites are subject to numerous problems, including the introduction ... subnetwork alternate routing, loss of functionality, difficulty of Flow Control resolution, higher cost than non-translating/mapping Gateways , and the necessity of re-creating T/ MG's when a given suite changes ... Host addressing is the most significant problem. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc875.txt -- 23.3 Кб -- 23.09.1992
Похожие документы
Похожие документы
81298. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc874.txt
INC-PROJECT, MAP-CRITIQUE.NLS.10, >, 12-Aug-83 11:46 AMW ;;;; RFC 874 September 1982 M82-50 A CRITIQUE OF X.25 M.A. PADLIPSKY THE MITRE CORPORATION Bedford, Massachusetts ABSTRACT The widely touted network interface protocol, "X.25", and its attendant conceptual framework, the International Standards Organization's Reference Model for Open System Interconnection (ISORM), are analyzed and found wanting. ... That is, earlier references to "the X.25 protocol(s)" were not typographical errors. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc874.txt -- 36.5 Кб -- 23.09.1992
Похожие документы
Похожие документы
81299. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc873.txt
INC-PROJECT, MAP-ILLUSION.NLS.8, , 12-Aug-83 11:44 AMW ;;;; RFC 873 September 1982 M82-49 THE ILLUSION OF VENDOR SUPPORT M.A. PADLIPSKY THE MITRE CORPORATION Bedford, Massachusetts ABSTRACT The sometimes-held position that vendor supplied intercomputer networking protocols based upon the International Standards Organization's Reference Model for Open System Interconnection are worth waiting for, in particular in preference to protocols based upon the ... Are Vendors similarly motivated? ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc873.txt -- 23.6 Кб -- 23.09.1992
Похожие документы
Похожие документы
81300. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc872.txt
RFC 872 September 1982 M82-48 TCP-ON-A-LAN M.A. PADLIPSKY THE MITRE CORPORATION Bedford, Massachusetts Abstract The sometimes-held position that the DoD Standard Transmission Control Protocol (TCP) and Internet Protocol (IP) are inappropriate for use "on" a Local Area Network (LAN) is shown to be fallacious. ... This adjunct, the Internet Protocol (IP) was designed as a separate protocol from TCP, however, in order to allow it to play the same role it plays for TCP for other Host-Host protocols too. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc872.txt -- 22.9 Кб -- 23.09.1992
Похожие документы
Похожие документы