Re: [dhcwg] DHCPv6 and IPv6ND

"Bernie Volz (volz)" <> Wed, 15 November 2017 10:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2C0F1124205 for <>; Wed, 15 Nov 2017 02:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1p1MkXNiPb02 for <>; Wed, 15 Nov 2017 02:01:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9C61D12008A for <>; Wed, 15 Nov 2017 02:01:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=10197; q=dns/txt; s=iport; t=1510740099; x=1511949699; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lzsZd9a1z6L05h9YS5YuYRCkbntbdCSUwjZVXcme4JE=; b=HTlzlZWqTFXEUBF+fCXS1YHfyEe1+rFHwGPJrKMOvWGV3E1Wr3bgeVA+ vTo7YtRPJed0wtIONeQrL/RkQf0e7Huaq+sTkrIw4eHuK9sQKfaSSH6XJ yR2KyisSa9GbLLfFinp2RqTAz7HhKorkggeGg7aLfrOuQzwcNNhRXLHmE w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.44,398,1505779200"; d="scan'208,217";a="323859459"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Nov 2017 10:01:38 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id vAFA1c62004534 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Nov 2017 10:01:38 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 15 Nov 2017 04:01:37 -0600
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Wed, 15 Nov 2017 04:01:37 -0600
From: "Bernie Volz (volz)" <>
To: Alexandre Petrescu <>
CC: Ted Lemon <>, dhcwg <>
Thread-Topic: [dhcwg] DHCPv6 and IPv6ND
Date: Wed, 15 Nov 2017 10:01:37 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_FA0DADA0CD1645389E7119922AD106B9ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [dhcwg] DHCPv6 and IPv6ND
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 Nov 2017 10:01:41 -0000

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 <<>> 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.


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" <<> <>> wrote:
   Le 15/11/2017 à 03:49, Ted Lemon a écrit :
       On Nov 15, 2017, at 10:33 AM, Alexandru Petrescu
       <>>> 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.

dhcwg mailing list<>