[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bgp convergence problem

Subject: bgp convergence problem
From: mark.tinka at seacom.mu (Mark Tinka)
Date: Thu, 8 May 2014 07:51:13 +0200
In-reply-to: <4473ec67ca154791b977efe46c4d8ef9@BY2PR03MB505.namprd03.prod.outlook.com>
References: <[email protected]> <4473ec67ca154791b977efe46c4d8ef9@BY2PR03MB505.namprd03.prod.outlook.com>

On Wednesday, May 07, 2014 07:28:46 PM Peter Rubenstein 
wrote:

> Operationally speaking, AS1 should not be leaking routes
> from one upstream to the other.  Bad route policy. 
> Also, AS3 should not accept routes from AS1 that don't
> belong to it.  Customer router filtering would prevent
> this.

How I wish this happened in real life.

We are chasing route leaks several AS's down the path that 
are not even remotely connected to us on a weekly basis. But 
I guess that's what they pay us for :-(.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140508/f9c00753/attachment.pgp>

Follow-Ups:
- bgp convergence problem
  - From: morrowc.lists at gmail.com (Christopher Morrow)

References:
- bgp convergence problem
  - From: refresh.lsong at gmail.com (Song Li)
- bgp convergence problem
  - From: peteru at microsoft.com (Peter Rubenstein)

Prev by Date: Does Telus traffic shape their DSL or Fibre subscribers at all?
Next by Date: Getting pretty close to default IPv4 route maximum for 6500/7600 routers.
Previous by thread: bgp convergence problem
Next by thread: bgp convergence problem
Index(es):
- Date
- Thread