From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
kernel@pengutronix.de, mcr@sandelman.ca,
lukasz.duda@nordicsemi.no, martin.gergeleit@hs-rm.de
Subject: Re: [RFCv3 bluetooth-next 4/4] 6lowpan: iphc: add support for stateful compression
Date: Fri, 11 Dec 2015 18:05:46 +0100 [thread overview]
Message-ID: <20151211170541.GA1119@omega> (raw)
In-Reply-To: <1448796882-316-5-git-send-email-alex.aring@gmail.com>
Hi,
status update here.
I implemented successful basic 6CO RA messages at sending and
processing inside radvd.
There might also the question if processing 6CO inside kernel or
userspace? I put the basic functionality inside userspace for now.
I will send patches for this in the next days.
Anyway I figured some things out which was completely wrong inside this
patch.
- There exist one context based table only.
In rfc6282 stands:
The specification enables a node to use up to 16 contexts. The
context used to encode the source address does not have to be the
same as the context used to encode the destination address.
and I thought it was $SOME_TABLE[DCI] != $DIFFERENT_TABLE[SCI].
But it means in general simple that it can be: DCI != SCI.
With this knowledge the code gets much smaller.
- I also remove the validation check for contexts, it can be any
prefic/address. The lookup functionality will deal with that if the
context looks not correct or need additional changes.
The table is very KISS for now. Not much additional functionality is
there, if somebody needs that it can handled by
$USERSPACE_RA_6CO_handler.
- Alex
next prev parent reply other threads:[~2015-12-11 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 11:34 [RFCv3 bluetooth-next 0/4] 6lowpan: debugfs and stateful compression support Alexander Aring
[not found] ` <1448796882-316-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-11-29 11:34 ` [RFCv3 bluetooth-next 1/4] 6lowpan: add lowpan dev register helpers Alexander Aring
2015-12-01 20:38 ` Stefan Schmidt
2015-11-29 11:34 ` [RFCv3 bluetooth-next 2/4] 6lowpan: add debugfs support Alexander Aring
[not found] ` <1448796882-316-3-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-01 20:50 ` Stefan Schmidt
2015-11-29 11:34 ` [RFCv3 bluetooth-next 3/4] ipv6: add ipv6_addr_prefix_copy Alexander Aring
[not found] ` <1448796882-316-4-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-01 10:56 ` Hannes Frederic Sowa
2015-12-01 11:17 ` YOSHIFUJI Hideaki/吉藤英明
2015-12-01 11:38 ` Stefan Schmidt
2015-12-01 11:51 ` Duda, Lukasz
2015-11-29 11:34 ` [RFCv3 bluetooth-next 4/4] 6lowpan: iphc: add support for stateful compression Alexander Aring
2015-12-02 14:18 ` Stefan Schmidt
[not found] ` <565EFD9E.9020908-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-12-03 14:22 ` Alexander Aring
2015-12-04 12:13 ` Stefan Schmidt
2015-12-11 17:05 ` Alexander Aring [this message]
2015-12-11 17:13 ` Alexander Aring
2015-12-11 19:11 ` Stefan Schmidt
2015-12-11 19:49 ` Alexander Aring
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=20151211170541.GA1119@omega \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=lukasz.duda@nordicsemi.no \
--cc=martin.gergeleit@hs-rm.de \
--cc=mcr@sandelman.ca \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).