Hello This starts to sound a lot like pathlet routing:
http://www.cs.berkeley.edu/~pbg/pathlet_routing-sigcomm09.pdf There the path address is represented by a forwarding identifier that is locally assigned by the domains through which the path passes. - Hannu >-----Original Message----- >From: rrg-boun...@irtf.org [mailto:rrg-boun...@irtf.org] On >Behalf Of ext Tony Li >Sent: Saturday, June 05, 2010 02:32 >To: Toni Stoev; IRTF RRG >Subject: Re: [rrg] ILNP q1: Scalability > > > > >> But there is one certain point of intersection of addressing, >> forwarding and path selection: >> As clear an address shows a node's topological location, >that much it >> facilitates hop by hop path selection to that node, says: decision >> making for forwarding, sequentially. >> >> So why not just embed next hops in an address: locator? > > >So then the locator is basically a detailed path that has to >change anytime there's a topology change along the path. > >Tony > > >_______________________________________________ >rrg mailing list >rrg@irtf.org >http://www.irtf.org/mailman/listinfo/rrg > _______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
