[dhcwg] RFC 7031 on DHCPv6 Failover Requirements

rfc-editor@rfc-editor.org Fri, 27 September 2013 21:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A634721F83EF; Fri, 27 Sep 2013 14:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.296
X-Spam-Status: No, score=-102.296 tagged_above=-999 required=5 tests=[AWL=0.304, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id m6YHs6VVzVS1; Fri, 27 Sep 2013 14:44:10 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0EC21F94FF; Fri, 27 Sep 2013 14:43:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6E9E5B1E013; Fri, 27 Sep 2013 14:36:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130927213649.6E9E5B1E013@rfc-editor.org>
Date: Fri, 27 Sep 2013 14:36:49 -0700 (PDT)
Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [dhcwg] RFC 7031 on DHCPv6 Failover Requirements
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2013 21:44:10 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7031

        Title:      DHCPv6 Failover Requirements 
        Author:     T. Mrugalski, K. Kinnear
        Status:     Informational
        Stream:     IETF
        Date:       September 2013
        Mailbox:    tomasz.mrugalski@gmail.com, 
        Pages:      17
        Characters: 39321
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-dhcpv6-failover-requirements-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7031.txt

The DHCPv6 protocol, defined in RFC 3315, allows for multiple servers
to operate on a single network; however, it does not define any way
the servers could share information about currently active clients
and their leases.  Some sites are interested in running multiple
servers in such a way as to provide increased availability in case of
server failure.  In order for this to work reliably, the cooperating
primary and secondary servers must maintain a consistent database of
the lease information.  RFC 3315 allows for, but does not define, any
redundancy or failover mechanisms.  This document outlines
requirements for DHCPv6 failover, enumerates related problems, and
discusses the proposed scope of work to be conducted.  This document
does not define a DHCPv6 failover protocol.

This document is a product of the Dynamic Host Configuration Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC