RFC 7341 on DHCPv4-over-DHCPv6 (DHCP 4o6) Transport
rfc-editor@rfc-editor.org Thu, 14 August 2014 18:39 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1CF1A032A for <ietf-announce@ietfa.amsl.com>; Thu, 14 Aug 2014 11:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level:
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 ONGp7E_raCsn for <ietf-announce@ietfa.amsl.com>; Thu, 14 Aug 2014 11:39:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id BBFBC1A0340 for <ietf-announce@ietf.org>; Thu, 14 Aug 2014 11:39:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0C55A18B538; Thu, 14 Aug 2014 11:37:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7341 on DHCPv4-over-DHCPv6 (DHCP 4o6) Transport
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140814183755.0C55A18B538@rfc-editor.org>
Date: Thu, 14 Aug 2014 11:37:55 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/hVWQCKV5Zb7FlwIUOcasa8QKfRA
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Thu, 14 Aug 2014 18:39:58 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7341
Title: DHCPv4-over-DHCPv6 (DHCP 4o6) Transport
Author: Q. Sun, Y. Cui,
M. Siodelski, S. Krishnan, I. Farrer
Status: Standards Track
Stream: IETF
Date: August 2014
Mailbox: sunqi@csnet1.cs.tsinghua.edu.cn,
yong@csnet1.cs.tsinghua.edu.cn,
msiodelski@gmail.com,
suresh.krishnan@ericsson.com,
ian.farrer@telekom.de
Pages: 16
Characters: 35599
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dhc-dhcpv4-over-dhcpv6-09.txt
URL: https://www.rfc-editor.org/rfc/rfc7341.txt
IPv4 connectivity is still needed as networks migrate towards IPv6.
Users require IPv4 configuration even if the uplink to their service
provider supports IPv6 only. This document describes a mechanism for
obtaining IPv4 configuration information dynamically in IPv6 networks
by carrying DHCPv4 messages over DHCPv6 transport. Two new DHCPv6
messages and two new DHCPv6 options are defined for this purpose.
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/rfc.html
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