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

[c-nsp] Peering + Transit Circuits

Subject: [c-nsp] Peering + Transit Circuits
From: mark.tinka at seacom.mu (Mark Tinka)
Date: Tue, 25 Aug 2015 14:05:47 +0200
In-reply-to: <[email protected]>
References: <CAE_ug143GsMN3+CNz=AgTr+xjGWY2CrmXYW=jf36JQ3AAnukFw@mail.gmail.com> <CAP-guGX2xx4X4jCzOzbVwQzYJLh7NPhdSMJ7qjKV18bTc-7mrg@mail.gmail.com> <[email protected]> <CAE_ug14M_otpVujdEfW5VLr9n0=BzmrVjs1gscw=maY54QK4DQ@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]>


On 25/Aug/15 13:58, Scott Granados wrote:

> If you?re not enabling URPF at the peering routers and edges how do you handle things like RTBH?

D/RTBH still works fine.

S/RTBH would be an issue, but one could enable uRPF temporarily for that.

Mark.

References:
- Peering + Transit Circuits
  - From: tdurack at gmail.com (Tim Durack)
- Peering + Transit Circuits
  - From: bill at herrin.us (William Herrin)
- Peering + Transit Circuits
  - From: patrick at ianai.net (Patrick W. Gilmore)
- Peering + Transit Circuits
  - From: tdurack at gmail.com (Tim Durack)
- [c-nsp] Peering + Transit Circuits
  - From: nick at foobar.org (Nick Hilliard)
- [c-nsp] Peering + Transit Circuits
  - From: mark.tinka at seacom.mu (Mark Tinka)

Prev by Date: [c-nsp] Peering + Transit Circuits
Next by Date: [c-nsp] Peering + Transit Circuits
Previous by thread: [c-nsp] Peering + Transit Circuits
Next by thread: Peering + Transit Circuits
Index(es):
- Date
- Thread