On 18/Aug/15 15:31, Tim Durack wrote:
Not sure if I really want to get into using DSCP bits for basic IP service
though.
There are use-cases, but they would mostly be internal.
Mark.
On 18/Aug/15 18:02, Tim Durack wrote:
Can I ask why you terminate peering and transit on different routers? (Not
suggesting that is bad, just trying to understand the reason.)
Easier policy enforcement for us.
Lowers the chance of you dealing with traffic in ways you don't intend
(although
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.
On 18/Aug/15 14:29, Tim Durack wrote:
Question: What is the preferred practice for separating peering and transit
circuits?
1. Terminate peering and transit on separate routers.
We do this.
Makes policy enforcement easier.
Mark.
On 18/Aug/15 22:43, Nick Hilliard wrote:
i'd advise being careful with this approach: urpf at ixps is a nightmare.
We don't generally do uRPF at exchange points, for the simple reason
that the router is dedicated (meaning it does not carry a full table),
and peers leaking your routes to the
On 18/08/2015 22:10, William Herrin wrote:
This technique described isn't URPF, it's simple destination routing.
The routes I offer you via BGP are the only routes in my table, hence
the only routes I'm capable of routing. If you send me a packet for a
_destination_ I didn't offer to you, I
On Aug 18, 2015, at 8:47 AM, Gert Doering g...@greenie.muc.de wrote:
XR doesn't do it at all,
hrmph)
We have been asking about this as well, it might be worth revisiting.
- Jared
On Tue, Aug 18, 2015 at 4:43 PM, Nick Hilliard n...@foobar.org wrote:
On 18/08/2015 20:22, Tim Durack wrote:
This has always been my understanding - thanks for confirming. I'm weighing
cost-benefit, and looking to see if there are any other smart ideas. As
usual, it looks like simplest is
Why do I read this thread as “Peering + Transit Circus”
manning
bmann...@karoshi.com
PO Box 6151
Playa del Rey, CA 90296
310.322.8102
On 18August2015Tuesday, at 6:01, Jared Mauch ja...@puck.nether.net wrote:
On Aug 18, 2015, at 8:47 AM, Gert Doering g...@greenie.muc.de wrote:
XR
On 18/08/2015 21:56, Gert Doering wrote:
So how's that stopping one of your bilateral peers from sending you
traffic destined elsewhere?
it doesn't: you detect it and depeer them. If they force the situation
with static routes, the traffic will be dropped.
Nick
On 18/08/2015 20:22, Tim Durack wrote:
This has always been my understanding - thanks for confirming. I'm weighing
cost-benefit, and looking to see if there are any other smart ideas. As
usual, it looks like simplest is best.
i'd advise being careful with this approach: urpf at ixps is a
-- Forwarded message --
From: Tim Durack tdur...@gmail.com
Date: Tue, Aug 18, 2015 at 9:53 AM
Subject: Re: [c-nsp] Peering + Transit Circuits
To: Rolf Hanßen n...@rhanssen.de
Cc: cisco-...@puck.nether.net cisco-...@puck.nether.net
On Tue, Aug 18, 2015 at 9:45 AM, Rolf Hanßen n
On Tue, Aug 18, 2015 at 8:47 AM, Gert Doering g...@greenie.muc.de wrote:
Hi,
On Tue, Aug 18, 2015 at 08:29:31AM -0400, Tim Durack wrote:
4. Don't worry about peers stealing transit.
5. What is peering?
I'm afraid that the majority of answers will be 4./5., mixed with
6. what? how can
On Tue, Aug 18, 2015 at 8:47 AM, Gert Doering g...@greenie.muc.de wrote:
Hi,
(It would be cool if Cisco would understand that hardware forwarding
platforms need useful netflow with MAC-addresses in there... ASR9k at
least got working MAC-accounting, but more fine grained telemetry would
On Tue, Aug 18, 2015 at 9:38 AM, Gert Doering g...@greenie.muc.de wrote:
Hi,
On Tue, Aug 18, 2015 at 09:32:53AM -0400, Tim Durack wrote:
(It would be cool if Cisco would understand that hardware forwarding
platforms need useful netflow with MAC-addresses in there... ASR9k at
[..]
At
On Tue, Aug 18, 2015 at 11:25 AM, Scott Granados sc...@granados-llc.net
wrote:
So in our case we terminate peering and transit on different routers.
Peering routers have well flow enabled (the one that starts with a J that’s
inline). With NFSEN / NFDUMP we’re able to collect that flow data
16 matches
Mail list logo
