[dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-pd-relay-requirements-01.txt
internet-drafts@ietf.org Mon, 08 June 2020 16:32 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 966343A0AB9; Mon, 8 Jun 2020 09:32:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: dhcwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dhcwg@ietf.org
Message-ID: <159163392155.1591.14364550477839428172@ietfa.amsl.com>
Date: Mon, 08 Jun 2020 09:32:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/hCiWF1rCOwzqBoD3HovJHZGU6sU>
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-pd-relay-requirements-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2020 16:32:02 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration WG of the IETF. Title : DHCPv6 Prefix Delegating Relay Authors : Ian Farrer Naveen Kottapalli Martin Hunek Richard Patterson Filename : draft-ietf-dhc-dhcpv6-pd-relay-requirements-01.txt Pages : 11 Date : 2020-06-08 Abstract: Operational experience with DHCPv6 prefix delegation (PD) 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 not being routed. 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-pd-relay-requirements/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-pd-relay-requirements-01 https://datatracker.ietf.org/doc/html/draft-ietf-dhc-dhcpv6-pd-relay-requirements-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-pd-relay-requirements-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-pd-rela… internet-drafts
- Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-pd-… ianfarrer