netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nakam@linux-ipv6.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] [IPV6] MIP6: Loadable module support for MIPv6.
Date: Tue, 26 Jun 2007 23:56:44 -0700 (PDT)	[thread overview]
Message-ID: <20070626.235644.90119583.davem@davemloft.net> (raw)
In-Reply-To: <11799066192758-git-send-email-nakam@linux-ipv6.org>

From: nakam@linux-ipv6.org
Date: Wed, 23 May 2007 16:50:19 +0900

> From: Masahide NAKAMURA <nakam@linux-ipv6.org>
> 
> This patch makes MIPv6 loadable module named "mip6".
> 
> Here is a modprobe.conf(5) example to load it automatically
> when user application uses XFRM state for MIPv6:
> 
> alias xfrm-type-10-43 mip6
> alias xfrm-type-10-60 mip6
> 
> Some MIPv6 feature is not included by this modular, however,
> it should not be affected to other features like either IPsec
> or IPv6 with and without the patch.
> We may discuss XFRM, MH (RAW socket) and ancillary data/sockopt
> separately for future work.
> 
> Loadable features:
> * MH receiving check (to send ICMP error back)
> * RO header parsing and building (i.e. RH2 and HAO in DSTOPTS)
> * XFRM policy/state database handling for RO
> 
> These are NOT covered as loadable:
> * Home Address flags and its rule on source address selection
> * XFRM sub policy (depends on its own kernel option)
> * XFRM functions to receive RO as IPv6 extension header
> * MH sending/receiving through raw socket if user application
>   opens it (since raw socket allows to do so)
> * RH2 sending as ancillary data
> * RH2 operation with setsockopt(2)
> 
> Signed-off-by: Masahide NAKAMURA <nakam@linux-ipv6.org>

Patch applied, thank you!

      parent reply	other threads:[~2007-06-27  6:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  7:50 [PATCH 2/2] [IPV6] MIP6: Loadable module support for MIPv6 nakam
2007-05-23  9:54 ` Ingo Oeser
2007-05-24  1:48   ` Masahide NAKAMURA
2007-05-24  8:36     ` Ingo Oeser
2007-05-24 13:23       ` Masahide NAKAMURA
2007-05-24  8:36     ` Herbert Xu
2007-06-27  6:56 ` David Miller [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=20070626.235644.90119583.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=nakam@linux-ipv6.org \
    --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).