SEND-based Source-Address Validation Implementation
draft-ietf-savi-send-06

The information below is for an old version of the document
Document Type Active Internet-Draft (savi WG)
Last updated 2012-03-08 (latest revision 2011-10-04)
Replaces draft-bagnulo-savi-send
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd Jean-Michel Combes
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SAVI Working Group                                            M. Bagnulo
Internet-Draft                                        A. Garcia-Martinez
Intended status: Standards Track                                    UC3M
Expires: April 6, 2012                                   October 4, 2011

          SEND-based Source-Address Validation Implementation
                        draft-ietf-savi-send-06

Abstract

   This memo describes SEND SAVI, a mechanism to provide source address
   validation using the SEND protocol.  The proposed mechanism is
   intended to complement ingress filtering techniques to provide a
   finer granularity on the control of the source addresses used.

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 April 6, 2012.

Copyright Notice

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

Bagnulo & Garcia-Martinez  Expires April 6, 2012                [Page 1]
Internet-Draft                  SEND SAVI                   October 2011

Table of Contents

   1.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Non-normative Background to SEND SAVI  . . . . . . . . . . . .  4
     3.1.  Address Validation Scope . . . . . . . . . . . . . . . . .  4
     3.2.  Binding Creation for SEND SAVI . . . . . . . . . . . . . .  4
     3.3.  SAVI Logging . . . . . . . . . . . . . . . . . . . . . . .  6
     3.4.  SEND SAVI Protection Perimeter . . . . . . . . . . . . . .  6
   4.  SEND SAVI Specification  . . . . . . . . . . . . . . . . . . .  8
     4.1.  SEND SAVI Data Structures  . . . . . . . . . . . . . . . .  8
     4.2.  SEND SAVI Device Configuration . . . . . . . . . . . . . .  9
     4.3.  Traffic Processing . . . . . . . . . . . . . . . . . . . . 10
       4.3.1.  Transit Traffic Processing . . . . . . . . . . . . . . 10
       4.3.2.  Local Traffic Processing . . . . . . . . . . . . . . . 10
     4.4.  SEND SAVI Port Configuration Guidelines  . . . . . . . . . 22
     4.5.  VLAN Support . . . . . . . . . . . . . . . . . . . . . . . 23
     4.6.  Protocol Constants . . . . . . . . . . . . . . . . . . . . 23
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
     5.1.  Protection Against Replay Attacks  . . . . . . . . . . . . 25
     5.2.  Protection Against Denial of Service Attacks . . . . . . . 26
     5.3.  Security Logging . . . . . . . . . . . . . . . . . . . . . 28
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 28
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 28
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 28
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 29
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29

Bagnulo & Garcia-Martinez  Expires April 6, 2012                [Page 2]
Internet-Draft                  SEND SAVI                   October 2011

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   This memo describes SEND SAVI (SEcure Neighbor Discovery Source-
Show full document text