Поиск по:mirror.msu.net -
Поискать по всем серверам
На этой странице приведены все страницы сервера mirror.msu.net ,которые мы индексируем. Показаны документы 80801 - 80820 из 81894.
[ В начало ] Пред. | 4037 |
4038 |
4039 |
4040 |
4041
|
4042 |
4043 |
4044 |
4045 |
4046 | След. [ В конец ]
Упорядочить по:
URL
|
дате изменения
80801. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1683.txt
Network Working Group R. Clark Request for Comments: 1683 M. Ammar Category: Informational K. Calvert Georgia Institute of Technology August 1994 Multiprotocol Interoperability In IPng Status of this Memo This memo provides information for the Internet community. ... Clark, Ammar & Calvert [Page 3] RFC 1683 Multiprotocol Interoperability In IPng August 1994 It is likely that many future network systems will be configured to support multiple protocols including IPng. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1683.txt -- 28.5 Кб -- 08.08.1994
Похожие документы
Похожие документы
80802. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1672.txt
Network Working Group N. Brownlee Request for Comments: 1672 The University of Auckland Category: Informational August 1994 Accounting Requirements for IPng Status of this Memo This memo provides information for the Internet community. ... It recommends that all IPng packets carry accounting tags, which would vary in size. ... The model is very general, with accounting variables being defined for various layers of a protocol stack. ... For the application variables, a separate tag seems sensible. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1672.txt -- 7.0 Кб -- 05.08.1994
Похожие документы
Похожие документы
80803. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1671.txt
Network Working Group B. Carpenter Request for Comments: 1671 CERN Category: Informational August 1994 IPng White Paper on Transition and Other Considerations Status of this Memo This memo provides information for the Internet community. ... D) IPv4 to IPng address mapping. ... An IPv4 packet must be able to find its way from any IPv4 host, to any other IPv4 or IPng host, or vice versa, through a mixture of IPv4 and IPng routers, with no (zero, null) modifications to the IPv4 hosts. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1671.txt -- 18.2 Кб -- 05.08.1994
Похожие документы
Похожие документы
80804. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1681.txt
Network Working Group S. Bellovin Request for Comments: 1681 AT&T Bell Laboratories Category: Informational August 1994 On Many Addresses per Host Status of this Memo This memo provides information for the Internet community. ... Bellovin [Page 1] RFC 1681 On Many Addresses per Host August 1994 Security is another reason, in some cases. ... Some Bellovin [Page 4] RFC 1681 On Many Addresses per Host August 1994 hosts need to live on both logical networks at once, to avoid an extra hop through a router. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1681.txt -- 12.7 Кб -- 04.08.1994
Похожие документы
Похожие документы
80805. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1680.txt
Network Working Group C. Brazdziunas Request for Comments: 1680 Bellcore Category: Informational August 1994 IPng Support for ATM Services Status of this Memo This memo provides information for the Internet community. ... Sophisticated" link technologies like ATM are emerging in the marketplace allowing several virtual channels to be established over a single wire (or fiber) potentially based on an applications' network performance objectives. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1680.txt -- 18.4 Кб -- 04.08.1994
Похожие документы
Похожие документы
80806. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1679.txt
Network Working Group D. Green Request for Comments: 1679 P. Irey Category: Informational D. Marlow K. O'Donoghue NSWC-DD August 1994 HPN Working Group Input to the IPng Requirements Solicitation Status of this Memo This memo provides information for the Internet community. ... Executive Summary The Navy's High Performance Network (HPN) working group has studied the requirements of mission critical applications on Navy platforms. ... These are also issues of importance to the HPN working group. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1679.txt -- 23.4 Кб -- 04.08.1994
Похожие документы
Похожие документы
80807. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1678.txt
Network Working Group E. Britton Request for Comments: 1678 J. Tavs Category: Informational IBM August 1994 IPng Requirements of Large Corporate Networks Status of this Memo This memo provides information for the Internet community. ... Among business users the major requirements we see for IPng are: -- smooth migration from, and coexistence with, IPv4; -- predictable levels of service for predictable costs; -- security; and -- accommodation of multiple protocols suites. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1678.txt -- 19.2 Кб -- 04.08.1994
Похожие документы
Похожие документы
80808. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1675.txt
Network Working Group S. Bellovin Request for Comments: 1675 AT&T Bell Laboratories Category: Informational August 1994 Security Concerns for IPng Status of this Memo This memo provides information for the Internet community. ... Network-level firewalls often need to check both the source and destination address. ... Bellovin [Page 2] RFC 1675 Security Concerns for IPng August 1994 Dual-stack approaches, such as in TUBA's transition plan [2], imply multiple addresses for each host. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1675.txt -- 9.1 Кб -- 04.08.1994
Похожие документы
Похожие документы
80809. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1674.txt
Network Working Group M. Taylor Request for Comments: 1674 CDPD Consortium Category: Informational August 1994 A Cellular Industry View of IPng Status of this Memo This memo provides information for the Internet community. ... Distribution of this memo is unlimited. ... As the leading service providers for this nascent technology, which will provide the capability for mobility of native mainstream connectionless network layer-based applications it is our intention to support whatever form IPng takes. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1674.txt -- 7.0 Кб -- 04.08.1994
Похожие документы
Похожие документы
80810. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1673.txt
Network Working Group R. Skelton Request for Comments: 1673 EPRI Category: Informational August 1994 Electric Power Research Institute Comments on IPng Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. ... Skelton [Page 2] RFC 1673 EPRI Comments on IPng August 1994 - Routing table economy Network addressing must achieve significant economy in routing database size with very large networks. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1673.txt -- 8.3 Кб -- 04.08.1994
Похожие документы
Похожие документы
80811. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1670.txt
... Timescales In order to allow key decisions to be taken early, I would like to see IPng decisions and timescales broken down into into smaller parts, for example: - address structure and allocation mechanism - name service changes - host software and programming interface changes - routing protocol changes Although interrelated, not all details need to be defined by the same date. ... Provide for transition autonomy. Let systems and sites transition at different times, as convenient for them. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1670.txt -- 6.2 Кб -- 04.08.1994
Похожие документы
Похожие документы
80812. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1669.txt
Network Working Group J. Curran Request for Comments: 1669 BBN Category: Informational August 1994 Market Viability as a IPng Criteria Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. ... Can IPng compete against IPv4? ... To gain connectivity to otherwise unreachable IPng hosts For existing sites with valid IPv4 network assignments, connectivity is not affected until address depletion occurs. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1669.txt -- 8.9 Кб -- 04.08.1994
Похожие документы
Похожие документы
80813. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1668.txt
... August 1994 Unified Routing Requirements for IPng Status of this Memo This memo provides information for the Internet community. ... To provide scalable routing, IPng addressing must provide support for topologically significant address assignment. ... Therefore, IPng packet format must provide efficient determination of the full hierarchical Estrin, Li & Rekhter [Page 1] RFC 1668 Unified Routing Requirements for IPng August 1994 destination address. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1668.txt -- 6.0 Кб -- 04.08.1994
Похожие документы
Похожие документы
80814. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1667.txt
Network Working Group S. Symington Request for Comments: 1667 MITRE Corporation Category: Informational D. Wood MITRE Corporation M. Pullen George Mason University August 1994 Modeling and Simulation Requirements for IPng Status of this Memo This memo provides information for the Internet community. ... The requirements for real-time response, multicasting, and resource reservation are set forth, based on our best current understanding of the future of Defense Modeling and Simulation. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1667.txt -- 17.9 Кб -- 04.08.1994
Похожие документы
Похожие документы
80815. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/bellcore-tcav2-01.txt
Bellcore Threshold Crossing Alert Objects June 1994 Definitions of Managed Objects for Threshold Crossing Alerts SNMPv2 MIB bellcore-tcav2-01.txt (See bellcore-tcav1-01.mib for SNMPv1 MIB) June 1994 Version 1.1 Tracy A. Brown, Kaj Tesink (editors) Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 tacox@mail.bellcore.com, kaj@cc.bellcore.com 1. ... Tracy A. Brown, Kaj Tesink (editors) [Page 1] Bellcore Threshold Crossing Alert Objects June 1994 3. ... This object is read-write. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/mibs/private.mibs/bellcore-tcav2-01.txt -- 27.5 Кб -- 03.08.1994
Похожие документы
Похожие документы
80816. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1665.txt
... 2 2.1 Object Definitions .. ... 3 3.1 Applying MIB II to managing SNA NAUs .. ... to keyboard usable by operator cdeb(3) - time to Change Direction/End Bracket. ::= { snaLuRtmEntry 5 } snaLuRtmBoundary1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION This object contains the value of the first boundary in units of 1/10th of a second. ::= { snaLuRtmEntry 6 } snaLuRtmBoundary2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1665.txt -- 131.3 Кб -- 21.07.1994
Похожие документы
Похожие документы
80817. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1663.txt
... Configuration Option Format .. ... 6 5.3 Using Multi-Link Procedure.. ... If reliable transmission over the HDLC link is desired, the implementation MUST specify the Numbered-Mode Configuration Option during Link Establishment phase. ... Configuration Option Format Description The LCP Numbered-Mode Configuration Option negotiates the use of Numbered-Mode on the link. ... In addition, the Numbered-Mode Configuration Option is negotiated with appropriate addresses for the Multi-Link Procedure. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1663.txt -- 17.9 Кб -- 19.07.1994
Похожие документы
Похожие документы
80818. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1662.txt
... Flag | ... FCS | ... Escaped data is transmitted on the link as follows: Simpson [Page 8] RFC 1662 HDLC-like Framing July 1994 0x7e is encoded as 0x7d, 0x5e. (Flag Sequence) 0x7d is encoded as 0x7d, 0x5d. (Control Escape) 0x03 is encoded as 0x7d, 0x23. ... When mark idle is used on a bit-synchronous link, the implementation MUST ensure at least 15 consecutive "1" bits between Flags during the idle period, and that the Flag Sequence is always generated at the beginning of a frame after an idle period...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1662.txt -- 47.9 Кб -- 19.07.1994
Похожие документы
Похожие документы
80819. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1661.txt
... The Configure-Request packet indicates the desire to open a connection and may specify Configuration Options. ... Implementation Note: Although the Configure-Nak and Configure-Reject cause the same state transition in the automaton, these packets have significantly different effects on the Configuration Options sent in the resulting Configure-Request packet. ... Options .. ... An implementation MUST NOT include multiple Authentication- Protocol Configuration Options in its Configure-Request packets....
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1661.txt -- 101.6 Кб -- 19.07.1994
Похожие документы
Похожие документы
80820. http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1656.txt
Network Working Group P. Traina Request for Comments: 1656 cisco Systems Category: Informational July 1994 BGP-4 Protocol Document Roadmap and Implementation Experience Status of this Memo This memo provides information for the Internet community. ... This network consists of multiple BGP-3 and BGP-4 speakers carrying full routing information injected from Alternet, EBone, Sprint, CERFnet, and cisco. ... July 1994. ... Traina [Page 3] RFC 1656 BGP-4 Implementation July 1994 [4] Fuller V., Li. ...
[
Сохраненная копия
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc1656.txt -- 8.5 Кб -- 19.07.1994
Похожие документы
Похожие документы