IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 and IPv6ND

<mohamed.boucadair@orange.com> Thu, 16 November 2017 10:08 UTC

Return-Path: <mohamed.boucadair@orange.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 DCCE7126DFB for <dhcwg@ietfa.amsl.com>; Thu, 16 Nov 2017 02:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXK39hpSEpOJ for <dhcwg@ietfa.amsl.com>; Thu, 16 Nov 2017 02:08:29 -0800 (PST)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCFF8126C2F for <dhcwg@ietf.org>; Thu, 16 Nov 2017 02:08:29 -0800 (PST)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 70BC760F76; Thu, 16 Nov 2017 11:08:28 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 50C0C180076; Thu, 16 Nov 2017 11:08:28 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0361.001; Thu, 16 Nov 2017 11:08:27 +0100
From: mohamed.boucadair@orange.com
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, Ted Lemon <mellon@fugue.com>
CC: dhcwg <dhcwg@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] DHCPv6 and IPv6ND
Thread-Index: AQHTXqV6/64lorm6QoWdIRZ/749NYaMWx92A
Date: Thu, 16 Nov 2017 10:08:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A07B80E@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <cf2e41a05fd742a3b576ee317c5392f6@XCH15-06-08.nw.nos.boeing.com> <E94F8CD6-EC4E-4B61-92B6-99FBD1D494A4@fugue.com> <8d935331012947aa942e8dc2a48d889f@XCH15-06-08.nw.nos.boeing.com> <54D1B686-A5FA-42A0-8A57-067562313488@fugue.com> <38ef2544-df5c-4677-ffaa-7b084eb300fa@gmail.com> <CAPt1N1k7CBvTOHFFoNeS6TMq_dkvSQTJ4TXR=Yt8S-6p--eabg@mail.gmail.com> <e4df5049-2548-6762-994d-a12c8f663e59@gmail.com> <8E4C374A-DA6D-4FAB-AAEA-7EB4A2A655D8@fugue.com> <68a1f0db-58d3-fe0e-8169-127c0b629df1@gmail.com> <89CE6E3F-7501-4A8D-9A1B-5638A8845E7D@fugue.com> <7ef058e6-0360-f86c-b7d8-8eaf129a7f95@gmail.com> <CAPt1N1=o+N64kdoYSSG38rwazAj_Lj9xLUV4uDCAzxbcpref1g@mail.gmail.com> <d194e3a4-620f-dde3-c836-3b5122d2805b@gmail.com> <FA0DADA0-CD16-4538-9E71-19922AD106B9@cisco.com> <c1209cd5-270e-63fe-8d78-c6371f9f56ef@gmail.com> <2907A64D-BB00-4922-BA6F-AA596AC878AB@fugue.com> <0b88f8af-2cbd-e6b2-ff22-50d682a66e8f@gmail.com> <953BFAD3-BAD7-4A1D-A102-2A6C7873052C@fugue.com> <3f898368-6222-d87c-7baa-38dea51a6980@gmail.com>
In-Reply-To: <3f898368-6222-d87c-7baa-38dea51a6980@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/gegYM-BdLOpvlkkDbdY-zgNTrKo>
Subject: Re: [dhcwg] DHCPv6 and IPv6ND
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Nov 2017 10:08:36 -0000

Hi Alex, 

I disagree.

The problems you are describing are implementation ones. 

Cheers,
Med

> -----Message d'origine-----
> De : dhcwg [mailto:dhcwg-bounces@ietf.org] De la part de Alexandru
> Petrescu
> Envoyé : jeudi 16 novembre 2017 07:38
> À : Ted Lemon
> Cc : dhcwg; Bernie Volz (volz)
> Objet : Re: [dhcwg] DHCPv6 and IPv6ND
> 
> 
> 
> Le 16/11/2017 à 06:29, Ted Lemon a écrit :
> > I'm having trouble figuring out how changing the port would help.
> > You'd still have to make the same modifications.   You'd still have
> > to define a business model.
> 
> _If_ there is a standard that says port number is variable, and if
> hardware manufacturer implements it, then it will help.
> 
> If not, not.
> 
> If so, this entire issue about making DHCPv6 work on 3GPP networks
> should be forgotten.   It's impossible to make it work.
> 
> That puts the discussion of DHCPv6 and IPv6ND outside the 3GPP context
> altogether.
> 
> For the business model: I am not an economist.
> 
> Alex
> 
> >
> >
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email