datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Enhanced Duplicate Address Detection
draft-ietf-6man-enhanced-dad-04

Document type: Active Internet-Draft (6man WG)
Document stream: IETF
Last updated: 2013-11-04
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

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

Network Working Group                                           R. Asati
Internet-Draft                                                  H. Singh
Updates: 4862, 4861 (if approved)                              W. Beebee
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: May 08, 2014                                            E. Dart
                                   Lawrence Berkeley National Laboratory
                                                               W. George
                                                       Time Warner Cable
                                                            C. Pignataro
                                                     Cisco Systems, Inc.
                                                       November 04, 2013

                  Enhanced Duplicate Address Detection
                    draft-ietf-6man-enhanced-dad-04

Abstract

   Appendix A of the IPv6 Duplicate Address Detection (DAD) document in
   RFC 4862 discusses Loopback Suppression and DAD.  However, RFC 4862
   does not settle on one specific automated means to detect loopback of
   Neighbor Discovery (ND of RFC 4861) messages used by DAD.  Several
   service provider communities have expressed a need for automated
   detection of looped backed ND messages used by DAD.  This document
   includes mitigation techniques and then outlines the Enhanced DAD
   algorithm to automate detection of looped back IPv6 ND messages used
   by DAD.  For network loopback tests, the Enhanced DAD algorithm
   allows IPv6 to self-heal after a loopback is placed and removed.
   Further, for certain access networks the document automates resolving
   a specific duplicate address conflict.

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 May 08, 2014.

Asati, et al.             Expires May 08, 2014                  [Page 1]
Internet-Draft                Enhanced DAD                 November 2013

Copyright Notice

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

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Operational Mitigation Options  . . . . . . . . . . . . . . .   4
     3.1.  Disable DAD on Interface  . . . . . . . . . . . . . . . .   4
     3.2.  Dynamic Disable/Enable of DAD Using Layer 2 Protocol  . .   5
     3.3.  Operational Considerations  . . . . . . . . . . . . . . .   5
   4.  The Enhanced DAD Algorithm  . . . . . . . . . . . . . . . . .   6
     4.1.  General Rules . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Processing Rules for Senders  . . . . . . . . . . . . . .   7
     4.3.  Processing Rules for Receivers  . . . . . . . . . . . . .   8
     4.4.  Impact on SEND  . . . . . . . . . . . . . . . . . . . . .   8
     4.5.  Changes to RFC 4862 . . . . . . . . . . . . . . . . . . .   8
     4.6.  Changes to RFC 4861 . . . . . . . . . . . . . . . . . . .   9
   5.  Actions to Perform on Detecting a Genuine Duplicate . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Terminology

   o  DAD-failed state - Duplication Address Detection failure as
      specified in [RFC4862].  Failure also includes if the Target

[include full document text]