SAVI K.Xu, G.Hu, J.Bi, M.Xu
Internet Draft Tsinghua Univ.
Intended status: Standard Tracks F.Shi
Expires: November 2013 China Telecom
May 7, 20133
A General Framework of Source Address Validation and Traceback for
IPv4/IPv6 Transition Scenarios
IP spoofing always is bothering us along with the Internet invention.
With the rapid development of IPv6 next generation Internet, this
issue is more prominent. Though many studies have made their
contributions to the prevention of IP-spoofing, the most excellent
one is the SAVI (Source Address Validation Improvement) proposal
advocated by IETF, since it can prevent IP-spoofing from happening by
automatically binding the key properties of hosts in layer2 access
subnet. Nevertheless, till now, SAVI only focuses on the IPv6 stack
and simple network access scenarios. To the best of our knowledge,
there is no solution even has paid attention to IPv4/IPv6 transition
scenarios. Given the fact that IPv4/IPv6 transition will continue to
be adopted for a long period of time, this issue is becoming
increasingly urgent. However, since transition schemes are plenty and
diverse, hardly can an ordinary solution satisfy all the requirements
of various transition scenarios. In this document, we present an
improved general SAVI-based framework of IP source address validation
and traceback for IPv4/IPv6 transition scenarios. To achieve this
goal, we extract essential and mutual properties from these
transition schemes, and create sub-solutions for each property.
Naturally, if one transition scheme is proposed by combining some
properties, the corresponding sub-solutions would be included into
its IP source address validation and traceback solution. Therefore,
the advantage of this framework is its capability to adapt to all the
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current.
Xu, et al. Expires November 7, 2013 [Page 1]
Internet-Draft SAVI Transition May 2013
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 7, 2013.
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents carefully,
as they describe your rights and restrictions with respect to this
document. Code Components extracted from this document must include
Simplified BSD License text as described in Section 4.e of the Trust
Legal Provisions and are provided without warranty as described in
the Simplified BSD License.
(This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November 10
2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
Table of Contents
1. Introduction ............................................. 3
2. Conventions used in this document ........................ 5
3. Framework description .................................... 5
3.1. Property Extraction ................................... 5
3.2. Solutions of IP source address alidation .............. 7
3.3. Solutions to IP source address traceback ............. 10