Browse Prior Art Database

A Method for Generating Semantically Opaque Interface Identifiers (IIDs) with the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (RFC7943)

IP.com Disclosure Number: IPCOM000247611D
Original Publication Date: 2016-Sep-01
Included in the Prior Art Database: 2016-Sep-20
Document File: 20 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Gont: AUTHOR [+2]

Abstract

The benefits of stable IPv6 addresses are discussed in [RFC7721]. Providing address stability across server reinstallations or when a database of previous DHCPv6 address leases is unavailable is of use not only when a DHCPv6 server must be reinstalled or the address- lease database becomes corrupted, but is also of use when implementation constraints (e.g., a DHCPv6 server implementation on an embedded device) make it impossible for a DHCPv6 server implementation to maintain a database of previous DHCPv6 address leases. Additionally, [RFC7031] describes scenarios where multiple DHCPv6 servers are required to run in such a way as to provide increased availability in case of server failures.

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

Independent Submission                                           F. Gont Request for Comments: 7943                        SI6 Networks / UTN-FRH Category: Informational                                           W. Liu ISSN: 2070-1721                                      Huawei Technologies                                                           September 2016

 A Method for Generating Semantically Opaque Interface Identifiers (IIDs)      with the Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

Abstract

   This document describes a method for selecting IPv6 Interface    Identifiers that can be employed by Dynamic Host Configuration    Protocol for IPv6 (DHCPv6) servers when leasing non-temporary IPv6    addresses to DHCPv6 clients.  This method is a DHCPv6 server-side    algorithm that does not require any updates to the existing DHCPv6    specifications.  The aforementioned method results in stable    addresses within each subnet, even in the presence of multiple DHCPv6    servers or DHCPv6 server reinstallments.  It is a DHCPv6 variant of    the method specified in RFC 7217 for IPv6 Stateless Address    Autoconfiguration.

IESG Note

   A predecessor to this document was earlier a working group document    in the DHC WG.  The WG decided to stop further work in this area    because such work was not considered useful.

   The proposal described in this document has an unaddressed failure    case that makes it unsuitable for use as the mechanism to provide the    claimed failover features for DHCPv6 servers.  Specifically, when a    DHCPv6 client DECLINEs a provided address there is no recovery    mechanism described that will result in the DHCPv6 client obtaining a    working IPv6 address.

 Gont & Liu                    Informational                     [Page 1]
 RFC 7943           Stable and Opaque IIDs with DHCPv6     September 2016

 Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

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

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the ...