IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 and IPv6ND

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 15 November 2017 02:33 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 8AEA1129485 for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 18:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 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] 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 OPDMajFR2-Sr for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 18:33:40 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 D26EF120724 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 18:33:39 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAF2XbYL020895; Wed, 15 Nov 2017 03:33:37 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C1B51201392; Wed, 15 Nov 2017 03:33:37 +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 AA442200D0A; Wed, 15 Nov 2017 03:33:37 +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 vAF2Xagc002927; Wed, 15 Nov 2017 03:33:37 +0100
To: Ted Lemon <mellon@fugue.com>
Cc: 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>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <68a1f0db-58d3-fe0e-8169-127c0b629df1@gmail.com>
Date: Wed, 15 Nov 2017 03:33:35 +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: <8E4C374A-DA6D-4FAB-AAEA-7EB4A2A655D8@fugue.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/l2iEyjzgVjMZGBUqxXvi-PYwL3o>
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 02:33:41 -0000


Le 15/11/2017 à 03:27, Ted Lemon a écrit :
> On Nov 15, 2017, at 10:26 AM, Alexandre Petrescu 
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>> Because of many reasons.
> 
> Can you list some of those reasons?

The raw message from modem manufacturer is "clients at host side can not 
use DHCPv6 to get prefix from MDM [modem], they can use RS/RA to get 
prefix as DHCPv6 functionality is not supported in MDM".

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.

Alex

v2.23.0 | Report a Bug | By Email