DHCPv6 Failover Protocol
draft-ietf-dhc-dhcpv6-failover-protocol-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (dhc WG)
|
|
Last updated |
|
2017-01-19
(latest revision 2016-10-13)
|
|
Replaces |
|
draft-ietf-dhc-dhcpv6-failover-design
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Bernie Volz
|
|
Shepherd write-up |
|
Show
(last changed 2016-11-01)
|
| IESG |
IESG state |
|
Waiting for Writeup
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Suresh Krishnan
|
|
Send notices to |
|
"Bernie Volz" <volz@cisco.com>
|
| IANA |
IANA review state |
|
IANA - Not OK
|
|
IANA action state |
|
None
|
Dynamic Host Configuration (DHC) T. Mrugalski
Internet-Draft ISC
Intended status: Standards Track K. Kinnear
Expires: April 16, 2017 Cisco
October 13, 2016
DHCPv6 Failover Protocol
draft-ietf-dhc-dhcpv6-failover-protocol-03
Abstract
DHCPv6 as defined in "Dynamic Host Configuration Protocol for IPv6
(DHCPv6)" (RFC3315) does not offer server redundancy. This document
defines a protocol implementation to provide DHCPv6 failover, a
mechanism for running two servers with the capability for either
server to take over clients' leases in case of server failure or
network partition. It meets the requirements for DHCPv6 failover
detailed in "DHCPv6 Failover Requirements" (RFC7031).
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 16, 2017.
Copyright Notice
Copyright (c) 2016 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
Mrugalski & Kinnear Expires April 16, 2017 [Page 1]
Internet-Draft DHCPv6 Failover Protocol October 2016
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 . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 5
3. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Failover Concepts and Mechanisms . . . . . . . . . . . . . . 8
4.1. Required Server Configuration . . . . . . . . . . . . . . 8
4.2. IPv6 Address and Delegable Prefix Allocation . . . . . . 9
4.2.1. Independent Allocation . . . . . . . . . . . . . . . 9
4.2.2. Proportional Allocation . . . . . . . . . . . . . . . 10
4.3. Lazy Updates . . . . . . . . . . . . . . . . . . . . . . 13
4.4. Maximum Client Lead Time (MCLT) . . . . . . . . . . . . . 13
4.4.1. MCLT example . . . . . . . . . . . . . . . . . . . . 14
5. Message and Option Definitions . . . . . . . . . . . . . . . 16
5.1. Message Framing for TCP . . . . . . . . . . . . . . . . . 16
5.2. Failover Message Format . . . . . . . . . . . . . . . . . 16
5.3. Messages . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.1. BNDUPD . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.2. BNDREPLY . . . . . . . . . . . . . . . . . . . . . . 18
5.3.3. POOLREQ . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.4. POOLRESP . . . . . . . . . . . . . . . . . . . . . . 18
5.3.5. UPDREQ . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.6. UPDREQALL . . . . . . . . . . . . . . . . . . . . . . 18
5.3.7. UPDDONE . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.8. CONNECT . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.9. CONNECTREPLY . . . . . . . . . . . . . . . . . . . . 19
5.3.10. DISCONNECT . . . . . . . . . . . . . . . . . . . . . 19
5.3.11. STATE . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.12. CONTACT . . . . . . . . . . . . . . . . . . . . . . . 19
5.4. Transaction Id . . . . . . . . . . . . . . . . . . . . . 20
5.5. Options . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.5.1. OPTION_F_BINDING_STATUS . . . . . . . . . . . . . . . 20
5.5.2. OPTION_F_CONNECT_FLAGS . . . . . . . . . . . . . . . 21
5.5.3. OPTION_F_DNS_REMOVAL_INFO . . . . . . . . . . . . . . 22
5.5.4. OPTION_F_DNS_HOST_NAME . . . . . . . . . . . . . . . 23
5.5.5. OPTION_F_DNS_ZONE_NAME . . . . . . . . . . . . . . . 23
Show full document text