IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 and IPv6ND

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 15 November 2017 13:36 UTC

Return-Path: <alexandru.petrescu@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 C546B12714F for <dhcwg@ietfa.amsl.com>; Wed, 15 Nov 2017 05:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 EdjSgY5kr-Jd for <dhcwg@ietfa.amsl.com>; Wed, 15 Nov 2017 05:36:16 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76D06128DF6 for <dhcwg@ietf.org>; Wed, 15 Nov 2017 05:36:10 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAFDa6YH020864; Wed, 15 Nov 2017 14:36:06 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2FF3C203D5A; Wed, 15 Nov 2017 14:36:06 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 200B4201624; Wed, 15 Nov 2017 14:36:06 +0100 (CET)
Received: from [132.166.84.19] ([132.166.84.19]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAFDa3Ci032072; Wed, 15 Nov 2017 14:36:04 +0100
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: Ted Lemon <mellon@fugue.com>, dhcwg <dhcwg@ietf.org>
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>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <c1209cd5-270e-63fe-8d78-c6371f9f56ef@gmail.com>
Date: Wed, 15 Nov 2017 14:36:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <FA0DADA0-CD16-4538-9E71-19922AD106B9@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/DZiC6NpihSdGnd2Q_DJ5UtJHfOM>
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: Wed, 15 Nov 2017 13:36:18 -0000

I am afraid there is no 3GPP modem for smartphone that lets DHCPv6 through.

Qualcomm blocks multicast UDP 547 whereas Balong blocks multicast 
altogether.

I do need a modem to connect on 4G, LTE-V2X and pre-5G that does let 
DHCPv6 through.

But I would like to ask you: if no such modem exist on the market, why 
not modifying the DHCPv6 protocol to work on non-547 ports and on unicast?

Alex

Le 15/11/2017 à 11:01, Bernie Volz (volz) a écrit :
> I don’t see how this is an IETF issue. Push pn the vendor to fix it; or 
> don’t buy it.
> 
> - Bernie (from iPhone)
> 
> On Nov 15, 2017, at 5:57 PM, Alexandre Petrescu 
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
> 
>> YEs, a problem with software that runs on a particular hardware problem.
>>
>> Another problem with that software too, is that it is closed source 
>> and a very high price to buy.  Moreover, it is almost forbidden to 
>> modify it by other company than the writer.
>>
>> Very many people were tempted to fix that software but it looks very 
>> hard to access.
>>
>> Alex
>>
>> Le 15/11/2017 à 10:07, Ted Lemon a écrit :
>>> How can it be a hardware problem?  Bits are bits. Don't you mean "a 
>>> problem with software that runs on a particular hardware platform?"
>>> On Nov 15, 2017 15:48, "Alexandre Petrescu" 
>>> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com> 
>>> <mailto:alexandru.petrescu@gmail.com>> wrote:
>>>    Le 15/11/2017 à 03:49, Ted Lemon a écrit :
>>>        On Nov 15, 2017, at 10:33 AM, Alexandru Petrescu
>>>        <alexandru.petrescu@gmail.com 
>>> <mailto:alexandru.petrescu@gmail.com>
>>>        <mailto:alexandru.petrescu@gmail.com>
>>>        <mailto:alexandru.petrescu@gmail.com
>>>        <mailto:alexandru.petrescu@gmail.com>>> wrote:
>>>            They dont understand that nobody asks them to implement
>>>            DHCPv6 on the modem.  The DHCPv6 happens between ARM and the
>>>            cellular operator.  Both sides are ready, yet the middle
>>>            (the 'modem') blocks 547.
>>>            That's the problem.
>>>        I'm confused.   I thought you were saying that we can't do ND,
>>>        but it sounds like what we can't do is DHCP.   And the reason we
>>>        can't do it is a misconfigured middlebox, not a protocol issue.
>>>    I was saying the DHCPv6+ND is unsolved in cellular.  It is not a
>>>    protocol issue but a hardware problem.
>>>    There are protocol solutions to the hardware problems, like ability
>>>    to vary port numbers.
>>>    Or we can further wait for hardware issues to be solved, if ever.
>>>    Alex
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org <mailto:dhcwg@ietf.org>
>> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email