[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RRG] On deployability



Tony,

> One of the issues that came up today was that of incremental
> deployability.  Many people felt that incremental deployability is an
> absolute hard and fast requirement.
>
> My question: suppose that we had a solution that was a
> ships-in-the-night deployment?  Would that suffice?  Just as we are
> rolling out IPv6 in parallel with IPv4, would it be sensible to roll
> out IPv6+ in parallel with v6 and v4?  Assume that some form of
> tunneling could be used to bridge islands of connectivity.

There's a lot of detail behind the word "deployability"...

There's the question of needing some other node to change because
you want to achieve something. That's why we are talking about network
based approaches where the routing pain and deployment opportunity
coincide.

It also relates to the question of needing your peer to upgrade
before you get any of the benefits.

Then there's the question of needing to change many software
components in your box. For instance, not enough to upgrade your
OS but also have to upgrade the applications.

And the question of what infrastructure (DHT etc) needs to be
in place.

But to answer your IPv6+ question, we'd have to know what "+"
means. From the first item above I think it follows that
hosts will not change. So this probably means that its plain
old IPv6 to the hosts. Hence, we're essentially talking about
fancy new routing and identifier schemes within the network.
That might not need to have anything to do with IPv6 per
se (as LISP has shown). But there are a lot of possible
designs, so my conclusions may not hold for new ideas
that we have not seen yet.

Research questions aside, I'm not personally convinced
that it is worthwhile to design architectures that would
require applications to use new APIs. At least not before
we have exhausted other alternatives.

Jari


--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg