DHCPv6 Prefix Delegating relay

Document Type Replaced Internet-Draft (dhc WG)
Authors Ian Farrer  , Naveen Kottapalli  , Martin Hunek  , Richard Patterson 
Last updated 2020-01-24 (latest revision 2019-12-17)
Replaced by RFC 8987
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted by a WG (wg milestone: Jan 2020 - Adopt DHCPv6 Prefix ... )
Document shepherd Tomek Mrugalski
IESG IESG state Replaced by draft-ietf-dhc-dhcpv6-pd-relay-requirements
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Tomek Mrugalski <tomasz.mrugalski@gmail.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Operational experience with DHCPv6 prefix delegation has shown that when the DHCPv6 relay function is not co-located with the DHCPv6 server function, issues such as timer synchronization between the DHCP functional elements, rejection of client's messages by the relay, and other problems have been observed. These problems can result in prefix delegation failing or traffic to/from clients addressed from the delegated prefix being unrouteable. Although [RFC8415] mentions this deployment scenario, it does not provide necessary detail on how the relay element should behave when used with PD. This document describes functional requirements for a DHCPv6 PD relay when used for relaying prefixes delegated by a separate DHCPv6 server.


Ian Farrer (ian.farrer@telekom.de)
Naveen Kottapalli (naveen.sarma@gmail.com)
Martin Hunek (martin.hunek@tul.cz)
Richard Patterson (richard@helix.net.nz)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)