Re: [dhcwg] Call for adoption: draft-mrugalski-softwire-dhcpv4-over-v6-option-01

Sun Qi <sunqi.thu@gmail.com> Thu, 11 October 2012 12:57 UTC

Return-Path: <sunqi.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 B51D821F8779 for <dhcwg@ietfa.amsl.com>; Thu, 11 Oct 2012 05:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level:
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 hHUPCxUSuxK4 for <dhcwg@ietfa.amsl.com>; Thu, 11 Oct 2012 05:57:50 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id F3B2221F8740 for <dhcwg@ietf.org>; Thu, 11 Oct 2012 05:57:49 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id j40so1401026qab.10 for <dhcwg@ietf.org>; Thu, 11 Oct 2012 05:57:49 -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=upOEHRrbD0t3Aamk9Ln84nb4kMqUauW4xI4rzRVD6lw=; b=g820BYSQ4WZjDLdKdBfDiPkP0ymEQDndHW6yQClDEPIxRz7tgZq37Gxr17rip702B6 ZpmfJFiUdbZGdQ32PXGWKpFKjOXlWwHw+pBy/+szFDzD3GOR3Ojmybqh7syYiW+GphKM 8r7SNMCeAVFMYbXSPSYVabrM5hnx8m9Ekop4ma+nOAfcwGl9WQmTpxVCZs6dk5LtUioJ ebsSCNuHwhfRGKWPvb4ekrnd5i/ODI7EY9uj8orRjiW/71lFcRN/FF6Ls7pcUD1y9blb KU8ulnK6AVjSRIo8D0mrRJMk75I5uO4Y2QK1v3MI92KnnYSZDCtRs1MJz4jQyjkGfSlx ocQQ==
MIME-Version: 1.0
Received: by 10.229.206.37 with SMTP id fs37mr316720qcb.65.1349960269408; Thu, 11 Oct 2012 05:57:49 -0700 (PDT)
Received: by 10.49.50.105 with HTTP; Thu, 11 Oct 2012 05:57:49 -0700 (PDT)
In-Reply-To: <2C2153F1-1FF3-4D30-8C7A-52B7AB7F21F0@employees.org>
References: <EDE04BE3-EF07-4CD2-B8D9-D82A570E8C19@nominum.com> <2C2153F1-1FF3-4D30-8C7A-52B7AB7F21F0@employees.org>
Date: Thu, 11 Oct 2012 20:57:49 +0800
Message-ID: <CA+-i+toSv2yUUg+ft4L5=bJBGF8cO9u+bCCoqPmPHci-WdB1Fg@mail.gmail.com>
From: Sun Qi <sunqi.thu@gmail.com>
To: Ole Trøan <otroan@employees.org>
Content-Type: multipart/alternative; boundary="0016369f9c7b51a9f904cbc81e91"
Cc: dhcwg WG <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Call for adoption: draft-mrugalski-softwire-dhcpv4-over-v6-option-01
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, 11 Oct 2012 12:57:50 -0000

Hi Ole,

Here are my opinions.

1) In IPv4-over-IPv6 scenarios, it is needed to allocate IPv4 address to
users in IPv6 access network. DHCPv4 is the right protocol to assign IPv4
address.

2) Using a Client Relay Agent is helpful to avoid modifications of DHCPv4
client, which will cause less change to current network and users.

3) draft-mrugalski-softwire-dhcpv4-over-v6-option describes a DHCPv6 option
that is used to tell the CRA the unicast IPv6 address of TSV/TRA. IMO this
option can make the CRA work better.

Best Regards!
Qi Sun

2012/10/10 Ole Trøan <otroan@employees.org>

> > The authors have requested that the working group adopt
> draft-mrugalski-softwire-dhcpv4-over-v6-option as a working group work
> item.   The document is within the scope of the current charter.   It
> describes a DHCPv6 option that is used to configure client relay agents
> (draft-ietf-dhc-dhcpv4-over-ipv6).
> >
> > If you think the working group should be working on such an option,
> please respond to this message by saying so.   If you think we should not,
> please say that.
>
> I think we should not. including draft-ietf-dhc-dhcpv4-over-ipv6.
>
> a) DHC should wait until it is clear what the outcome of softwire is.
> there are multiple solutions to the same problem proposed.
>     hopefully one will not end up with standardizing all of them. DHCPv4
> over IPv6 is only needed in one of the solution sets.
> b) is this the right solution? if the working group doesn't think solving
> the problem of running DHCPv6 over IPv4 should use a CRA.
>     why is that the correct solution for DHCPv4 over IPv6?
>
> cheers,
> Ole
>  _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>