[rfc-dist] RFC 8539 on Softwire Provisioning Using DHCPv4 over DHCPv6

rfc-editor@rfc-editor.org Fri, 15 March 2019 23:07 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7499F13130A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 15 Mar 2019 16:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id byNHBK3EPXt9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 15 Mar 2019 16:07:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 799151312CE for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 15 Mar 2019 16:07:27 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D9CD8B826A8; Fri, 15 Mar 2019 16:07:14 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id A698AB826A6; Fri, 15 Mar 2019 16:07:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20190315230713.A698AB826A6@rfc-editor.org>
Date: Fri, 15 Mar 2019 16:07:13 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8539_on_Softwire_Provisioning_Using_DHC?= =?utf-8?q?Pv4_over_DHCPv6?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        RFC 8539

        Title:      Softwire Provisioning Using DHCPv4 over DHCPv6 
        Author:     I. Farrer, 
                    Q. Sun,
                    Y. Cui,
                    L. Sun
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2019
        Mailbox:    ian.farrer@telekom.de, 
        Pages:      18
        Characters: 39504
        Updates:    RFC 7598

        I-D Tag:    draft-ietf-dhc-dhcp4o6-saddr-opt-08.txt

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

        DOI:        10.17487/RFC8539

DHCPv4 over DHCPv6 (RFC 7341) is a mechanism for dynamically
configuring IPv4 for use as an over-the-top service in an IPv6-only
network.  Softwires are an example of such a service.  For DHCPv4
over DHCPv6 (DHCP 4o6) to function with some IPv4-over-IPv6 softwire
mechanisms and deployment scenarios (e.g., RFC 7596 or RFC 7597), the
operator needs to know the IPv6 address that the client will use as
the source of an IPv4-in-IPv6 softwire tunnel.  This address, in
conjunction with the client's IPv4 address, and (in some deployments)
the Port Set ID are used to create a binding table entry in the
operator's softwire tunnel concentrator.  This memo defines a DHCPv6
option to convey IPv6 parameters for establishing the softwire tunnel
and a DHCPv4 option (to be used only with DHCP 4o6) to communicate
the source tunnel IPv6 address between the DHCP 4o6 client and
server.  It is designed to work in conjunction with the IPv4 address
allocation process.

"DHCPv6 Options for Configuration of Softwire Address and Port-Mapped                 
Clients" (RFC 7598) describes a deterministic DHCPv6-based mechanism
for provisioning softwires.  This document updates RFC 7598, allowing
OPTION_S46_BR (90) to be enumerated in the DHCPv6 client's Option
Request Option (ORO) request and to appear directly within subsequent
messages sent by the DHCPv6 server.

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

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

rfc-dist mailing list