Keith Moore <[EMAIL PROTECTED]> wrote:
|Neither does it scale to expect all hosts to maintain
|enough information to let them do routing.
On the contrary, distributed host-based routing is one of the few solutions
that does scale well. The availability of resources to deal with the routing
grows directly in proportion to the consumers of those resources. It is
traditional centralized routing that suffers from issues of scale, though
these are variably exaggerated and minimized depending on the case that is
being argued.
Personally I would have liked to see routing confined to the stack and hidden
from applications with portable identifiers or a similar indirection mechanism.
Unfortunately, this would have conflicted with the address allocation business
model as currently envisioned, so the functionality (or, rather, a subset of
the functionality) was percolated up to the application layer. So it goes.
Dan Lanciani
ddl@danlan.*com
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
