- NANOG - lists.nanog.org

mae-east atm vic^h^h^hpeer sought
by Randy Bush 13 Nov '00

13 Nov '00

i am looking for one of our current mae-east fddi peers who wants to play a bit with mae-east atm, has a peermaker account, .... respond to me, not the list, please. thanks. randy

1 0

11/11/00 Internet Routing Problems
by Randy Bush 13 Nov '00

13 Nov '00

could servint (as 7960) please clean up their multi-day ongoing problem so that those of us who use these data detect other problems? thanks. randy From: stats(a)merit.edu Reserved Network and Host Announcements (includes prefixes longer than /27 bits) ---------------------------------------- 195.55.126.144/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.126.144/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.126.144/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.126.176/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.126.176/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.126.176/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.192/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.192/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.192/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.8/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.8/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.8/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.88/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.88/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.127.88/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.14.16/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.14.16/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.14.16/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.14.8/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.14.8/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.14.8/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.141.240/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.141.240/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.141.240/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.15.16/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.15.16/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.15.16/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.15.48/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.15.48/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.15.48/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.128/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.128/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.128/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.160/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.160/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.160/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.168/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.168/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.168/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.176/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.176/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.176/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.192/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.192/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.151.192/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.178.2/32 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.178.2/32 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.178.2/32 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.178.4/32 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.178.4/32 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.178.4/32 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.0/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.0/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.0/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.112/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.112/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.112/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.32/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.32/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.32/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.64/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.64/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.64/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.96/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.96/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.190.96/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.192/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.192/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.192/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.224/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.224/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.224/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.201.248/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 IGP 195.55.201.248/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 IGP 195.55.201.248/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 IGP 195.55.208.0/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.0/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.0/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.64/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.64/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.64/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.72/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.72/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.72/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.208.72/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.120/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.120/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.120/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.128/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.128/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.128/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.160/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.160/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.160/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.160/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.160/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.160/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.64/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.64/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.223.64/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.0/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.0/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.0/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.0/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.32/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.32/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.32/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.32/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.40/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.40/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.40/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.48/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.48/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.224.48/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.225.64/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.225.64/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.225.64/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.225.96/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.225.96/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.225.96/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.0/28 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.0/28 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.0/28 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.128/27 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.128/27 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.128/27 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.16/29 at Mae-East from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.16/29 at Mae-West from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE 195.55.244.16/29 at AADS from Servint (AS7960) ASPATH=7960 6813 12956 3352 INCOMPLETE ***** Too many entries. List Truncated! ***** -30-

3 5

Re: 11/11/00 Internet Routing Problems
by John Fraizer 13 Nov '00

13 Nov '00

Mike, I have worked with your NOC staff before. I draw my personal conclusions from past experience. If the caliber of your people has improved over the past two years, kudos. It isn't apparent from my vantagepoint. By the way, "because" is NOT spelled "becuase." I point this out _because_ you mispelled it not once but, twice in your rebuttal. > Mike Gibbs > Director of Engineering and Operations > ServInt Corp Frightening. --- John Fraizer EnterZone, Inc On Mon, 13 Nov 2000, Mike Gibbs wrote: > On Mon, 13 Nov 2000, John Fraizer wrote: > > > > > On Mon, 13 Nov 2000, Steve Gibbard wrote: > > > > > > > > Doesn't Servint have a NOC? > > > > > > (sorry, couldn't resist) > > > > > > -Steve > > > > They have one listed at puck.nether.net but, that doesn't mean it's > > staffed by clued people. > > > Hey now, lets not attack a group of people becuase you think they might > not know a command on a cisco router, and thus they must not be a good or > clueful NOC. > > Thats like saying, becuase someone doesn't have enable on thier routers, > they don't know how to understand cisco commands. > > > > > > How hard is it to type: > > > > "show ip bgp neighbor N.N.N.N advertised-routes" > > > > ...and verify that you're not leaking crap like that whenever you make a > > change? Isn't that one of the questions on the Clue++ exam? > > > > > > > > > > Mike Gibbs > Director of Engineering and Operations > ServInt Corp >

1 0

RE: ISP recommedation in Washington DC area
by Jason Jin 13 Nov '00

13 Nov '00

Hello, we are currently using UUNET as our ISP. We're looking for a separate T1 for redundency. can somebody suggest some ISP's in Washington D.C area, what's the issue I should looking to before selecting one ISP over another. Any suggestion or pointer to relevent resources will be much appreciated. TIA, . Jason

2 1

Re: MCI WORLDCOM TO PAY $3.5 MILLION
by Sean Donelan 13 Nov '00

13 Nov '00

There are several, off the top of my head Bay Area DDoS Working Group BORG Commercial Internet Exchange Internet Engineering Task Force IOPS IPEG ISP/Consortium Information Technology Association of America North American Network Operators Group Cross-Industry Working Team (XIWT) Being a member of a consortium is different from contributing to or following any recommendation of a consortium. I don't think yet another consortium is the answer. I believe this has fundamentally become a management issue (and their legal advisors). Unless and until the various provider's senior management believe this will substantially affect their business, nothing will happen. For the last five years, I've been in favor of a technical solution. I've changed my position, and believe the Sprint engineers were correct. It is not a technical problem, and the engineers can't fix it. There are three basic methods to make it in their business interest 1) Public pressure 2) Government pressure 3) Legal pressure If Sprint faced a $1 million fine everytime they blackholed someone else's routes, perhaps they would fix their processes. On Mon, 13 November 2000, J Bacher wrote: > On Sun, 12 Nov 2000, Mark Mentovai wrote: > > Is there a consortium of big-time Internet operators? There should be - > Preferably not to the exclusion of all others.

1 0

Re: MCI WORLDCOM TO PAY $3.5 MILLION
by Sean Donelan 13 Nov '00

13 Nov '00

On Sun, 12 November 2000, "Mark Mentovai" wrote: > But these problems were corrected, no? The point I'm trying to make is that > these operators don't make any additional profits by doing the wrong thing > and then fixing it (as they did, unless someone can point to instances in > which brokenness wasn't fixed after it was brought to their attention) than > by doing the right thing from the start (verifying announcements, etc.) > The way I see it, aside from the extra time and "hassle" involved in doing > it right, doing it wrong and doing it right are the same in the bookkeeper's > eyes. After blackholing one of my customer routes for 72 hours, Sprint finally fixed it. The customer believing it was my problem, and the Sprint sales person who mysteriously showed up on the customer's doorsteep following the incident selling how much more reliable buying directly from Sprint would be, decided it would be in their interest to buy from a bigger network such as Sprint. So, yes, they do make more money by disrupting the operations of small ISPs. Do they do it on purpose? I don't believe they are organized enough to do it on purpose. Is it in their interest to fix it? No.

2 1

Re: MCI WORLDCOM TO PAY $3.5 MILLION
by Sean Donelan 13 Nov '00

13 Nov '00

On Sun, 12 November 2000, "Mark Mentovai" wrote: > The drive to "slam" is pushed by dollars. I can't think of any situation in > which someone might profit from announcing address space without > authorization. The problems facing the Internet are mostly due to laziness > and lack of clue, enabled by an experimental infrastructure designed to > support neither of these things. IP assumes non-hostile, non-lazy, and > non-clueless nodes. Sure it is. When I asked why did providers announced addresses improperly, I've been told by both Sprint and UUNET engineers "because they paid us and you don't."

2 1

Re: MCI WORLDCOM TO PAY $3.5 MILLION
by Sean Donelan 13 Nov '00

13 Nov '00

On Sun, 12 November 2000, "Mark Mentovai" wrote: > Failing that - a push from within the community to clean things up - I fear > that governmental intervention is the only solution. I only hope that when > it comes down to regulating the Internet, it will be handled by a new > authority responsible only for inter-network communications. I think that > it would be a mistake to try to tack this responsibility onto the FCC or > FBI. They're not international enough to handle issues fairly, for > starters. I also haven't been impressed with any government agency's > technological prowess. How many folks remember when the FCC's ip address block was blackholed by an customer of Sprint and UUNET for an entire weekend? Even FCC staffer's couldn't get into their own network for 48 hours. I still wonder if the FCC was ever told by Sprint and UUNET the reason why their network was down for the weekend was due to a routing error in their networks, or if they just wrote it off as one of those weird Internet things.

1 0

Re: Defeating DoS Attacks Through Accountability
by Sean Donelan 13 Nov '00

13 Nov '00

On Sun, 12 November 2000, Daniel Senie wrote: > I'm not sure you're being clear. If someone has portable /24 or /16, and > does NOT do their own BGP, but contracts with ONE ISP to do that > advertisement. How do other ISPs know that ISP has permission? We could > point to the RADB, but it's chock full of bogus data. We could point to > ARIN, but their database just says the owner of the net in question is > whomever it is. Those who own that space have a legitimate right to use > that space, so telling them to get ISP-provided space is a non-starter. > > I agree it's a problem in need of a proper solution. The solution has to > account for portable address space not owned by providers. There are several steps involved. I am talking about the very first step. If someone has portable /24 or /16 space, there is a coordinator of record listed in ARIN's, RIPE's or APNIC's database. The first ISP to inject the address into BGP must have proper authorization from the coordinator of record. If we start out with garbage, the rest is irrelevant. We need to get the starting point fixed. The argument "they are paying us, so we do whatever they tell us" is bogus. After we have a good starting point, what do we do about the transitive validation, i.e. how do you know the entire AS path is valid? It should come as no surprise, I think ARIN is messed up. In addition to the coordinator of record and list of in-addr.arpa name servers, I think it should include a routing delegation. Either listing the ASN's directly with the delegation, such as RIPE, or providing a pointer to a third-party routing database of record for the IP address block. But the transitive steps are garbage if the starting point is garbage. As we've seen with the RADB, when anyone can put junk into the database, it gets full of junk. Sean Doran's 0/0 routes are the perfect example. If a complete answer is "hard," can we at least work on getting the first step correct?

1 0

Re: Defeating DoS Attacks Through Accountability
by Mauro Lollo 12 Nov '00

12 Nov '00

If possible, ARIN, or another "authority" should retain more information about the profile of address space, including delegations. As you noted, announcing first and fixing later is like a hit and run, then returning a while later to scrape up the fellow off the road. We just repatriated a portable /24 from a rouge who was using it, supposedly telling his upstream that we had "given them permission"......NOT. I suppose the question is, could a governing body (outside of government), ever keep reasonable control over things without the complete obedience of providers? M. >From: Mark Prior <mrp(a)connect.com.au> >To: Sean Donelan <sean(a)donelan.com> >CC: nanog(a)merit.edu >Subject: Re: Defeating DoS Attacks Through Accountability >Date: Sun, 12 Nov 2000 16:53:27 +1030 > > > But the current practice of announcing first, and only after you kill >some > innocent bystander's network, then fixing it; needs to stop. > > Every IP address should be traceable to an original recorded >delegation. > If the "paperwork" isn't complete or is inaccurate, we should work on >fixing > it. Sticking our heads in the sand, and announcing the network until > someone complains is not good. > >How would you propose to handle the case where an organisation has >their own IP space which isn't currently advertised and then you >receive a request from a third party to route it to them? > >Mark. > _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.

2 1