Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-04.txt
Peng Wu <pengwu.thu@gmail.com> Thu, 13 September 2012 09:31 UTC
Return-Path: <pengwu.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8C5621F856F for <dhcwg@ietfa.amsl.com>; Thu, 13 Sep 2012 02:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_111=0.6, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwN7S-EhujsL for <dhcwg@ietfa.amsl.com>; Thu, 13 Sep 2012 02:31:13 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5829D21F8554 for <dhcwg@ietf.org>; Thu, 13 Sep 2012 02:31:13 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so3579095vbb.31 for <dhcwg@ietf.org>; Thu, 13 Sep 2012 02:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=AuWNDfX4WddffDIHajzZS8m9TThiucs41nGRpsi1c0g=; b=IgmE5EVSefknlRNwu6k3RwVgl2Xzdk73UGF7GOzyWJUy4Fnttag/iCL6q9cmsbibI/ IISAeMDKogrSo6f7BrDrBpzjf/lgx7/A1MH3m+47JWe+t3OcXicUETNdLnWQ/y8GIp1M vt3IbuwDHMN2QjrbUCFeEV30wCLPdCJOLGSaZ3fYtZTgz1GvLLCS41JuE0nPmB3gKwRo /eY7wQoPysWjQU/nCNs8kCtQ4TW8LxwraMlUpWX8j97B4pGTY0AWS8pgMxye5YgyoBkq wY7QhKcVqu5PAp23Akbxlvrr1QC50xYIxsZ2sw258BjKqv9d0ZqEW6MDBl8/TrsKhSLw wGBA==
MIME-Version: 1.0
Received: by 10.220.155.3 with SMTP id q3mr910497vcw.11.1347528672496; Thu, 13 Sep 2012 02:31:12 -0700 (PDT)
Received: by 10.58.35.168 with HTTP; Thu, 13 Sep 2012 02:31:12 -0700 (PDT)
In-Reply-To: <20120913085320.22965.11088.idtracker@ietfa.amsl.com>
References: <20120913085320.22965.11088.idtracker@ietfa.amsl.com>
Date: Thu, 13 Sep 2012 17:31:12 +0800
Message-ID: <CAC16W0A9g=nMrRRPBTjkdXX6boZ1D-6QGcxn42L6ZEYeONypFQ@mail.gmail.com>
From: Peng Wu <pengwu.thu@gmail.com>
To: dhc WG <dhcwg@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-04.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: Thu, 13 Sep 2012 09:31:14 -0000
Hi all, This is mainly a "polishing" update of the draft. Most of the technical specifications remains the same as last version. The main updates are: a)substential edits b)Re-structure the contents of choosing between DHCPv4 over IPv6/DHCPv4 over tunnel/DHCPv6 c)Make the usage of relay-encapsulation clear through the document, rather than just reference the draft. Thanks Ted for so many valuable inputs. On Thu, Sep 13, 2012 at4:53 PM, <internet-drafts@ietf.org> wrote: > > 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 IPv6 Transport > Author(s) : Yong Cui > Peng Wu > Jianping Wu > Ted Lemon > Filename : draft-ietf-dhc-dhcpv4-over-ipv6-04.txt > Pages : 14 > Date : 2012-09-13 > > Abstract: > In IPv6 networks, there remains a need to provide IPv4 service for > some residual devices. This document describes a mechanism for > allocating IPv4 addresses to such devices, using DHCPv4 with an IPv6 > transport. It is done by putting a special relay agent function > (Client Relay Agent) on the client side, as well as extending the > behavior of the server; in the case where DHCP server only supports > IPv4 transport, a relay agent is extended to support IPv6 transport > (IPv6-Transport Relay Agent) and relay DHCP traffic for the server, > with a new Relay Agent Information sub-option added to carry the IPv6 > address of the Client Relay Agent. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv4-over-ipv6 > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-ipv6-04 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv4-over-ipv6-04 > > > 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
- [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ip… internet-drafts
- Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-ove… Peng Wu