Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81501 - 81520 из 81894.
[ В начало ] Пред. | 4072 |
4073 |
4074 |
4075 |
4076
|
4077 |
4078 |
4079 |
4080 |
4081 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
81501. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.tl1mib.txt
Timeplex TIME/LAN 100 Management Information Base January 7, 1992 Table of Contents Table of Contents 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . 1 2. OBJECTS . . . . . . . . . . . . . . . . . . . . . . . . . 1 2.1. Object Definitions . . . . . . . . . . . . . . . 2 2.2. TL1 System Group . . . . . . . . . . . . . . . . 3 2.3. TL1 Interfaces Group . . . . . . . . . . . . . . 4 2.4. TL1 IP Group . . . . . . . . . . . . . . . . . . 8 2.5. TL1 TCP Group . . . . . . . . . . . . . . . . . 22
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.tl1mib.txt -- 317.0 Кб -- 19.02.1992
Похожие документы
Похожие документы
81502. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.tl1traps.txt
... SPECIFIC TRAPS . ... OSPF Traps . ... Generic field: 1 VBL: TL1 MIB variable 'tl1snmpLastTrapMessage' 2 Timeplex TIME/LAN 100 Enterprise-Specific Traps August 26, 1991 LINKDOWN TRAP Cause: issued after a network link interface has been declared down. ... Specific field: 193 VBL: TL1 MIB variable 'tl1snmpLastTrapMessage' 5 Timeplex TIME/LAN 100 Enterprise-Specific Traps August 26, 1991 T5 NEW LSA RECEIVED Cause: issued when OSPF detects the receipt of a new instantiation of a link state advertisement...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.tl1traps.txt -- 13.6 Кб -- 19.02.1992
Похожие документы
Похожие документы
81503. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.umib.txt
... Timeplex DDN Group -- Timeplex X25 Group -- Timeplex FDDI Group -- Timeplex TLIP Group The following groups have been reserved (see Object Definitions), but no objects have yet been identified within these groups: -- Timeplex AT (Address Translation) Group -- Timeplex ICMP Group -- Timeplex RIP Group -- Timeplex UDP Group Object Definitions enterprises see RFC 1066 timeplex OBJECT IDENTIFIER ::= { enterprises 16 } umgmt ... Access: read-write. Status: mandatory. ... Access: read-only. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.umib.txt -- 55.8 Кб -- 18.02.1992
Похожие документы
Похожие документы
81504. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.utraps.txt
... The SNMP Trap messages are divided into 2 groups: generic and specific. ... The following defines the generic traps together with the values of their respective 'generic' and 'specific' fields: COLDSTART TRAP Cause: issued upon power-up. ... Generic field: 2 Specific field: reason (bits 30-31) 0 = scheduled 1 = link error 2 = indeterminate 3 = frame reject state information (bits 0-23) LINKUP TRAP Cause: issued after a network link interface (LAPB) has been declared up. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/timeplex.utraps.txt -- 6.6 Кб -- 18.02.1992
Похожие документы
Похожие документы
81505. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1301.txt
... Protocol description 3 2.1 Definition of terms 3 2.2 Packet format 6 2.2.1. ... Master quit 30 3.3.3. ... The process receiving the nak[deny] must report the failure to its client. empty(2) dally(0) An empty[dally] packet is multicast to maintain synchronization when no client data is available. cancel(1) If a producer finds itself in possession of a transmit token and has no data to send, it may cancel the token [request] by multicasting an empty[cancel] message . hibernate(2) If the ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1301.txt -- 90.8 Кб -- 18.02.1992
Похожие документы
Похожие документы
81506. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RIPEnotes/ripe-nic2.txt
RIPE NCC Activity Plan R. Blokzijl May 5, 1991 ref.: ripe-w07 Introduction This document describes the activity plan for the proposed RIPE Network Co- ordination Center (NCC). ... The NCC will coordinate and execute the exchange of database informa- tion with NCC's outside Europe. The result will be that for the end user of the database one uniform set of global information will be available. ... While some basic support will be given the NCC will not provide full support for these tools. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RIPEnotes/ripe-nic2.txt -- 11.3 Кб -- 07.02.1992
Похожие документы
Похожие документы
81507. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RIPEnotes/ripe-nic.txt
version 1.6 ripe-w06 RIPE Network Coordination Center (RIPE NCC) R.Blokzijl, Y.Devillers, D.Karrenberg, R.Volk 16 September, 1990 1 Introduction Experience in the RIPE community, and in the Internet community at large, has shown that certain information and coordination services are needed for the proper functioning of the Internet. ... In accordance with the RIPE Terms of Reference, the main objective of the RIPE NCC is to give support to the networking organisations that cooperate in RIPE. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RIPEnotes/ripe-nic.txt -- 7.5 Кб -- 07.02.1992
Похожие документы
Похожие документы
81508. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RIPEnotes/ripe-ncc.txt
Procedures to set up the RIPE NCC --------------------------------- R. Blokzijl June 10, 1991 (annex to ripe-w07) 1. ... At the 8th RIPE meeting it was decided to request RARE to act as the organisation that provides the legal environment for the RIPE NCC. ... A selection board consisting of representatives from RIPE and the RARE EC will appoint the NCC staff. ... A selection board consisting of representatives of RIPE, the RARE REC and the NCC manager will do the final selection. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RIPEnotes/ripe-ncc.txt -- 3.8 Кб -- 07.02.1992
Похожие документы
Похожие документы
81509. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1300.txt
Network Working Group S. Greenfield Request for Comments: 1300 Ziff-Davis February 1992 Remembrances of Things Past Status of this Memo This memo provides information for the Internet community. ... Distribution of this memo is unlimited. ... Author's Address Stanley R. Greenfield Ziff-Davis One Park Avenue New York, NY 10016 EMail: 0004689513@mcimail.com Greenfield [Page 4] ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1300.txt -- 5.8 Кб -- 06.02.1992
Похожие документы
Похожие документы
81510. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1298.txt
... February 1992 SNMP over IPX Status of this Memo This memo provides information for the Internet community. ... Abstract This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. ... This memo addresses the use of SNMP over the IPX protocol, which has become quite widespread principally due to the popularity of Novell NetWare. ... 2] Novell, Inc., ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1298.txt -- 8.7 Кб -- 06.02.1992
Похожие документы
Похожие документы
81511. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1297.txt
... January 1992 NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS") Status of the Memo This memo provides information for the Internet community. ... If the trouble ticket system is thoroughly enough integrated with a mail system, or if the system is used by Network Engineers as well as Network Operators, then some problems can be dispatched simply by placing the appropriate Engineer or Operator name in an "assigned to" field of the trouble ticket. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1297.txt -- 33.2 Кб -- 30.01.1992
Похожие документы
Похожие документы
81512. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1296.txt
... Abstract This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables. DNS entries are collected by a program called ZONE, which searches the Internet and retrieves data from all known domains. ... Before the Domain Name System was established, practically all hosts on the Internet were registered with the Network Information Center (SRI-NIC) and entries were placed in the Official Host Table for each one. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1296.txt -- 20.6 Кб -- 29.01.1992
Похожие документы
Похожие документы
81513. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1295.txt
Network Working Group The North American Directory Forum Request for Comments: 1295 January 1992 User Bill of Rights for entries and listings in the Public Directory Status of this Memo This memo provides information for the Internet community. ... User Bill of Rights for entries and listings in the Public Directory The mission of the North American Directory Forum is to provide interconnected electronic directories which empower users with unprecedented access to public information. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1295.txt -- 4.4 Кб -- 29.01.1992
Похожие документы
Похожие документы
81514. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1285.txt
... FddiResourceId ::= INTEGER (0.. ... REFERENCE "ANSI { fddiMAC 29 }" ::= { snmpFddiMACEntry 10 } snmpFddiMACPathsRequested OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "A value that indicates PATH(s) desired for this MAC. ... 65535) ACCESS read-only STATUS mandatory DESCRIPTION Case [Page 29] RFC 1285 FDDI MIB January 1992 "The value of the SMT index associated with this PORT." ::= { snmpFddiPORTEntry 1 } snmpFddiPORTIndex OBJECT-TYPE SYNTAX INTEGER (1.. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1285.txt -- 98.4 Кб -- 23.01.1992
Похожие документы
Похожие документы
81515. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1294.txt
... Q.922 Address* | ... Optional Pad(s) (0x00) | ... Address resolution may be accomplished using the standard Address Resolution Protocol (ARP) [6] encapsulated within a SNAP encoded Frame Relay packet as follows: +-----------------------+-----------------------+ | ... For example, IP encapsulated with this NLPID value will have the following format: Bradley, Brown, Malis [Page 25] RFC 1294 Multiprotocol over Frame Relay January 1992 +-----------------------+-----------------------+ |Q.922 Address | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1294.txt -- 54.7 Кб -- 16.01.1992
Похожие документы
Похожие документы
81516. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1292.txt
Network Working Group R. Lang Request for Comments: 1292 SRI International FYI: 11 R. Wright Lawrence Berkeley Laboratory Editors January 1992 A Catalog of Available X.500 Implementations Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract The goal of this document is to provide information regarding the availability and capability of implementations of X.500. Comments and critiques of this
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1292.txt -- 127.4 Кб -- 02.01.1992
Похожие документы
Похожие документы
81517. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1199.txt
Network Working Group J. Reynolds Request for Comments: 1199 ISI December 1991 Request for Comments Summary RFC Numbers 1100-1199 Status of This Memo This RFC is a slightly annotated list of the 100 RFCs from RFC 1100 through RFCs 1199. ... This memo provides information for the Internet community. It does not specify an Internet standard. ... This RFC provides information for the Internet community, and does not specify any standard. ... This RFC does not specify an Internet standard. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1199.txt -- 46.4 Кб -- 31.12.1991
Похожие документы
Похожие документы
81518. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1290.txt
Network Working Group J. Martin Request for Comments: 1290 Ohio State University FYI: 10 December 1991 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places Status of this Memo This RFC provides information for the Internet community. ... Martin [Page 4] RFC 1290 Searching for Treasure December 1991 2.07 VAX book (Document) Joe St Sauver of the University of Oregon has developed a very complete guide of information on the network available via anonymous FTP. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1290.txt -- 46.9 Кб -- 31.12.1991
Похожие документы
Похожие документы
81519. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1291.txt
Network Working Group V. Aggarwal Request for Comments: 1291 JvNCnet Computer Network December 1991 Mid-Level Networks Potential Technical Services Status of this Memo This RFC provides information for the Internet community. ... Abstract This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. ... 3 3.1 Domain Name Service.. ... 4 3.3 Network Time.. ... Network Information Services.. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1291.txt -- 24.7 Кб -- 28.12.1991
Похожие документы
Похожие документы
81520. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1142.txt
Network Working Group D. Oran, Editor Request for Comments: 1142 Digital Equipment Corp. February 1990 OSI IS-IS Intra-domain Routing Protocol Status of this Memo This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard. Distribution of this memo is unlimited. NOTE: This is a bad ASCII version of this document. The official document is the PostScript file, which has the diagrams in place. Please use the PostScript version of this memo. ISO/IEC DIS
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1142.txt -- 416.4 Кб -- 28.12.1991
Похожие документы
Похожие документы