[savi] Fwd: New Version Notification for draft-shi-savi-access-01.txt
Zhu Liang <tshbruce@gmail.com> Wed, 09 May 2012 02:22 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 8E6E011E8087 for <savi@ietfa.amsl.com>; Tue, 8 May 2012 19:22:57 -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 UUXmktHV92yD for <savi@ietfa.amsl.com>; Tue, 8 May 2012 19:22:56 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6880811E8074 for <savi@ietf.org>; Tue, 8 May 2012 19:22:53 -0700 (PDT)
Received: by wibhj6 with SMTP id hj6so1166051wib.13 for <savi@ietf.org>; Tue, 08 May 2012 19:22:52 -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=44gKO1yQ7K8WN86X+WtC0zHkbiw+SXme3wzFCvHthf8=; b=AZtpPfGyTYB4XEPP+j4ygcNMRbeuiGfKlZEgcwXuF8aQZ13aU0ROpXuXomZMcvBABg MiBAkAbVa7vzJKNu7Kc7/Iju063UEL2chUSAHZofdpYbgeaIXtWw9ULdfSFt03EMqVtW CHBvObZ74KoI1rN5VLq/LjYxgb9ZkDOj07XGbaQWCFaT1teREmmVaj6xEJezQwhc2qIK o81B8Qea24oa2c2N7ZoD7ht9G59ADl9a6cOZW8X0uaF0RUpIEqURast6qTPSEpu5r+U1 49YTPBJA+7veZZRx/1YfPeXnzPaAuyqmTsuWryvXwVj8KxrbxyFl5kEZIs8mRS+PsDYP uLCA==
MIME-Version: 1.0
Received: by 10.180.84.4 with SMTP id u4mr38102500wiy.2.1336530172466; Tue, 08 May 2012 19:22:52 -0700 (PDT)
Received: by 10.180.88.35 with HTTP; Tue, 8 May 2012 19:22:52 -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:22:52 +0800
Message-ID: <CALp7iBdAHEeswdxuRA854zJ6hQeHP_Ah8FkcHYGamWngatjd+g@mail.gmail.com>
From: Zhu Liang <tshbruce@gmail.com>
To: savi@ietf.org
Content-Type: multipart/alternative; boundary="f46d044303f429578e04bf912e47"
X-Mailman-Approved-At: Wed, 09 May 2012 08:13:35 -0700
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:27:50 -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