From: David Miller <davem@davemloft.net>
To: nakam@linux-ipv6.org
Cc: hsantos@av.it.pt, yoshfuji@linux-ipv6.org, anttit@tcs.hut.fi,
vnuorval@tcs.hut.fi, netdev@vger.kernel.org,
usagi-core@linux-ipv6.org
Subject: Re: [RFC] Mobile IPv6 introduction
Date: Wed, 02 Aug 2006 14:14:01 -0700 (PDT) [thread overview]
Message-ID: <20060802.141401.105110100.davem@davemloft.net> (raw)
In-Reply-To: <44D0A294.5000208@linux-ipv6.org>
From: Masahide NAKAMURA <nakam@linux-ipv6.org>
Date: Wed, 02 Aug 2006 22:03:16 +0900
> If there is much requirement to add new type number without any
> modification of kernel code at all I would support ICMPv6 filter
> approach, too.
There is no such requirement, please just continue to prepare
your current patches for inclusion.
There is a limit to how much nit-picking we can do for such
a large body of work, and we should thus take evolutionary
approach to this work. We can make all kinds of refinements
later to improve the implementation.
prev parent reply other threads:[~2006-08-02 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 9:23 [RFC] Mobile IPv6 introduction Masahide NAKAMURA
2006-07-29 9:28 ` [PATCH 0/23][XFRM] MIPv6 CN introduction (part A) (Re: [RFC] Mobile IPv6 introduction) Masahide NAKAMURA
2006-07-29 9:37 ` [PATCH 0/20][IPV6/XFRM] MIPv6 CN (part B) Masahide NAKAMURA
2006-08-02 0:30 ` David Miller
2006-08-02 8:26 ` Masahide NAKAMURA
2006-07-29 14:12 ` [RFC] Mobile IPv6 introduction Hugo Santos
2006-08-02 0:35 ` David Miller
2006-08-02 0:58 ` Hugo Santos
2006-08-02 1:04 ` David Miller
2006-08-02 1:52 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-02 7:58 ` Ville Nuorvala
2006-08-02 11:03 ` Hugo Santos
2006-08-02 3:24 ` Masahide NAKAMURA
2006-08-02 10:47 ` Hugo Santos
2006-08-02 13:03 ` Masahide NAKAMURA
2006-08-02 21:14 ` 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=20060802.141401.105110100.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=anttit@tcs.hut.fi \
--cc=hsantos@av.it.pt \
--cc=nakam@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=usagi-core@linux-ipv6.org \
--cc=vnuorval@tcs.hut.fi \
--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 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).