Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81841 - 81860 из 81894.
Упорядочить по:
URL
|
дате изменения
81841. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1022.txt
... Partridge Trewitt [Page 2] RFC 1022 HEMS Protocol October 1987 STANDARD MESSAGE FORMAT Every HEMP message is put in the general form shown in Figure 1. +-------------------------------+ : leader : +-------------------------------+ : encryption section : +-------------------------------+ : reply encryption section : +-------------------------------+ : authentication ... The data section of all protocol error messages has the same format, which is shown in Figure 10. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1022.txt -- 25.1 Кб -- 29.10.1987
Похожие документы
Похожие документы
81842. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1027.txt
Network Working Group Smoot Carl-Mitchell Request for Comments: 1027 Texas Internet Consulting John S. Quarterman Texas Internet Consulting October 1987 Using ARP to Implement Transparent Subnet Gateways Status of this Memo This RFC describes the use of the Ethernet Address Resolution Protocol (ARP) by subnet gateways to permit hosts on the connected subnets to communicate without being aware of the existence of subnets, using the technique of "Proxy ARP" [6]. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1027.txt -- 21.4 Кб -- 26.10.1987
Похожие документы
Похожие документы
81843. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1026.txt
... Component Ordering In most cases, ordering of O/R name components is not significant for the mappings specified by this document. However, Organisational Units and Domain Defined Attributes are specified as SEQUENCE, in P1.ORName, and so their order may be significant. ... In particular, there are some difficulties where Organisation or PRMD is omitted: The following sentence of RFC-987 should be removed: 4.2.1 (Page 27): "If one of the hierarchical components is omitted .... tuple)." ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1026.txt -- 7.7 Кб -- 05.10.1987
Похожие документы
Похожие документы
81844. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1025.txt
... In general, this is done by using a test program or user Telnet program to open connections to your own or other TCP implementations. ... Featherweight Division 1 point for talking to yourself (opening a connection). 1 point for saying something to yourself (sending and receiving data). 1 point for gracefully ending the conversation (closing the connection without crashing). 2 points for repeating the above without reinitializing the TCP. 5 points for a complete conversation via the testing gateway....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1025.txt -- 12.0 Кб -- 05.10.1987
Похожие документы
Похожие документы
81845. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1019.txt
... Standard Mathematical Systems - a Proposed Architecture We postulate that there is an "Abstract Syntax" for any mathematical expression. ... If pointing is supported, then a DISP component must be able to pass back the selected subexpression(s) in Abstract Syntax. ... For example, the ED should be able to receive a standard Abstract Syntax representation for an expression, plus an editing command in Abstract Syntax (e.g., Edit[expr, cmd]), and return an Abstract Syntax representation for the result....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1019.txt -- 21.2 Кб -- 25.09.1987
Похожие документы
Похожие документы
81846. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1017.txt
Network Working Group Barry M. Leiner Request for Comments: 1017 RIACS August 1987 Network Requirements for Scientific Research Internet Task Force on Scientific Computing STATUS OF THIS MEMO This RFC identifies the requirements on communication networks for supporting scientific research. ... The user needs to access resources available on the network, and needs to obtain a name or address. ... The identification scheme used for access to the network should be available for use by resources as well. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1017.txt -- 48.3 Кб -- 12.08.1987
Похожие документы
Похожие документы
81847. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1018.txt
Network Working Group A. McKenzie Request for Comments: 1018 BBN Labs August 1987 Some Comments on SQuID Status of this Memo This memo is a discussion of some of the ideas expressed in RFC-1016 on Source Quench. This memo introduces the distinction of the cause of congestion in a gateway between the effects of "Funneling" and "Mismatch". ... One form of congestion is the result of the merger of several independent data streams from diverse sources at a common point in their communication path. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1018.txt -- 8.6 Кб -- 12.08.1987
Похожие документы
Похожие документы
81848. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1016.txt
... The proposal is for each source host IP module to introduce some delay between datagrams sent to the same destination host. ... If a gateway discards a datagram, it may send a source quench message to the Internet source host of the datagram. ... A significant problem is the delay between when some intermediate node starts dropping datagrams and sending source quenches to the time when the source quenches arrive at the source host and can begin to effect the behavior at the data source. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1016.txt -- 46.8 Кб -- 18.07.1987
Похожие документы
Похожие документы
81849. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1015.txt
Network Working Group Barry M. Leiner Request for Comments: 1015 RIACS July 1987 Implementation Plan for Interagency Research Internet STATUS OF THIS MEMO The RFC proposes an Interagency Research Internet as the natural outgrowth of the current Internet. ... There are networks being supported by a number of the Federal agencies interested in scientific research, and many scientists throughout the country have access to one or more of these networks. ... Agency | ... Network Research Community |- ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1015.txt -- 61.4 Кб -- 15.07.1987
Похожие документы
Похожие документы
81850. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1014.txt
Network Working Group Sun Microsystems, Inc. Request for Comments: 1014 June 1987 XDR: External Data Representation Standard STATUS OF THIS MEMO This RFC describes a standard that Sun Microsystems, Inc., and others are using, one we wish to propose for the Internet's consideration. ... The XDR standard makes the following assumption: that bytes (or octets) are portable, where a byte is defined to be 8 bits of data. ... For each data type in the language we show a general paradigm declaration. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1014.txt -- 38.3 Кб -- 30.06.1987
Похожие документы
Похожие документы
81851. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1013.txt
Network Working Group Robert W. Scheifler Request for Comments: 1013 June 1987 X WINDOW SYSTEM PROTOCOL, VERSION 11 Alpha Update April 1987 Copyright (c) 1986, 1987 Massachusetts Institute of Technology X Window System is a trademark of M.I.T. Status of this Memo This RFC is distributed to the Internet community for information only. It does not establish an Internet standard. The X window system has been widely reviewed and tested. The internet community is encouraged to experiment with it. Distribution of
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1013.txt -- 234.3 Кб -- 25.06.1987
Похожие документы
Похожие документы
81852. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1008.txt
Network Working Group Wayne McCoy Request for Comments: 1008 June 1987 IMPLEMENTATION GUIDE FOR THE ISO TRANSPORT PROTOCOL Status of this Memo This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. Distribution of this memo is unlimited. IMPLEMENTATION GUIDE FOR THE ISO TRANSPORT
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1008.txt -- 196.7 Кб -- 11.06.1987
Похожие документы
Похожие документы
81853. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1007.txt
... Transport protocol data unit; g. CR. ... CLASS 2 | ... TS User-Data | ... The elections of these options to be taken in an implementation to which this supplement applies are defined in Paragraph 4.4. a. a. Class of service --agreement as to one of five classes of transport service , depending on which classes are supported by the entities, the quality of the network service available and the degree of resilience to network errors and failure required by the peer transport users. b....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1007.txt -- 49.8 Кб -- 11.06.1987
Похожие документы
Похожие документы
81854. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1009.txt
Network Working Group R. Braden Request for Comments: 1009 J. Postel Obsoletes: 985 ISI June 1987 Requirements for Internet Gateways Status of this Memo This document is a formal statement of the requirements to be met by gateways used in the Internet system. As such, it is an official specification for the Internet community. Distribution of this memo is unlimited. This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols. While it was written
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1009.txt -- 123.1 Кб -- 07.06.1987
Похожие документы
Похожие документы
81855. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1012.txt
Network Working Group J. Reynolds Request for Comments: 1012 J. Postel ISI June 1987 BIBLIOGRAPHY OF REQUEST FOR COMMENTS 1 THROUGH 999 STATUS OF THIS MEMO This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. Distribution of this memo is unlimited. REQUEST FOR COMMENTS DOCUMENTS 1 - Crocker, Steve, "Host Software", RFC 1 (NIC 4687), UCLA/NMC, 7 April 1969. 2 - Duvall, Bill,
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1012.txt -- 123.5 Кб -- 06.06.1987
Похожие документы
Похожие документы
81856. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1011.txt
Network Working Group J. Reynolds Request for Comments: 1011 J. Postel ISI Obsoletes: RFCs 991, 961, 943, 924, 901, 880, 840 May 1987 OFFICIAL INTERNET PROTOCOLS STATUS OF THIS MEMO This memo is an official status report on the protocols used in the Internet community. ... INTRODUCTION 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. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1011.txt -- 71.0 Кб -- 30.05.1987
Похожие документы
Похожие документы
81857. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1010.txt
Network Working Group J. Reynolds Request for Comments: 1010 J. Postel ISI Obsoletes RFCs: 990, 960, 943, 923, 900, 870, May 1987 820, 790, 776, 770, 762, 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 ASSIGNED NUMBERS Status of this Memo This memo is an official status report on the numbers used in protocols in the Internet community. ... 91] Reynolds, J. and J. Postel, "Official Internet Protocols", RFC 1011, Information Sciences Institute, May 1987. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1010.txt -- 74.9 Кб -- 30.05.1987
Похожие документы
Похожие документы
81858. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc826.txt
Network Working Group David C. Plummer Request For Comments: 826 (DCP@MIT-MC) November 1982 An Ethernet Address Resolution Protocol -- or -- Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware Abstract The implementation of protocol P on a sending host S decides, through protocol P's routing mechanism, that it wants to transmit to a target host T located some place on a connected piece of 10Mbit Ethernet cable. ... Am I the target protocol address? ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc826.txt -- 22.1 Кб -- 11.05.1987
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std37.txt -- 22.1 Кб -- 11.05.1987
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std37.txt -- 22.1 Кб -- 11.05.1987
Похожие документы
81859. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1005.txt
... These enhancements increase the size of the PSN field, allow ARPANET hosts to use logical names to address each other, allow for the communication of type-of-service information from the host to the PSN and enable the PSN to provide congestion feedback to the host on a connection basis. ... HOST | ... In these cases, the host can submit a type 11 (Name Server Request) message to the PSN, which requests the PSN to translate the destination name and return a list of the addresses to which it maps. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1005.txt -- 67.5 Кб -- 07.05.1987
Похожие документы
Похожие документы
81860. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1004.txt
... The network may drop, duplicate or deliver messages with errors. ... The procedures are intended for distributed systems where each user i runs a common protocol automaton using private state variables for each of possibly several associations simultaneously, one for each user j. An association is initiated by interrogating the Cookie Jar for a one-time key K(i,j), which is used to encrypt the checksum which authenticates messages exchanged between the users. ... message ID +-----------+-----------+...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1004.txt -- 21.5 Кб -- 22.04.1987
Похожие документы
Похожие документы