Re: new version of the draft

Scott_Brim@cornell.edu Fri, 18 December 1992 18:06 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08709; 18 Dec 92 13:06 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08703; 18 Dec 92 13:06 EST
Received: from babyoil.ftp.com by CNRI.Reston.VA.US id aa20054; 18 Dec 92 13:08 EST
Received: from MITCHELL.CIT.CORNELL.EDU by ftp.com with SMTP id AA14127; Fri, 18 Dec 92 13:03:40 -0500
Received: from MITCHELL.CIT.CORNELL.EDU by mitchell.cit.cornell.edu (4.1/1.34/Honig-1.3) id AA11139; Fri, 18 Dec 92 13:03:21 EST
Message-Id: <9212181803.AA11139@mitchell.cit.cornell.edu>
To: kasten@ftp.com
Cc: criteria@ftp.com
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Scott_Brim@cornell.edu
Subject: Re: new version of the draft
In-Reply-To: Frank Kastenholz's message of Fri, 18 Dec 1992 09:17:26 -0500. <9212181417.AA04363@ftp.com>
Date: Fri, 18 Dec 1992 13:03:20 -0500
X-Orig-Sender: swb@nr-tech.cit.cornell.edu

Right on (although not totally appropriate for the criteria list).
The commercial providers, at least, will continue to offer translation
service as long as it makes them money, which will be a very long time.
They will offer application-level gateways for even longer, and even
after we run out of globally unique IPv4 addresses, I suspect that the
service providers will support IPv4 between their own customers.  The
force working against balkanization is the introduction of new services
and features which can only be run over a common lower layer.  I believe
there will be plenty of these -- I can't imagine "mail-enabled
videoconferencing" for example(!).

So balkanization isn't a Solution, but translation/encapsulation
services -- the so-called transition period -- will be with us for ages,
and any Solution should include efficient ones.

							Scott