hi Roman,
I would propose BGP on CE-PE link, with some BGP community policy. Then the customer would send you community strings which govern local preference and announcements of those prefixes. I made several such policy implementations based on Easynet BGP policy: http://lg.easynet.net/bgppolicy.php This is a very detailed document, and it covers all possible needs for an SP. Typically you only need to implement a part of it. cheers, stan ----- Original Message ----- > From: Roman Hochuli <[email protected]> > To: "[email protected]" <[email protected]> > Cc: > Sent: Friday, November 2, 2012 9:56 AM > Subject: [swinog] routing protocols between isp and customer? > > Hey All > > Quick question: do you allow/run routing protocols between your (isp-) > network and your customer? > If so: which protocols? > If not: what reasons do you tell the customer? > > > In particular I am interested to know about setups when they want to > announce the prefix/subnet you assigned them from your PA-space back to > you because they want to run redundant routers. > > The setup would probably look like this: > > Customer Subnet 10.0.0.0/27 > / \ > | | > [customer router a] - <routing protocol x> - [customer router b] > | | > <routing protocol y> <routing protocol y> > | | > [isp router a] - <routing protocol z> - [isp router b] > | | > \ / > ISP Network 10.0.0.0/8 > > -- > Best regards, > Roman Hochuli > Operations Manager > > nexellent ag > Saegereistrasse 33 > CH-8152 Glattbrugg > > Phone: +41 44 872 20 00 > Fax: +41 44 872 20 01 > URL: www.nexellent.ch > X-NCC-RegID: ch.nexellent > > Imagination is the one weapon in the war > against reality. > -- Jules de Gaultier > > > _______________________________________________ > swinog mailing list > [email protected] > http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog > _______________________________________________ swinog mailing list [email protected] http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
