Just to be clear, Internap's solution doesn't use "more specifics" to steer traffic. The mechanisms in place to protect yourself from normal route leaking should apply just the same.
--chip On Thu, Nov 5, 2015 at 5:01 AM, Christopher Morrow <[email protected]> wrote: > Also, please, if you use one of this sort of device filter your > prefixes toward your customers/peers/transits... Do not be the next > person to leak their internap-box-routes to the world, m'kay? :) > > On Thu, Nov 5, 2015 at 8:53 PM, Fred Hollis <[email protected]> wrote: > > Hi, > > > > No particular experience with Internaps optimization...however I > wouldn't be > > that sure if I would use it within our networks, because you always have > the > > conflict of this not being their core business as they want to sell their > > optimized IP transit. > > > > However, some time ago we tried Border6 in an evaluation and then finally > > put it into production. Not only the optimization is nice, but the > reporting > > is so extremely detailed making it very transparent where the transit has > > congestion issues and which prefix is routed (in and out) through which > > upstream. > > > > For sure traffic engineering/optimization is not a trivial task but > requires > > deep thinking and understanding of the whole BGP and routing picture. > > > > > > On 05.11.2015 at 09:03 Paras wrote: > >> > >> Does anyone know or have any experience with Internap's route > >> optimization? Is it any good? > >> > >> I've heard of competing solutions as well, such as the one provided by > >> Noction. > >> > >> Thanks for your input, > >> Paras > >> > > > -- Just my $.02, your mileage may vary, batteries not included, etc....
