6man Working Group F. Costa
Internet-Draft J-M. Combes, Ed.
Intended status: Standards Track X. Pougnard
Expires: October 11, 2013 France Telecom Orange
H. Li
Huawei Technologies
April 9, 2013
Duplicate Address Detection Proxy
draft-ietf-6man-dad-proxy-07
Abstract
The document describes a proxy based mechanism allowing the use of
Duplicate Address Detection (DAD) by IPv6 nodes in a point-to-
multipoint architecture with "split-horizon" forwarding scheme,
primarily deployed for Digital Subscriber Line (DSL) and Fiber access
architectures. Based on the DAD signalling, the first hop router
stores in a Binding Table all known IPv6 addresses used on a point-
to-multipoint domain (e.g. VLAN). When a node performs DAD for an
address already used by another node, the first hop router replies
instead of this last one.
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 October 11, 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
Costa, et al. Expires October 11, 2013 [Page 1]
Internet-Draft DAD-Proxy April 2013
(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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Why existing IETF solutions are not sufficient? . . . . . . . 4
3.1. Duplicate Address Detection . . . . . . . . . . . . . . . 5
3.2. Neighbor Discovery Proxy . . . . . . . . . . . . . . . . . 5
3.3. 6LoWPAN Neighbor Discovery . . . . . . . . . . . . . . . . 5
3.4. IPv6 Mobility Manager . . . . . . . . . . . . . . . . . . 6
4. Duplicate Address Detection Proxy (DAD-Proxy)
specifications . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. DAD-Proxy Data structure . . . . . . . . . . . . . . . . . 6
4.2. DAD-Proxy mechanism . . . . . . . . . . . . . . . . . . . 7
4.2.1. No entry exists for the tentative address . . . . . . 7
4.2.2. An entry already exists for the tentative address . . 7
4.2.3. Confirmation of reachability to check the validity
of the conflict . . . . . . . . . . . . . . . . . . . 9
5. Manageability Considerations . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7.1. Interoperability with SEND . . . . . . . . . . . . . . . . 11
7.2. IP source address spoofing protection . . . . . . . . . . 11
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. DAD Proxy state machine . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Costa, et al. Expires October 11, 2013 [Page 2]