[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ocean: do not boil
- To: "Tony Hain" <alh-ietf@tndh.net>
- Subject: RE: ocean: do not boil
- From: Randy Bush <randy@psg.com>
- Date: Tue, 24 Sep 2002 13:22:24 -0700
- Cc: v6ops@ops.ietf.org
- Delivery-date: Tue, 24 Sep 2002 13:23:58 -0700
- Envelope-to: v6ops-data@psg.com
> So all content sites are held hostage until their ISP gets around
> to providing IPv6 service...
nice hyperventilation. but if you'll look at the beginning of this
thread, the basic idea is that we should not try to provide v4<->v6
access to *all* services. in fact, i listed the service(s) which
_must_ be interoperable.
>> a content site is not a 'consumer'. they are provdng a
>> servce. if they want to provide the service, they need
>> things like mains power, the appropriate ip service(s), etc.
> This model precludes any consumer from providing content.
> Specifically it precludes any peer-to-peer applications. I
> realize that many ISPs currently don't like the idea of a
> consumer hosting personal web or mail services, but their
> business practice should not have any impact on the range of
> technology standards we are developing.
no, but nice emotional appeal. those evil isps just won't let good
red-blooded amurikans do anything. we should put them in jail.
it merely says that when you decide to provide a service you must
have the tools to provide it. if you want to provide email
service, you need smtp, not http. if you want folk to access your
server over tv, you need to put it on a tv service. if you want it
on v4, you need to put it on v4. same for v6.
> I can understand the desire to sort and prioritize to manage resource
> constraints, but at the moment I see an abundance of people willing to
> work on the problems.
there is an abundance of people willing to make careers at making a
complex world to try to put marketing whitewash on the fact that it
is still hard to have a merged v4/v6 infrastructure because
o few vendors make the hardware
o there is no motivation to move to v6
it's like the failing sales force going back to engineering for an
endless list of features which they hope will sell the product.
a good recipe for turning a failing sales force into a failing
company.
but this is the engineering department, and our task is to do our
job prudently and properly. we need to make sure that the *basic*
and *critical* things needed to operate v6 in a v4 world can be
done, and done reliably and scalably.
randy