DHCPv6 Prefix Delegating Relay Requirements
draft-ietf-dhc-dhcpv6-pd-relay-requirements-05

Document Type Active Internet-Draft (dhc WG)
Authors Ian Farrer  , Naveen Kottapalli  , Martin Hunek  , Richard Patterson 
Last updated 2021-01-05 (latest revision 2021-01-04)
Replaces draft-fkhp-dhc-dhcpv6-pd-relay-requirements
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Apr 2020 - WGLC DHCPv6 Prefix D... )
Document shepherd Bernie Volz
Shepherd write-up Show (last changed 2020-11-23)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD √Čric Vyncke
Send notices to Bernie Volz <volz@cisco.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state EDIT
Details
DHC Work Group                                                 I. Farrer
Internet-Draft                                       Deutsche Telekom AG
Intended status: Standards Track                           N. Kottapalli
Expires: 8 July 2021                                       Benu Networks
                                                                M. Hunek
                                         Technical University of Liberec
                                                          R.P. Patterson
                                                              Sky UK Ltd
                                                            January 2021

              DHCPv6 Prefix Delegating Relay Requirements
             draft-ietf-dhc-dhcpv6-pd-relay-requirements-05

Abstract

   This document 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 document 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 5 July 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Farrer, et al.             Expires 8 July 2021                  [Page 1]
Internet-Draft               DHCPv6 PD Relay                January 2021

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   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 . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     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 . . . . . . . .   7
   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  . . . . . . . . . . . . . . . .  10
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

Farrer, et al.             Expires 8 July 2021                  [Page 2]
Internet-Draft               DHCPv6 PD Relay                January 2021

1.  Introduction

   For internet service providers that offer native IPv6 access with
Show full document text