Jeff Wheeler writes:
>On Thu, Dec 15, 2011 at 1:07 AM, Keegan Holley
> wrote:
>> Had in interesting conversation with a transit AS on behalf of a customer
>> where I found out they are using communities to raise the local preference
>
>That sounds like a disreputable practice.
>
>While not quite as
vijay gill writes:
>This is probably going to be a somewhat unpopular opinion, mostly
>because people cannot figure out their COGS. If you can get transit
>for cheaper than your COGS, you are better off buying transit and not
>peering. There are some small arguments to be made for latency and
>'ch
Steven M. Bellovin writes:
>Unless, of course, someone one hop away -- a peer? a customer? an
>upstream or downstream? someone on the same LAN at certain exchange
>points? -- sends you a CLNP packet at link level...
True enough, and mistakenly enabling ISIS on external ports has been
known to ha
Jared Mauch writes:
> No really, the reason for some leaks isn't because so-and-so was
>never a customer, they were. 5 years ago. nobody removed the routes from
>the IRR or AS-SET or and now the route is learned via
>some other location and it's bypassed your perimiter security and
>infi
Robert E. Seastrom writes:
>Not sure what you mean by this, but the painful reality is that most
>stuff, once deployed, gets promptly forgotten about, much the same as
>you might ignore a wall wart power supply under your desk until it
>started smelling funny or stopped delivering electricity. Thu
5 matches
Mail list logo
