datatracker.ietf.org
Sign in
Version 5.13.0, 2015-03-25
Report a bug

SAVI for Mixed Address Assignment Methods Scenario
draft-ietf-savi-mix-07

Document type: Active Internet-Draft (savi WG)
Document stream: IETF
Last updated: 2015-03-08
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: WG Consensus: Waiting for Write-Up
Document shepherd: Jean-Michel Combes

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

SAVI                                                               J. Bi
Internet-Draft                                                    G. Yao
Intended status: Standards Track                          Tsinghua Univ.
Expires: September 9, 2015                                    J. Halpern
                                                               Newbridge
                                                   E. Levy-Abegnoli, Ed.
                                                                   Cisco
                                                           March 8, 2015

           SAVI for Mixed Address Assignment Methods Scenario
                         draft-ietf-savi-mix-07

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 9, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Bi, et al.              Expires September 9, 2015               [Page 1]
Internet-Draft                  SAVI MIX                      March 2015

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Scope . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Recommendations for preventing collisions . . . . . . . . . .   5
   6.  Resolving binding collisions  . . . . . . . . . . . . . . . .   5
     6.1.  Same Address on Different Binding Anchors . . . . . . . .   5
       6.1.1.  Basic preference  . . . . . . . . . . . . . . . . . .   6
       6.1.2.  Overwritten preference  . . . . . . . . . . . . . . .   6
       6.1.3.  Multiple SAVI Device Scenario . . . . . . . . . . . .   7
     6.2.  Same Address on the Same Binding Anchor . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   There are currently several SAVI documents ([RFC6620], [savi-dhcp]
   and [RFC7219]) that describe the different methods by which a switch
   can discover and record bindings between a node's IP address and a
   binding anchor and use that binding to perform source address
   validation.  Each of these documents specifies how to learn on-link
   addresses, based on the method used for their assignment,
   respectively: StateLess Autoconfiguration (SLAAC), Dynamic Host
   Control Protocol (DHCP) and Secure Neighbor Discovery (SeND).  Each
   of these documents describes separately how one particular method
   deals with address collisions (same address, different binding
   anchor).

   While multiple IP assignment methods can be used in the same layer-2
   domain, a SAVI device might have to deal with a mix of SAVI methods.
   The purpose of this document is to provide recommendations to avoid

[include full document text]