RFC 5210: A Source Address Validation Architecture (SAVA) Testbed and Deployment Experience
In plain English — editorial summary, not part of the RFC
Because the Internet forwards packets according to the IP destination address, packet forwarding typically takes place without inspection of the source address and malicious attacks have been launched using spoofed source addresses. In an effort to enhance the Internet with IP source address validation, a prototype implementation of the IP Source Address Validation Architecture (SAVA) was created and an evaluation was conducted on an IPv6 network. This document reports on the prototype implementation and the test results, as well as the lessons and insights gained from experimentation. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5210
- Published
- June 2008
- Authors
- J. Wu; J. Bi; X. Li; G. Ren; K. Xu; M. Williams
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5180IPv6 Benchmarking Methodology for Network Interconnect DevicesCurrent
May 2008
- RFC 5172Negotiation for IPv6 Datagram Compression Using IPv6 Control ProtocolCurrent
March 2008
- RFC 5118Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6)Current
February 2008
- RFC 5072IP Version 6 over PPPUpdated
September 2007
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 4980Analysis of Multihoming in Network Mobility SupportCurrent
October 2007
- RFC 5454Dual-Stack Mobile IPv4Current
March 2009
- RFC 5460DHCPv6 Bulk LeasequeryUpdated
February 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?