[dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv4-over-dhcpv6-02.txt

Qi Sun <sunqi.csnet.thu@gmail.com> Fri, 18 October 2013 16:36 UTC

Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A8A6E11E8271 for <dhcwg@ietfa.amsl.com>; Fri, 18 Oct 2013 09:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id GjQyCKX0Z2GQ for <dhcwg@ietfa.amsl.com>; Fri, 18 Oct 2013 09:36:59 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id D71B511E825D for <dhcwg@ietf.org>; Fri, 18 Oct 2013 09:36:58 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id wz7so3205pbc.38 for <dhcwg@ietf.org>; Fri, 18 Oct 2013 09:36:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=rT71c9p8zyt8dmaAIPz7kBPZtHZf1/N8P6FUNr0IUUs=; b=nOYvpZiSOBbN2EkGmzCQn4chpUTOHZdFE6a6GBXEU6xH3P/xgmmp31wAZgNp+TrhCB HhXiRhg1lClHjqYK+IxugPCsfObYZA/QBQ6mJv2begJdu3khjFQVoaK8eMgwXYZ1K6mN 0MXKpvFnbr5mdnOZX87FnsMqOv7cw4wCoCkN8wswLEXs99eJ8x4J7wsgdIlUU4xIAF12 jCd95eD4Lb/QkwWY6c9uuim4ujlyldcj71f95V/ZpTqRmvnLPDwzWt3wW+soVDNxso/q 2fzV1o0PZMKISA5lrasdZyL0X/lNFKI5kJjnwLGC+OSpWEzWVVO3z+3DzWbqnMf12FwY e00A==
X-Received: by with SMTP id xd5mr3841730pbc.47.1382114218582; Fri, 18 Oct 2013 09:36:58 -0700 (PDT)
Received: from [] ([]) by mx.google.com with ESMTPSA id py4sm3367175pbb.33.2013. for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Oct 2013 09:36:57 -0700 (PDT)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-11-79937785
Date: Sat, 19 Oct 2013 00:34:23 +0800
References: <20131018161735.4087.55554.idtracker@ietfa.amsl.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Message-Id: <79CAAE76-FCDC-49D2-A079-2E753D1B9E51@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Subject: [dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv4-over-dhcpv6-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 18 Oct 2013 16:36:59 -0000

Dear all, 

We have submitted a new version of draft-ietf-dhc-dhcpv4-over-dhcpv6 to address the issues raised during/after the Berlin meeting.

1) Update the format of the two newly defined DHCPv6 messages with a 'flag' field.
1) Define a Unicast Flag to indicate the wrapped DHCPv4 message should be unicast or broadcast as in IPv4 environment.
2) Polish the text & correct a couple of nits

Please can you review the draft. Comments are always welcome. 


Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: 2013年10月19日 上午12时17分35秒格林尼治标准时间+0800
> To: i-d-announce@ietf.org
> Cc: dhcwg@ietf.org
> Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-dhcpv6-02.txt
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.
> 	Title           : DHCPv4 over DHCPv6 Transport
> 	Author(s)       : Qi Sun
>                          Yong Cui
>                          Marcin Siodelski
>                          Suresh Krishnan
>                          Ian Farrer
> 	Filename        : draft-ietf-dhc-dhcpv4-over-dhcpv6-02.txt
> 	Pages           : 13
> 	Date            : 2013-10-18
> Abstract:
>   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 as well as a new DHCPv6 option are defined for the purpose
>   of conveying DHCPv4 messages through IPv6 networks.
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv4-over-dhcpv6
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-02
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv4-over-dhcpv6-02
> 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 mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg