| 1 |
<pre>Network Working Group J. Curran |
| 2 |
Request for Comments: 1669 BBN |
| 3 |
Category: Informational August 1994 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Market Viability as a IPng Criteria</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. This memo |
| 11 |
does not specify an Internet standard of any kind. Distribution of |
| 12 |
this memo is unlimited. |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
This document was submitted to the IETF IPng area in response to <a href="./rfc1550">RFC</a> |
| 17 |
<a href="./rfc1550">1550</a>. Publication of this document does not imply acceptance by the |
| 18 |
IPng area of any ideas expressed within. Comments should be |
| 19 |
submitted to the [email protected] mailing list. |
| 20 |
|
| 21 |
Introduction |
| 22 |
|
| 23 |
In an open marketplace, adoption of new technology is driven by |
| 24 |
consumer demand. New technologies that wish to succeed in the |
| 25 |
marketplace must provide new capabilities or reduced costs to gain |
| 26 |
consumer confidence. Internetworking technologies can be |
| 27 |
particularly difficult to deploy and must provide a correspondingly |
| 28 |
high return on investment. In order to determine market viability of |
| 29 |
new internetworking technology, it's necessary to compare the |
| 30 |
required deployment effort against the potential benefits as seen by |
| 31 |
the customer. "Viability in the Marketplace" is an important |
| 32 |
requirement for any IPng candidate and this paper is an attempt to |
| 33 |
summarize some important factors in determing market viability of |
| 34 |
IPng proposals. |
| 35 |
|
| 36 |
"Pushing" Internetworking Technology |
| 37 |
|
| 38 |
It has been asserted by some that the adoption of a single IPng |
| 39 |
protocol by the computing industry would generate general acceptance |
| 40 |
in the networking industry. There is ample evidence to support this |
| 41 |
view; for example, some of the today's more prevalent networking |
| 42 |
protocols gained initial market acceptance through bundling with |
| 43 |
computer operating systems (e.g. IP via UNIX, DECNET via VMS, etc.) |
| 44 |
It should be noted, however, that this approach to technology |
| 45 |
deployment is by no means assured, and some of today's most popular |
| 46 |
internetworking software (Novell, etc.) have thrived despite |
| 47 |
alternatives bundled by computing manufacturers. Given that IPng |
| 48 |
will have to compete against an well established and mature |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Curran [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1669">RFC 1669</a> IPng White Paper on Market Viability August 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
internetworking protocol (IP version 4), promotion of an IPng |
| 58 |
solution by computer system manufacturers should be recognized as |
| 59 |
highly desirable but not sufficient on its own to ensure IPng |
| 60 |
acceptance in the marketplace. |
| 61 |
|
| 62 |
Can IPng compete against IPv4? |
| 63 |
|
| 64 |
Given the large installed base of IPv4 systems, computer system |
| 65 |
manufacturers will need to continue to provide IPv4 capabilities for |
| 66 |
the foreseeable future. With both IPng and IPv4 support in their new |
| 67 |
systems, users will be facing a difficult choice between using IPv4 |
| 68 |
and IPng for internetworking. Existing IPv4 users will migrate to |
| 69 |
IPng for one of three possible reasons: |
| 70 |
|
| 71 |
New functionality not found in IPv4 |
| 72 |
|
| 73 |
IPng needs to provide functionality equivalent to that currently |
| 74 |
provided by IPv4. It remains to be seen whether additional |
| 75 |
functionality (such as resource reservation, mobility, |
| 76 |
autoconfiguration, autoregistration, or security) will be included in |
| 77 |
the base specification of any IPng candidate. In order to provide |
| 78 |
motivation to migrate to IPng, it will be necessary for IPng |
| 79 |
proposals to offer capabilities beyond those already provided IPv4. |
| 80 |
|
| 81 |
Reduced costs by using IPng |
| 82 |
|
| 83 |
It is quite unlikely that migration to IPng will result in cost |
| 84 |
savings in any organization. Migration to IPng will certainly result |
| 85 |
in an increased need for training and engineering, and hence |
| 86 |
increased costs. |
| 87 |
|
| 88 |
To gain connectivity to otherwise unreachable IPng hosts |
| 89 |
|
| 90 |
For existing sites with valid IPv4 network assignments, connectivity |
| 91 |
is not affected until address depletion occurs. Systems with |
| 92 |
globally-unique IPv4 addresses will have complete connectivity to any |
| 93 |
systems since backwards-compatible communication is required of new |
| 94 |
IPng hosts. |
| 95 |
|
| 96 |
From the perspective of an existing IPv4 site, IPng provides little |
| 97 |
tangible benefit until IPv4 address depletion occurs and |
| 98 |
organizations reachable only via IPng appear. Given the absence of |
| 99 |
benefits from migration, it is uncertain whether a significant base |
| 100 |
of IPng sites will be occur prior to IPv4 address depletion. |
| 101 |
|
| 102 |
Sites which are not yet running IP have little motivation to deploy |
| 103 |
IPng for the immediate future. As long as IPv4 network assignments |
| 104 |
are available, new sites have an choice to use IPv4 which provides |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Curran [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1669">RFC 1669</a> IPng White Paper on Market Viability August 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
the sufficient internetworking capabilities (measured in |
| 114 |
functionality, cost, and connectivity) for many organizations today. |
| 115 |
Given the parity in IPng and IPv4 capabilities, IPv4 (as a more |
| 116 |
mature internetworking protocol) is the more probable choice for |
| 117 |
organizations just now selecting an internetworking protocol. |
| 118 |
|
| 119 |
Once IPv4 address assignments are no longer available, sites wishing |
| 120 |
to participate in the global Internet will have a very difficult |
| 121 |
decision in selection of an internetworking protocol. The current |
| 122 |
suite of IPng proposals cannot provide complete internetworking |
| 123 |
between IPng-only sites and IPv4-only sites since (by definition) |
| 124 |
there will be insufficient space to map all IPng addresses into the |
| 125 |
IPv4 address space. As none of the proposals currently call for |
| 126 |
dynamic network address translation (NAT), it is inevitable that |
| 127 |
IPng-only sites will have access to a partial set of IPv4 sites at |
| 128 |
any given moment. |
| 129 |
|
| 130 |
Internetworking services which do not allow complete access to the |
| 131 |
global Internet (IPv4 and IPng in the post-IPv4-address-depletion |
| 132 |
world) are clearly not as valuable as services which offer complete |
| 133 |
Internet access. Sites which are unable to obtain IPv4 network |
| 134 |
assignments will be seeking Internet services which can provide |
| 135 |
complete Internet service. Additionally, some sites will have |
| 136 |
"privately numbered" IPv4 networks and will desire similar Internet |
| 137 |
services which provide transparent access to the entire Internet. The |
| 138 |
development of network address translation devices and subsequent |
| 139 |
services is highly likely under these market conditions. |
| 140 |
|
| 141 |
Summary |
| 142 |
|
| 143 |
No internetworking vendor (whether host, router, or service vendor) |
| 144 |
can afford to deploy and support products and services which are not |
| 145 |
desired in the marketplace. Given the potential proliferation of |
| 146 |
network address translation devices, it is not clear that IPng will |
| 147 |
secure sufficient following to attain market viability. In the past, |
| 148 |
we have seen internetworking protocols fail in the marketplace |
| 149 |
despite vendor deployment and IPng cannot succeed if it is not |
| 150 |
deployed by organizations. As currently envisioned, IPng may not be |
| 151 |
ambitious enough in the delivery of new capabilities to compete |
| 152 |
against IPv4 and the inevitable arrival of network address |
| 153 |
translation devices. In order to meet the requirement for "viability |
| 154 |
in the marketplace', IPng needs to deliver clearly improved |
| 155 |
functionality over IPv4 while offering some form transparent access |
| 156 |
between the IPv4 and IPng communities once IPv4 address depletion has |
| 157 |
occurred. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Curran [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1669">RFC 1669</a> IPng White Paper on Market Viability August 1994</span> |
| 167 |
|
| 168 |
|
| 169 |
Security Considerations |
| 170 |
|
| 171 |
Security issues are not discussed in this memo. |
| 172 |
|
| 173 |
Author's Address |
| 174 |
|
| 175 |
John Curran |
| 176 |
BBN Technology Services, Inc. |
| 177 |
10 Moulton Street |
| 178 |
Cambridge MA 02138 |
| 179 |
|
| 180 |
EMail: [email protected] |
| 181 |
|
| 182 |
|
| 183 |
|
| 184 |
|
| 185 |
|
| 186 |
|
| 187 |
|
| 188 |
|
| 189 |
|
| 190 |
|
| 191 |
|
| 192 |
|
| 193 |
|
| 194 |
|
| 195 |
|
| 196 |
|
| 197 |
|
| 198 |
|
| 199 |
|
| 200 |
|
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 |
|
| 206 |
|
| 207 |
|
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
Curran [Page 4] |
| 221 |
</pre> |