RFC 1687 (rfc1687) - Page 2 of 13


A Large Corporate User's View of IPng



Alternative Format: Original Text Document



RFC 1687         A Large Corporate User's View of IPng       August 1994


       highlight is that end users actually buy applications -- not
       networking technologies.

   4)  There are really only two compelling reasons for a large end
       user to deploy IPng:

       A) The existence of must-have products which are tightly coupled
           with IPng.
       B) Receipt of a command to deploy IPng from senior management.
          The former would probably be a function of significant
          technological advances.  The latter probably would be a
          function of a convergence of IPng with International
          Standards (OSI).

   5)  Five end user requirements for IPng are presented:

       A) The IPng approach must permit piecemeal transitions.
       B) The IPng approach must not hinder technological advances.
       C) The IPng approach is expected to foster synergy with
          International Standards (OSI).
       D) The IPng approach should have "Plug and Play" networking
          capabilities.
       E) The IPng approach must have network security characteristics
          which are better than existing IPv4 protocols.

Introduction

   The goal of this paper is to examine the implications of IPng from
   the point of view of Fortune 100 corporations which have heavily
   invested in TCP/IP technology in order to achieve their (non-computer
   related) business goals.

   It is our perspective that End Users currently view IPng with
   disfavor.  This note seeks to explain some of the reasons why an end
   user's viewpoint may differ significantly from a "traditional IETF"
   perspective.  It addresses some of the reasons which cause IPng to be
   viewed by end users as a "threat" rather than as an "opportunity".
   It enumerates some existing End User dissatisfactions with IPv4
   (i.e., current TCP/IP network layer).  These dissatisfactions may
   perhaps be eventually exploited to "sell" IPng to users.  Finally, it
   identifies the most compelling reasons for end users to deploy IPng.
   In any case, the IETF community should be warned that their own
   enthusiasm for IPng is generally not shared by end users and that
   convincing end users to deploy IPng technologies may be very
   difficult -- assuming it can be done at all.






Fleischman