Network Working Group W. Dec
Internet-Draft Cisco Systems
Intended status: Standards Track T. Mrugalski, Ed.
Expires: August 27, 2012 ISC
T. Sun
China Mobile
B. Sarikaya
Huawei USA
February 24, 2012
DHCPv6 Route Options
draft-ietf-mif-dhcpv6-route-option-04
Abstract
This document describes DHCPv6 Route Options for provisioning IPv6
routes on DHCPv6 client nodes. This is expected to improve the
ability of an operator to configure and influence a nodes' ability to
pick an appropriate route to a destination when this node is multi-
homed and where other means of route configuration may be
impractical.
Requirements Language
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 RFC 2119 [RFC2119].
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 August 27, 2012.
Copyright Notice
Dec, et al. Expires August 27, 2012 [Page 1]
Internet-Draft DHCPv6 Route Options February 2012
Copyright (c) 2012 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Problem overview . . . . . . . . . . . . . . . . . . . . . . . 3
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Use cases . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Raised concerns . . . . . . . . . . . . . . . . . . . . . 9
3.2.1. Vendor-specific option . . . . . . . . . . . . . . . . 9
3.2.2. Unicast RA . . . . . . . . . . . . . . . . . . . . . . 9
3.2.3. DHCPv6 requires client to use one server . . . . . . . 10
3.2.4. Use VLANs . . . . . . . . . . . . . . . . . . . . . . 10
4. DHCPv6 Based Solution . . . . . . . . . . . . . . . . . . . . 11
4.1. Default route configuration . . . . . . . . . . . . . . . 11
4.2. Configuring on-link routes . . . . . . . . . . . . . . . . 11
4.3. Deleting obsolete route . . . . . . . . . . . . . . . . . 11
4.4. Applicability to routers . . . . . . . . . . . . . . . . . 12
4.5. Updating Routing Information . . . . . . . . . . . . . . . 12
4.6. Limitations . . . . . . . . . . . . . . . . . . . . . . . 13
5. DHCPv6 Route Options . . . . . . . . . . . . . . . . . . . . . 13
5.1. Next Hop Option Format . . . . . . . . . . . . . . . . . . 14
5.2. Route Prefix Option Format . . . . . . . . . . . . . . . . 15
6. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 16
7. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 17
7.1. Conflict resolution . . . . . . . . . . . . . . . . . . . 18
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. Contributors and Acknowledgements . . . . . . . . . . . . . . 19
datatracker.ietf.org