[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [RRG] Long term clean-slate only for the RRG?
> You - or at least Tony - seem to be focusing on Getting It
> Right for the long-term: forever. This surely requires a
> clean-slate approach, with an entirely new routing and
> addressing architecture.
> Perhaps you could start with IPv6 and make radical changes
> along the lines of GSE - but the result would be something
> quite different from IPv6 and would involve major changes to
> host stacks and applications, and I guess to TCP, UDP, SCTP etc.
That was my understanding too (that's why it is called Research Group). I assume it depends on the interpretation of "clean-slate".
> The most substantial solutions to the routing scaling problem
> proposed so far are:
Probably true as technical solution, there are also a set of business solutions possible (e.g., charge for the prefix announcement (-> make disaggregation more costly).
> It would take many years to devise the optimal Clean Slate approach.
> As part of doing so, you would need to incorporate
> transition mechanisms which will enable the majority of
> end-users to be attracted to it - even in the early days when
> few others use the new system - rather than keeping going
> with the IPv4 (or perhaps IPv6) Internet.
It typically takes already today many years until the IETF has produced a protocol specification, so a large amount of time needs to be factored in anyway. The users (not only end-users) are attracted as soon as they see a benefit for the migration cost.
> Then it would take years to create all the new protocols in
> detail, write the software, get it built into existing
> routers and hosts, and to create new or radically re-written
> applications for the new system. (You would need to have a
> plan for motivating application programmers to make such huge
> investments, before many, or any, users used the new system.)
> A Long Term Clean-Slate project would be much more ambitious
> than IPng - which involved minimal changes to host stacks and
> applications compared to what you need to do. 12 or so years
> later, that project has yet to achieve success.
Any project has to achieve success (that is not a matter of short vs. long term).
My experience tells me, that it does not matter whether you do minimal or large changes, since you need to touch equipment anyway. Sometimes minim al changes are even a bigger problem, since they are not that obvious.
to unsubscribe send a message to email@example.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