Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81821 - 81840 из 81894.
Упорядочить по:
URL
|
дате изменения
81821. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1045.txt
Network Working Group David Cheriton Request for Comments: 1045 Stanford University February 1988 VMTP: VERSATILE MESSAGE TRANSACTION PROTOCOL Protocol Specification STATUS OF THIS MEMO This RFC describes a protocol proposed as a standard for the Internet community. Comments are encouraged. Distribution of this document is unlimited. OVERVIEW This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically designed to support the transaction
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1045.txt -- 259.7 Кб -- 23.02.1988
Похожие документы
Похожие документы
81822. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1044.txt
Network Working Group K. Hardwick Request for Comments: 1044 NSC J. Lekashman NASA-Ames GE February 1988 Internet Protocol on Network Systems HYPERchannel Protocol Specification STATUS OF THIS MEMO The intent of this document is to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel [1] equipment. ... 4 Basic (16-bit address) Message Proper header . ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1044.txt -- 99.5 Кб -- 17.02.1988
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std45.txt -- 99.5 Кб -- 17.02.1988
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std45.txt -- 99.5 Кб -- 17.02.1988
Похожие документы
81823. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1043.txt
... SECTION 1 COMMAND NAME AND OPTION CODE 4 SECTION 2 COMMAND MEANINGS 4 Facilities Subcommands 4 Edit Subcommands 8 Transmit Subcommands 8 Erase Subcommands 10 Format Subcommands 10 Miscellaneous Subcommands 13 SECTION 3 DEFAULT AND MINIMAL IMPLEMENTATION 15 SECTION 4 MOTIVATION FOR THE OPTION 17 SECTION 5 DESCRIPTION AND IMPLEMENTATION RULES 17 The DODIIS DET Model 17 Negotiating the DET Option 18 DET Facilities Negotiation 18 General ... FACILITIES SUBCOMMANDS. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1043.txt -- 57.7 Кб -- 08.02.1988
Похожие документы
Похожие документы
81824. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1042.txt
Network Working Group J. Postel Request for Comments: 1042 J. Reynolds ISI Obsoletes: RFC-948 February 1988 A Standard for the Transmission of IP Datagrams over IEEE 802 Networks Status of this Memo This RFC specifies a standard method of encapsulating the Internet Protocol (IP) [1] datagrams and Address Resolution Protocol (ARP) [2] requests and replies on IEEE 802 Networks. ... This specification allows the use of either size of address within a given IEEE 802 network. ... Header Format Header .. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1042.txt -- 34.6 Кб -- 03.02.1988
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std43.txt -- 34.6 Кб -- 03.02.1988
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std43.txt -- 34.6 Кб -- 03.02.1988
Похожие документы
81825. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1041.txt
Network Working Group J. Rekhter Request For Comments: 1041 T.J. Watson Research Center, IBM January 1988 Telnet 3270 Regime Option STATUS OF THIS MEMO This RFC specifies a proposed standard for the Internet community. ... Motivation for the option This option allows a telnet server running VM or MVS to negotiate with the telnet client on the type of data stream (3270 or NVT ASCII) which both sides are willing support. ... Either Telnet client or Telnet server can initialize 3270-REGIME negotiation. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1041.txt -- 12.0 Кб -- 28.01.1988
Похожие документы
Похожие документы
81826. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1038.txt
... Basic Security: Used to carry security level and accrediting authority flags. 0 00011 var. ... Option type: 130 Option length: variable; minimum length: 4 The option identifies the U.S. security level to which the datagram is to be protected, and the accrediting authorities whose protection rules apply to each datagram. ... TYPE = 130 LENGTH CLASSIFICATION PROTECTION VARIABLE PROTECTION AUTHORITY LEVEL FLAGS FIGURE 10-A. SECURITY OPTION FORMAT 9.3.15.3.1 Length. ... The minimum length option is 4. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1038.txt -- 16.1 Кб -- 25.01.1988
Похожие документы
Похожие документы
81827. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1040.txt
Network Working Group J. Linn (BBNCC) Request for Comments: 1040 IAB Privacy Task Force Obsoletes RFCs: 989 January 1988 Privacy Enhancement for Internet Electronic Mail: Part I: Message Encipherment and Authentication Procedures STATUS OF THIS MEMO This RFC suggests a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. ... Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1040.txt -- 73.9 Кб -- 22.01.1988
Похожие документы
Похожие документы
81828. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1037.txt
Network Working Group B. Greenberg Request for Comments: 1037 S. Keene December 1987 NFILE - A File Access Protocol STATUS OF THIS MEMO This document includes a specification of the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark. The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas. A secondary goal is to make the
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1037.txt -- 189.0 Кб -- 17.12.1987
Похожие документы
Похожие документы
81829. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1036.txt
Network Working Group M. Horton Request for Comments: 1036 AT&T Bell Laboratories Obsoletes: RFC-850 R. Adams Center for Seismic Studies December 1987 Standard for Interchange of USENET Messages STATUS OF THIS MEMO This document defines the standard format for the interchange of network News messages among USENET hosts. ... Therefore, the rule is adopted that all USENET news messages must be formatted as valid Internet mail messages, according to the Internet standard RFC-822. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1036.txt -- 45.8 Кб -- 10.12.1987
Похожие документы
Похожие документы
81830. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1035.txt
... Standard RRs 13 3.3.1. ... To the user, the domain tree is a single information space; the resolver is responsible for hiding the distribution of data among name servers from the user. ... When the resolver processes a user query it asks a known name server for the information; in return, the resolver either receives the desired information or a referral to another name server. ... Resolvers answer user queries with information they acquire via queries to foreign name servers and the local cache. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1035.txt -- 120.7 Кб -- 24.11.1987
Похожие документы
Похожие документы
81831. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1034.txt
Network Working Group P. Mockapetris Request for Comments: 1034 ISI Obsoletes: RFCs 882, 883, 973 November 1987 DOMAIN NAMES - CONCEPTS AND FACILITIES 1. STATUS OF THIS MEMO This RFC is an introduction to the Domain Name System (DNS), and omits many details which can be found in a companion RFC, "Domain Names - Implementation and Specification" [RFC-1035]. That RFC assumes that the reader is familiar with the concepts discussed in this memo. A subset of DNS functions and data types constitute an official
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1034.txt -- 124.1 Кб -- 24.11.1987
Похожие документы
Похожие документы
81832. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1033.txt
Network Working Group M. Lottor Request For Comments: 1033 SRI International November 1987 DOMAIN ADMINISTRATORS OPERATIONS GUIDE STATUS OF THIS MEMO This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. ... A zone file typically contains all the data for a particular domain. ... For each zone it will normally contain the domain name of the zone and the file name that contains the data to load for the zone. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1033.txt -- 36.2 Кб -- 11.11.1987
Похожие документы
Похожие документы
81833. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1028.txt
... By this model, a protocol entity on a logically remote host (possibly the gateway itself) interacts with a protocol entity resident on the gateway in order to alter or retrieve named portions (variables) of the gateway state. ... The _GW_pr_in_egp_errors Variable The variable such that the initial portion of its name is represented symbolically as "_GW_pr_in_egp_errors" and numerically as: 01 04 01 03 05 has an integer value that represents the number of EGP protocol errors. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1028.txt -- 79.6 Кб -- 11.11.1987
Похожие документы
Похожие документы
81834. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1032.txt
Network Working Group M. Stahl Request for Comments: 1032 SRI International November 1987 DOMAIN ADMINISTRATORS GUIDE STATUS OF THIS MEMO This memo describes procedures for registering a domain with the Network Information Center (NIC) of Defense Data Network (DDN), and offers guidelines on the establishment and administration of a domain in accordance with the requirements specified in RFC-920. ... Lazear, W.D., "MILNET Name Domain Transition", RFC-1031, Mitre Corporation, October 1987. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1032.txt -- 29.0 Кб -- 10.11.1987
Похожие документы
Похожие документы
81835. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1031.txt
... The RFC is designed as an aid to implementors and administrators by providing 1) an overview of the transition process from host tables to domains, 2) a potential timetable for the transition, and 3) references to documentation and software relating to the DDN/ARPANET domain system. ... A likely scenario is that applications like TELNET and FTP will use the domain system and that MAIL will continue to use the host table for name resolution. ... His mail addresses are: ARPANET: sra@xx.lcs.mit.edu. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1031.txt -- 20.1 Кб -- 10.11.1987
Похожие документы
Похожие документы
81836. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1020.txt
Network Working Group S. Romano Request for Comments: 1020 M. Stahl Obsoletes RFCs: 997, 990, 960, 943, SRI 923, 900, 870, 820, 790, 776, 770, 762, November 1987 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 INTERNET NUMBERS STATUS OF THIS MEMO This memo is an official status report on the network numbers used in the Internet community. Distribution of this memo is unlimited. Introduction The responsibility for the assignment of IP numbers and ASNs has been assumed by Hostmaster at the
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1020.txt -- 141.6 Кб -- 10.11.1987
Похожие документы
Похожие документы
81837. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1030.txt
... All data are actually allocated by the application, given to the protocol layer, and copied into NETBLT packets. ... The table headers have the following definitions: BS/BI burst size in packets and burst interval in milliseconds PSZ number of bytes in DATA /LDATA packet data segment BFSZ number of bytes in NETBLT buffer XFSZ number of kilobytes in transfer NBUFS number of outstanding buffers #LOSS number of data packets lost #RXM number of data packets retransmitted DTMOS number of...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1030.txt -- 40.1 Кб -- 06.11.1987
Похожие документы
Похожие документы
81838. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1021.txt
Network Working Group C. Partridge Request For Comment: 1021 BBN/NNSC G. Trewitt Stanford October 1987 THE HIGH-LEVEL ENTITY MANAGEMENT SYSTEM (HEMS) STATUS OF THIS MEMO An overview of the RFCs which comprise the High-Level Entity Management System is provided. ... MONITORING AND CONTROL Historically, the IP community has divided network management into two distinct types of activities: monitoring and control. ... The Query Processor The query processor is the key to the management system. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1021.txt -- 13.4 Кб -- 29.10.1987
Похожие документы
Похожие документы
81839. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1024.txt
... Events contain an initial event object followed by an optional number of objects related to the event. ... InterfaceData ::= [0] IMPLICIT SET { addresses [0] IMPLICIT SET of IpAddress, mtu [1] IMPLICIT INTEGER , netMask [2] IMPLICIT IpAddress, pktsIn [3] IMPLICIT Counter , pktsOut [4] IMPLICIT Counter , inputPktsDropped [5] IMPLICIT Counter , outputPktsDropped [6] IMPLICIT Counter , bcastPktsIn [7] IMPLICIT Counter OPTIONAL , bcastPktsOut [8] IMPLICIT Counter ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1024.txt -- 120.5 Кб -- 29.10.1987
Похожие документы
Похожие документы
81840. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1023.txt
... The data in the entity is modeled as a hierarchy and specific items are named by giving the path from the root of the tree. ... ASN.1 data items may be either a "simple type" such as integer or octet string or a "structured type", a collection of data items. ... GET-MATCH array value template GET-MATCH array <array> should be a array (dictionary containing only one type of item). ... SET-MATCH array mvalue svalue SET-MATCH dict <array> should be a array (dictionary containing only one type of item)....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1023.txt -- 40.1 Кб -- 29.10.1987
Похожие документы
Похожие документы