Re: [Softwires] [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6

<mohamed.boucadair@orange.com> Mon, 15 April 2013 15:13 UTC

Return-Path: <mohamed.boucadair@orange.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 EF32921F9027; Mon, 15 Apr 2013 08:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[AWL=0.354, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=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 ixigbBimPcUb; Mon, 15 Apr 2013 08:13:59 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id ECDC921F9339; Mon, 15 Apr 2013 08:13:58 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 452C826413E; Mon, 15 Apr 2013 17:13:58 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 2089535C061; Mon, 15 Apr 2013 17:13:58 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Mon, 15 Apr 2013 17:13:57 +0200
From: mohamed.boucadair@orange.com
To: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, "Ted.Lemon@nominum.com" <Ted.Lemon@nominum.com>
Date: Mon, 15 Apr 2013 17:13:57 +0200
Thread-Topic: [Softwires] [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6
Thread-Index: Ac456UpaXm149FUSRWyBTyyXxBXHqQAAPU8A
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC2D7C6B8@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EC2D7C673@PUEXCB1B.nanterre.francetelecom.fr> <CD91E01D.64AFF%ian.farrer@telekom.de>
In-Reply-To: <CD91E01D.64AFF%ian.farrer@telekom.de>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
Cc: "softwires@ietf.org" <softwires@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "sunqi.thu@gmail.com" <sunqi.thu@gmail.com>
Subject: Re: [Softwires] [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6
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 Apr 2013 15:14:00 -0000

Hi Ian,

Thanks for the clarification.
I understood from your answer: dhcpv6 will be used for both MAP and lw4over6 and both don't require draft-scskf-* for IP address + port provisioning.

Given currently no additional dhcpv4 only options is required for any of the solutions we are discussing in softwire, I do still think it is not justified to take on a solution for a problem which may not exist.

draft-scskf-* proposal can be revived when there is a real need to support dhcpv4-only options. No?

Cheers,
Med

>-----Message d'origine-----
>De : ian.farrer@telekom.de [mailto:ian.farrer@telekom.de]
>Envoyé : lundi 15 avril 2013 16:56
>À : BOUCADAIR Mohamed OLNC/OLN; Ted.Lemon@nominum.com
>Cc : softwires@ietf.org; dhcwg@ietf.org; sunqi.thu@gmail.com
>Objet : Re: [Softwires] [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-
>over-dhcpv6
>
>Hi Med,
>
>It would still work for lw-4o6 and the unified CPE. All of the basic
>params for configuring lw4o6/MAP1:1 can be provisioned through the
>OPTION_MAP_BIND that is proposed in the unified CPE draft over DHCPv6.
>Additional DHCPv4 only options would be done via the DHCPv4oDHCPv6 method
>for both lw4o6 and MAP-E.
>
>We still need to agree on which option will be used for provisioning the
>address of the lwAFTR/MAP BR, however. There was some discussion on this
>on the SW ML last week, but no conclusion reached.
>
>
>Cheers,
>Ian
>
>On 15/04/2013 16:47, "mohamed.boucadair@orange.com"
><mohamed.boucadair@orange.com> wrote:
>
>>Re-,
>>
>>Thanks for clarifying Ted. I must admit this is not what I understood
>>when I read draft-scskf-*.
>>
>>Does the same conclusion applies also for lw-4over6? (I'm naively
>>assuming, given the approach defined in draft-ietf-softwire-unified-cpe,
>>the same dhcpv6 to configure MAP will also be used lw-4over6)
>>
>>Cheers,
>>Med
>>
>>>-----Message d'origine-----
>>>De : Ted Lemon [mailto:Ted.Lemon@nominum.com]
>>>Envoyé : lundi 15 avril 2013 16:39
>>>À : BOUCADAIR Mohamed OLNC/OLN
>>>Cc : Qi Sun; dhcwg@ietf.org; Softwires (softwires@ietf.org)
>>>Objet : Re: [dhcwg] Adoption call on draft-scskf-dhc-dhcpv4-over-dhcpv6
>>>
>>>On Apr 15, 2013, at 10:27 AM, <mohamed.boucadair@orange.com> wrote:
>>>> Are you saying MAP is not a concerned with this draft and dhcpv6 can be
>>>used for MAP?
>>>
>>>For configuring the MAP-E prefix and port set, yes.   That was the
>>>discussion we had in Softwires in Orlando: cover the easy stuff with
>>>DHCPv6
>>>(this is the existing DHCPv6 MAP option), and then if someone needs
>>>legacy
>>>IPv4 services or stateful address allocation, do it with DHCPv4-over-
>>>DHCPv6.
>>
>>_______________________________________________
>>Softwires mailing list
>>Softwires@ietf.org
>>https://www.ietf.org/mailman/listinfo/softwires