netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vince Fuller <vaf@cisco.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Vince Fuller <vaf@cisco.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001] ipv4: enable use of 240/4 address space
Date: Fri, 11 Jan 2008 09:29:15 -0800	[thread overview]
Message-ID: <20080111172915.GA6199@cisco.com> (raw)
In-Reply-To: <p73bq7smx1t.fsf@bingen.suse.de>

On Fri, Jan 11, 2008 at 12:17:02PM +0100, Andi Kleen wrote:
> Vince Fuller <vaf@cisco.com> writes:
> 
> > from Vince Fuller <vaf@vaf.net>
> >
> > This set of diffs modify the 2.6.20 kernel to enable use of the 240/4
> > (aka "class-E") address space as consistent with the Internet Draft
> > draft-fuller-240space-00.txt.
> 
> Wouldn't it be wise to at least wait for it becoming an RFC first? 

There is reasonable consensus on making use of 240/4; some applications,
such as ISAKMP and automatic ipv6-to-IPv4 tunneling, still need to determine
if they should treat the space as "public" or "private" but that shouldn't
affect whether kernel support is added.

Solaris recently added support for 240/4 and OSX already has it. I thought
the Linux kernel developers might appreciate having patches to do likewise.

I leave it up to you, the developers, to decide if you want to use these
patches.

	--Vince

  parent reply	other threads:[~2008-01-11 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08  1:10 [PATCH 001/001] ipv4: enable use of 240/4 address space Vince Fuller
2008-01-11  6:33 ` David Miller
2008-01-11 11:17 ` Andi Kleen
2008-01-11 12:41   ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-12  1:48     ` David Miller
2008-01-12  5:12       ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-11 17:29   ` Vince Fuller [this message]
2008-01-12  1:49     ` David Miller
2008-01-12 11:23       ` Jan Engelhardt
2008-01-12  5:47 ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-17 23:04 ` Jan Engelhardt
2008-01-18  0:28   ` Vince Fuller
2008-01-18  1:13 ` [PATCH] IPv4: Enable " Jan Engelhardt
2008-01-18  1:26   ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-18  1:52     ` Jan Engelhardt
2008-01-18  2:13       ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-18  2:15         ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-19 13:44         ` Jan Engelhardt
2008-01-19 15:30           ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-21 11:19             ` David Miller

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=20080111172915.GA6199@cisco.com \
    --to=vaf@cisco.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).