SAVI Requirements and Solutions for ISP IPv6 Access Network
draft-shi-savi-access-11

Document Type Expired Internet-Draft (individual)
Last updated 2017-11-17 (latest revision 2017-05-16)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-shi-savi-access-11.txt

Abstract

Internet is always confronted with many security threats based on IP address spoofing which can enable impersonation and malicious traffic redirection. Unfortunately, the Internet architecture fails to provide the defense mechanism. Source Address Validation Improvement (SAVI) was developed to prevent IP source address spoofing. Especially, the mechanism is essential for ISPs. However, due to the diversity of address assignment methods, SAVI solution is also different accordingly. This document describes five scenarios of ISPs'IPv6 access network, and moreover, states its SAVI requirements and tentative solutions accordingly.

Authors

Fan Shi (shifan@ctbri.com.cn)
DENG Hui (xuke@mail.tsinghua.edu.cn)
Liang Zhu (tshbruce@gmail.com)
Guangwu Hu (hgw09@mails.tsinghua.edu.cn)

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