[458] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: filtering long prefixes

daemon@ATHENA.MIT.EDU (Dave Siegel)
Fri Sep 22 14:28:43 1995

From: Dave Siegel <dsiegel@rtd.com>
To: mark@MainStreet.Net (Mark Kent)
Date: Fri, 22 Sep 1995 10:46:47 -0700 (MST)
Cc: smd%icp.net@MERIT.EDU, smd%sprint.net@MERIT.EDU, markk@internic.net,
        nanog@MERIT.EDU, cidrd@IEPG.ORG
In-Reply-To: <199509211442.HAA14353@mainstreet.net> from "Mark Kent" at Sep 21, 95 07:42:36 am
Resent-From: nanog@MERIT.EDU

> By initially routing long prefixes in 206 you are the ones who have
> created the mess.  So, you made a mistake.  Move on higher up the
> chain and try again.  Cutting off companies retroactively is not the
> answer.  You need to put filters in that cut no one off today,
> but protect against growth tomorrow.

Did the threat of charging for domain names stop people from registering
domain names left and right for no apparent reason?

No.

It seems that the only way for people to pay attention to issues like this is
to have it start affecting them one day.  Then they start paying attention to
the problem, and work to correct it.

Sean is willing to correct connectivity problems on a case by case basis, as
he has mentioned in a number of his messages.  He is willing to accept "cards
and letters" in the form of trouble tickets, and deal with the issues.  I
consider this sufficient.

Dave

-- 
Dave Siegel			President, RTD Systems & Networking, Inc.
(520)318-0696			Systems Consultant -- Unix, LANs, WANs, Cisco
dsiegel@rtd.com			User Tracking & Acctg -- "Written by an ISP, 
http://www.rtd.com/						for an ISP."


home help back first fref pref prev next nref lref last post