Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80681 - 80700 из 81894.
[ В начало ] Пред. | 4031 |
4032 |
4033 |
4034 |
4035
|
4036 |
4037 |
4038 |
4039 |
4040 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80681. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1759.txt
Network Working Group R. Smith Request for Comments: 1759 Texas Instruments Category: Standards Track F. Wright Lexmark International T. Hastings Xerox Corporation S. Zilles Adobe Systems, Inc. J. Gyllenskog Hewlett-Packard Company March 1995 Printer MIB 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)
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1759.txt -- 234.6 Кб -- 22.03.1995
Похожие документы
Похожие документы
80682. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1786.txt
Network Working Group T. Bates Request for Comments: 1786 MCI Telecommunications Corporation Category: Informational E. Gerich Merit, Inc. L. Joncheray Merit, Inc. J-M. Jouanigot CERN D. Karrenberg RIPE NCC M. Terpstra Bay Networks, Inc. J. Yu Merit, Inc. March 1995 Representation of IP Routing Policies in a Routing Registry (ripe-81++) 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
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1786.txt -- 131.5 Кб -- 21.03.1995
Похожие документы
Похожие документы
80683. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1785.txt
Network Working Group G. Malkin Request for Comments: 1785 Xylogics, Inc. Updates: 1350 A. Harkin Category: Informational Hewlett Packard Co. March 1995 TFTP Option Negotiation Analysis Status of this Memo This memo provides information for the Internet community. ... From these results and examinations, it is clear that the TFTP option Malkin & Harkin [Page 1] RFC 1785 TFTP Option Negotiation Analysis March 1995 negotiation mechanism is fully backward-compatible with unmodified TFTP servers. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1785.txt -- 4.3 Кб -- 20.03.1995
Похожие документы
Похожие документы
80684. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1784.txt
... March 1995 TFTP Timeout Interval and Transfer Size Options Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... mode | ... timeout| 0 | ... This is a NULL-terminated field. ... Transfer Size Option Specification The TFTP Read Request or Write Request packet is modified to include the tsize option as follows: +-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+ | ... size | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1784.txt -- 7.0 Кб -- 20.03.1995
Похожие документы
Похожие документы
80685. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1783.txt
... March 1995 TFTP Blocksize Option Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Malkin & Harkin [Page 1] RFC 1783 TFTP Blocksize Option March 1995 mode The mode of the file transfer: "netascii", "octet", or "mail", as defined in [1]. ... March 1995. Malkin & Harkin [Page 4] RFC 1783 TFTP Blocksize Option March 1995 Authors' Addresses Gary Scott Malkin Xylogics, Inc. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1783.txt -- 8.6 Кб -- 20.03.1995
Похожие документы
Похожие документы
80686. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1782.txt
... A new type of TFTP packet, the Option Acknowledgment (OACK), is used to acknowledge a client's option negotiation request. ... Malkin & Harkin [Page 3] RFC 1782 TFTP Option Extension March 1995 When the client appends options to the end of a Read Request packet, three possible responses may be returned by the server: OACK - acknowledge of Read Request and the options; DATA - acknowledge of Read Request, but not the options; ERROR - the request has been denied. ... OACK |3|1| 2048 octets of data | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1782.txt -- 12.2 Кб -- 20.03.1995
Похожие документы
Похожие документы
80687. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1770.txt
... Abstract This memo defines an IPv4 option to provide a sender directed multi- destination delivery mechanism called Selective Directed Broadcast Mode (SDBM). The SDBM provides unreliable UDP delivery to a set of IP addresses included in the option field of an IPv4 datagram. ... IP ADDRESS 1 | IP ADDRESS 1(Cont) | ... Figure 1 IP Option Field Layout Graff [Page 2] RFC 1770 Selective Directed Broadcast Protocol March 1995 The TYPE field specifies the copy flag, class, and option number. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1770.txt -- 12.3 Кб -- 20.03.1995
Похожие документы
Похожие документы
80688. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1775.txt
... If a user accesses the Internet by running a terminal program on their PC and then dials up a public service which provides the Internet applications, then that user has Mediated Internet access. The public service has Client or Full access, but the user does not. ... If a user from the internal internet has a desktop computer and reaches out to the Internet, through the firewall, by running any Internet applications, such as a Web browser, then that user has Client Internet access. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1775.txt -- 9.3 Кб -- 20.03.1995
Похожие документы
Похожие документы
80689. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1781.txt
Network Working Group S. Kille Request for Comments: 1781 ISODE Consortium Obsoletes: 1484 March 1995 Category: Standards Track Using the OSI Directory to Achieve User Friendly Naming Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Kille [Page 12] RFC 1781 User Friendly Naming March 1995 Greater than 2 Make an approximate and substring match on friendly country and organisation. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1781.txt -- 47.0 Кб -- 17.03.1995
Похожие документы
Похожие документы
80690. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1779.txt
Network Working Group S. Kille Request for Comments: 1779 ISODE Consortium Obsoletes: 1485 March 1995 Category: Standards Track A String Representation of Distinguished Names Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Abstract The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1779.txt -- 13.1 Кб -- 17.03.1995
Похожие документы
Похожие документы
80691. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1778.txt
... Standard Attribute Syntax Encodings For the purposes of defining the encoding rules for the standard attribute syntaxes, the following auxiliary BNF definitions will be used: <a> ::= 'a' | ... Undefined Values of type Undefined are encoded as if they were values of type Octet String, with the string value being the BER-encoded version of the value. ... Case Ignore List Values of type caseIgnoreListSyntax are encoded according to the following BNF: <caseignorelist> ::= <caseignorestring> | ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1778.txt -- 19.6 Кб -- 17.03.1995
Похожие документы
Похожие документы
80692. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1777.txt
... Protocol Model The general model adopted by this protocol is one of clients performing protocol operations against servers. ... Yeong, Howes Kille [Page 18] RFC 1777 LDAP March 1995 } } BindResponse ::= [ APPLICATION 1] LDAPResult UnbindRequest ::= [ APPLICATION 2] NULL SearchRequest ::= [ APPLICATION 3] SEQUENCE { baseObject LDAPDN, scope ENUMERATED { baseObject (0), singleLevel (1), wholeSubtree (2) }, derefAliases ENUMERATED { neverDerefAliases ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1777.txt -- 45.4 Кб -- 17.03.1995
Похожие документы
Похожие документы
80693. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1773.txt
Network Working Group P. Traina Request for Comments: 1773 cisco Systems Obsoletes: 1656 March 1995 Category: Informational Experience with the BGP-4 protocol Status of this Memo This memo provides information for the Internet community. ... Traina [Page 1] RFC 1773 Experience with the BGP-4 Protocol March 1995 Documentation BGP is an inter-autonomous system routing protocol designed for TCP/IP internets. ... 7] Traina P., "BGP Version 4 Protocol Analysis", RFC 1774, cisco Systems, March 1995. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1773.txt -- 20.5 Кб -- 16.03.1995
Похожие документы
Похожие документы
80694. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1774.txt
Network Working Group P. Traina, Editor Request for Comments: 1774 cisco Systems Category: Informational March 1995 BGP-4 Protocol Analysis Status of this Memo This memo provides information for the Internet community. ... BGP-4 is an inter-autonomous system routing protocol designed for TCP/IP internets. ... BGP assumes that routing within an autonomous system is done by an intra- autonomous system routing protocol. ... BGP is a real inter-autonomous system routing protocol. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1774.txt -- 24.3 Кб -- 16.03.1995
Похожие документы
Похожие документы
80695. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1772.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. ... BGP implementations should allow an AS to ignore routes with certain AS's in the AS_PATH path attribute. ... Each border gateway should use identical tags for announcing exterior routing information (received via BGP) both into the IGP and when propagating this information to other internal peers (peers within the same AS). ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1772.txt -- 43.9 Кб -- 16.03.1995
Похожие документы
Похожие документы
80696. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1771.txt
Network Working Group Y. Rekhter Request for Comments: 1771 T.J. Watson Research Center, IBM Corp. Obsoletes: 1654 T. Li Category: Standards Track cisco Systems Editors March 1995 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
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1771.txt -- 129.8 Кб -- 16.03.1995
Похожие документы
Похожие документы
80697. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1769.txt
... It can operate in both unicast modes (point to point) and broadcast modes (point to multipoint). ... Mode: This is a three-bit integer indicating the mode, with values defined as follows: Mode Meaning ------------------------------------ 0 reserved 1 symmetric active 2 symmetric passive 3 client 4 server 5 broadcast 6 reserved for NTP control message 7 reserved for private use In unicast mode the client sets this field to 3 (client) in the request and the server sets it to 4 (server) in the reply. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1769.txt -- 34.6 Кб -- 16.03.1995
Похожие документы
Похожие документы
80698. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9502.txt
February 1995 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 9 DANTE . ... This may sound very familiar to the networking community but in the commercial world the Cooper [Page 10] Internet Monthly Report February 1995 Internet is not yet the standard information medium, security being one major concern. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/museum/imr/imr9502.txt -- 83.6 Кб -- 11.03.1995
Похожие документы
Похожие документы
80699. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1768.txt
... This mapping is obtained in the following manner: a) If there is a multicast capable IS reachable on the subnetwork then the SNPA address used by an End System originating a multi- cast PDU is either the paired SNPA address obtained from the multicast address mapping information associated with the group Network address in the multicast PDU 's Destination ... CLNP multicast uses a dynamic binding of a group Network address (up to 20 bytes) to any subnetwork address. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1768.txt -- 109.9 Кб -- 02.03.1995
Похожие документы
Похожие документы
80700. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1767.txt
Network Working Group D. Crocker Request for Comments: 1767 Brandenburg Consulting Category: Standards Track March 1995 MIME Encapsulation of EDI Objects Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Application/EDIFACT specification.. ... Introduction Electronic Data Interchange (EDI) provides a means of conducting structured transactions between trading partners. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1767.txt -- 15.9 Кб -- 01.03.1995
Похожие документы
Похожие документы