Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-05.txt

Peng Wu <pengwu.thu@gmail.com> Mon, 17 September 2012 04:48 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 6934421F84CE; Sun, 16 Sep 2012 21:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, 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 C1FOiqxWuAzP; Sun, 16 Sep 2012 21:48:15 -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 2F5A321F845B; Sun, 16 Sep 2012 21:48:15 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so7464296vbb.31 for <multiple recipients>; Sun, 16 Sep 2012 21:48:14 -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 :cc:content-type; bh=d51IyJbzbMd8p4Sny2q4GyVlQ87BMbrQ66zJE12unt8=; b=BTRpBWHhIBjWSLTw7ti87lrA5YWREQj++6gegrKZsTBylJY2JQgU71sVBhUVgf/XJF MBaCM8VmVM4AK3LK4lg+pbOOtwuU4la3O1avxFiqcqmyfnVsCywqu3Bt0Igob7RR+EJp zlMloJiquqNJhDEyilwDczy0I/AcVjLVxnWz9OeyyouQpr9qhwCz32m9bwyi7g/cWKuT owUZ/1ChvK8ynURQfyg/O/OydD3JAzw1znKlxNP1pTofxSORoQPs2hKCuyUQb6qTDG8F O3xJ/qH+7xm5VekArjfkFo7I4Vd3iEsdw0NIN9qmCwEyGS/COxY0pH0xhNkzppZWp+3I Xwiw==
MIME-Version: 1.0
Received: by 10.52.34.162 with SMTP id a2mr1206638vdj.19.1347857294318; Sun, 16 Sep 2012 21:48:14 -0700 (PDT)
Received: by 10.58.35.168 with HTTP; Sun, 16 Sep 2012 21:48:14 -0700 (PDT)
In-Reply-To: <20120917041558.21836.74237.idtracker@ietfa.amsl.com>
References: <20120917041558.21836.74237.idtracker@ietfa.amsl.com>
Date: Mon, 17 Sep 2012 12:48:14 +0800
Message-ID: <CAC16W0DZ+k2ZGJmPOZfQ=Lpx-ZKeCJqPdt0j34EjN0m_AEL9sg@mail.gmail.com>
From: Peng Wu <pengwu.thu@gmail.com>
To: internet-drafts@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Cc: dhcwg@ietf.org, i-d-announce@ietf.org
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-05.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: Mon, 17 Sep 2012 04:48:16 -0000

Hi all,

This version is pretty much identical to the -04 version in content.
Only three, non-technical modifications:
1)adjust the section numbers for the appendix part
2)change the reference on the client-id draft to be Normative
3)remove a redundant sentence on relay encapsulation in section 6.

On Mon, Sep 17, 2012 at 12:15 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-05.txt
>         Pages           : 14
>         Date            : 2012-09-16
>
> 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-05
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv4-over-ipv6-05
>
>
> 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