[c-nsp] single static ip address for customer(s)

[Gert Doering]

Hi,

On Fri, Jun 22, 2012 at 03:02:58PM +1000, Andrew Jones wrote:
> I think may I deleted the original post(s) in this thread, but has anyone mentioned LISP.
> 
> Seems like a perfect use case for it.

Yay, tunnels, to compensate for lack of routing clue.

(Did I mention we changed one of our upstream providers due to excessive MPLS 
tunneling, combined with excessive lack of clue?)

Anyway.  I don't see why this is supposed to be difficult, unless you're 
dealing with /32- or /64-routes in the order of "50.000 or more".

 - give every router a network block, announce that block as *block* into
   your internal routing (iBGP), do not announce more specifics

 - if that customer ever ends up on a different box, just permit the /32

 - if most of the customers never move to different POPs, and you don't
   have to split routers too often, customer churn will make sure that
   most of your customers will still stick to the "aggregation router"

 - in case you really have to split a router into multiple routers due
   to capacity reason, announce the aggregate from both, announce the
   more specifics to the local "to core" router, limit propagation from
   there.  Yes, somewhat painful for the inital setup, or when you add
   network blocks.  Trivial if properly maintained and documented.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20120622/cbf32b63/attachment.sig>