Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81541 - 81560 из 81894.
[ В начало ] Пред. | 4074 |
4075 |
4076 |
4077 |
4078
|
4079 |
4080 |
4081 |
4082 |
4083 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
81541. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-internet-mib.txt
... A value of 0.0.0.0 indicates no address. ... INDEX { telnetSerialPortIndex } ::= { telnetSerialPortTable 1 } TelnetSerialPortEntry ::= SEQUENCE { telnetSerialPortIndex INTEGER , telnetSerialPortOptionDisplay INTEGER , telnetSerialPortCsiEscape INTEGER , telnetSerialPortEchoMode INTEGER , telnetSerialPortNewlineMode INTEGER , telnetSerialPortTransmitMode INTEGER , telnetSerialPortTransmitCharacterTimes INTEGER , telnetSerialPortAbortOutputCharacter INTEGER , telnetSerialPortAttentionCharacter...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-internet-mib.txt -- 149.0 Кб -- 07.11.1991
Похожие документы
Похожие документы
81542. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-bootstrap-server-mib.txt
... Corresponds directly to the value labeled 'Version' in the MANAGER STATUS display." ::= { activeEntry 6 } activeCurrentSequence OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The current dialog sequence number. ... Corresponds directly to the value labeled 'Dump Operations Completed:' in the MANAGER STATUS display." ::= { dump 5 } dumpActive OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "The number of dumps in progress. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-bootstrap-server-mib.txt -- 71.1 Кб -- 07.11.1991
Похожие документы
Похожие документы
81543. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-ethernet-mib.txt
XYPLEX ETHERNET MIB 23 May 91 Definitions of Managed Objects for Xyplex Ethernet Interfaces 23 May 1991 Xyplex Document Number 420-0547-A Xyplex, Inc. ... The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex. ::= { etherEntry 1 } etherAlignmentErrors OBJECT -TYPE SYNTAX Counter [Page 8] XYPLEX ETHERNET MIB 23 May 91 ACCESS read-only STATUS mandatory DESCRIPTION A count of frames received on a particular ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-ethernet-mib.txt -- 27.7 Кб -- 07.11.1991
Похожие документы
Похожие документы
81544. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-minimal-mib.txt
... Please express comments to Xyplex. ... Xyplex [Page 2] XYPLEX MINIMAL MIB 21 Oct 91 3. ... Corresponds directly to SERVER IDENTIFICATION and the value labeled 'Identification:' on the SERVER CHARACTERISTICS display. ::= { system 1 } Xyplex [Page 9] XYPLEX MINIMAL MIB 21 Oct 91 -- the Character group -- Implementation of this group is mandatory for all Xyplex -- systems with character stream physical ports charPhysNumber OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-minimal-mib.txt -- 49.4 Кб -- 07.11.1991
Похожие документы
Похожие документы
81545. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-system-mib.txt
... The System MIB is mandatory for all Xyplex systems. ... Corresponds directly to the value labeled 'Crate Transition Count: in the SERVER ALTERNATE STATUS display. ::= { xSystem 29 } sysResourceNumber OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION [Page 17] XYPLEX SYSTEM MIB 17 Oct 91 The number of resource entries in the Resource table. ::= { xSystem 30 } sysFeatureNumber OBJECT-TYPE SYNTAX INTEGER ACCESS read-only ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-system-mib.txt -- 46.5 Кб -- 07.11.1991
Похожие документы
Похожие документы
81546. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-lat-mib.txt
... Corresponds directly to the value labeled 'Discarded Nodes:' in the SERVER STATUS display." ::= { lat 12 } latInMessages OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of LAT messages received. ... Corresponds directly to the value labeled 'Multiple Node Addresses:' in the SERVER COUNTERS display." ::= { lat 17 } latInDuplicates OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of duplicate LAT messages received. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-lat-mib.txt -- 61.8 Кб -- 07.11.1991
Похожие документы
Похожие документы
81547. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-ieee-ethernet-hub-mib.txt
... Please express comments to Xyplex. ... The IEEE 802 Hub MIB is mandatory for all Xyplex hubs managed via SNMP. ... Definitions XYPLEX -IEEE- HUB - MIB DEFINITIONS ::= BEGIN IMPORTS enterprises FROM RFC1155-SMI DisplayString FROM RFC1158- MIB OBJECT-TYPE FROM RFC1212-CONCISE- MIB ; xyplex OBJECT IDENTIFIER ::= { enterprises 33 } ieeeHub OBJECT IDENTIFIER ::= { xyplex 10001 } -- From this point on, all object descriptors and -- identifiers are as specified in [11] except for the -- reduction...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-ieee-ethernet-hub-mib.txt -- 44.4 Кб -- 07.11.1991
Похожие документы
Похожие документы
81548. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-parameter-client-mib.txt
... Page 2] XYPLEX PARAMETER CLIENT MIB 18 Oct 91 3. ... Definitions XYPLEX -PARAM-CLIENT- MIB DEFINITIONS ::= BEGIN IMPORTS enterprises, Counter FROM RFC1155-SMI DisplayString FROM RFC1158- MIB OBJECT-TYPE FROM RFC1212-CONCISE- MIB DateTime, AddressType FROM XYPLEX -SYSTEM- MIB ; xyplex OBJECT IDENTIFIER ::= { enterprises 33 } paramClient OBJECT IDENTIFIER ::= { xyplex 7 } -- This MIB module uses the extended OBJECT-TYPE macro as -- defined in [9] -- this is the ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-parameter-client-mib.txt -- 34.8 Кб -- 07.11.1991
Похожие документы
Похожие документы
81549. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-ethernet-hub-mib.txt
XYPLEX ETHERNET HUB MIB 17 Oct 91 Definitions of Managed Objects for Xyplex Ethernet Hubs 17 October 1991 Xyplex Document Number 420-0540-A Xyplex, Inc. ... Abstract This memo defines a private portion of the Management Information Base (MIB), within the Xyplex branch, for use with SNMP over various transport services, such as UDP or [Page 1] XYPLEX ETHERNET HUB MIB 17 Oct 91 Ethernet. ... Page 2] XYPLEX ETHERNET HUB MIB 17 Oct 91 3. ... The Hub MIB is mandatory for all Xyplex hubs managed via SNMP. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-ethernet-hub-mib.txt -- 27.1 Кб -- 07.11.1991
Похожие документы
Похожие документы
81550. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-bootstrap-client-mib.txt
XYPLEX BOOTSTRAP CLIENT MIB 22 May 91 Definitions of Managed Objects for Xyplex Bootstrap Clients 22 May 1991 Xyplex Document Number 420-0537-A Xyplex, Inc. ... Abstract This memo defines a private portion of the Management Information Base (MIB), within the Xyplex branch, for use [Page 1] XYPLEX BOOTSTRAP CLIENT MIB 22 May 91 with SNMP over various transport services, such as UDP or Ethernet. In particular, it defines objects for managing a client of Xyplex bootstrap service. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/xyplex-bootstrap-client-mib.txt -- 15.9 Кб -- 07.11.1991
Похожие документы
Похожие документы
81551. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1270.txt
Network Working Group F. Kastenholz, Editor Request for Comments: 1270 Clearpoint Research Corporation October 1991 SNMP Communications Services Status of This Memo This memo provides information for the Internet community. ... Connection Oriented vs. ... In the short-term, the Simple Network Management Protocol (SNMP), defined in RFC 1067, was to be used to manage nodes in the Internet community. ... For SNMP, connectionless transport service (UDP) is specified in the Protocol Specification [1]. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1270.txt -- 26.6 Кб -- 30.10.1991
Похожие документы
Похожие документы
81552. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1269.txt
... Definitions RFC1269-MIB DEFINITIONS ::= BEGIN IMPORTS NetworkAddress, IpAddress, Counter FROM RFC1155-SMI mib-2 FROM RFC1213-MIB OBJECT-TYPE FROM RFC-1212 TRAP-TYPE FROM RFC-1215; -- This MIB module uses the extended OBJECT-TYPE macro as -- defined in [9], and the TRAP-TYPE macro as defined -- in [10]. bgp OBJECT IDENTIFIER ::= { mib-2 15 } bgpVersion OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "Vector of supported BGP protocol version numbers. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1269.txt -- 26.1 Кб -- 26.10.1991
Похожие документы
Похожие документы
81553. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1268.txt
... Obsoletes: RFC 1164 P. Gross ANS Editors October 1991 Application of the Border Gateway Protocol in the Internet Status of this Memo This protocol is being developed by the Border Gateway Protocol Working Group (BGP) of the Internet Engineering Task Force (IETF). ... BGP | ... Each border gateway should use identical tags for announcing exterior routing information (received via BGP) both into the IGP and into Internal BGP when propagating this information to other border gateways within the same AS...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1268.txt -- 31.4 Кб -- 25.10.1991
Похожие документы
Похожие документы
81554. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1267.txt
... The error notification mechanism used in BGP assumes that the transport protocol supports a "graceful" close, i.e., that all outstanding data will be delivered before the connection is closed. ... Total Path Attributes Length | ... If a system does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the NOTIFICATION message with Hold Timer Expired Error Code must be sent and the BGP connection closed...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1267.txt -- 79.8 Кб -- 25.10.1991
Похожие документы
Похожие документы
81555. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1266.txt
... October 1991 Experience with the BGP Protocol 1. ... BGP is an inter-autonomous system routing protocol designed for the TCP/IP internets. ... This is because a large percentage of packets carrying BGP information are being dropped due to congestion. ... Therefore, since BGP is not the cause of congestion, and cannot directly influence dropping at the routers, replacing TCP (as the BGP transport) with another transport protocol would have no effect on packets being dropped due to congestion. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1266.txt -- 22.4 Кб -- 25.10.1991
Похожие документы
Похожие документы
81556. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1265.txt
... BGP is an inter-autonomous system routing protocol designed for the TCP/IP internets. ... If we denote the total number of networks in the Internet by N, the mean AS distance of the Internet by M (distance at the level of an autonomous system , expressed in terms of the number of autonomous systems), the total number of autonomous systems in the Internet by A, and assume that the networks are uniformly distributed among the autonomous systems, then the worst case amount of ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1265.txt -- 21.2 Кб -- 25.10.1991
Похожие документы
Похожие документы
81557. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1264.txt
Network Working Group R. Hinden Request for Comments: 1264 BBN October 1991 Internet Engineering Task Force Internet Routing Protocol Standardization Criteria Status of this Memo This informational RFC presents procedures for creating and documenting Internet standards on routing protocols. ... 6) There must be operational experience with the routing protocol. ... 6) No operational experience is required for the routing protocol at this stage in the standardization process. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1264.txt -- 17.6 Кб -- 25.10.1991
Похожие документы
Похожие документы
81558. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1263.txt
... It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve the Internet protocol suite. ... Backward Compatible Extensions In a backward compatible extension, the protocol is modified in such a fashion that the new version of the protocol can transparently inter-operate with existing versions of the protocol. This generally implies no changes to the protocol's header. ... Protocol ID | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1263.txt -- 53.8 Кб -- 19.10.1991
Похожие документы
Похожие документы
81559. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc809.txt
INDRA Note 1185 INDRA Feb. 1982 Working Paper RFC 809 UCL FACSIMILE SYSTEM Tawei Chang ABSTRACT: This note describes the features of the computerised facsimile system developed in the Department of Computer Science at UCL. First its functions are considered and the related experimental work are reported. Then the disciplines for system design are discussed. Finally, the implementation of the system are described, while detailed description are given as appendices. Department of Computer Science University
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc809.txt -- 162.6 Кб -- 17.10.1991
Похожие документы
Похожие документы
81560. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc808.txt
Network Working Group J. Postel Request for Comments: 808 ISI 1 March 1982 SUMMARY OF COMPUTER MAIL SERVICES MEETING HELD AT BBN ON 10 JANUARY 1979 Introduction: This note is a very belated attempt to document a meeting that was held three years ago to discuss the state of computer mail in the ARPA community and to reach some conclusions to guide the further development of computer mail systems such that a coherent total mail service would continue to be provided. ... Managing the Message Service 5. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc808.txt -- 16.1 Кб -- 17.10.1991
Похожие документы
Похожие документы