DHCPv6 Prefix Delegating Relay
draft-ietf-dhc-dhcpv6-pd-relay-requirements-02
DHC Work Group I. Farrer
Internet-Draft Deutsche Telekom AG
Intended status: Standards Track Naveen. Kottapalli
Expires: April 10, 2021 Benu Networks
M. Hunek
Technical University of Liberec
R. Patterson
Sky UK Ltd
October 7, 2020
DHCPv6 Prefix Delegating Relay
draft-ietf-dhc-dhcpv6-pd-relay-requirements-02
Abstract
This memo describes operational problems that are known to occur when
using DHCPv6 relays with Prefix Delegation. These problems can
prevent successful delegation and result in routing failures. To
address these problems, this memo provides necessary functional
requirements for operating DHCPv6 relays with Prefix Delegation.
It is recommended that any network operator that is using DHCPv6
prefix delegation with relays should ensure that these requirements
are followed on their networks.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 10, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Farrer, et al. Expires April 10, 2021 [Page 1]
Internet-Draft DHCPv6 PD Relay October 2020
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Topology . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 5
3. Problems Observed with Existing Delegating Relay
Implementations . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. DHCP Messages not being Forwarded by the Delegating Relay 5
3.2. Delegating Relay Loss of State on Reboot . . . . . . . . 6
3.3. Multiple Delegated Prefixes for a Single Client . . . . . 6
3.4. Dropping Messages from Devices with Duplicate MAC
addresses and DUIDs . . . . . . . . . . . . . . . . 6
3.5. Forwarding Loops between Client and Relay . . . . . . . . 6
4. Requirements for Delegating Relays . . . . . . . . . . . . . 7
4.1. General Requirements . . . . . . . . . . . . . . . . . . 7
4.2. Routing Requirements . . . . . . . . . . . . . . . . . . 8
4.3. Service Continuity Requirements . . . . . . . . . . . . . 9
4.4. Operational Requirements . . . . . . . . . . . . . . . . 9
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
For Internet service providers that offer native IPv6 access with
prefix delegation to their customers, a common deployment
architecture is to have a DHCPv6 relay agent function located in the
ISP's Layer-3 customer edge device and separate, centralized DHCPv6
server infrastructure. [RFC8415] describes the functionality of a
Show full document text