Re: [lisp] LISP EID Block Size

> -----Original Message-----
> From: lisp-bounces@ietf.org [mailto:lisp-bounces@ietf.org] On Behalf Of Darrel
> Lewis (darlewis)
> Sent: Monday, November 04, 2013 9:45 AM
> To: Sander Steffann
> Cc: LISP mailing list list
> Subject: Re: [lisp] LISP EID Block Size
> 
> 
> On Nov 4, 2013, at 12:36 AM, Sander Steffann <sander@steffann.nl> wrote:
> 
> > Hi,
> >
> >> We see just this (peering) happening between LISP Service Providers in the US
> now.
> >
> > What exactly do you mean with 'peering' in this context?
> 
> If a given PxTR provider is responsible for originating EID prefixes into the DFZ
> on behalf of their subscribers (LISP Mapping and Proxy services customers) want
> to widen their footprint/capacity of transit of Proxy-ITRs, they can agree to
> exchange these EID-prefixes and announce them on each other's behalf.
> 
> So if LISP Mapping/Proxy Provider Foo is originating 172.16.1.0/20 and LISP
> Mapping/Proxy Provider Bar is originating 10.1.1.0/22, and they come to an
> bilateral agreement to share Proxy-ITR capacity they can agree to peer (via, for
> example, eBGP multi-hop) and propagate the prefixes that that the other is
> originating.  Note that the origin AS for these two EID prefixes remains Foo and
> Bar's respectively.
> 
> Today some providers are redistributing registered EID prefixes directly via their
> map-servers, and some are using static routes independent of redistribution for
> origination.  (I prefer the latter, but YMMV.)
[PV] 
Darrel,

I am unaware of any providers in the US doing this.  I would welcome any introductions on your part :) 

Paul

> 
> -Darrel
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp