Last Call: <draft-ietf-dhc-dhcp4o6-saddr-opt-04.txt> (Softwire Provisioning using DHCPv4 Over DHCPv6) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 24 August 2018 17:44 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8379B127333; Fri, 24 Aug 2018 10:44:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dhc-dhcp4o6-saddr-opt-04.txt> (Softwire Provisioning using DHCPv4 Over DHCPv6) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
CC: volz@cisco.com, dhc-chairs@ietf.org, Bernie Volz <volz@cisco.com>, dhcwg@ietf.org, draft-ietf-dhc-dhcp4o6-saddr-opt@ietf.org, suresh@kaloom.com
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-ID: <153513269245.23044.6829646881746864971.idtracker@ietfa.amsl.com>
Date: Fri, 24 Aug 2018 10:44:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UJidP8NlSy3GrmCc8mdbxXxD61Y>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 24 Aug 2018 17:45:02 -0000

The IESG has received a request from the Dynamic Host Configuration WG (dhc)
to consider the following document: - 'Softwire Provisioning using DHCPv4
Over DHCPv6'
  <draft-ietf-dhc-dhcp4o6-saddr-opt-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-09-07. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   DHCPv4 over DHCPv6 (RFC7341) is a mechanism for dynamically
   configuring IPv4 over an IPv6-only network.  For DHCPv4 over DHCPv6
   to function with some IPv4-over-IPv6 softwire mechanisms and
   deployment scenarios, the operator needs to know the IPv6 address
   that the client will use as the source of 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.

   This document updates "DHCPv6 Options for Configuration of Softwire
   Address and Port-Mapped Clients" (RFC7598), allowing OPTION_S46_BR
   (90) to be enumerated in the DHCPv6 client's ORO request and appear
   directly within subsequent messages sent by the DHCPv6 server.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcp4o6-saddr-opt/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcp4o6-saddr-opt/ballot/


No IPR declarations have been submitted directly on this I-D.