[50638] in North American Network Operators' Group
RE: Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (Phil Rosenthal)
Tue Aug 6 14:44:38 2002
Reply-To: <pr@isprime.com>
From: "Phil Rosenthal" <pr@isprime.com>
To: "'E.B. Dreger'" <eddy+public+spam@noc.everquick.net>,
<nanog@merit.edu>
Date: Tue, 6 Aug 2002 14:44:10 -0400
In-Reply-To: <Pine.LNX.4.20.0208061822210.3196-100000@www.everquick.net>
Errors-To: owner-nanog-outgoing@merit.edu
---
So explain how this is superior to DNS entr(y|ies) stating who your
peers and upstreams are. And there's nothing to say that one could not
specify allowed filters in DNS, too.
If someone wants me to advertise 192.168.7/24, and DNS indicates the
proper netblock is 192.168.0/19 and their ASN is not origin or adjacent
hop, I'll be suspicious. What I do from there becomes a policy
question; I probably would contact the IP block owner to verify the
request.
---
My way isn't superior at all to a secure BGP solution, but until that
exists, I need a choice.
I am definitely on the bandwagon for the need for a secure BGP.
--Phil
