Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80841 - 80860 из 81894.
[ В начало ] Пред. | 4039 |
4040 |
4041 |
4042 |
4043
|
4044 |
4045 |
4046 |
4047 |
4048 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80841. http://mirror.msu.net/pub/slackware-current/source/n/network-scripts/scripts/host.conf
order hosts, bind multi on
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/slackware-current/source/n/network-scripts/scripts/host.conf -- 1.0 Кб -- 07.07.1994
Похожие документы
Похожие документы
80842. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1627.txt
... SUMMARY Re-use of Internet addresses for private IP networks is the topic of the recent RFC 1597 [1]. ... RFC 1597 produces apparent relief from IPv4 address space exhaustion by masking those networks that are not connecting to the Internet, today. ... Lear, Fair, Crocker & Kessler [Page 4] RFC 1627 Network 10 Considered Harmful July 1994 Problems with Examples RFC 1597 gives several examples of IP networks that need not have globally unique address spaces. ... RIPE NCC, RFC 1597, March 1994. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1627.txt -- 19.4 Кб -- 30.06.1994
Похожие документы
Похожие документы
80843. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9405.txt
May 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. ... 2 (May/June 1994) has gone to press. ... May 1994. ... 32 2 519 6819 NETWORK SERVICES CONFERENCE 94 ------------------------------ from 28 to 30 November 1994 Cooper [Page 46] Internet Monthly Report May 1994 in London (UK) *CALL FOR PAPERS* deadline 1 July 1994. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9405.txt -- 96.6 Кб -- 14.06.1994
Похожие документы
Похожие документы
80844. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1638.txt
Network Working Group F. Baker Request For Comments: 1638 ACC Category: Standards Track R. Bowen IBM Editors June 1994 PPP Bridging Control Protocol (BCP) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... One system is elected as the "Root", which periodically emits a message called a Bridge Protocol Data Unit (BPDU), heard by all of its neighboring bridges. ... Source MAC Address | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1638.txt -- 58.1 Кб -- 08.06.1994
Похожие документы
Похожие документы
80845. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1639.txt
... Abstract This paper describes a convention for specifying address families other than the default Internet address family in FTP commands and replies. Introduction In the File Transfer Protocol (STD 9, RFC 959), the PORT command argument <host-port> specifies the data port to be used to establish a data connection for FTP (STD 9, RFC 959). This argument is also used in the PASV reply to request the server-DTP to listen on a data port other than its default data port. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1639.txt -- 10.8 Кб -- 08.06.1994
Похожие документы
Похожие документы
80846. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1637.txt
... Also required as part of this infrastructure is support in the Domain Name System (DNS) for mapping between names and NSAP addresses. This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. ... NSAP-to-name translation is accomplished through use of the PTR RR (see STD 13, RFC 1035 for a description of the PTR RR). ... NAME / | ... Manning & Colella [Page 7] RFC 1637 DNS NSAP RRs June 1994 ;;;;;; ;;;;;; Master File for domain nsap.nist.gov. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1637.txt -- 22.3 Кб -- 08.06.1994
Похожие документы
Похожие документы
80847. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1640.txt
Network Working Group S. Crocker Request for Comments: 1640 TIS Category: Informational June 1994 The Process for Organization of Internet Standards Working Group (POISED) Status of this Memo This memo provides information for the Internet community. ... Given the strong consensus that emerged at that meeting, the group decided to implement the selection process by the next IETF meeting, with the new IESG and IAB members to begin their terms at the termination of the IETF meeting in March. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1640.txt -- 22.3 Кб -- 08.06.1994
Похожие документы
Похожие документы
80848. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1630.txt
Network Working Group T. Berners-Lee Request for Comments: 1630 CERN Category: Informational June 1994 Universal Resource Identifiers in WWW A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web Status of this Memo This memo provides information for the Internet community. ... Printable It is possible to express any URI using 7-bit ASCII characters so that URIs may, if necessary, be passed using pen and ink. ... Two schemes are defined. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1630.txt -- 57.3 Кб -- 07.06.1994
Похожие документы
Похожие документы
80849. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1633.txt
Network Working Group R. Braden Request for Comments: 1633 ISI Category: Informational D. Clark MIT S. Shenker Xerox PARC June 1994 Integrated Services in the Internet Architecture: an Overview Status of this Memo This memo provides information for the Internet community. ... We can thus augment the service model by allowing the network to notify (either implicitly through packet drops or explicitly through control packets) rate-adaptive applications to change their traffic characterization. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1633.txt -- 88.6 Кб -- 07.06.1994
Похожие документы
Похожие документы
80850. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1636.txt
Network Working Group R. Braden Request for Comments: 1636 ISI Category: Informational D. Clark MIT Laboratory for Computer Science S. Crocker Trusted Information Systems, Inc. C. Huitema INRIA, IAB Chair June 1994 Report of IAB Workshop on Security in the Internet Architecture February 8-10, 1994 Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document is a
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1636.txt -- 128.7 Кб -- 07.06.1994
Похожие документы
Похожие документы
80851. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1625.txt
... B. Kahle WAIS, Inc. ... Introduction The network publishing system, Wide Area Information Servers (WAIS), is designed to help users find information over a computer network. ... The protocol, Z39.50-1988, is used to connect WAIS clients and servers and is based on the 1988 Version of the NISO Z39.50 Information Retrieval Service and Protocol Standard. ... From the beginning, WAIS committed to use the Z39.50-1988 standard as the information retrieval protocol between WAIS clients and servers. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1625.txt -- 15.3 Кб -- 07.06.1994
Похожие документы
Похожие документы
80852. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi24.txt
... Abstract This document provides information for the novice Internet user about using the File Transfer Protocol (FTP). ... A user of an FTP program must log in to both hosts in order to transfer a file from one to the other. ... IAFA Working Group [Page 1] RFC 1635 How To FTP May 1994 However, Internet users may also take advantage of a wealth of information available from archive sites by using a general purpose account called "anonymous FTP". ... The resulting files are always in binary format. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi24.txt -- 27.6 Кб -- 24.05.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1635.txt -- 27.6 Кб -- 24.05.1994
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1635.txt -- 27.6 Кб -- 24.05.1994
Похожие документы
80853. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1634.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/rfc1634.txt -- 55.0 Кб -- 23.05.1994
Похожие документы
Похожие документы
80854. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RAREreports/rtr11.txt
Network Working Group P. Barker Request for Comments: 1617 University College London RARE Technical Report: 11 S. Kille Obsoletes: 1384 ISODE Consortium Category: Informational T. Lenggenhager SWITCH May 1994 Naming and Structuring Guidelines for X.500 Directory Pilots Status of this Memo This memo provides information for the Internet community. ... Example: 8kiu8z7e 4.4.2 Organisational Attributes associatedDomain [RFC 1274] The Internet domain name for an organisation or one of its units. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/RAREreports/rtr11.txt -- 56.4 Кб -- 23.05.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1617.txt -- 56.4 Кб -- 23.05.1994
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1617.txt -- 56.4 Кб -- 23.05.1994
Похожие документы
80855. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1623.txt
... Obsoletes: 1398 May 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/rfc1623.txt -- 38.8 Кб -- 23.05.1994
Похожие документы
Похожие документы
80856. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi11.txt
Network Working Group A. Getchell Request for Comments: 1632 Lawrence Livermore National Laboratory FYI: 11 S. Sataluri Obsoletes: 1292 AT&T Bell Laboratories Category: Informational Editors May 1994 A Revised Catalog of Available X.500 Implementations Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document is the result of a survey that gathered new or updated
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/fyi/fyi11.txt -- 122.2 Кб -- 19.05.1994
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1632.txt -- 122.2 Кб -- 19.05.1994
Похожие документы
[ Сохраненная копия ] Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1632.txt -- 122.2 Кб -- 19.05.1994
Похожие документы
80857. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1624.txt
Network Working Group A. Rijsinghani, Editor Request for Comments: 1624 Digital Equipment Corporation Updates: 1141 May 1994 Category: Informational Computation of the Internet Checksum via Incremental Update Status of this Memo This memo provides information for the Internet community. ... It updates the method described in RFC 1141. ... Checksum verification by end systems .. ... RFC 1071, on pages 4 and 5, describes a procedure to incrementally update the standard Internet checksum. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1624.txt -- 10.6 Кб -- 19.05.1994
Похожие документы
Похожие документы
80858. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1620.txt
... The architecture still works if this assumption is violated, but it does not have a means to prevent multiple host- router and router-router hops through the shared medium. ... Indeed, for network management purposes, a router plays the role of a host by originating and terminating datagrams. ... The host initially uses some "default" router for any new destination address. If the default is the wrong choice, that router returns a Redirect message and forwards the datagram. ... Networks A, .. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1620.txt -- 44.9 Кб -- 18.05.1994
Похожие документы
Похожие документы
80859. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1622.txt
... Pip Specification The Pip header is partitioned into three parts, the Initial Part, the Transit Part, and the Options Part. ... Options Part | ... Options Contents | ... As long as the Version field is 8, the Initial Part and Options Part of the Pip Header is as specified in this standard. ... Francis [Page 5] RFC 1622 Pip Header Processing May 1994 2.1.4 Options Present This field indicates which of the Options indicated by the Options Contents field are actually present in the Options Part. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1622.txt -- 35.0 Кб -- 18.05.1994
Похожие документы
Похожие документы
80860. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1621.txt
Network Working Group P. Francis Request for Comments: 1621 NTT Category: Informational May 1994 Pip Near-term Architecture Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Preamble During 1992 and 1993, the Pip internet protocol, developed at Belclore, was one of the candidate replacments for IP. In mid 1993, Pip was merged with another candidate, the Simple Internet Protocol
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1621.txt -- 126.9 Кб -- 18.05.1994
Похожие документы
Похожие документы