R: not rewriting next-hop, pointing default, ...

Enke Chen enkechen at cisco.com
Fri Sep 12 17:29:27 UTC 1997


For ISPs with a lot of direct (i.e., private) peers, on the public 
NAP routers you may want to consider not installing the routes from the
private peers.  This approach could reduce the damage to your private
links by default-pointing attack.  It may also make you less likely
a target due to black-holing of certain traffic. 

This approach is not applicable if transit service is provided at 
the public NAP. 

-- Enke

> Nanog archive
> ----------------------------------------------------------------------
> [Prev][Next][Index][Thread]
> 
> Re: not rewriting next-hop, pointing default, ...
> 
> ----------------------------------------------------------------------
> 
>    * To: dlr at bungi.com (Dave Rand)
>    * Subject: Re: not rewriting next-hop, pointing default, ...
>    * From: Naiming Shen <nshen at mci.net>
>    * Date: Fri, 12 Sep 1997 10:00:23 -0400
>    * cc: Randy Bush <randy at psg.com>, Naiming Shen <nshen at mci.net>,
>      nanog at merit.edu
>    * In-reply-to: Your message of "Thu, 11 Sep 1997 22:02:35 PDT."
>      <m0x9NsK-0000LvC at daver.bungi.com>
>    * Sender: owner-nanog at merit.edu
> 
> ----------------------------------------------------------------------
> 
> Ha, it's amazing how fast people learn when they have to. Yesterday
> someone send us a traceroute:
> 
> % traceroute -g 192.41.177.98 www.mci.net
> ....
>  6  core1-hssi3-0-gw.Washington.mci.net (204.70.1.222)  246 ms 
>   Naiming Shen                                  MCI
> - MCI Internet Engineering                      2100 Reston Parkway
> - +1 703-715-7056 fax:703-715-7066 v272-7056    Reston, VA 20191
> 
> ----------------------------------------------------------------------



More information about the NANOG mailing list