[42548] in North American Network Operators' Group
Re: What Worked - What Didn't
daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Sep 17 18:06:15 2001
Date: Mon, 17 Sep 2001 17:54:51 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: Roeland Meyer <rmeyer@mhsc.com>
Cc: "'Randy Bush'" <randy@psg.com>,
Daniel Golding <dgolding@sockeye.com>, nanog@merit.edu
Message-ID: <20010917175451.U11946@puck.nether.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EA9368A5B1010140ADBF534E4D32C728069ED0@condor.mhsc.com>; from rmeyer@mhsc.com on Mon, Sep 17, 2001 at 02:32:56PM -0700
Errors-To: owner-nanog-outgoing@merit.edu
You obviously haven't had cases where a telco cuts or swings
the wrong circuit.
Telco: "We think we've swung it ok"
Me: "Circuit is still up, never took a hit"
Telco: "Hmm."
me (thinking): "I wonder whose circuit they just took down"
with cdp or looking at the path-trace one could take advantage
of these situations with great ease.
- jared
On Mon, Sep 17, 2001 at 02:32:56PM -0700, Roeland Meyer wrote:
>
> |> From: Randy Bush [mailto:randy@psg.com]
> |> Sent: Monday, September 17, 2001 1:45 PM
>
> |> inter-isp peering and intra-isp ibgp to be covered fairly quickly. i
> |> would suggest having one's provisioning folk working with
> |> bgp customers
> |> to close that avenue as well, starting with the more
> |> critical customers.
> |>
> |> also, think about your igp.
>
> Why, IGP shouldn't even be visible from outside the border, neh? Internal
> issues are, internal issues. If it leaks, plug the leak.
--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
