[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30175.1584726407@localhost>
Date: Fri, 20 Mar 2020 13:46:47 -0400
From: Michael Richardson <mcr@...delman.ca>
To: Alexander Aring <alex.aring@...il.com>
cc: davem@...emloft.net, kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
kuba@...nel.org, dav.lebrun@...il.com, stefan@...enfreihafen.org,
kai.beckmann@...rm.de, martin.gergeleit@...rm.de,
robert.kaiser@...rm.de, netdev@...r.kernel.org
Subject: Re: [PATCHv2 net-next 0/5] net: ipv6: add rpl source routing
Alexander Aring <alex.aring@...il.com> wrote:
> should happen. So far I understand there exists a draft yet which
> describes the cases (inclusive a Hop-by-Hop option which we also not
> support yet).
> https://tools.ietf.org/html/draft-ietf-roll-useofrplinfo-35
The need for the hop-by-hop encapsulation is, I hope, now unnecessary.
draft-ietf-roll-unaware-leaves describes how very low duty cycle systems
(window-smash alerts, etc.) could participate in RPL without being routers.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@...delman.ca http://www.sandelman.ca/ | ruby on rails [
Download attachment "signature.asc" of type "application/pgp-signature" (488 bytes)
Powered by blists - more mailing lists