Re: [rrg] Locator: routing scalability

[Toni Stoev <[e-mail]>]

On Friday 15 May 2009 05:03:14 Toni Stoev sent:
> > > Does locator have to facilitate routing with its structure?
> > > 
> > > Toni
> > 
> > I have the same answer.
> > Yes it must.
> > With strategy C such that by 90 % a single table-offset (i.e. as by the  
> > locator) retrieves the next hop.
> > 
> > Heiner
> 
> The next hop is a neighbor node. What is the easiest case to retrieve it from locator? Locator containing it.
> So here's next question I have the pleasure to ask our attentive peers:
> Must locator structure show explicit topology/reachability/routability?
> 
> My answer: Let me listen before speak.
> 
> Toni
> 

My opinion is that locator must contain next hops along a path from a root router to a node within a routing domain. Thus locator will be a safe way for a packet en route to its destination, within locator's routing domain.
And especially, being quite relevant to topology, locator will natively provide intra-domain routing scalability.
Furthermore, locator being an intra-domain asset, locator quantity growth will be clearly decoupled from inter-domain routing.

Consider,
Toni Stoev