An implementation approach to Source Address Validation
draft-baker-savi-one-implementation-approach-00

Document Type Expired Internet-Draft (individual)
Last updated 2010-05-10
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-baker-savi-one-implementation-approach-00.txt

Abstract

This note is intended to flesh out a comment made on a mailing list. It describes one of many possible implementation approaches to SAVI systems, and is intended as much as anything to be an existence proof that there is at least one that would work. Requirements The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

Authors

Fred Baker (fred@cisco.com)

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