DHCPv6 Prefix Delegating relay
draft-fkhp-dhc-dhcpv6-pd-relay-requirements-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

DHC Work Group                                                 I. Farrer
Internet-Draft                                       Deutsche Telekom AG
Intended status: Standards Track                      Naveen. Kottapalli
Expires: December 27, 2019                                 Benu Networks
                                                                M. Hunek
                                         Technical University of Liberec
                                                      Richard. Patterson
                                                           June 25, 2019

                     DHCPv6 Prefix Delegating relay
             draft-fkhp-dhc-dhcpv6-pd-relay-requirements-00

Abstract

   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.

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 December 27, 2019.

Farrer, et al.          Expires December 27, 2019               [Page 1]
Internet-Draft               DHCPv6 PD relay                   June 2019

Copyright Notice

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

   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 Relays
       Implementations . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  DHCP Messages not being Forwarded by the Delegating relay   5
     3.2.  Delegating Relay Loss of State on Reboot  . . . . . . . .   5
     3.3.  Multiple Simultaneous Delegated Prefixes for a Single
           DUID      on a Single Client  . . . . . . . . . . . . . .   5
     3.4.  Dropping Messages from Devices with Duplicate MAC
           addresses       and DUIDs . . . . . . . . . . . . . . . .   6
   4.  Requirements for Delegating Relays  . . . . . . . . . . . . .   6
     4.1.  General Requirements  . . . . . . . . . . . . . . . . . .   6
     4.2.  Routing Requirements  . . . . . . . . . . . . . . . . . .   7
     4.3.  Service Continuity Requirements . . . . . . . . . . . . .   7
     4.4.  Operational Requirements  . . . . . . . . . . . . . . . .   8
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   For internet service providers that offer native IPv6 access with
   prefix delegation to their customers, a common deployment