RFC 8987 on DHCPv6 Prefix Delegating Relay Requirements

rfc-editor@rfc-editor.org Mon, 01 March 2021 00:45 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E77D3A10AC; Sun, 28 Feb 2021 16:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level:
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2wAo1Z_yPiO; Sun, 28 Feb 2021 16:45:43 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A74F63A10A7; Sun, 28 Feb 2021 16:45:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AB85CF4074C; Sun, 28 Feb 2021 16:45:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg5ODcgb24gREhDUHY2IFByZWZpeCBEZWxlZ2F0aW5nIFJlbGF5IFJlcXVpcmVtZW50cw==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dhcwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210301004542.AB85CF4074C@rfc-editor.org>
Date: Sun, 28 Feb 2021 16:45:42 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3jC04BzsWsJco_5ctnrMwl_fcGU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2021 00:45:46 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8987

        Title:      DHCPv6 Prefix Delegating Relay Requirements 
        Author:     I. Farrer,
                    N. Kottapalli,
                    M. Hunek,
                    R. Patterson
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2021
        Mailbox:    ian.farrer@telekom.de,
                    nkottapalli@benunets.com,
                    martin.hunek@tul.cz,
                    richard.patterson@sky.uk
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-dhcpv6-pd-relay-requirements-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8987

        DOI:        10.17487/RFC8987

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 using DHCPv6 prefix
delegation with relays ensure that these requirements are followed on
their networks.

This document is a product of the Dynamic Host Configuration Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC