Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 81481 - 81500 из 81894.
[ В начало ] Пред. | 4071 |
4072 |
4073 |
4074 |
4075
|
4076 |
4077 |
4078 |
4079 |
4080 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
81481. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1319.txt
... Executive Summary This document describes the MD2 message-digest algorithm. ... MD, TEST_BLOCK_LEN, TEST_BLOCK_COUNT); /* Initialize block */ for (i = 0; i TEST_BLOCK_LEN; i++) block[i] = ( unsigned char )(i 0xff); /* Start timer */ time ( startTime); /* Digest blocks */ MDInit ( context ); for (i = 0; i TEST_BLOCK_COUNT; i++) MDUpdate ( context , block, TEST_BLOCK_LEN); MDFinal ( digest , context ); /* Stop timer */ time ( endTime); printf ( done\n ); printf ( ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1319.txt -- 26.1 Кб -- 15.04.1992
Похожие документы
Похожие документы
81482. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1318.txt
... RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. ... Telnet MIB | ... INDEX { paraInSigPortIndex, paraInSigName } ::= { paraInSigTable 1 } ParaInSigEntry ::= SEQUENCE { paraInSigPortIndex INTEGER , paraInSigName INTEGER , paraInSigState Character MIB Working Group [Page 6] RFC 1318 PARALLEL-PRINTER-LIKE- MIB April 1992 INTEGER , paraInSigChanges Counter } paraInSigPortIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1318.txt -- 20.1 Кб -- 15.04.1992
Похожие документы
Похожие документы
81483. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1317.txt
... Further MIBs may appear above these. ... PPP MIB | RS-232-like MIB | ... Its value is the same as rs232PortIndex for the port . ::= { rs232SyncPortEntry 1 } rs232SyncPortClockSource OBJECT-TYPE SYNTAX INTEGER { internal(1), external(2), split(3) } ACCESS read-write STATUS mandatory DESCRIPTION Source of the port 's bit rate clock. 'split' means the tranmit clock is internal and the receive clock is external. ::= { rs232SyncPortEntry 2 } rs232SyncPortFrameCheckErrs OBJECT-TYPE ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1317.txt -- 30.7 Кб -- 15.04.1992
Похожие документы
Похожие документы
81484. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1316.txt
... The Character MIB's central abstraction is a port. ... Although not architecturally pure, they are included here for simplicy's sake. ::= { charPortEntry 10 } charPortInFlowState OBJECT -TYPE SYNTAX INTEGER { none(1), unknown(2), stop(3), go(4) } ACCESS read-only STATUS mandatory DESCRIPTION The current operational state of input flow control on the port . 'none' indicates not applicable. 'unknown' indicates this level does not know. 'stop' indicates flow not allowed. 'go' indicates ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1316.txt -- 35.3 Кб -- 15.04.1992
Похожие документы
Похожие документы
81485. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1315.txt
... 19 Brown, Baker & Carvalho [Page 1] RFC 1315 Frame Relay DTE MIB April 1992 1. ... Brown, Baker Carvalho [Page 11] RFC 1315 Frame Relay DTE MIB April 1992 REFERENCE Draft American National Standard T1.618-1991, Section 3.3.4 ::= { frCircuitEntry 5 } frCircuitSentFrames OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION The number of frames sent from this virtual circuit since it was created. ::= { frCircuitEntry 6 } frCircuitSentOctets OBJECT-TYPE ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1315.txt -- 34.0 Кб -- 09.04.1992
Похожие документы
Похожие документы
81486. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1314.txt
Network Working Group A. Katz Request for Comments: 1314 D. Cohen ISI April 1992 A File Format for the Exchange of Images in the Internet Status of This Memo This document specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Abstract This document defines a standard file format for the exchange of fax-like black and white images within the Internet. ... Images should be encoded as one TIFF strip per page. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1314.txt -- 53.8 Кб -- 09.04.1992
Похожие документы
Похожие документы
81487. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1312.txt
... April 1992 Message Send Protocol 2 Status of this Memo This memo defines an Experimental Protocol for the Internet community. ... Discussion The Message Send Protocol is used to send a short message to a given user on a given terminal on a given host. ... All comparisons of parts (e.g., recipient, Nelson & Arnold [Page 1] RFC 1312 Message Send Protocol 2 April 1992 cookie, etc.) are case-insensitive. ... A server may choose to accept, reject or ignore messages in which the SENDER part is empty. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1312.txt -- 18.6 Кб -- 08.04.1992
Похожие документы
Похожие документы
81488. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1305.txt
Network Working Group David L. Mills Request for Comments: 1305 University of Delaware Obsoletes RFC-1119, RFC-1059, RFC-958 March 1992 Network Time Protocol (Version 3) Specification, Implementation and Analysis Note: This document consists of an approximate rendering in ASCII of the PostScript document of the same name. It is provided for convenience and for use in searches, etc. However, most tables, figures, equations and captions have not been rendered and the pagination and section headings are not
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1305.txt -- 300.9 Кб -- 07.04.1992
Похожие документы
Похожие документы
81489. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc855.txt
... For example, any option which requires a parameter is such a case. ... Postel & Reynolds [Page 2] RFC 855 May 1983 Thus, for option "ABC", which requires subnegotiation, the formats of the TELNET commands are: IAC WILL ABC Offer to use option ABC (or favorable acknowledgment of other party's request) IAC DO ABC Request for other party to use option ABC (or favorable acknowledgment of other party's offer) IAC SB ABC <parameters> IAC SE One step of subnegotiation, used by either party. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc855.txt -- 6.9 Кб -- 07.04.1992
Похожие документы
Похожие документы
81490. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1313.txt
Network Working Group C. Partridge Request for Comments: 1313 BBN 1 April 1992 Today's Programming for KRFC AM 1313 Internet Talk Radio Status of this Memo This memo provides information for the Internet community. ... Here's today's programming for today, Wednesday, 1 April 1992. ... Partridge [Page 1] RFC 1313 Today's Programming for KRFC AM 13XX 1 April 1991 Marty in the Morning (6 AM) Join the irrepressable Marty for five hours of eye-opening talk and commentary. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1313.txt -- 6.3 Кб -- 31.03.1992
Похожие документы
Похожие документы
81491. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1280.txt
Network Working Group Internet Activities Board Request for Comments: 1280 J. Postel, Editor Obsoletes: RFCs 1250, March 1992 1100, 1083, 1130, 1140, 1200 STD: 1 IAB OFFICIAL PROTOCOL STANDARDS Status of this Memo This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). ... Standard Protocol . ... Elective Protocol . ... Standard Protocol The IAB has established this as an official standard protocol for the Internet. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1280.txt -- 69.8 Кб -- 14.03.1992
Похожие документы
Похожие документы
81492. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1311.txt
Network Working Group Internet Activities Board Request for Comments: 1311 J. Postel, Editor March 1992 Introduction to the STD Notes Status of this Memo This RFC describes a new sub-series of RFCs, called STDs (Standards). ... The intent is to identify clearly for the Internet community those RFCs which document Internet standards. ... The Assignment of STD Numbers There is a need to be very clear about which specifications have completed the full process of standardization in the Internet. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1311.txt -- 12.0 Кб -- 14.03.1992
Похожие документы
Похожие документы
81493. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1310.txt
Network Working Group Internet Activities Board Request for Comments: 1310 Lyman Chapin, Chair March 1992 The Internet Standards Process Status of this Memo This informational memo presents the current procedures for creating and documenting Internet Standards. ... 23 IAB [Page 1] RFC 1310 Internet Standards Process March 1992 1. ... The status of specifications on the Internet standards track is summarized periodically in a summary RFC entitled "IAB Official Protocol Standards" [2]. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1310.txt -- 54.5 Кб -- 13.03.1992
Похожие документы
Похожие документы
81494. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi14.txt
Network Working Group C. Weider Request for Comments: 1309 ANS FYI: 14 J. Reynolds ISI S. Heker JvNC March 1992 Technical Overview of Directory Services Using the X.500 Protocol Status of this Memo This memo provides information for the Internet community. ... This FYI RFC is a product of the Directory Information Services (pilot) Infrastructure Working Group (DISI). ... Each Directory entry contains information about one object; for example, a person, a computer network, or an organization. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi14.txt -- 35.9 Кб -- 12.03.1992
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1309.txt -- 35.9 Кб -- 12.03.1992
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1309.txt -- 35.9 Кб -- 12.03.1992
Похожие документы
81495. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi13.txt
Network Working Group C. Weider Request for Comments: 1308 ANS FYI: 13 J. Reynolds ISI March 1992 Executive Introduction to Directory Services Using the X.500 Protocol Status of this Memo This memo provides information for the Internet community. ... It briefly discusses the deficiencies in currently deployed Internet Directory Services, and then illustrates the solutions provided by X.500. This FYI RFC is a product of the Directory Information Services (pilot) Infrastructure Working Group (DISI). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi13.txt -- 10.2 Кб -- 12.03.1992
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1308.txt -- 10.2 Кб -- 12.03.1992
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1308.txt -- 10.2 Кб -- 12.03.1992
Похожие документы
81496. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1307.txt
... Bring Down: While DSLCP is in the Coming Up state, the transport provider requested link teardown. ... Transport Teardown | ... The specific events of interest to the DSLCP are: Transport provider link setup request Transport provider link teardown request Link setup request failed Link setup request succeeded Link teardown request succeeded Link teardown request failed Network link is down Young Nicholson [Page 8] RFC 1307 Dynamically Switched Link...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1307.txt -- 24.6 Кб -- 11.03.1992
Похожие документы
Похожие документы
81497. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1306.txt
... March 1992 Experiences Supporting By-Request Circuit-Switched T3 Networks Status of this Memo This RFC provides information for the Internet community. ... This involves activating the circuit-switched connection when an application program engages in a bulk data transfer, and releasing the connection when the transfer is complete. ... Once the link is up, the application begins sending data, and the network routes all the data from the application through the switched network. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1306.txt -- 26.2 Кб -- 11.03.1992
Похожие документы
Похожие документы
81498. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1304.txt
... 25 SNMP Working Group [Page 1] RFC 1304 SIP Objects February 1992 1. ... The total includes only unerrored L2PDUs. ::= { sipL2Entry 2 } sipL2SentCounts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION The number of SIP Level 2 PDUs that have been sent by this system across the SNI. ::= { sipL2Entry 3 } -- The total number of SIP L2PDU errors can be calculated as -- the sum of: -- sipL2HcsOrCRCErrors -- sipL2PayloadLengthErrors -- sipL2SequenceNumberErrors ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1304.txt -- 52.3 Кб -- 27.02.1992
Похожие документы
Похожие документы
81499. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1303.txt
... Objects .. ... 6 3.2.3 Mapping of the DESCRIPTION clause .. ... Usage Example Consider how one might document the 4BSD/ISODE Secure SNMP agent : FourBSD-ISODE DEFINITIONS ::= BEGIN IMPORTS MODULE-CONFORMANCE FROM RFC -1303 -- everything -- FROM RFCxxxx-MIB -- everything -- FROM RFC1213-MIB -- everything -- FROM UNIX-MIB -- everything -- FROM EVAL-MIB; fourBSD-isode-support MODULE-CONFORMANCE LAST-UPDATED 9201252354Z PRODUCT-RELEASE ISODE 7.0 + 'Secure' SNMP upgrade for SunOS 4.1 ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1303.txt -- 23.4 Кб -- 26.02.1992
Похожие документы
Похожие документы
81500. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi12.txt
... Abstract This FYI RFC document is intended for existing Internet Network Information Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities. ... Therefore, an Internet NIC must have policies, procedures, and delivery mechanisms in place to serve not only end-users, but to aid other information providers and user support agencies. ... All of these networks provide NICs....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi12.txt -- 29.5 Кб -- 25.02.1992
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1302.txt -- 29.5 Кб -- 25.02.1992
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1302.txt -- 29.5 Кб -- 25.02.1992
Похожие документы