Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80541 - 80560 из 81894.
[ В начало ] Пред. | 4024 |
4025 |
4026 |
4027 |
4028
|
4029 |
4030 |
4031 |
4032 |
4033 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80541. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1907.txt
... 255)) MAX-ACCESS read-only STATUS current DESCRIPTION "A textual description of the entity. ... SNMPv2 Working Group Standards Track [Page 15] RFC 1907 Management Information Base for SNMPv2 January 1996 ::= { snmp 17 } snmpInGetResponses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS obsolete DESCRIPTION The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity . ::= { snmp 18 } snmpInTraps OBJECT-TYPE ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1907.txt -- 35.1 Кб -- 19.01.1996
Похожие документы
Похожие документы
80542. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1906.txt
Network Working Group SNMPv2 Working Group Request for Comments: 1906 J. Case Obsoletes: 1449 SNMP Research, Inc. ... SNMPv2 over DDP .. ... 11 SNMPv2 Working Group Standards Track [Page 1] RFC 1906 Transport Mappings for SNMPv2 January 1996 9. ... SNMPv2 over DDP This is an optional transport mapping. ... SNMPv2 Working Group Standards Track [Page 8] RFC 1906 Transport Mappings for SNMPv2 January 1996 An NBP name to DDP address mapping can also be confirmed implicitly using only SNMP transactions. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1906.txt -- 27.8 Кб -- 19.01.1996
Похожие документы
Похожие документы
80543. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1905.txt
Network Working Group SNMPv2 Working Group Request for Comments: 1905 J. Case Obsoletes: 1448 SNMP Research, Inc. ... This alternate Response-PDU is formatted with the same value in its request-id field as the received GetRequest-PDU, with the value of its error-status field set to `tooBig', the value of its error-index field set to SNMPv2 Working Group Standards Track [Page 10] RFC 1905 Protocol Operations for SNMPv2 January 1996 zero, and an empty variable-bindings field. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1905.txt -- 55.2 Кб -- 19.01.1996
Похожие документы
Похожие документы
80544. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1904.txt
... Mapping of the OBJECT-GROUP macro .. ... 10 3.5 Mapping of the OBJECT-GROUP value .. ... 13 SNMPv2 Working Group Standards Track [Page 1] RFC 1904 Conformance Statements for SNMPv2 January 1996 5.2 Mapping of the DESCRIPTION clause .. ... Mapping of the OBJECTS clause The OBJECTS clause, which must be present, is used to name each object contained in the conformance group. ... Mapping of the DESCRIPTION clause The DESCRIPTION clause must be present for each use of the GROUP or OBJECT clause. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1904.txt -- 47.0 Кб -- 19.01.1996
Похожие документы
Похожие документы
80545. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1903.txt
... S. Waldbusser International Network Services January 1996 Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... SYNTAX INTEGER (0.. ... Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1903.txt -- 52.4 Кб -- 19.01.1996
Похожие документы
Похожие документы
80546. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1902.txt
... empty Text ::= """" string """" END -- names of objects ObjectName ::= OBJECT IDENTIFIER NotificationName ::= OBJECT IDENTIFIER -- syntax of objects ObjectSyntax ::= CHOICE { simple SimpleSyntax, -- note that SEQUENCEs for conceptual tables and -- rows are not mentioned here... application-wide ApplicationSyntax } -- built-in ASN.1 types SimpleSyntax ::= CHOICE { -- INTEGERs with a more restrictive range -- may also be used integer-value -- includes Integer32 INTEGER (-2147483648.. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1902.txt -- 76.6 Кб -- 19.01.1996
Похожие документы
Похожие документы
80547. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1901.txt
... 2 2.1 Structure of Management Information .. ... 3 2.4 Protocol Operations .. ... References [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. ... 6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1901.txt -- 16.5 Кб -- 19.01.1996
Похожие документы
Похожие документы
80548. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1894.txt
... MTA | ... However, an MTA MAY report on the delivery status for several recipients of the same message in a single DSN. ... This field is required. ... The date-time lexical token is defined in [8]. action- field = Action : action-value action-value = failed / delayed / delivered / relayed / expanded address -type = atom arrival-date- field = Arrival-Date : date-time delivery - status -content = per- message -fields 1*( CRLF per- recipient -fields ) diagnostic-code- ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1894.txt -- 76.6 Кб -- 09.01.1996
Похожие документы
Похожие документы
80549. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1893.txt
Network Working Group G. Vaudreuil Request for Comments: 1893 Octel Network Services Category: Standards Track January 1996 Enhanced Mail System Status Codes Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Vaudreuil Standards Track [Page 5] RFC 1893 Mail System Status Codes January 1996 X.1.5 Destination address valid This mailbox address as specified was valid. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1893.txt -- 28.6 Кб -- 09.01.1996
Похожие документы
Похожие документы
80550. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1892.txt
Network Working Group G. Vaudreuil Request for Comments: 1892 Octel Network Services Category: Standards Track January 1996 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... The parameter is the MIME content sub-type of the second body part of the Multipart/Report. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1892.txt -- 8.6 Кб -- 09.01.1996
Похожие документы
Похожие документы
80551. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1891.txt
... Framework for the Delivery Status Notification Extension The following service extension is therefore defined: (1) The name of the SMTP service extension is Delivery Status Notification ; (2) the EHLO keyword value associated with this extension is DSN , the meaning of which is defined in section 4 of this memo; (3) no parameters are allowed with this EHLO keyword value; (4 ... If the NOTIFY parameter for the alias contained the SUCCESS keyword, the MTA issues a "relayed" DSN. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1891.txt -- 64.7 Кб -- 09.01.1996
Похожие документы
Похожие документы
80552. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1884.txt
... The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 nodes required addresses. ... IPv6 Addressing.. ... 2.0 IPv6 ADDRESSING IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces. ... An IPv6 unicast address refers to a single interface. A single interface may be assigned multiple IPv6 addresses of any type (unicast, anycast, and multicast). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1884.txt -- 38.0 Кб -- 08.01.1996
Похожие документы
Похожие документы
80553. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1879.txt
Network Working Group B. Manning, Editor Request for Comments: 1879 ISI Category: Informational January 1996 Class A Subnet Experiment Results and Recommendations Status of this Memo This memo provides information for the Internet community. ... Equipment that depends on use of a classful routing protocol, such a RIPv1 are prone to misconfiguration. ... RIPv1 use will create an aggregate Manning Informational [Page 3] RFC 1879 Class A Subnet Experiment January 1996 announcement. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1879.txt -- 11.3 Кб -- 05.01.1996
Похожие документы
Похожие документы
80554. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1876.txt
Network Working Group C. Davis Request for Comments: 1876 Kapor Enterprises Updates: 1034, 1035 P. Vixie Category: Experimental Vixie Enterprises T. Goodwin FORE Systems I. Dickinson University of Warwick January 1996 A Means for Expressing Location Information in the Domain Name System Status of this Memo This memo defines an Experimental Protocol for the Internet community. ... Davis, et al Experimental [Page 1] RFC 1876 Location Information in the DNS January 1996 2. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1876.txt -- 29.9 Кб -- 04.01.1996
Похожие документы
Похожие документы
80555. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1865.txt
... Abstract This memo is targeted towards the EDI community that is unfamiliar with the Internet, including EDI software developers, users, and service providers. ... How might an ISP be used for EDI? ... The mail user agent may also process attached files using a proprietary format within a mail message, using one of the common de-facto standards, or using the Multipurpose Internet Mail Houser, et al Informational [Page 9] RFC 1865 EDI Meets the Internet January 1996 Extensions (MIME) internet...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1865.txt -- 97.1 Кб -- 03.01.1996
Похожие документы
Похожие документы
80556. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1887.txt
Network Working Group Y. Rekhter Request for Comments: 1887 cisco Systems Category: Informational T. Li cisco Systems Editors December 1995 An Architecture for IPv6 Unicast Address Allocation Status of this Memo This document provides information for the Internet community. ... Alternatively, should the routing domain draw IPv6 addresses for all the hosts within the domain from a single IPv6 address prefix, boundary routing information can be summarized into the single IPv6 address prefix. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1887.txt -- 65.5 Кб -- 02.01.1996
Похожие документы
Похожие документы
80557. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1886.txt
... The changes include a new resource record type to store an IPv6 address, a new domain to support lookups based on an IPv6 address, and updated definitions of existing query types that return Internet addresses as part of additional section processing. ... NEW RESOURCE RECORD DEFINITION AND DOMAIN A new record type is defined to store a host's IPv6 address. ... 2.1 AAAA record type The AAAA resource record type is a new record specific to the Internet class that stores a single IPv6 address. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1886.txt -- 7.3 Кб -- 02.01.1996
Похожие документы
Похожие документы
80558. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1885.txt
... ICMPv6 (ICMP for IPv6).. ... 3 2.2 Message Source Address Determination.. ... ICMPv6 Error Messages.. ... In that case, the error message is silently dropped after any IPv6 -layer processing. (e) An ICMPv6 error message MUST NOT be sent as a result of receiving: (e.1) an ICMPv6 error message , or (e.2) a packet destined to an IPv6 multicast address (there are two exceptions to this rule: (1) the Packet Too Big Message - Section 3.2 - to allow Path MTU discovery to work for ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1885.txt -- 32.5 Кб -- 02.01.1996
Похожие документы
Похожие документы
80559. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1883.txt
... IPv6 Header Format.. ... 8 4.2 Options.. ... 13 4.5 Fragment Header.. 19 4.6 Destination Options Header.. ... Deering Hinden Standards Track [Page 7] RFC 1883 IPv6 Specification December 1995 4.1 Extension Header Order When more than one extension header is used in the same packet , it is recommended that those headers appear in the following order: IPv6 header Hop-by-Hop Options header Destination Options header (note 1) Routing header Fragment header Authentication ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1883.txt -- 81.2 Кб -- 02.01.1996
Похожие документы
Похожие документы
80560. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1882.txt
... Discussion On the first day of Christmas, technology gave to me: A database with a broken b-tree (what the hell is a b-tree anyway?) On the second day of Christmas, technology gave to me: Two transceiver failures (CRC errors? ... On the third day of Christmas, technology gave to me: Three French users (who, of course, think they know everything) Two transceiver failures (which are now spewing packets all over the net) And a database with a broken b-tree (Backup? ... Two transceiver failures (SQE? ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1882.txt -- 9.9 Кб -- 21.12.1995
Похожие документы
Похожие документы