From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <alex.aring@gmail.com>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, kuba@kernel.org, dav.lebrun@gmail.com,
stefan@datenfreihafen.org, kai.beckmann@hs-rm.de,
martin.gergeleit@hs-rm.de, robert.kaiser@hs-rm.de,
netdev@vger.kernel.org
Subject: Re: [PATCHv2 net-next 0/5] net: ipv6: add rpl source routing
Date: Fri, 20 Mar 2020 13:46:47 -0400 [thread overview]
Message-ID: <30175.1584726407@localhost> (raw)
In-Reply-To: <20200320023901.31129-1-alex.aring@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Alexander Aring <alex.aring@gmail.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@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-03-20 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 2:38 [PATCHv2 net-next 0/5] net: ipv6: add rpl source routing Alexander Aring
2020-03-20 2:38 ` [PATCHv2 net-next 1/5] include: uapi: linux: add rpl sr header definition Alexander Aring
2020-03-20 2:38 ` [PATCHv2 net-next 2/5] addrconf: add functionality to check on rpl requirements Alexander Aring
2020-03-20 2:38 ` [PATCHv2 net-next 3/5] net: ipv6: add support for rpl sr exthdr Alexander Aring
2020-03-20 17:56 ` Michael Richardson
2020-03-20 2:39 ` [PATCHv2 net-next 4/5] net: add net available in build_state Alexander Aring
2020-03-20 2:39 ` [PATCHv2 net-next 5/5] net: ipv6: add rpl sr tunnel Alexander Aring
2020-03-20 22:40 ` David Ahern
2020-03-20 17:46 ` Michael Richardson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30175.1584726407@localhost \
--to=mcr@sandelman.ca \
--cc=alex.aring@gmail.com \
--cc=dav.lebrun@gmail.com \
--cc=davem@davemloft.net \
--cc=kai.beckmann@hs-rm.de \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=martin.gergeleit@hs-rm.de \
--cc=netdev@vger.kernel.org \
--cc=robert.kaiser@hs-rm.de \
--cc=stefan@datenfreihafen.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.