Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80781 - 80800 из 81894.
[ В начало ] Пред. | 4036 |
4037 |
4038 |
4039 |
4040
|
4041 |
4042 |
4043 |
4044 |
4045 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80781. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1696.txt
... Table of Contents 1 Introduction .. ... Definitions Modem - MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE , OBJECT-IDENTITY, Counter32 , Integer32 FROM SNMPv2-SMI DisplayString FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF mib -2 FROM RFC1213- MIB ; mdmMIB MODULE-IDENTITY LAST-UPDATED 9406120000Z ORGANIZATION IETF Modem Management Working Group Barnes, Brown, Royston Waldbusser [Page 2] RFC 1696 Modem ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1696.txt -- 53.8 Кб -- 22.08.1994
Похожие документы
Похожие документы
80782. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1650.txt
... In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. ... The following hardware chipsets are -- provided for 802.3: dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } dot3ChipSetAMD7990 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 1 } dot3ChipSetAMD79900 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 2 } dot3ChipSetAMD79C940 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 3 } dot3ChipSetIntel ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1650.txt -- 40.5 Кб -- 22.08.1994
Похожие документы
Похожие документы
80783. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1694.txt
... Brown & Tesink [Page 7] RFC 1694 SMDS Interface Objects August 1994 ifOutErrors The number of SIP Level 3 PDUs discarded in the egress direction, because of errors. ... Thus, -- sipL2ReceivedCounts defines the number of -- correct SIP Level 2 PDUs delivered to the reassembly -- process. sipL2HcsOrCRCErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Brown Tesink [Page 15] RFC 1694 SMDS Interface Objects August 1994 The number of received SIP ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1694.txt -- 71.4 Кб -- 22.08.1994
Похожие документы
Похожие документы
80784. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1697.txt
... 2 2.1 Object Definitions .. ... Definitions RDBMS-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE , NOTIFICATION-TYPE, Counter32, Gauge32, Integer32 FROM SNMPv2-SMI DisplayString, DateAndTime, AutonomousType FROM SNMPv2-TC applIndex ... Development 1080 Marina Village Parkway Alameda, CA 94501 US Tel: +1 510 748 3418 Fax: +1 510 748 2770 E-mail: daveb@ingres.com DESCRIPTION The MIB module to describe objects for generic relational databases. ::= { mib-2 39 } rdbmsObjects ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1697.txt -- 75.4 Кб -- 22.08.1994
Похожие документы
Похожие документы
80785. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1657.txt
... INDEX { bgpPeerRemoteAddr } ::= { bgpPeerTable 1 } BgpPeerEntry ::= SEQUENCE { bgpPeerIdentifier IpAddress, bgpPeerState INTEGER , bgpPeerAdminStatus INTEGER , bgpPeerNegotiatedVersion Integer32, bgpPeerLocalAddr IpAddress, bgpPeerLocalPort INTEGER , bgpPeerRemoteAddr IpAddress, bgpPeerRemotePort INTEGER , bgpPeerRemoteAs INTEGER , bgpPeerInUpdates Counter32, bgpPeerOutUpdates Counter32, bgpPeerInTotalMessages Counter32, bgpPeerOutTotalMessages Counter32, bgpPeerLastError ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1657.txt -- 45.4 Кб -- 17.08.1994
Похожие документы
Похожие документы
80786. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1692.txt
... D. Cohen Myricom J. Postel ISI August 1994 Transport Multiplexing Protocol (TMux) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... TMux is a protocol which allows multiple short transport segments, independent of application type, to be combined between a server and host pair. ... Hence, a TMux message appears as: | ... Each segment, Bi, is preceded by a 4 octet TMux mini header....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1692.txt -- 26.5 Кб -- 16.08.1994
Похожие документы
Похожие документы
80787. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1691.txt
... The architecture should assume data storage in UNIX file systems. ... Document Object Lines Field Description Comments ----- ---------------------- ---------------------------- 1 Document Object number 0 = Master Document Object 1-9 = Reference Document Object 2 Library name Server name 3 Collection name 4 Document ID 8-digit number 5 Author name 6 Volume 7 Title 8 Edition Data Object Lines Field Description Comments ----- ---------------------- ----------------------------...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1691.txt -- 21.0 Кб -- 16.08.1994
Похожие документы
Похожие документы
80788. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1690.txt
Network Working Group G. Huston Request for Comments: 1690 AARNet Category: Informational August 1994 Introducing the Internet Engineering and Planning Group (IEPG) Status of this Memo This memo provides information for the Internet community. ... Huston [Page 1] RFC 1690 The Internet Engineering and Planning Group August 1994 Constituency Membership of the IEPG shall be open. ... Any member of the Internet community may join the IEPG mailing list. The mailing list is "iepg@iepg.org". ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1690.txt -- 3.9 Кб -- 16.08.1994
Похожие документы
Похожие документы
80789. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi25.txt
Network Working Group J. Foster, Editor Request for Comments: 1689 University of Newcastle upon Tyne RARE Technical Report: 13 August 1994 FYI: 25 Category: Informational A Status Report on Networked Information Retrieval: Tools and Groups Produced as a collaborative effort by the Joint IETF/RARE/CNI Networked Information Retrieval - Working Group (NIR-WG) Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi25.txt -- 367.7 Кб -- 16.08.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RAREreports/rtr13.txt -- 367.7 Кб -- 16.08.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1689.txt -- 367.7 Кб -- 16.08.1994
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RAREreports/rtr13.txt -- 367.7 Кб -- 16.08.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1689.txt -- 367.7 Кб -- 16.08.1994
Похожие документы
80790. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9407.txt
... Cooper [Page 3] Internet Monthly Report July 1994 5. ... A total of 75 Internet -Draft actions were taken during the month of July , 1994 : (Revised draft (o), New Draft (+) ) WG I-D Title Filename ------ ----------------------------------------------------- (isis) o Integrated IS-IS Management Information Base draft-ietf-isis-mib-04.txt (mhsds) o Representing Tables and Subtrees in the Directory draft-ietf-mhsds-subtrees ... 3 EDUCOM Cooper [Page 39] Internet Monthly Report July 1994 Nov....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9407.txt -- 99.9 Кб -- 12.08.1994
Похожие документы
Похожие документы
80791. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1688.txt
Network Working Group W. Simpson Request for Comments: 1688 Daydreamer Category: Informational August 1994 IPng Mobility Considerations Status of this Memo This memo provides information for the Internet community. ... Introduction Current versions of the Internet Protocol make an implicit assumption that a node's point of attachment remains fixed. ... For correspondent nodes which do not implement mobility functions, topological changes should not be communicated to the correspondent. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1688.txt -- 19.7 Кб -- 10.08.1994
Похожие документы
Похожие документы
80792. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1676.txt
Network Working Group A. Ghiselli Request for Comments: 1676 D. Salomoni Category: Informational C. Vistoli INFN/CNAF August 1994 INFN Requirements for an IPng Status of this Memo This memo provides information for the Internet community. ... The Ghiselli, Salomoni & Vistoli [Page 2] RFC 1676 INFN Requirements for an IPng August 1994 multicast capability as well as any other new features that fit in a datagram network should be supported. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1676.txt -- 9.3 Кб -- 10.08.1994
Похожие документы
Похожие документы
80793. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1666.txt
... 2 2.1 Object Definitions .. ... 3 3.1 Applying MIB II to managing SNA NAUs .. ... to keyboard usable by operator cdeb(3) - time to Change Direction/End Bracket. ::= { snaLuRtmEntry 5 } snaLuRtmBoundary1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION This object contains the value of the first boundary in units of 1/10th of a second. ::= { snaLuRtmEntry 6 } snaLuRtmBoundary2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1666.txt -- 132.2 Кб -- 10.08.1994
Похожие документы
Похожие документы
80794. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1682.txt
Network Working Group J. Bound Request for Comments: 1682 Digital Equipment Corporation Category: Informational August 1994 IPng BSD Host Implementation Analysis Status of this Memo This memo provides information for the Internet community. ... In addition a host will be required to maintain an integrated network layer below the transport layer software to support either the IPng or IPv4 network layer and associated components. ... Selection of the network layer (IPv4 or IPng) at the transport layer. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1682.txt -- 22.8 Кб -- 09.08.1994
Похожие документы
Похожие документы
80795. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1687.txt
Network Working Group E. Fleischman Request for Comments: 1687 Boeing Computer Services Category: Informational August 1994 A Large Corporate User's View of IPng Status of this Memo This memo provides information for the Internet community. ... A key point to Fleischman [Page 1] RFC 1687 A Large Corporate User's View of IPng August 1994 highlight is that end users actually buy applications -- not networking technologies. ... It is our perspective that End Users currently view IPng with disfavor. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1687.txt -- 34.3 Кб -- 09.08.1994
Похожие документы
Похожие документы
80796. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1686.txt
Network Working Group M. Vecchi Request for Comments: 1686 Time Warner Cable Category: Informational August 1994 IPng Requirements: A Cable Television Industry Viewpoint Status of this Memo This memo provides information for the Internet community. ... 10 3.11 Datagram service .. ... The perspective taken is to position IPng as a potential internetworking technology to support the global requirements of the future integrated broadband networks that the cable industry is designing and deploying. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1686.txt -- 39.1 Кб -- 09.08.1994
Похожие документы
Похожие документы
80797. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1664.txt
... S. Giordano Centro Svizzero Calcolo Scientifico R. Hagens Advanced Network & Services August 1994 Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables Status of this Memo This memo defines an Experimental Protocol for the Internet community. ... Abstract This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. ... In DNS an entry like *.net2...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1664.txt -- 50.6 Кб -- 09.08.1994
Похожие документы
Похожие документы
80798. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1633.ps
... Contents 1 Introduction 2 2 Elements of the Architecture 3 2.1 Integrated Services Model : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 4 2.2 Reference Implementation Framework : : : : : : : : : : : : : : : : : : : : : : : : : : 6 3 Integrated Services Model 10 3.1 Quality of Service Requirements : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 11 RFC 1633 Integrated Services in the ... Section 3 discusses realґtime service models [SCZ93a, SCZ93b]. ...
[
Текст
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1633.ps -- 203.2 Кб -- 09.08.1994
Похожие документы
Похожие документы
80799. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RAREreports/rtr12.txt
Network Working Group H. Alvestrand Request for Comments: 1685 UNINETT RARE Technical Report: 12 August 1994 Category: Informational Writing X.400 O/R Names Status of this Memo This memo provides information for the Internet Community. ... They should be written using UPPER CASE. ... In order to represent visually an address to a human user, and to enable the user to enter the address into a user interface, each attribute value needs to be associated with the correct attribute type. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RAREreports/rtr12.txt -- 21.7 Кб -- 09.08.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1685.txt -- 21.7 Кб -- 09.08.1994
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1685.txt -- 21.7 Кб -- 09.08.1994
Похожие документы
80800. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1684.txt
Network Working Group P. Jurg Request for Comments: 1684 SURFnet bv Category: Informational August 1994 Introduction to White Pages Services based on X.500 Status of this Memo This memo provides information for the Internet community. ... Applications of X.500 .. ... 10 RARE Working Group on Network Applications Support [Page 1] RFC 1684 Introduction to X.500 White Pages Services August 1994 1. ... This has to be done for the White Pages service as well as for any deviating local application of X.500. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1684.txt -- 23.4 Кб -- 08.08.1994
Похожие документы
Похожие документы