Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

DHCPv6 Redundancy Deployment Considerations (RFC6853)

IP.com Disclosure Number: IPCOM000225620D
Original Publication Date: 2013-Feb-01
Included in the Prior Art Database: 2013-Feb-21
Document File: 32 page(s) / 34K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Brzozowski: AUTHOR [+4]

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

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