[46008] in North American Network Operators' Group
RE: Telco's write best practices for packet switching networks
daemon@ATHENA.MIT.EDU (Daniel Golding)
Thu Mar 7 11:50:41 2002
From: "Daniel Golding" <dgolding@sockeye.com>
To: "Christopher L. Morrow" <chris@UU.NET>,
"Ron da Silva" <ron@aol.net>
Cc: <nanog@merit.edu>
Date: Thu, 7 Mar 2002 11:48:55 -0500
Message-ID: <GKEFKKIKGCMICPKBAEIMMEIHCGAA.dgolding@sockeye.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-reply-to: <Pine.GSO.4.33.0203061626500.3098-100000@rampart.argfrp.us.uu.net>
Errors-To: owner-nanog-outgoing@merit.edu
Well, considering that Ron works for AOL, I would think he's all over "wierd
applications" and "odd protocols" :)
- Daniel Golding
>
>
>
> On Wed, 6 Mar 2002, Ron da Silva wrote:
>
> >
> > On Wed, Mar 06, 2002 at 03:04:00PM +0000, Christopher L. Morrow wrote:
> > >
> > > ...For a backbone filtering is another story entirely. Filtering
> > > backbone equipment for it's protection is also a completely different
> > > topic...
> >
> > Filtering on the backbone is exactly what I mean. Clueful backbone
> > providers should know the ins and outs of their data...
>
> Wow, this is a bold statement... do you deal at all with asymetrically
> routed customers? odd protocols? wierd applications? for any 'large' sized
> provider knowledge of the traffic beyond "its ip" is going to be a very
> difficult task. Even knowledge of address ranges crossing the network is a
> tough task give some customers default all traffic via one provider OUT
> and in through an alternate provider (assymetrical routing).
>
> Really, filtering anything but point incidents isn't a simple task, and at
> times point incidents are a challenge :)
>
