DHCPv6 Redundancy Deployment Considerations
RFC 6853
| Document | Type |
RFC - Best Current Practice
(February 2013; No errata)
Also known as BCP 180
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-jjmb-dhc-dhcpv6-redundancy-consider | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6853 (Best Current Practice) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| IESG note | Ted Lemon (ted.lemon@nominum.com) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) J. Brzozowski
Request for Comments: 6853 Comcast Cable Communications
BCP: 180 J. Tremblay
Category: Best Current Practice Videotron G.P.
ISSN: 2070-1721 J. Chen
Time Warner Cable
T. Mrugalski
ISC
February 2013
DHCPv6 Redundancy Deployment Considerations
Abstract
This document provides information for those wishing to use DHCPv6 to
support their deployment of IPv6. In particular, it discusses the
provision of semi-redundant DHCPv6 services.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6853.
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.
Brzozowski, et al. Best Current Practice [Page 1]
RFC 6853 DHCPv6 Redundancy Considerations February 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Scope and Assumptions . . . . . . . . . . . . . . . . . . . . 2
2.1. Applicability to Prefix Delegation . . . . . . . . . . . . 3
3. Service Provider Deployment . . . . . . . . . . . . . . . . . 3
4. Enterprise Deployment . . . . . . . . . . . . . . . . . . . . 4
5. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 5
5.1. DHCPv6 Servers . . . . . . . . . . . . . . . . . . . . . . 5
5.2. DHCPv6 Relays . . . . . . . . . . . . . . . . . . . . . . 5
5.3. DHCPv6 Clients . . . . . . . . . . . . . . . . . . . . . . 5
6. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Split Prefixes . . . . . . . . . . . . . . . . . . . . . . 6
6.2. Multiple Unique Prefixes . . . . . . . . . . . . . . . . . 8
6.3. Identical Prefixes . . . . . . . . . . . . . . . . . . . . 10
7. Challenges and Issues . . . . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . . 15
1. Introduction
Redundancy and high availability for many components of IPv6
infrastructure are desirable and, in some deployments, mandatory.
Unfortunately, for DHCPv6 there is currently no standards-based
failover or redundancy protocol. An interim solution is to provide
semi-redundant services: this document specifies an architecture by
which this can be achieved.
2. Scope and Assumptions
DHCPv6 redundancy may be useful in a wide range of scenarios.
Although the architecture suggested in this document is able to be
used in a wide range of networks, just two deployment environments
are discussed here: service provider and enterprise network. All
other scenarios may be generalized to one of these two cases.
In the rest of the document, the following assumptions are made with
regards to the existing DHCPv6 infrastructure, regardless of the
environment being considered:
1. At least two DHCPv6 servers provide a service to the same
clients. (The architecture does not limit the number of servers,
and more may be provided if required.)
Brzozowski, et al. Best Current Practice [Page 2]
RFC 6853 DHCPv6 Redundancy Considerations February 2013
Show full document text