Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80961 - 80980 из 81894.
[ В начало ] Пред. | 4045 |
4046 |
4047 |
4048 |
4049
|
4050 |
4051 |
4052 |
4053 |
4054 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80961. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1539.txt
... Obsoletes: 1391 October 1993 FYI: 17 Category: Informational The Tao of IETF A Guide for New Attendees of the Internet Engineering Task Force Status of this Memo This memo provides information for the Internet community. ... 4 IETF Mailing Lists . ... Internet Engineering Task Force [Page 13] RFC 1539 The Tao of IETF October 1993 On the host "ds.internic.net", documents are stored in the directory "/pub/current-ietf-docs" under subdirectories named for each Area and then for each Working Group. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1539.txt -- 48.1 Кб -- 06.10.1993
Похожие документы
Похожие документы
80962. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1536.txt
... The onus of requerying in case no response is seen in a "reasonable" period of time, lies with the client. ... If the client desires the server to recurse and the server architecture allows recursion, the server chains this request to these known servers closest to the queried name. ... If a server does not have an answer now, it is very unlikely it will be any better the next time you query it, specially when it claims to be authoritative over a domain. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1536.txt -- 25.9 Кб -- 06.10.1993
Похожие документы
Похожие документы
80963. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1535.txt
... Category: Informational October 1993 A Security Problem and Proposed Correction With Widely Deployed DNS Software Status of this Memo This memo provides information for the Internet community. ... Example: foobar.company.com or fooschool.university.edu. ... Local Name Space Administration The specification of the Domain Name System and the software that implements it provides an undifferentiated hierarchy which permits delegation of administration for subordinate portions of the name space. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1535.txt -- 10.5 Кб -- 06.10.1993
Похожие документы
Похожие документы
80964. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1537.txt
... SOA records A problem I've found in quite some nameservers is that the various timers have been set (far) too low. ... First of all a short explanation of the timers used in the SOA record: Beertema [Page 1] RFC 1537 Common DNS Data File Configuration Errors October 1993 - Refresh: The SOA record of the primary server is checked every "refresh" time by the secondary servers; if it has changed, a zone transfer is done. ... Wildcard MX records Wildcard MX records should be avoided where possible. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1537.txt -- 20.4 Кб -- 06.10.1993
Похожие документы
Похожие документы
80965. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1530.txt
Network Working Group C. Malamud Request for Comments: 1530 Internet Multicasting Service Category: Informational M. Rose Dover Beach Consulting, Inc. October 1993 Principles of Operation for the TPC.INT Subdomain: General Principles and Policy Status of this Memo This memo provides information for the Internet community. ... 3] Malamud, C., and M. Rose, "Principles of Operation for the TPC.INT Subdomain: Technical Procedures", RFC 1528, Internet Multicasting Service, Dover Beach Consulting, Inc., ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1530.txt -- 15.7 Кб -- 05.10.1993
Похожие документы
Похожие документы
80966. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1529.txt
... October 1993 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies Status of this Memo This memo provides information for the Internet community. ... The technical procedures for remote printing are defined in [1]. ... Models of Operation for Remote Printing Servers Remote printer servers in the tpc.int subdomain consume resources that are typically recovered from neither the initiator nor the recipient of the remote printing service. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1529.txt -- 11.9 Кб -- 05.10.1993
Похожие документы
Похожие документы
80967. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1528.txt
... October 1993 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures Status of this Memo This memo defines an Experimental Protocol for the Internet community. ... 3 3.1 Content-Types .. ... The remote output device may consist of a standard line printer, a printer with Malamud & Rose [Page 1] RFC 1528 Remote Printing -- Technical Procedures October 1993 multiple fonts and faces, a printer that can reproduce graphics, or a facsimile device. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1528.txt -- 19.1 Кб -- 05.10.1993
Похожие документы
Похожие документы
80968. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1538.txt
... The Logical Null XID communicates the sending node's desire to negotiate connection parameters. ... Complete Session Data Flow Node 1 Node 2 Logical Null XID ------------------------- (UDP Datagram) Logical Null XID ------------------------- (UDP Datagram) ------------------------ XID Request (UDP Datagram) Logical SNA XID -------------------------- (UDP Datagram) ------------------------ TCP SYN ( TCP Message) TCP SYN ACK ----------------------------- ( ... Data...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1538.txt -- 21.7 Кб -- 05.10.1993
Похожие документы
Похожие документы
80969. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1527.txt
Network Working Group G. Cook Request for Comments: 1527 Cook Report Category: Informational September 1993 What Should We Plan Given the Dilemma of the Network? ... Abstract Early last year, as the concluding effort of an 18 month appointment at the US Congress Office of Technology Assessment (OTA), I drafted a potential policy framework for Congressional action on the National Research and Education Network (NREN). ... 4 Whom Shall the Network Serve? 5 Access to the NREN is a key policy issue . ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1527.txt -- 46.8 Кб -- 29.09.1993
Похожие документы
Похожие документы
80970. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1526.txt
... Abstract This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. ... Introduction This memo specifies methods for assigning a 6 octet system identifier portion of the OSI NSAP address formats described in "Guidelines for OSI NSAP Allocation in the Internet" [1], in a fashion that ensures that the ID is unique within a routing domain. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1526.txt -- 17.5 Кб -- 29.09.1993
Похожие документы
Похожие документы
80971. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1525.txt
... This group is applicable to source route only, and SRT bridges. ... Otherwise, it will be silently discarded. ::= { dot1dSrPortEntry 7 } dot1dSrPortSpecInFrames OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION The number of Specifically Routed frames, also referred to as Source Routed Frames, that have been received from this port 's segment. ::= { dot1dSrPortEntry 8 } dot1dSrPortSpecOutFrames OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1525.txt -- 38.2 Кб -- 29.09.1993
Похожие документы
Похожие документы
80972. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1520.txt
... Category: Informational C. Topolcic CNRI September 1993 Exchanging Routing Information Across Provider Boundaries in the CIDR Environment Status of this Memo This memo provides information for the Internet community. ... In addition, during the second phase some of the Type 3 providers may become CIDR-capable as well. ... It is still expected that a border router in a CIDR-capable provider would be able to aggregate routing information it receives from a CIDR-incapable Type 3 provider. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1520.txt -- 20.9 Кб -- 23.09.1993
Похожие документы
Похожие документы
80973. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1519.txt
Network Working Group V. Fuller Request for Comments: 1519 BARRNet Obsoletes: 1338 T. Li Category: Standards Track cisco J. Yu MERIT K. Varadhan OARnet September 1993 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... 15 5.2 Routing advertisements .. ... Exhaustion of the class B network address space. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1519.txt -- 59.6 Кб -- 23.09.1993
Похожие документы
Похожие документы
80974. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1518.txt
... Topics covered include: - Benefits of encoding some topological information in IP addresses to significantly reduce routing protocol overhead; - The anticipated need for additional levels of hierarchy in Internet addressing to support network growth; - The recommended mapping between Internet topological entities (i.e., service providers , and service subscribers) and IP addressing and routing components; - The recommended division of IP ... A brief discussion of IP routing is provided. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1518.txt -- 71.9 Кб -- 23.09.1993
Похожие документы
Похожие документы
80975. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1517.txt
Network Working Group Internet Engineering Steering Group Request for Comments: 1517 R. Hinden, Editor Category: Standards Track September 1993 Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Routing information overload. ... IESG [Page 3] RFC 1517 CIDR Applicability Statement September 1993 6. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1517.txt -- 8.2 Кб -- 23.09.1993
Похожие документы
Похожие документы
80976. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1524.txt
Network Working Group N. Borenstein Request for Comments: 1524 Bellcore Category: Informational September 1993 A User Agent Configuration Mechanism For Multimedia Mail Format Information Status of This Memo This memo provides information for the Internet community. ... Abstract This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. ... Mailcap file for Bellcore lab 214. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1524.txt -- 26.8 Кб -- 22.09.1993
Похожие документы
Похожие документы
80977. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1523.txt
Network Working Group N. Borenstein Request for Comments: 1523 Bellcore Category: Informational September 1993 The text/enriched MIME Content-type Status of this Memo This memo provides information for the Internet community. ... The syntax of "text/enriched" is very simple. ... Borenstein [Page 9] RFC 1523 A text/enriched MIME Content-type September 1993 Beyond simply defining new formatting commands, however, it may sometimes be necessary to define formatting commands that can take arguments. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1523.txt -- 32.9 Кб -- 22.09.1993
Похожие документы
Похожие документы
80978. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1522.txt
Network Working Group K. Moore Request for Comments: 1522 University of Tennessee Obsoletes: 1342 September 1993 Category: Standards Track MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. ... Ordinary ASCII text and encoded-words may appear together in the same header field. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1522.txt -- 23.0 Кб -- 22.09.1993
Похожие документы
Похожие документы
80979. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1521.txt
Network Working Group N. Borenstein Request for Comments: 1521 Bellcore Obsoletes: 1341 N. Freed Category: Standards Track Innosoft September 1993 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies Status of this Memo This RFC 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
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1521.txt -- 184.0 Кб -- 22.09.1993
Похожие документы
Похожие документы
80980. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1513.txt
... At a minimum, each object has a name, a syntax, an access-level, and an implementation-status. ... station set the sourceRoutingStatsStatus entry to valid(1). ::= { sourceRoutingStatsEntry 2 } sourceRoutingStatsInFrames OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION The count of frames sent into this ring from another ring . ::= { sourceRoutingStatsEntry 3 } sourceRoutingStatsOutFrames OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1513.txt -- 120.1 Кб -- 20.09.1993
Похожие документы
Похожие документы