Re: [v6ops] Who implements the DHCP service?

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 20 November 2017 11:30 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0E7127010 for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 03:30:53 -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 aoOQYr0ANAiD for <v6ops@ietfa.amsl.com>; Mon, 20 Nov 2017 03:30:51 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 ECB971200FC for <v6ops@ietf.org>; Mon, 20 Nov 2017 03:30:50 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAKBUmF7062651; Mon, 20 Nov 2017 12:30:48 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DED2E205E4E; Mon, 20 Nov 2017 12:30:48 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id CFC0C205D0A; Mon, 20 Nov 2017 12:30:48 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAKBUmoT008527; Mon, 20 Nov 2017 12:30:48 +0100
To: v6ops@ietf.org
References: <7FC2CA6E-8BF7-47BC-9164-1877FAF83FD0@gmail.com> <AM5PR0701MB283634D35008FC7AAF934B88E02E0@AM5PR0701MB2836.eurprd07.prod.outlook.com> <fd860e6c2af84c4d9774ce67f4468720@XCH15-06-08.nw.nos.boeing.com> <43186ad6-dc2f-c9d8-2884-db4a097f142d@gmail.com> <655879d9e7274da88ee2cd33a0202dd7@XCH15-06-08.nw.nos.boeing.com> <9FDA6FE7-C03C-4AA9-BED4-F0D7ED63FBBF@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <97a1f13f-e9dd-8120-0301-3eac6cef80fd@gmail.com>
Date: Mon, 20 Nov 2017 12:30:48 +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: <9FDA6FE7-C03C-4AA9-BED4-F0D7ED63FBBF@gmail.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/v6ops/PLG1H94tlDE4O0ey-C9w63-pT2Y>
Subject: Re: [v6ops] Who implements the DHCP service?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 11:30:53 -0000

Hi Fred,

If you refer to the danir draft, we could add a small cloud, or a few
dots, to say there are many intermediary routers in between.

About the question in the Topic line "who implements the DHCP service".

There is at least one trial in cellular network that has DHCP Service on
the PGW (I copy the relevant person).

Some earlier modem in Huawei E392 USB key (User Equipment) may host a
'proxy' DHCP Server that replies to Requests issued by the linux
computer.  We are checking that now to be sure.

The modem Qualcomm QDSP6 MDM9207 (a modem present in many smartphones)
does not 'support' DHCPv6; the ticket response person recommends the use
of RS/RA instead of DHCP.  By 'not support' one should read that it does
not implement a DHCPv6 proxy (like the Huawei does), and it blocks
DHCPv6 Solicit that is multicast and is port 547 (does not block DHCPv6
Solicit unicast 547, nor multicast 24683).

On the ARM part of the Sierra module WP76xx (a recent IoT device), and
on Android Huawei Mate 8, we do support DHCPv6 clients with Prefix
Delegation feature.

For home, small boxes like openwrt do have odhclient with prefix
delegation feature.

There are at least three independent publicly available open-source
DHCPv6 clients with PD feature.

Alex



Le 20/11/2017 à 02:27, Fred Baker a écrit :
> One comment on the draft in question.
> 
> Looking at figure 1 (applies to all of the figures, but let me be 
> specific for the purposes of a comment) I don't see any reason to 
> believe that the node marked "Delegating Router" is in fact a router
>  or is connected directly to the "Upstream Interface". AFAIK, given 
> the relay capability present in RFC 3315, the common practice is to 
> have a more central server respond to IA_NA and IA_PD requests, and 
> simply have a router connected on the ISP link. That might get 
> complex to draw in a figure, but I'd worry about any implicit 
> assumption in the WG version of the document that only routers 
> implemented the PD service.
> 
> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>