All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: IPv6 support
Date: Thu, 05 Nov 2009 17:19:51 +0530	[thread overview]
Message-ID: <4AF2BBDF.9060505@suse.de> (raw)
In-Reply-To: <B3F6BEAE-A564-475F-93D5-7D6E0FC79147@oracle.com>

Hi Chuck,

Thanks much for the detailed update.

On 11/02/2009 10:10 PM, Chuck Lever wrote:
> On Nov 2, 2009, at 3:20 AM, Suresh Jayaraman wrote:
>> Hi Chuck et al,
>>
>> Thanks for all the excellent work on IPv6 support. There have been
>> considerable amount of development that has been happening recently.
>> However, it's not very clear what are the missing pieces or open
>> problems (if any).
> 
> There's a working document on the linux-nfs.org wiki that has a full
> list, but I can't seem to get to linux-nfs.org right now.

Is this what you mentioned?

http://wiki.linux-nfs.org/wiki/index.php/Server_IPv6_support
http://wiki.linux-nfs.org/wiki/index.php/NFSv4_Introduction#IPv6_support_for_the_client

> 
> The long answer depends on your definition of "full".  :-)
> 
> Does that include complete support for link-local IPv6 addresses?  Does
> that include full support for netids in the kernel?  Does that include
> complete multi-homed host support in lockd and statd?  Does that include
> full support for internationalized domain names?  Does that include IPv6
> netgroup support?  Does it include IPv6 support in TCP wrappers?  Does
> it include support for systems that have no IPv4 addresses (not even
> loopback)?
> 
> There are a bunch of details that still need to be worked through.  I've
> only been able to guess at what features are required, and which can be
> implemented at a later time.  What I would dearly love to have is a list
> of specific features that folks feel is a baseline (based on actual
> data, of course).  

I'd try and see if I could get the list of specific features.

> 
> Plus, most distributions don't have fluent user space infrastructure for
> IPv6 yet.  NetworkManager is one area that may need work.  The Network
> Administration tool in Fedora is still IPv4-centric, iirc.  We don't
> have firewall admin tools that handle IPv6 rules.  Unlike IPv4, admins
> can (and often do) use IPv6-aware kernels without ipv6.ko, so all of our
> tools and support have to be careful about using IPv6 when the O/S may
> not support it.  This is different than IPv4, which is nearly always
> available.
> 

Thanks,

-- 
Suresh Jayaraman

  parent reply	other threads:[~2009-11-05 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  8:20 IPv6 support Suresh Jayaraman
2009-11-02 16:40 ` Chuck Lever
2009-11-02 20:43   ` Jeff Layton
2009-11-05 11:49   ` Suresh Jayaraman [this message]
2009-11-05 14:41     ` Chuck Lever
2009-11-19 15:17   ` IPv6 support: dreaming of Ivan Shmakov
     [not found]     ` <87hbsqbl3d.fsf_-_-Hr8DDCuc/25fzK4uoAgqGcYP0srqJqIshoJSb6RVeLg@public.gmane.org>
2009-11-19 16:05       ` Chuck Lever
2009-11-19 16:18   ` IPv6 support Ivan Shmakov
2011-01-18 13:40 Mika Liljeberg
2021-02-02  0:28 IPv6 Support Raymond Yeung

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=4AF2BBDF.9060505@suse.de \
    --to=sjayaraman@suse.de \
    --cc=chris.mason@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.