[savi] New Version Notification for draft-xu-savi-transition-01.txt
胡光武 <hgw09@mails.tsinghua.edu.cn> Tue, 08 May 2012 15:35 UTC
Return-Path: <hgw09@mails.tsinghua.edu.cn>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC7E21F8620 for <savi@ietfa.amsl.com>; Tue, 8 May 2012 08:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.16
X-Spam-Level:
X-Spam-Status: No, score=0.16 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, J_CHICKENPOX_51=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WuBPhWYd8fUL for <savi@ietfa.amsl.com>; Tue, 8 May 2012 08:35:26 -0700 (PDT)
Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4170821F8617 for <savi@ietf.org>; Tue, 8 May 2012 08:35:24 -0700 (PDT)
Received: from [59.66.207.142] (helo=DaiGuaPC) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from <hgw09@mails.tsinghua.edu.cn>) id 1SRmRc-0005y7-HV for savi@ietf.org; Tue, 08 May 2012 23:35:20 +0800
From: 胡光武 <hgw09@mails.tsinghua.edu.cn>
To: savi@ietf.org
References: <20120508142340.28128.6064.idtracker@ietfa.amsl.com> <201205082244402673085@mail.tsinghua.edu.cn>
In-Reply-To: <201205082244402673085@mail.tsinghua.edu.cn>
Date: Tue, 08 May 2012 23:35:18 +0800
Message-ID: <002101cd2d30$2c36a030$84a3e090$@mails.tsinghua.edu.cn>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0022_01CD2D73.3A5B3FC0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJAvRKsatDJYsjXFoNY2lDfG6YX4ADYE6buldIjTxA=
Content-Language: zh-cn
X-Mailman-Approved-At: Wed, 09 May 2012 08:13:35 -0700
Subject: [savi] New Version Notification for draft-xu-savi-transition-01.txt
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/savi>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 15:35:29 -0000
Hi, buddys, this is our new version draft about adopt SAVI into transition scenarios, please give us feedback if you have any comments. Guangwu Hu >A new version of I-D, draft-xu-savi-transition-01.txt has been successfully submitted by Guangwu Hu and posted to the IETF repository. > >Filename: draft-xu-savi-transition >Revision: 01 >Title: A general SAVI-based source address validation and traceback framework for 4over6 transition scenarios >Creation date: 2012-05-08 >WG ID: Individual Submission >Number of pages: 18 > >Abstract: > Many proposals have been presented for preventing IP spoofing from > occurring in network. An outstanding of them is the SAVI (Source > Address Validation Improvement) proposal which was advocated by IETF > SAVI workgroup for solving this problem from user access switch. SAVI > Working Group is developing standardize mechanisms that prevent nodes > attached to the same IP link from spoofing each other's IP addresses, > and achieve IP source address validation at a finer granularity. > However, up to now, to the best of our knowledge, none of them has > focused on the scenarios of 4over6 transition, that is, IPv4 packets > transit IPv6 network and arrive at other edge IPv4 network(s). With > the boom of IPv6 networks, this issue becomes more and more urgent. > In addition, since 4over6 plans are plenty and various, one solution > cannot meet all requirements of these plans. This document describes > a framework of IP source address validation and traceback for 4over6 > transition scenarios, which extract out the essential and mutual > properties from these plans and form corresponding sub-solution for > each property. When one 4over6 plan is combined by some of them, the > solution of IP source address validation and traceback for this plan > are directly comprised of the combination of corresponding sub- > solution. Thus, the most exciting advantage of this framework is that > it is a once for all solution no matter how 4over6 plans changes. > > > > >The IETF Secretariat >