On Jul 25, 2009, Tony Li wrote:
An Internet architecture must be versatile enough to enable
applications
to use their own identifiers. But to do this, the Internet
architecture
itself must incorporate identifiers for only two purposes: to
identify a
peer service for contact establishment, and to identify a session
instantiated during contact establishment. On top of that,
applications
can do what they want, such as providing a means to identify hosts
for
fault finding. Does this make sense?
Well, to me, central to the notion of the Internet architecture and
more
specifically to a routing architecture is the notion of topology. It
would seem somewhat challenging to be able to describe topology
without
being able to describe a graph. And if we want to be able to
describe a
graph, we need to be able to articulate the nodes and edges in that
graph. I don't see how to do this with just service identifiers.
Tony -
This is about identification, not about routing.
For routing, I agree that it would be useful to have locators which
route to a given host -- or better: to a given stack, since this is the
entity through which one must pass to reach a given service or session.
- Christian
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
