Re: [RAM] Comment on draft-farinacci-lisp-00.txt (LISP)

[JUAN-JOSE.ADAN at giss.seg-social.es]

Eliot,

Eliot Lear <lear at cisco.com> wrote on 17/04/2007
17:30:11:

> Yakov,
> > What you called "end-end names" are not really "end-end
names" but
> > locators. It just the scope of these locators is not the whole
> > Internet. What you do at the boundaries is mapping of site-wide
> > locators into the ISP locators. 
> >   
> 
> I think this is a great way to look at the engineering problems we
are 
> targeting.  Scope in the case of LISP indicates the appropriate
lookup 
> mechanism.  How that scope is determined is something of an open
> question.  For instance, one could say that an address falls
within the 
> global routing scope if an entry for it exists within the RIB.  One
> could say that an address falls within the global LISP scope (for
lack 
> of better words) if an EID/RLOC mapping can somehow be determined.

I think this is not very different from what I proposed
in the
draft on TIDR, where there are a couple of tables:
the RIB for
"locator prefixes", and the TIB (i.e. the
Tunnel Information Base)
for the "identifier prefixes". It is outside
the interdomain
infrastructure when "identifier prefixes"
become "locator prefixes".

And it is the presence of the LOCATOR attribute what
permits to
say whether a prefix is a "locator prefix"
or an "identifier prefix".

When I first wrote the draft on TIDR I had a couple
of choices:
either to use the LOCATOR attribute to assign locators
to
identifiers, or to use the IDENTIFIERS attribute to
specify
which identifiers can be reached through the locator
specified
in the BGP update. 

In my draft I selected the first choice because I
thought
the LOCATOR attribute provided a smoother deployment.
But
I have been thinking more on this topic and now I
think
that a new IDENTIFIERS attribute would give additional
benefits with regard to the BGP update processing.

I will try to send a note tomorrow explaining this,
to see
if the BGP-based push method that I proposed in the
TIDR
draft could be useful.

Regards,
Juanjo
_______________________________________________
RAM mailing list
RAM at iab.org
https://www1.ietf.org/mailman/listinfo/ram