The main distinction between our approach and a PKI-based approach is
the concept of triggering alarms as opposed to identifying
the source of problems. In Secure-BGP, a router can verify the
correctness of a single route advertisement by contacting a PKI and a
central authority to test the validity of the signatures embedded in
the advertisement . For example, in Figure 1 (Case(i)),
each AS appends an advertisement with a signature
generated
using its public key. Another AS can use a PKI to check whether
is the correct signature of
. In this case, any
misconfigured/malicious AS propagating an invalid route will not be
able to append the correct signatures of other AS's and can be identified.
Without either of these two infra-structural pieces, a router cannot
verify a single route advertisement in isolation. The Whisper model
is to consider two different route advertisements to the same
destination and check whether they are consistent with each other.
For example, in Figure 1 Case(ii), each route
advertisement is associated with a signature of an AS path. AS
receives two advertisements to destination
and can compare the
signatures
and
to check whether the routes
and
are consistent. When two routes are detected
as inconsistent, the Whisper protocol can determine that at
least one of the routes is invalid. However, it cannot clearly
pinpoint the source of the invalid route. Upon detecting
inconsistencies, the Whisper protocol can trigger alarms
notifying operators about the existence of a problem. This method is
based on the composition of well-known principles of weak
authentication as discussed by Arkko and Nikander [11].
Whisper does not require the underlying Internet topology to have multiple disjoint paths to every destination AS. As long as an adversary propagating an invalid route is not on every path to the destination, whisper will have two routes to check for consistency: (a) the genuine route to the destination; (b) invalid path through the adversary.