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

Document Type Active Internet-Draft (savi WG)
Last updated 2016-06-22 (latest revision 2016-05-21)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Jean-Michel Combes
Shepherd write-up Show (last changed 2016-06-12)
IESG IESG state AD Evaluation
Consensus Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to (None)
SAVI                                                               J. Bi
Internet-Draft                                            Tsinghua Univ.
Intended status: Standards Track                                  G. Yao
Expires: November 22, 2016                                         Baidu
                                                              J. Halpern
                                                               Newbridge
                                                   E. Levy-Abegnoli, Ed.
                                                                   Cisco
                                                            May 21, 2016

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

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.

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 November 22, 2016.

Copyright Notice

   Copyright (c) 2016 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

Bi, et al.              Expires November 22, 2016               [Page 1]
Internet-Draft                  SAVI MIX                        May 2016

   publication of this document.  Please review these documents
   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Recommendations for preventing collisions . . . . . . . . . .   5
   6.  Resolving binding collisions  . . . . . . . . . . . . . . . .   6
     6.1.  Same Address on Different Binding Anchors . . . . . . . .   6
       6.1.1.  Basic preference  . . . . . . . . . . . . . . . . . .   6
       6.1.2.  Overwritten preference  . . . . . . . . . . . . . . .   7
       6.1.3.  Multiple SAVI Device Scenario . . . . . . . . . . . .   8
     6.2.  Same Address on the Same Binding Anchor . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   There are currently several Source Address Validaiton Improvement
   (SAVI) documents ([RFC6620], [RFC7513] 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
   technique 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 SAVI method deals with address
   collisions (same address, different binding anchor).
Show full document text