Skip to main content

Generic Threats to Routing Protocols
draft-beard-rpsec-routing-threats-01

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Bob Beard
Last updated 2008-04-16 (Latest revision 2003-03-04)
Replaced by RFC 4593
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-rpsec-routing-threats
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Routing protocols are subject to attacks that can harm individual users or the network operations as a whole. The lack of a common set of security requirements has led to the use in existing routing protocol of a variety of different security solutions, which provide various levels of security coverage. The RPSEC working group intends to deliver in a separate document a set of security requirements for consideration of routing protocol designers. The first step in developing the security requirements is to analyze the threats that face routing protocols. This document describes the threats, including threat sources and capabilities, threat actions, and threat consequences as well as a breakdown of routing functions that might be separately attacked.

Authors

Bob Beard

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)