updated draft/status/new mail list for IPv7 proposal

ULLMANN@PROCESS.COM (Robert L Ullmann) Fri, 08 January 1993 20:56 UTC

Received: by world.std.com (5.65c/Spike-2.0) id AA12361; Fri, 8 Jan 1993 15:56:55 -0500
Errors-To: ipv7-request@world.std.com
Sender: ipv7-request@world.std.com
Reply-To: ipv7@world.std.com
Precedence: bulk
Return-Path: <ULLMANN@PROCESS.COM>
Received: from alcor.process.com by world.std.com (5.65c/Spike-2.0) id AA12320; Fri, 8 Jan 1993 15:56:49 -0500
Message-Id: <199301082056.AA12320@world.std.com>
Date: Fri, 8 Jan 1993 15:55 -0500
From: ULLMANN@PROCESS.COM (Robert L Ullmann)
To: big-internet@munnari.oz.au
Cc: ipv7@world.std.com
Subject: updated draft/status/new mail list for IPv7 proposal
Status: R

Hi,

This is a status update on the IPv7 protocol described in
draft-ullmann-ipv7-02.txt, just updated (4 January). Even if
you have read previous versions, you should review this.

There is also a companion document on routing not released yet.

To outline what this IPv7 is about, it:

*	Meets all of the criteria musts, and most of the shoulds
	(and all of them at least as well as v4).

*	Provides a new IP version that interoperates with the
	existing one; it does NOT require a costly transition plan;
	it is deployed as a new version as vendors routinely do.

*	Uses Administrative Domains in the addressing; this
	is a political necessity as the Internet expands.

*	Allows 10^6 hosts in each net; 10^8 nets in each AD,
	and 10^8 ADs. (Enough? :-) The layer boundaries are done
	with flexible masks, of course.

*	Separates the forwarding-decision complexity from the
	routing explosion, and provides a method to make forwarding
	decision time near-linear with the number of datagrams. (I.e. much
	less than the ~N(d) * log N(r) typical in v4 routers.)

*	This also provides for datagrams following flows in a very
	general model. (E.g. allowing a flow to be bandwidth reserved
	for any use between two sites, not just particular machines.)

*	Also upgrades TCP to remove its current painful limitations.
	(With present CPU and LAN speeds, e.g. 200 mips/100mbps, both
	sequence space and window in TCPv4 are too small.)

*	Provides for ICMP messages to travel through both versions
	and be interpreted properly to the extent needed by existing
	implementations.

*	And miscellaneous other good stuff, so go read it.

The discussion list is   ipv7@world.std.com
Remember that subscription requests go to ipv7-request@world.std.com,
not to the list.

Archive of the list is   world.std.com:/pub/ipv7/...

Best Regards,
Robert