From: Petr Baudis <pasky@pasky.ji.cz>
To: "David S. Miller" <davem@redhat.com>
Cc: zdzichu@irc.pl, linux-kernel@vger.kernel.org
Subject: Re: 2.4 and full ipv6 - will it happen?
Date: Thu, 12 Sep 2002 17:06:09 +0200 [thread overview]
Message-ID: <20020912150609.GE21715@pasky.ji.cz> (raw)
In-Reply-To: <20020818.213719.117777405.davem@redhat.com>
Dear diary, on Mon, Aug 19, 2002 at 06:37:19AM CEST, I got a letter,
where "David S. Miller" <davem@redhat.com> told me, that...
> Full IPv6 stack is beeing mantained by USAGI project.
>
> Yes, and based upon previous attempts to get them to merge their work
> into the mainline, we believe at this point that they actually enjoy
> being a totally seperate project and not merging completely is a
> feature for them.
>
> USAGI may only accept that comment, and the only way they may
> disprove it is to merge their code to us as we have continually
> requested them to do so.
...
FYI, early at this morning (UTC), Yuji Sekiya <sekiya@sfc.wide.ad.jp> wrote on
the USAGI list:
======
> Is there any chance the work of the USAGI project will
> be included in the vanilla kernel(2.4?/2.5?) in the near
> future? Will we see better ipv6 support in 2.6 ?
Yes, we will send patches to mainline kernel.
At least we will send the below patches by end of Setpember.
We are now working.
- IPv6 default route fix
- Source address seletcion
- Privacy extension
- IPv4/IPv6 double bind
- NDP timer improvement
- IPsec for IPv6
======
So, let's watch them and hope that they will fulfill this and send some usable
patches to you..
PS: Sorry for replying to such an old thread, I only thought that people not
subscribed on the USAGI mailing list may be still interested in this.
--
Petr "Pasky" Baudis
* ELinks maintainer * IPv6 guy (XS26 co-coordinator)
* IRCnet operator * FreeCiv AI occassional hacker
.
<Beeth> Girls are like internet domain names, the ones I like are already taken.
<honx> Well, you can still get one from a strange country :-P
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/
next prev parent reply other threads:[~2002-09-12 15:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 4:39 Tomasz Torcz, BG
2002-08-19 4:37 ` David S. Miller
2002-08-19 5:16 ` Tomasz Torcz, BG
2002-08-19 5:12 ` David S. Miller
2002-08-19 23:34 ` Thunder from the hill
2002-08-19 23:23 ` David S. Miller
2002-08-19 23:49 ` Daniel Berlin
2002-08-19 23:54 ` Alan Cox
2002-08-20 0:32 ` Rik van Riel
2002-08-20 13:54 ` kuznet
2002-08-20 6:56 ` Thunder from the hill
2002-08-21 20:24 ` Kelsey Hudson
2002-08-21 21:31 ` Bernd Eckenfels
2002-08-21 21:44 ` Thunder from the hill
2002-08-21 22:03 ` Bernd Eckenfels
2002-08-21 23:13 ` Russell King
2002-08-22 0:05 ` Bernd Eckenfels
2002-08-22 6:08 ` Thunder from the hill
2002-08-26 18:55 ` Kelsey Hudson
2002-08-26 19:44 ` Bernd Eckenfels
2002-08-26 21:51 ` Michael H. Warfield
2002-08-26 23:48 ` Bernd Eckenfels
2002-08-27 16:07 ` Michael H. Warfield
2002-08-28 19:14 ` Bernd Eckenfels
2002-08-29 2:05 ` Michael H. Warfield
2002-08-29 18:47 ` Bernd Eckenfels
2002-08-21 22:08 ` Alan Cox
2002-08-22 6:12 ` Thunder from the hill
2002-08-22 12:27 ` Rik van Riel
2002-08-22 18:22 ` Alan Cox
2002-08-22 18:26 ` Bernd Eckenfels
2002-08-22 19:19 ` Russell King
2002-09-12 15:06 ` Petr Baudis [this message]
2002-09-13 1:47 ` David S. Miller
2002-08-19 7:27 ` Chris Wedgwood
2002-08-19 12:25 ` Alan Cox
2002-08-19 22:39 ` Kelsey Hudson
2002-08-20 6:17 ` Val Henson
2002-08-19 23:56 Leif Sawyer
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=20020912150609.GE21715@pasky.ji.cz \
--to=pasky@pasky.ji.cz \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
/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®