linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Lukasz Duda <lukasz.duda@nordicsemi.no>
Cc: alex.aring@gmail.com, linux-wpan@vger.kernel.org,
	linux-bluetooth@vger.kernel.org
Subject: Re: [RFC v2 0/4] Adding stateful compression to IPHC
Date: Mon, 13 Jul 2015 10:15:08 -0400	[thread overview]
Message-ID: <4784.1436796908@sandelman.ca> (raw)
In-Reply-To: <1436788233-13960-1-git-send-email-lukasz.duda@nordicsemi.no>


Lukasz Duda <lukasz.duda@nordicsemi.no> wrote:
    > There is a need for parsing the 6CO option in ndisc.c which parses Router
    > Advertisement messages. Today the function calls to IPHC (6lowpan module) are
    > quite hard to implement in ndisc.c, as there is no guarantee that the 6lowpan
    > module will be loaded or not. It would make sense to build 6lowpan module
    > as in-build part of IPv6. The features could be compiled in by using #defines.

    > What do you think about moving 6lowpan as a component of IPv6 and modify ndisc.c
    > to handled 6LoWPAN specific options? Do you see any other solution to make sure
    > that 6CO is parsed and acted upon and still keep 6lowpan as a stand-alone module?

What about if ndisc.c accepted non-exclusive registrations for ND type codes?
Then 6lowpan could register itself as handler for RAs, and could process the
6CO options, ABROs, etc.
(BTW: 6tisch contemplates extending ABROs as well: there is more to come)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



  parent reply	other threads:[~2015-07-13 14:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 11:50 [RFC v2 0/4] Adding stateful compression to IPHC Lukasz Duda
2015-07-13 11:50 ` [RFC v2 1/4] 6lowpan: Introduce debugfs entry for 6lowpan module Lukasz Duda
2015-07-23  6:07   ` Alexander Aring
2015-07-13 11:50 ` [RFC v2 2/4] 6lowpan: Add stateful compression component of " Lukasz Duda
2015-07-23  6:52   ` Alexander Aring
2015-07-23  6:59     ` Alexander Aring
2015-07-13 11:50 ` [RFC v2 3/4] 6lowpan: Add stateful compression support for iphc.c Lukasz Duda
2015-07-23  7:48   ` Alexander Aring
2015-07-23  8:20     ` Duda, Lukasz
2015-07-13 11:50 ` [RFC v2 4/4] Bluetooth: 6lowpan: Enable stateful compression in bluetooth_6lowpan Lukasz Duda
2015-07-23  7:55   ` Alexander Aring
2015-07-23  8:09     ` Duda, Lukasz
2015-07-13 13:09 ` [RFC v2 0/4] Adding stateful compression to IPHC Jukka Rissanen
2015-07-15 13:42   ` Duda, Lukasz
2015-07-16  7:25     ` Jukka Rissanen
2015-07-13 14:15 ` Michael Richardson [this message]
2015-07-15  9:55 ` Duda, Lukasz
2015-07-23  8:22 ` Alexander Aring
2015-10-12 16:15 ` Alexander Aring
2015-10-13  8:36   ` Duda, Lukasz

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=4784.1436796908@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=alex.aring@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=lukasz.duda@nordicsemi.no \
    /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).