Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80821 - 80840 из 81894.
[ В начало ] Пред. | 4038 |
4039 |
4040 |
4041 |
4042
|
4043 |
4044 |
4045 |
4046 |
4047 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80821. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1655.txt
... Abstract This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. ... Note that BGP speakers do not need to be a border gateway, and vice versa. ... Information received via Internal BGP by a border gateway A about a reachable network X cannot be propagated to any of the External BGP neighbors of A unless A has an IGP route to X and sufficient time has passed for the IGP routes to have converged. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1655.txt -- 43.6 Кб -- 19.07.1994
Похожие документы
Похожие документы
80822. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1654.txt
Network Working Group Y. Rekhter Request for Comments: 1654 T.J. Watson Research Center, IBM Corp. Category: Standards Track T. Li cisco Systems Editors July 1994 A Border Gateway Protocol 4 (BGP-4) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1654.txt -- 128.1 Кб -- 19.07.1994
Похожие документы
Похожие документы
80823. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1660.txt
... 2 3.1 Relationship to Interface MIB .. ... 295 Foster Street Littleton, MA 01460 Tel: 508-952-4816 Fax: 508-952-4887 E-mail: rlstewart@eng.xyplex.com Stewart [Page 3] RFC 1660 Parallel-printer-like MIB July 1994 DESCRIPTION The MIB module for Parallel-printer-like hardware devices. ::= { transmission 34 } -- Generic Parallel-printer-like information paraNumber OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1660.txt -- 17.4 Кб -- 19.07.1994
Похожие документы
Похожие документы
80824. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1659.txt
... 2 3.1 Relationship to Interface MIB .. ... Its value is the same as rs232PortIndex for the port . ::= { rs232SyncPortEntry 1 } Stewart [Page 10] RFC 1659 RS-232-like MIB July 1994 rs232SyncPortClockSource OBJECT-TYPE SYNTAX INTEGER { internal(1), external(2), split(3) } MAX-ACCESS read-write STATUS current DESCRIPTION Source of the port 's bit rate clock. 'split' means the tranmit clock is internal and the receive clock is external. ::= { rs232SyncPortEntry ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1659.txt -- 36.6 Кб -- 19.07.1994
Похожие документы
Похожие документы
80825. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1658.txt
... 3 3.1 Relationship to Interface MIB .. ... 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) } MAX-ACCESS read-only STATUS current 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/rfc1658.txt -- 32.8 Кб -- 19.07.1994
Похожие документы
Похожие документы
80826. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/bellcore-smdsxaomv1-00.txt
... MIB | ... 65535) ACCESS read-only STATUS mandatory DESCRIPTION "The value of this object identifies the ifIndex associated with the appropriate SNI sublayer. ... 65535) ACCESS read-only STATUS mandatory DESCRIPTION The value of this object identifies the ifIndex associated with the ICIP sublayer of the ICI. ::= { smdsIomIcipL2CurrentEntry 1 } smdsIomIcipL2CurrentTotalOut OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION The value of this ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/bellcore-smdsxaomv1-00.txt -- 84.0 Кб -- 15.07.1994
Похожие документы
Похожие документы
80827. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1653.txt
... Abstract This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. ... Such a server must accept the extended MAIL command and return a 552 reply code if the client's declared size exceeds its fixed size limit (if any), but it need not detect "temporary" limitations on message size. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1653.txt -- 18.5 Кб -- 14.07.1994
Похожие документы
Похожие документы
80828. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1652.txt
... Klensin, Freed, Rose, Stefferud & Crocker [Page 1] RFC 1652 SMTP 8bit-MIMEtransport July 1994 2. Framework for the 8bit MIME Transport Extension The 8bit MIME transport extension is laid out as follows: (1) the name of the SMTP service extension defined here is 8bit-MIMEtransport; (2) the EHLO keyword value associated with the extension is 8BITMIME; (3) no parameter is used with the 8BITMIME EHLO keyword; (4) one optional parameter using the keyword BODY is added to the MAIL FROM command. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1652.txt -- 12.6 Кб -- 14.07.1994
Похожие документы
Похожие документы
80829. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1651.txt
... July 1994 SMTP Service Extensions Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... On failure, the server SMTP responds with code 550. ... Responses from servers without extensions A server SMTP that conforms to RFC 821 but does not support the extensions specified here will not recognize the EHLO command and will consequently return code 500, as specified in RFC 821. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1651.txt -- 22.6 Кб -- 14.07.1994
Похожие документы
Похожие документы
80830. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1649.txt
... Category: Informational A. Hansen UNINETT July 1994 Operational Requirements for X.400 Management Domains in the GO-MHS Community Status of this Memo This memo provides information for the Internet community. ... Two types of management domains are defined by the X.400 model: an Administration Hagens & Hansen [Page 2] RFC 1649 X.400 Management in GO-MHS July 1994 Management Domain (ADMD) and a Private Management Domain (PRMD). ... 2) Specification of X.400 addresses seen from the RFC-822 world. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1649.txt -- 28.5 Кб -- 14.07.1994
Похожие документы
Похожие документы
80831. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1648.txt
... Abstract Both STD 11, RFC 822 [1] and STD 3, RFC 1123 [2] (Host Requirements) require that the email address "postmaster" be supported at all hosts. This paper extends this concept to X.400 mail domains which have registered RFC 1327 mapping rules, and which therefore appear to have normal RFC822-style addresses. ... For that reason, both RFC 822 and the Internet Host Requirements [2] require that the address "postmaster" be supported at every Internet host. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1648.txt -- 9.6 Кб -- 14.07.1994
Похожие документы
Похожие документы
80832. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1645.txt
... Upon opening the connection, the server issues a "220" level message (indicating the willingness of the server to accept SNPP commands). ... Possible responses from the SNPP server, with suggested text, in response to a PAGEr command are: 250 Pager ID Accepted 421 Too Many Errors, Goodbye (terminate connection) 421 Gateway Service Unavailable (terminate connection) 550 Error, Invalid Pager ID 554 Error, failed (technical reason) The level 2 enhancements affect the PAGEr command. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1645.txt -- 31.5 Кб -- 13.07.1994
Похожие документы
Похожие документы
80833. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1647.txt
... IAC SB TN3270E FUNCTIONS REQUEST <function-list> IAC SE Either side may send this command. ... Kelly [Page 30] RFC 1647 TN3270 Enhancements July 1994 13.4 Examples The following example shows a TN3270E -capable server and a traditional tn3270 client establishing a connection: Server : IAC DO TN3270E Client : IAC WON'T TN3270E Server : IAC DO TERMINAL-TYPE Client : IAC WILL TERMINAL-TYPE Server : IAC SB TERMINAL-TYPE SEND IAC SE Client : IAC SB TERMINAL-TYPE IS IBM-3278-2...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1647.txt -- 83.4 Кб -- 13.07.1994
Похожие документы
Похожие документы
80834. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1646.txt
... The first defines a way by which a TN3270 client can request a specific device (LUname) from a TN3270 server. The second extension specifies how a TN3270 printer device can be requested by a TN3270 client and the manner in which the 3270 printer status information can be sent to the TN3270 server. ... Once the End-Of-Record IAC is processed, the TN3270 Client sends the status message to the server when it is ready to receive more print data. ... 3 Intervention Required - Printer Not Ready. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1646.txt -- 27.9 Кб -- 12.07.1994
Похожие документы
Похожие документы
80835. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1644.txt
... Segment #2 is a non-SYN segment that contains a TCP option. ... c rcv ACK(SYN) / | ... Receive {SYN} segment in LISTEN-TW, LISTEN-LA, LISTEN-LA*, LISTEN-CL, or LISTEN-CL* state => { Braden [Page 36] RFC 1644 Transaction/TCP July 1994 If ( (Segment contains CC option AND CCrecv != 0 ) then { If (state = LISTEN-TW AND Elapsed > MSL ) then <Send RST, drop segment, and return>. if (SEG.CC > CCrecv ) then { <Implicitly ACK FIN and data in retransmission queue>; <Close and delete TCB>; <Reprocess segment>...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1644.txt -- 86.3 Кб -- 12.07.1994
Похожие документы
Похожие документы
80836. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9406.txt
June 1994 INTERNET MONTHLY REPORTS ------------------------ The purpose of these reports is to communicate to the Internet Research Group the accomplishments, milestones reached, or problems discovered by the participating organizations. ... page 12 INTERNIC. . ... Cooper [Page 40] Internet Monthly Report June 1994 2.2 About the RIPE NCC The RIPE Network Coordination Centre supports all those RIPE activities which cannot be effectively performed by volunteers from the participating organisations. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9406.txt -- 125.0 Кб -- 12.07.1994
Похожие документы
Похожие документы
80837. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1643.txt
... Obsoletes: 1623, 1398 July 1994 STD: 50 Category: Standards Track Definitions of Managed Objects for the Ethernet-like Interface Types Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... In particular, it defines objects for managing ethernet-like objects. ... In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1643.txt -- 39.1 Кб -- 11.07.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std50.txt -- 39.1 Кб -- 11.07.1994
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/std/std50.txt -- 39.1 Кб -- 11.07.1994
Похожие документы
80838. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1642.txt
... Abstract The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to as Unicode) which encompasses most of the world's writing systems. ... Overview UTF-7 encodes Unicode characters as US-ASCII, together with shift sequences to encode characters outside that range. ... Goldsmith & Davis [Page 9] RFC 1642 UTF-7 July 1994 Summary The UTF-7 encoding allows Unicode characters to be encoded within the US-ASCII 7 bit character set. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1642.txt -- 28.1 Кб -- 11.07.1994
Похожие документы
Похожие документы
80839. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1641.txt
... July 1994 Using Unicode with MIME Status of this Memo This memo defines an Experimental Protocol for the Internet community. ... Abstract The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to as Unicode) which encompasses most of the world's writing systems. ... MIME (RFC 1521 and RFC 1522) extends Internet mail to support different media types and character sets, and thus could support Unicode in mail messages. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1641.txt -- 12.0 Кб -- 11.07.1994
Похожие документы
Похожие документы
80840. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1610.txt
Network Working Group Internet Architecture Board Request for Comments: 1610 J. Postel, Editor Obsoletes: RFCs 1600, 1540, 1500, 1410, July 1994 1360, 1280, 1250, 1100, 1083, 1130, 1140, 1200 STD: 1 Category: Standards Track INTERNET 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 Architecture Board (IAB). ... Standard Protocol . ... Draft Standard Protocol . ... Elective Protocol . ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1610.txt -- 80.4 Кб -- 08.07.1994
Похожие документы
Похожие документы