[nsp] BGP tweaking possibility

[Tim]

I can vouch for the sockeye boxes.  The only thing I did not like about them
was that the fee is service based, and therefore, re-occurring.   This is
understandable as it must cost a fortune to have all those point of presence
DC's tabulating the latency information.

Unfortunately for me, I was only looking for a netflow collector/reporting
tool, so I did not actually decide to go with their service, I simply used
ntop instead.  If the ASP modeled company I work for gets clients in Europe
and Au, then we may actually use the sockeye boxes in the end, after all.

----- Original Message -----
From: "Tuc" <tuc at ttsg.com>
To: "Tony Tauber" <ttauber at genuity.net>
Cc: <cisco-nsp at puck.nether.net>
Sent: Wednesday, July 16, 2003 11:09 AM
Subject: Re: [nsp] BGP tweaking possibility


> > > I've had 2 good suggestions off list so far. One is a commercial
> > > solution (ick) ...and the other I don't fully understand yet so I
> > > have to go do more Cisco reading. The recurring cisco wording from
> > > the other suggestion on and off list is to use "Policies" to do what
> > > I want. /me grabs Cisco dictionaries/URLs to read up on what
> > > policies will do.
> >
> > My understanding of the RouteScience and Sockeye boxes is that they
> > can affect the traffic outbound from you to your provider(s) by
> > adjusting the routes they hear on the basis of some criteria and
> > perhaps bandwidth is one of them.  If the other suggestion is BGP
> > policy propagation, from the use I'm familiar with, it doesn't do what
> > you want.
> >
> I wouldn't have used the Sockeye if it did use policies. That
> would mean it would need to make route_maps or other. Sockeye uses BGP to
> "whisper" more specific paths with next hop information.
>
> Tuc/TTSG Internet Services, Inc.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/