Hey Christian, Long time no see. Hope you are well. I perused your proposal and I was wondering if you could elaborate more on how this achieves the rrg mission of scalability.
While I see how your proposal is attractive to applications developers, how will it re-enable effective aggregation? Not only will sites still want PI addresses to avoid renumbering, but won't networks still wish to announce more specifics for ingress TE purposes? How does your proposal address these concerns? How will the routing table growth get controlled? Dan Jen On Tue, 2009-11-10 at 04:37 -0500, Christian Vogt wrote: > Dear all - > > A few meetings ago, we had an interesting discussion on evolving the > traditional sockets interface towards one that is name-oriented. A > significant part of the research group deemed this idea a candidate > solution to the routing scalability problem, since the resulting > identifier-locator separation would enable multi-homing and reduce the > cost of network renumbering. I would like to point you to a paper that > elaborates on the name-oriented sockets interface, considering the > comments from the discussion we had: > > http://christianvogt.mailup.net/pub/2009/vogt-2009-name-oriented-sockets.pdf > > Your comments are welcome as usual. Although the paper is yet to be > completed, it contains all major aspects of the solution proposed. > > - Christian > > > _______________________________________________ > rrg mailing list > [email protected] > http://www.irtf.org/mailman/listinfo/rrg _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
