Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80941 - 80960 из 81894.
[ В начало ] Пред. | 4044 |
4045 |
4046 |
4047 |
4048
|
4049 |
4050 |
4051 |
4052 |
4053 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80941. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/bellcore-tcav2-00.txt
Bellcore Threshold Crossing Alert Objects December 1993 Definitions of Managed Objects for Threshold Crossing Alerts SNMPv2 MIB bellcore-tcav2.txt (See bellcore-tcav1.mib for SNMPv1 MIB) December 1993 Version 1.0 Tracy A. Brown (editor) Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 tacox@mail.bellcore.com 1. ... Tracy A. Brown (editor) [Page 1] Bellcore Threshold Crossing Alert Objects December 1993 3. ... 6 6.1 The Threshold Crossing Alert Group Group .. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/bellcore-tcav2-00.txt -- 24.2 Кб -- 13.12.1993
Похожие документы
Похожие документы
80942. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1552.txt
Network Working Group W. Simpson Request for Comments: 1552 Daydreamer Category: Standards Track December 1993 The PPP Internetwork Packet Exchange Control Protocol (IPXCP) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... 6 3.1 IPX-Network-Number .. ... Simpson [Page 7] RFC 1552 PPP IPXCP December 1993 A summary of the IPX-Network-Number Configuration Option format is shown below. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1552.txt -- 29.8 Кб -- 08.12.1993
Похожие документы
Похожие документы
80943. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1553.txt
Network Working Group S. Mathur Request for Comments: 1553 M. Lewis Category: Standards Track Telebit Corporation December 1993 Compressing IPX Headers Over WAN Media (CIPX) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... For normal IPX packet traffic, CIPX can provide a compression ratio of approximately 2:1 including both IPX header and data. ... Packet Length | ... Number | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1553.txt -- 47.3 Кб -- 04.12.1993
Похожие документы
Похожие документы
80944. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1551.txt
... Glossary Of Terms Primary Network Number: Every IPX WAN router has a "primary network number". ... If the router is prepared to assign an IPX network number to the link, it sends its primary network number in the Timer Request WNodeID field, and omits the Extended Node ID option. On the other hand, if the router is NOT prepared to assign an IPX network number to the link, it sets the Timer Request WNodeID field to zero, and includes its primary network number in an Extended Node ID option. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1551.txt -- 53.9 Кб -- 04.12.1993
Похожие документы
Похожие документы
80945. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1549.txt
... 12 APPENDIX A. Fast Frame Check Sequence (FCS) Implementation .. ... PPP uses the HDLC Frame Check Sequence for error detection. ... Aborting a Transmission On asynchronous links, frames may be aborted by transmitting a "0" stop bit where a "1" bit is expected (framing error) or by transmitting a Control Escape octet followed immediately by a closing Flag Sequence. ... Aborting a Transmission Frames may be aborted by transmitting a Control Escape octet followed immediately by a closing Flag Sequence...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1549.txt -- 36.5 Кб -- 04.12.1993
Похожие документы
Похожие документы
80946. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1548.txt
... LCP Packet Formats .. ... 46 6.6 Protocol-Field-Compression .. ... Protocol | ... Protocol field values in the "c***" to "f***" range identify packets as link-layer Control Protocols (such as LCP). ... 5.1 Configure-Request Description An implementation wishing to open a connection MUST transmit a LCP packet with the Code field set to 1 (Configure-Request), and the Simpson [Page 29] RFC 1548 The Point-to-Point Protocol December 1993 Options field filled with any desired changes to the link defaults....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1548.txt -- 110.0 Кб -- 04.12.1993
Похожие документы
Похожие документы
80947. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1547.txt
Network Working Group D. Perkins Request for Comments: 1547 Carnegie Mellon University Category: Informational December 1993 Requirements for an Internet Standard Point-to-Point Protocol Status of this Memo This memo provides information for the Internet community. ... Abstract This document discusses the evaluation criteria for an Internet Standard Data Link Layer protocol to be used with point-to-point links. ... 8 2.7 Multiple Physical and Data Link Layer Protocols.. ... 13 3.5 Multi-Point Links .. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1547.txt -- 49.6 Кб -- 04.12.1993
Похожие документы
Похожие документы
80948. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9310.txt
... page 39 Cooper [Page 2] Internet Monthly Report October 1993 INTERNET ENGINEERING REPORTS ---------------------------- IETF MONTHLY REPORT for October, 1993 1. ... A total of 88 Internet -Draft actions were taken during the month of October , 1993 : (Revised draft (o), New Draft (+) ) (idpr) o Definitions of Managed Objects for the Inter-Domain Policy Routing Protocol (Version 1) draft-ietf-idpr-mib-03.txt (x400ops) o Operational Requirements for X.400 Management Domains in the GO-MHS...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9310.txt -- 96.8 Кб -- 17.11.1993
Похожие документы
Похожие документы
80949. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1546.txt
Network Working Group C. Partridge Request for Comments: 1546 T. Mendez Category: Informational W. Milliken BBN November 1993 Host Anycasting Service Status of this Memo This memo provides information for the Internet community. ... A host transmits a datagram to an anycast address and the internetwork is responsible for providing best effort delivery of the datagram to at least one, and preferably only one, of the servers that accept datagrams for the anycast address. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1546.txt -- 22.7 Кб -- 12.11.1993
Похожие документы
Похожие документы
80950. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1544.txt
... Category: Standards Track November 1993 The Content-MD5 Header Field Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Abstract This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages. ... Generation of the Content-MD5 Field .. ... To generate the value of the Content-MD5 field, the MD5 algorithm is computed on the canonical form of the...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1544.txt -- 7.3 Кб -- 10.11.1993
Похожие документы
Похожие документы
80951. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1545.txt
Network Working Group D. Piscitello Request for Comments: 1545 Bellcore Category: Experimental November 1993 FTP Operation Over Big Address Records (FOOBAR) Status of this Memo This memo defines an Experimental Protocol for the Internet community. ... Introduction This RFC specifies a method for assigning long addresses in the HOST-PORT specification for the data port to be used in establishing a data connection for File Transfer Protocol, FTP (STD 9, RFC 959). ... This memo addresses these needs. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1545.txt -- 9.8 Кб -- 10.11.1993
Похожие документы
Похожие документы
80952. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1543.txt
Network Working Group J. Postel Request for Comments: 1543 ISI Obsoletes: RFCs 1111, 825 October 1993 Category: Informational Instructions to RFC Authors Status of this Memo This memo provides information for the Internet community. ... However, any Postel [Page 1] RFC 1543 Instructions to RFC Authors October 1993 topic related to computer communication may be acceptable at the discretion of the RFC Editor. ... If you plan to submit a document in PostScript please consult the RFC Editor first. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1543.txt -- 31.6 Кб -- 28.10.1993
Похожие документы
Похожие документы
80953. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1542.txt
... 14 4.1.2 BOOTREPLY Messages.. ... BOOTP Server Behavior.. ... For those server/relay agents which cannot cache the return route (because they are stateless, for example), the BOOTREPLY message SHOULD be sent to the client's hardware address, as taken from the BOOTP message, with a Spanning Tree Rooted RIF. ... 3.1 Client use of the 'flags' field 3.1.1 The BROADCAST flag Normally, BOOTP servers and relay agents attempt to deliver BOOTREPLY messages directly to a client using unicast delivery. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1542.txt -- 52.7 Кб -- 25.10.1993
Похожие документы
Похожие документы
80954. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1541.txt
... The Client-Server Protocol . 11 3.1 Client-server interaction - allocating a network address. ... Droms [Page 24] RFC 1541 Dynamic Host Configuration Protocol October 1993 Field DHCPOFFER DHCPACK DHCPNAK ----- --------- ------- ------- 'op' BOOTREPLY BOOTREPLY BOOTREPLY 'htype' (From Assigned Numbers RFC) 'hlen' (Hardware address length in octets) 'hops' 0 0 0 'xid' 'xid' from client 'xid' from client 'xid' from client DHCPDISCOVER DHCPREQUEST DHCPREQUEST message message ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1541.txt -- 95.7 Кб -- 25.10.1993
Похожие документы
Похожие документы
80955. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1540.txt
... 18 Internet Architecture Board [Page 1] RFC 1540 Internet Standards October 1993 6.2. ... Elective 1484 IDPR Inter-Domain Policy Routing Protocol Elective 1479 IDPR-ARCH Architecture for IDPR Elective 1478 PPP/Bridge MIB Bridge PPP MIB Elective 1474 PPP/IP MIB IP Network Control Protocol of PPP MIB Elective 1473 PPP/SEC MIB Security Protocols of PPP MIB Elective 1472 PPP/LCP MIB Link Control Protocol of PPP MIB Elective 1471 X25-MIB Multiprotocol Interconnect on X.25 MIB ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1540.txt -- 74.7 Кб -- 22.10.1993
Похожие документы
Похожие документы
80956. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9309.txt
September 1993 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 3 INTERNET ENGINEERING REPORTS . ... September 1993. ... Cooper [Page 13] Internet Monthly Report September 1993 RFC 1524: Borenstein, N., (Bellcore), "A User Agent Configuration Mechanism For Multimedia Mail Format Information", September 1993. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9309.txt -- 86.6 Кб -- 15.10.1993
Похожие документы
Похожие документы
80957. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1534.txt
... BOOTP clients and DHCP servers The format of DHCP messages is defined to be compatible with the format of BOOTP messages, so that existing BOOTP clients can interoperate with DHCP servers. ... If a DHCP server is configured to support BOOTP clients, it may be configured to supply static addresses, automatic addresses or both. ... If a DHCP server returns a automatic address, the BOOTP client will not be aware of the DHCP lease mechanism for network address assignment. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1534.txt -- 7.8 Кб -- 06.10.1993
Похожие документы
Похожие документы
80958. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1533.txt
... Obsoletes: 1497, 1395, 1084, 1048 R. Droms Category: Standards Track Bucknell University October 1993 DHCP Options and BOOTP Vendor Extensions Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Options may be fixed length or variable length. ... Alexander & Droms [Page 24] RFC 1533 DHCP Options and BOOTP Vendor Extensions October 1993 The code for this option is 54, and its length is 4....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1533.txt -- 50.7 Кб -- 06.10.1993
Похожие документы
Похожие документы
80959. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1532.txt
... 14 4.1.2 BOOTREPLY Messages.. ... BOOTP Server Behavior.. ... 3.1 Client use of the 'flags' field 3.1.1 The BROADCAST flag Normally, BOOTP servers and relay agents attempt to deliver BOOTREPLY messages directly to a client using unicast delivery. ... If an old client or server does set the BROADCAST flag to 1 incorrectly, conforming relay agents will generate broadcast BOOTREPLY Wimer [Page 17] RFC 1532 Clarifications and Extensions for BOOTP October 1993 messages to the corresponding client. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1532.txt -- 51.3 Кб -- 06.10.1993
Похожие документы
Похожие документы
80960. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1531.txt
... The Client-Server Protocol . 11 3.1 Client-server interaction - allocating a network address. ... Droms [Page 24] RFC 1531 Dynamic Host Configuration Protocol October 1993 Field DHCPOFFER DHCPACK DHCPNAK ----- --------- ------- ------- 'op' BOOTREPLY BOOTREPLY BOOTREPLY 'htype' (From Assigned Numbers RFC) 'hlen' (Hardware address length in octets) 'hops' 0 0 0 'xid' 'xid' from client 'xid' from client 'xid' from client DHCPDISCOVER DHCPREQUEST DHCPREQUEST message message ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1531.txt -- 94.9 Кб -- 06.10.1993
Похожие документы
Похожие документы