Re: [Softwires] Changes to DHCP MAP Option draft

Wojciech Dec <wdec.ietf@gmail.com> Mon, 15 July 2013 18:25 UTC

Return-Path: <wdec.ietf@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA5811E8149 for <softwires@ietfa.amsl.com>; Mon, 15 Jul 2013 11:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.391
X-Spam-Level:
X-Spam-Status: No, score=-2.391 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYmv6FgmXMTA for <softwires@ietfa.amsl.com>; Mon, 15 Jul 2013 11:25:43 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 24B4E11E81BD for <softwires@ietf.org>; Mon, 15 Jul 2013 11:25:40 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id cm16so1788185qab.14 for <softwires@ietf.org>; Mon, 15 Jul 2013 11:25:36 -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=Igr9D+zLTPEy80V/q+tTcSzhyXk1a1mCieaey/SD39U=; b=LgwnubhhBv8DiRUMkerUnCsNfaZt//cdd3PbShuAIDX0ZTadZliDH1MXctNRSeXsZA hIfOwn1hXhhbSpw35eXv9hYBpzeqyUs/epLz/aC5bLM8XJKJpNEhc+p1S6jd6+JF9Vbi 8Fe3x0fWNbPZPmnLVodZxipyEjyNnIkJLe3kmM8heedezNilnYkOK2pmnIohZJTd6uYX Cq+bI4+r3POjIg8eLO24Xg/KTG7Gw8sP4BOevZ2u+SFEPhDOb9ii6P9cXN2Gae0kSxgN u49R7xAgVj6DyDSNs6GOLQ8xvcdzFn7bXfo32SChsgzQsQO0c/5vpdxJxb5JYUOu0Hik niog==
MIME-Version: 1.0
X-Received: by 10.224.90.1 with SMTP id g1mr55577413qam.0.1373912735969; Mon, 15 Jul 2013 11:25:35 -0700 (PDT)
Received: by 10.49.134.2 with HTTP; Mon, 15 Jul 2013 11:25:35 -0700 (PDT)
In-Reply-To: <F2EFABB4-97DF-4D7D-BC5F-32AFF14C8FFC@gmail.com>
References: <CAFFjW4h=CxSRVdOg0M5RR3VzQSWLLo6zSxGtLUXrnZxX1AChNw@mail.gmail.com> <E3FAB1F4F41F3A45B287E8D9C53522FD4730C883@PACDCEXMB05.cable.comcast.com> <CAFFjW4i26QAUYuEVUa2bsT1qkbqNwcY2-w8FRjP9s3CAmgpSWA@mail.gmail.com> <F2EFABB4-97DF-4D7D-BC5F-32AFF14C8FFC@gmail.com>
Date: Mon, 15 Jul 2013 20:25:35 +0200
Message-ID: <CAFFjW4iWSJXp9t9XdkfHoHH=b_qF2=+j4=9AQhz4+SR8MsYJKg@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c2c74894774c04e190fc90"
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Changes to DHCP MAP Option draft
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 18:25:45 -0000

Hi Qi,

the scope  remains unchanged: Define DHCPv6 options for CPEs that a MAP CPE
can use. It so happens that these same options can be used by any A+P CPE,
and I have previously made the case that most of the existing proposals can
use the same scheme of dhcp options: Please see -
http://www.ietf.org/proceedings/84/slides/slides-84-softwire-13.pdf. This
was the document that actually paved for discussion of what then became the
uCPE.
What more, based on the prototype implementations of the options defined in
draft-ietf-map-dhcp-03 we know that they were perfectly capable of
addressing MAP, Lw46, ds-lite, etc, CPEs. The fact that they have changed
is to address the expressed reservations from parties about the options
being "too MAP specific", about flags, naming, etc. I gave the outline of
those changes before publishing, and they were also the subject of
discussion by numerous parties (not just authors) before.

Anyway, for me, the previous "MAP centric" draft was ready for WG last call
(bar a few edits). The changes made in -04 reflect the desire to actually
have a set of options that address common concerns that apply to A+P.
Perhaps you could explain what is the issue in this that needs to be
discussed?

Alternatively, we can proceed to nail any outstanding technical issues and
have the draft sail quickly.

Thanks.
Woj.




On 15 July 2013 19:41, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:

>
> Hi Woj ,
>
> The scope of the document has changed dramatically. I think it necessary
> to get more consensus from the WG to do so. From my reading, it's something
> different from the draft-ietf-softwire-map-dhcp. It's more like a
> 'unified-dhcp'. We need more discussing on this.
>
>
> Best Regards,
> Qi
>
>
> On 2013-7-16, at 上午12:01, Wojciech Dec wrote:
>
> Yes. See Mail of July 8. So far your objection is the only one, although I
> don't quite see in it any technically grounded objection.
> A fair bit of discussions between authors (MAP and lw46), softwire & dhc
> chairs, and WG participants have taken place, and naturally will also be
> held in Berlin.
>
> Re-spinning draft versions is easy.
>
>
> On 15 July 2013 17:29, Lee, Yiu <Yiu_Lee@cable.comcast.com> wrote:
>
>> Since this is a WG draft, did the authors ask the WG to update this? When
>> the WG accepted this draft, it was only for MAP. But seems the scope has
>> been changed. This should start as an Individual draft. I will recommend to
>> revert back to the last version and present this in Berlin to replace the
>> MAP draft if the WG agrees with it.
>>
>>
>> From: Wojciech Dec <wdec.ietf@gmail.com>
>> Date: Thursday, July 11, 2013 10:43 AM
>> To: Qi Sun <sunqi.csnet.thu@gmail.com>
>> Cc: Softwires-wg <softwires@ietf.org>
>> Subject: Re: [Softwires] Changes to DHCP MAP Option draft
>>
>>
>> Yes, there was a long thread started by Tomek. Given that the option is
>> applicable beyond MAP a *suggestion* was to rename it. I'm personally ok
>> either way. The "Softwire46" option is the currently proposed name.
>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
>>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>
>