From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: kumarkr@us.ibm.com
Cc: davem@redhat.com, ajtuomin@tml.hut.fi,
kkumar@beaverton.ibm.com.sgi.com, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, lpetande@tml.hut.fi,
netdev@oss.sgi.com, jagana@us.ibm.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCHSET] Mobile IPv6 for 2.5.45
Date: Sat, 02 Nov 2002 12:00:19 +0900 (JST) [thread overview]
Message-ID: <20021102.120019.45396269.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <OFCFEE31E7.E8F27031-ON88256C65.00068E7B@boulder.ibm.com>
In article <OFCFEE31E7.E8F27031-ON88256C65.00068E7B@boulder.ibm.com> (at Fri, 1 Nov 2002 17:15:09 -0800), "Krishna Kumar" <kumarkr@us.ibm.com> says:
> When the HA gets a registration request, it needs to perform the following
> actions :
> 1. perform DAD
> 2. get the list of prefixes supported on the home link of the MN.
> 3. create a tunnel between the HA and the MN
> 4. join the solicited node multicast group of the MN's home
> address.
> 5. add the MN's home address to the list of proxy neigh cache entry
> for the HA.
> 6. Send NA on behalf of the MN
> 7. add the new location of the MN in the binding cache.
> 8. and finally send the Binding Registration Success/Failure
> message.
>
> In the above list, the only activities which can be done in userspace are
> #7 and #8 (that I am aware of). The rest of the items can only be done in
> the
> kernel, atleast we need to move the support to kernel. If the HA
> registration
> is completely moved to userspace, it would still need these facilities (#1
> to #6) in the kernel to perform the actions for registration. So even with
> netlink
> we still need the infrastructure in the kernel.
1: True: we need some interface (and small code)
2: FALSE: you CAN listen icmp6 message via raw socket.
3: FALSE: you CAN create tunnel using raw socket;
however, we think this is implemented in kernel.
4,5,6: True: we need some interface to generate proxy ND.
(proxy ND is already in kernel.)
For 1,4,5,6: "proxy address" on a device would be a solution.
--yoshfuji
next prev parent reply other threads:[~2002-11-02 2:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 1:15 Krishna Kumar
2002-11-02 3:00 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2002-11-02 8:36 ` Pekka Savola
2002-11-02 8:23 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 21:13 Krishna Kumar
2002-11-03 2:23 ` Werner Almesberger
2002-11-02 1:03 Jean Tourrilhes
2002-11-02 0:32 Venkata Jagana
2002-11-01 6:51 Venkata Jagana
2002-11-01 10:37 ` David S. Miller
2002-11-01 2:19 Krishna Kumar
2002-11-01 2:17 ` David S. Miller
2002-11-01 2:36 ` YOSHIFUJI Hideaki / 吉藤英明
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=20021102.120019.45396269.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=ajtuomin@tml.hut.fi \
--cc=davem@redhat.com \
--cc=jagana@us.ibm.com \
--cc=kkumar@beaverton.ibm.com.sgi.com \
--cc=kumarkr@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lpetande@tml.hut.fi \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®