[savi] Last Call: <draft-ietf-savi-mix-12.txt> (SAVI for Mixed Address Assignment Methods Scenario) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 11 November 2016 00:58 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: savi@ietf.org
Delivered-To: savi@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E119129542; Thu, 10 Nov 2016 16:58:59 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <147882593931.19702.320979439293981385.idtracker@ietfa.amsl.com>
Date: Thu, 10 Nov 2016 16:58:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/savi/4InmNLnKkTmVQHR3d6YmDC4qUWQ>
Cc: savi-chairs@ietf.org, draft-ietf-savi-mix@ietf.org, savi@ietf.org, suresh.krishnan@ericsson.com, jeanmichel.combes@orange.com
Subject: [savi] Last Call: <draft-ietf-savi-mix-12.txt> (SAVI for Mixed Address Assignment Methods Scenario) to Proposed Standard
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 11 Nov 2016 00:58:59 -0000

The IESG has received a request from the Source Address Validation
Improvements WG (savi) to consider the following document:
- 'SAVI for Mixed Address Assignment Methods Scenario'
  <draft-ietf-savi-mix-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-11-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   In networks that use multiple techniques for address assignment, the
   appropriate Source Address Validation Improvement (SAVI) methods must
   be used to prevent spoofing of addresses assigned by each such
   technique.  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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-savi-mix/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-savi-mix/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc7039: Source Address Validation Improvement (SAVI) Framework (Informational - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.