[dhcwg] Last Call: <draft-ietf-dhc-dhcpv6-failover-protocol-03.txt> (DHCPv6 Failover Protocol) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 05 January 2017 14:33 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AAC612957E; Thu, 5 Jan 2017 06:33:03 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <148362678330.20563.1319130221697532021.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jan 2017 06:33:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/YLPc19CjLhl8rqdeojPIvNskxxE>
Cc: dhc-chairs@ietf.org, dhcwg@ietf.org, volz@cisco.com, draft-ietf-dhc-dhcpv6-failover-protocol@ietf.org
Subject: [dhcwg] Last Call: <draft-ietf-dhc-dhcpv6-failover-protocol-03.txt> (DHCPv6 Failover Protocol) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 05 Jan 2017 14:33:03 -0000

The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'DHCPv6 Failover Protocol'
  <draft-ietf-dhc-dhcpv6-failover-protocol-03.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-01-19. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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).




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-failover-protocol/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-failover-protocol/ballot/


No IPR declarations have been submitted directly on this I-D.