I'd say static routing for single homed deployments and BGP for dual homed. Anything else only if there's a very specific requirement. Whilst there are other options it doesn't mean you have to use or make all of them available. Keep in mind that someone will have to maintain/support that network. As others already mentioned, simplicity wins and tends to scale better as well.
On 17 June 2015 at 10:15, David Freedman <david.freed...@uk.clara.net> wrote: > also , let's not forget the folk using RFC4577 (OSPFv2) because customer > wants an OSPF network and needs the providers network to participate in the > routing. I have come across some of this stuff , and I would have given it > third place, possibly a tie with the folk using iBGP because they either > can't make the EBGP single as stuff work , or want to preserve AS-internal > BGP attributes (yes, bad , I know). > > > On 17 Jun 2015, at 10:09, Mick O'Donovan <modono...@btireland.net> > wrote: > > > > +1 > > > >> On 17/06/2015 09:37, David Freedman wrote: > >> I think you will find (1) at the top of the list (i.e simplicity taking > the ruling position) shortly followed by 4B , in many cases the provider > will give the customer a private ASN (even the same private ASN) to make > network management simpler. > >> > >> Dave > > > > > >
