IPng Requirements of Large Corporate Networks (RFC1678)
Original Publication Date: 1994-Aug-01
Included in the Prior Art Database: 2019-Feb-12
Internet Society Requests For Comment (RFCs)
E. Britton: AUTHOR [+1]
This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
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. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
This document was submitted to the IETF IPng area in response to RFC 1550. Publication of this document does not imply acceptance by the IPng area of any ideas expressed within. Comments should be submitted to the email@example.com mailing list. This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite.
As more and more corporations are using TCP/IP for their mission- critical applications, they are bringing additional requirements, summarized below, the satisfaction of which would make TCP/IP even more appealing to businesses. Since these are requirements rather than solutions, we include capabilities that might be provided in protocol layers other than the one that IPv4 occupies; i.e., these items might lie outside the scope typically envisioned for IPng, but we’ll refer to them as IPng requirements nonetheless. When we mention potential solutions, it is not to suggest that they are the best approach, but merely to clarify the requirement.
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.
We also mention several more specific requirements.
IPng must have a viable strategy for migration from, and coexistence with, IPv4. IPv4 and IPng must coexist well, because they will need to do so for several years. To encourage IPv4 users to upgrade to
Britton & Tavs [Page 1]
RFC 1678 IPng Requirements of Large Corporate Networks August 1994
IPng, IPng must offer compelling advantages and an easy migration path.
Corporate networks must meet promised levels of service while controlling costs through efficient use of resources. The IETF should consider both technical solutions (such as service classes and priorities) and administrative ones (such as accounting) to promote economy.
Many businesses will not connect to a network until they are confident that it will not significantly threaten the confidentiality, integrity, or availability of their data.
Corporations tend to use multiple protocols. Numerous forces stymie the desire to settle on just one protocol for a large corporation: diverse installed bases, skills, technical factors, and the general trend toward corporate decentralization. The IETF needs a strategy for heterogeneity flexible enough to accommodate the principal multiprotocol techniques, including multiprotocol transport, tunneling, and link sharing.
Some of these requirements might be satisfied by more extensive deployme...