From nobody Wed May 13 08:26:27 2015 Return-Path: X-Original-To: savi@ietfa.amsl.com Delivered-To: savi@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B83D1B2C6C; Wed, 13 May 2015 08:26:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yby3ycA-G32k; Wed, 13 May 2015 08:26:24 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AB21B2F47; Wed, 13 May 2015 08:26:15 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.0.2.p3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150513152615.4166.59657.idtracker@ietfa.amsl.com> Date: Wed, 13 May 2015 08:26:15 -0700 Archived-At: Cc: savi@ietf.org Subject: [savi] I-D Action: draft-ietf-savi-mix-08.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.15 List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2015 15:26:25 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : SAVI for Mixed Address Assignment Methods Scenario Authors : Jun Bi Guang Yao Joel M. Halpern Eric Levy-Abegnoli Filename : draft-ietf-savi-mix-08.txt Pages : 9 Date : 2015-05-13 Abstract: In case that multiple IP address assignment methods are allowed in a network, the corresponding SAVI methods should be enabled to prevent spoofing in the network. This document reviews how multiple SAVI methods can coexist in a single SAVI device and collisions are resolved when the same binding entry is discovered by two or more methods. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-savi-mix/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-savi-mix-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-savi-mix-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri May 29 15:03:02 2015 Return-Path: X-Original-To: savi@ietfa.amsl.com Delivered-To: savi@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7201A89AA; Fri, 29 May 2015 15:03:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.912 X-Spam-Level: X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdAhfm_tHqEU; Fri, 29 May 2015 15:02:59 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB841A89A6; Fri, 29 May 2015 15:02:59 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 2DFCE180207; Fri, 29 May 2015 15:00:47 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20150529220047.2DFCE180207@rfc-editor.org> Date: Fri, 29 May 2015 15:00:47 -0700 (PDT) Archived-At: Cc: savi@ietf.org, rfc-editor@rfc-editor.org Subject: [savi] RFC 7513 on Source Address Validation Improvement (SAVI) Solution for DHCP X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 22:03:00 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7513 Title: Source Address Validation Improvement (SAVI) Solution for DHCP Author: J. Bi, J. Wu, G. Yao, F. Baker Status: Standards Track Stream: IETF Date: May 2015 Mailbox: junbi@tsinghua.edu.cn, jianping@cernet.edu.cn, yaoguang@cernet.edu.cn, fred@cisco.com Pages: 54 Characters: 123735 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-savi-dhcp-34.txt URL: https://www.rfc-editor.org/info/rfc7513 DOI: http://dx.doi.org/10.17487/RFC7513 This document specifies the procedure for creating a binding between a DHCPv4/DHCPv6-assigned IP address and a binding anchor on a Source Address Validation Improvement (SAVI) device. The bindings set up by this procedure are used to filter packets with forged source IP addresses. This mechanism complements BCP 38 (RFC 2827) ingress filtering, providing finer-grained source IP address validation. This document is a product of the Source Address Validation Improvements Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC