[6lo] Fwd: Kernel implementation of DANIR for IoT Router - DHCPv6-PD and ND

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 16 September 2019 07:27 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4409412080E for <6lo@ietfa.amsl.com>; Mon, 16 Sep 2019 00:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.891
X-Spam-Status: No, score=-0.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, SPOOFED_FREEMAIL=1.739] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Cuz8R2Njpqbc for <6lo@ietfa.amsl.com>; Mon, 16 Sep 2019 00:27:46 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr []) (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 C386C12080D for <6lo@ietf.org>; Mon, 16 Sep 2019 00:27:45 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr []) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8G7Riiu152206; Mon, 16 Sep 2019 09:27:44 +0200
Received: from pisaure.intra.cea.fr (localhost []) by localhost (Postfix) with SMTP id F31AD200C2F; Mon, 16 Sep 2019 09:27:43 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr []) by pisaure.intra.cea.fr (Postfix) with ESMTP id D9B90200BA5; Mon, 16 Sep 2019 09:27:43 +0200 (CEST)
Received: from [] ([]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8G7RbQ1029209; Mon, 16 Sep 2019 09:27:37 +0200
References: <c7e54351-9096-53e7-0322-cf7d0abc58f2@gmail.com>
To: "6lo@ietf.org" <6lo@ietf.org>
Cc: Dmytro Shytyi <dmytro@shytyi.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Forwarded-Message-Id: <c7e54351-9096-53e7-0322-cf7d0abc58f2@gmail.com>
Message-ID: <c059a72a-9693-2e05-0d3c-0418810d9b21@gmail.com>
Date: Mon, 16 Sep 2019 09:27:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <c7e54351-9096-53e7-0322-cf7d0abc58f2@gmail.com>
Content-Type: multipart/alternative; boundary="------------FD9232F96C8AB93D719C83A1"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/q1OV7_x-tBORC4tMnLy4i0fpyaU>
Subject: [6lo] Fwd: Kernel implementation of DANIR for IoT Router - DHCPv6-PD and ND
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 07:27:49 -0000

Hi participants to 6lo WG,

One might be interested in this way of doing IoT Router with DHCPv6-PD 
and ND.


Alex and Dmytro

-------- Message transféré --------
Sujet : 	Kernel implementation of DANIR for IoT Router - DHCPv6-PD and ND
Date : 	Mon, 16 Sep 2019 09:21:46 +0200
De : 	Alexandre Petrescu <alexandre.petrescu@gmail.com>;
Pour : 	v6ops@ietf.org <v6ops@ietf.org>;


The kernel implementation of DANIR for IoT Router was finally working a 
few weeks ago.

It is an implementation of draft-shytyi-v6ops-danir-03.txt.  This is the 
right thing to do, instead of '64share' RFC7278.

In this video one can see the kernel in the IoT Router issues a DHCPv6 
PD request on its egress and obtains a /56; it then makes several /64s 
out of it and subsequently sends RAs with these on the ingress interfaces.

The DHCPv6 server is took off-the-shelf.  The PDP part is not present in 
the IoT Router, but we expect it to work ok on a ptp link on a cellular 
network to a smartphone.

The video recorded the virtual machines output on the IoT Router 
(featured below), the Client device behind it, and the DHCPv6-PD server.



Alexandre PETRESCU and Dmytro SHYTYI

PS: we will soon post the source code on github.