[savi] Fwd: New Version Notification for draft-shi-savi-access-01.txt
Zhu Liang <tshbruce@gmail.com> Wed, 09 May 2012 02:43 UTC
Return-Path: <tshbruce@gmail.com>
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 D546E21F85AF for <savi@ietfa.amsl.com>; Tue, 8 May 2012 19:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 P2U6gNwaRc9g for <savi@ietfa.amsl.com>; Tue, 8 May 2012 19:43:57 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 23A3021F85AE for <savi@ietf.org>; Tue, 8 May 2012 19:43:56 -0700 (PDT)
Received: by wibhn19 with SMTP id hn19so717719wib.13 for <savi@ietf.org>; Tue, 08 May 2012 19:43:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lH+vzta4EaehbLMxwJ5/RfhLtuOfjVyA7cd8hVaj6zc=; b=Ut2ok//wRx7glaJxRlwZcULA6sQS/9Ul3DukBLgzmDF0amNH0YWwR7J0mi0SEI7NKb dsMqaJtB2p1uuq28g3yQGNcKIgezqIiIkgYKtnAssE14S5cwx9V694P3Q4dR1ZOun6iX KtK0lxP1Mvjk/iMVex7VsgRXM0oZgxC+mj4IwdDNUk687Cs8HLuQpPhJEwcX8vB6Hf91 oEosaYiFO6x8R2NxvASIiQG0hulgFNWNllTJJUoYUXi0yTwLXGVAweMhRSvBCMVYzqVR zFb00eQ+/Au8DedqZIxkAzhYFb/d0p7fvp2O5J+BMN81EBUrZYI2X2gUI6L0L2JuLE5s jIuA==
MIME-Version: 1.0
Received: by 10.216.203.80 with SMTP id e58mr4200391weo.41.1336531436291; Tue, 08 May 2012 19:43:56 -0700 (PDT)
Received: by 10.180.88.35 with HTTP; Tue, 8 May 2012 19:43:56 -0700 (PDT)
In-Reply-To: <20120509014857.11692.55734.idtracker@ietfa.amsl.com>
References: <20120509014857.11692.55734.idtracker@ietfa.amsl.com>
Date: Wed, 09 May 2012 10:43:56 +0800
Message-ID: <CALp7iBch_P18cFCq5JXUruyw9TrLKKGBrYk7Hhi8ua=YHc=TFw@mail.gmail.com>
From: Zhu Liang <tshbruce@gmail.com>
To: savi@ietf.org
Content-Type: multipart/alternative; boundary="0016e6d7848a7dc74704bf91794a"
Subject: [savi] Fwd: New Version Notification for draft-shi-savi-access-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: Wed, 09 May 2012 02:43:58 -0000
---------- Forwarded message ---------- From: <internet-drafts@ietf.org> Date: 2012/5/9 Subject: New Version Notification for draft-shi-savi-access-01.txt To: tshbruce@gmail.com Cc: shifan@ctbri.com.cn, hgw09@mails.tsinghua.edu.cn, xuke@mail.tsinghua.edu.cn A new version of I-D, draft-shi-savi-access-01.txt has been successfully submitted by Liang Zhu and posted to the IETF repository. Filename: draft-shi-savi-access Revision: 01 Title: SAVI Requirements and Solutions for ISP IPv6 Access Network Creation date: 2012-05-09 WG ID: Individual Submission Number of pages: 14 Abstract: An Internet Service Provider (ISP) is always confronted with many security threats based on IP address spoofing. Unfortunately, the Internet architecture fails to provide the defense mechanism. Source Address Validation Improvement (SAVI) was developed to prevent IP source address spoofing which can enable impersonation and malicious traffic redirection. Thus, 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. The IETF Secretariat