2013
DOI: 10.17487/rfc7031
|View full text |Cite
|
Sign up to set email alerts
|

DHCPv6 Failover Requirements

Abstract: DHCPv6 Failover Requirements AbstractThe 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 th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2016
2016
2021
2021

Publication Types

Select...
2

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 3 publications
0
3
0
Order By: Relevance
“…From the observation, the existing methods work well in a controlled environment (Xi and Cheng-dong, 2017), which is explained in Section 1. In most of the existing methodologies, noise covariance is assumed to be stationary, but it may vary based on the environmental conditions (Mrugalski, 2013). This noise variation factor reduces the accuracy of position estimation.…”
Section: Discussionmentioning
confidence: 99%
“…From the observation, the existing methods work well in a controlled environment (Xi and Cheng-dong, 2017), which is explained in Section 1. In most of the existing methodologies, noise covariance is assumed to be stationary, but it may vary based on the environmental conditions (Mrugalski, 2013). This noise variation factor reduces the accuracy of position estimation.…”
Section: Discussionmentioning
confidence: 99%
“…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 addresslease 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.…”
Section: Introductionmentioning
confidence: 99%
“…The method specified in this document achieves the aforementioned properties by means of a calculated technique as opposed to, e.g., state sharing among DHCPv6 servers. This approach has already been suggested in [RFC7031]. We note that the method described in this document is essentially a DHCPv6 version of the "Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)" specified in [RFC7217].…”
Section: Introductionmentioning
confidence: 99%