This document discusses redundancy considerations for DHCPv6 and proposes three semi-redundant deployment models: split pools, multiple unique prefixes, and identical prefixes. It assumes multiple DHCPv6 servers provide addresses to the same clients without direct communication between servers. The models either use unique non-overlapping pools/prefixes or overlapping pools/prefixes with preference used to determine which server clients use. No standard redundancy protocol exists for DHCPv6 unlike DHCPv4.