Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Deaggregating for emergency purposes

  • From: Phil Rosenthal
  • Date: Mon Aug 05 19:19:32 2002

I had a problem in the past with Telia announcing sub aggregates from my
space, and even after getting in touch with their American NOC, I was
told "you need to contact our NOC in Europe" When doing that, I had
difficulty finding someone who spoke English -- needless to say, it took
a few hours to get that fixed.  Because I hadn't put more specifics in
the IRR, I had no choice but to just sit and deal with NOC employees who
couldn't care less.

You thing trusting another NOC with *YOUR* uptime is a better idea than
taking control?

-----Original Message-----
From: [] On Behalf Of
Richard A Steenbergen
Sent: Monday, August 05, 2002 6:53 PM
To: Phil Rosenthal
Subject: Re: Deaggregating for emergency purposes

On Mon, Aug 05, 2002 at 06:41:22PM -0400, Phil Rosenthal wrote:
> I am currently announcing only my aggregate routes, but I have lately 
> thought about the possibility of someone mistakenly, or maliciously, 
> announcing more specifics from my space. The best solution for an 
> emergency response to that (that I can think of), is registering all 
> of the /24's that make up my network, so if someone should announce a 
> more-specific, I can always announce the most specific that would be 
> accepted (assuming they don't announce the /24's too, it should be a 
> problem avoided)
> Does anyone else have any other ideas on ways to quickly deal with 
> someone else announcing your more specifics, since contacting their 
> NOC is likely going to take a long time...

Seems like a remarkable waste of time and IRR resources. That is why
NOCs exist, so you can contact them quickly and make those announcements

Richard A Steenbergen <>
PGP Key ID: 0x138EA177  (67 29 D7 BC E8 18 3E DA  B2 46 B3 D8 14 36 FE

Discussion Communities

About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home

Merit Network, Inc.