public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tomasz Torcz, BG" <zdzichu@irc.pl>
To: linux-kernel@vger.kernel.org
Subject: 2.4 and full ipv6 - will it happen?
Date: Mon, 19 Aug 2002 06:39:41 +0200	[thread overview]
Message-ID: <20020819043941.GA31158@irc.pl> (raw)


Some time ago Linux was first OS to have full RFC complaint IPv4 stack.
Linux still has superior networking, but protocol of the future is IPv6.
IPv6 stack in mainline is currently far from perfect. There is a hope,
however. Full IPv6 stack is beeing mantained by USAGI project. It's
clear, that USAGI's project will be integrated into mainline kernel.
What worries me - it's planned for 2.7, what is _BAD_ and late.
IMO, it can be included in any time. The sooner is better.
Marcelo - would you include full IPv6 stack in 2.4.20 if you get patches?
Please - it's important for Linux to be network OS choice in future.
It's barely possible with current IPv6 implementation.

My another concern is that Linux on Sparc machines is very unstable,
and main polish 6bone router - beeing a sparc machine - is not very
reliable. But that's another story.

-- 
Tomasz Torcz           Zjadanie martwych dzieci
zdzichu@irc.pl           jest barbarzynstwem!

             reply	other threads:[~2002-08-19  4:36 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19  4:39 Tomasz Torcz, BG [this message]
2002-08-19  4:37 ` 2.4 and full ipv6 - will it happen? 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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20020819043941.GA31158@irc.pl \
    --to=zdzichu@irc.pl \
    --cc=linux-kernel@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