Using the 8-bit TOS field for Extended Addressing...

"Jim Fleming" <JimFleming@ameritech.net> Wed, 11 September 2002 00:24 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00199 for <ietf-web-archive@odin.ietf.org>; Tue, 10 Sep 2002 20:24:18 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA06178 for ietf-outbound.10@loki.ietf.org; Tue, 10 Sep 2002 20:24:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA06148 for <ietf-mainout@loki.ietf.org>; Tue, 10 Sep 2002 20:20:22 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA00165 for ietf-mainout@loki.ietf.org; Tue, 10 Sep 2002 20:18:41 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from mail1-0.chcgil.ameritech.net (mail1-0.chcgil.ameritech.net [206.141.192.68]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00161 for <ietf@ietf.org>; Tue, 10 Sep 2002 20:18:37 -0400 (EDT)
Received: from repligate ([67.36.180.20]) by mail1-0.chcgil.ameritech.net (InterMail vM.4.01.02.17 201-229-119) with SMTP id <20020911002016.DBLV4136.mail1-0.chcgil.ameritech.net@repligate>; Tue, 10 Sep 2002 19:20:16 -0500
Message-ID: <019e01c25929$0e234980$8c56fea9@repligate>
From: Jim Fleming <JimFleming@ameritech.net>
To: Brian E Carpenter <brian@hursley.ibm.com>, Jason Gao <jag@kinet.com.cn>
Cc: ietf@ietf.org
References: <001f01c254dd$b30bdd40$5019e29f@fujitsu> <3D7B0CAD.C8339952@hursley.ibm.com> <00e601c257e9$19aa68b0$5019e29f@fujitsu> <3D7C924F.E3CE8130@hursley.ibm.com> <5.1.1.6.2.20020909192132.01ca6750@mira-sjcm-4.cisco.com> <019e01c25885$10551020$5019e29f@fujitsu> <3D7E08C0.5A49200D@hursley.ibm.com>
Subject: Using the 8-bit TOS field for Extended Addressing...
Date: Tue, 10 Sep 2002 19:20:37 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Brian E Carpenter" <brian@hursley.ibm.com>
To: "Jason Gao" <jag@kinet.com.cn>
Cc: <ietf@ietf.org>
Sent: Tuesday, September 10, 2002 9:59 AM
Subject: Re: Fuzzy-layering and its suggestion - Towards better QoS solution in the IPv6 network


> Jason Gao wrote:
> ...
> > > You don't get to pull a bit out for your private use.
> > >
> > It is still not a requirement that every node in the Internet must be DS-compliant.
> 
> These statements are both true. A node that chooses not to
> implement RFC 2474 cannot use the TOS bits for private purposes.
> 
>    Brian
> 

You seem to be confused about how the 32-bit, IPv4, end-to-end, Internet is defined.
You seem to be focused on nodes outside of the Internet, as opposed to the infrastructure
that creates what most people view as "the Internet".

From a user's point-of-view, the edge of the global, public, 32-bit, IPv4++ Internet
is defined as the collection of private companies and people, connected together, that
pass 160-bit headers with the **8-bit TOS field unchanged**. Those 8-bits can be used
to expand the addressing at the edges of that network, 4-bits are needed in each direction.
That expands the address space by adding 15 more Internets, as large as the legacy net.
That creates yet another layer or edge, composed of equipment that combines to make
people see 4 extended address bits, for a total of 36.

You can easily obtain code to do this, or help write more code to do it.

http://www.netfilter.org/
http://netfilter.samba.org
http://www.google.com/search?q=TOS+routing
http://www.google.com/search?q=packet+mangling

As for IPv6, one can not assume that the 128-bit DNS implies IPv6. As an example,
if you use a 2002 model year address, such as 2002:[IPv4]:* in the 128-bit DNS AAAA
records, your computer will likely generate IPv4 packet headers. A6 DNS records are
for IPv6. AAAA records work for IPv4++. Private companies and private individuals
are working together to define what goes in the AAAA records. You are FREE to
participate. Some private companies and closed societies may try to tell you that you are
not free to participate, but that is not the case. Even with tens of millions of dollars from
domain name sales and address space leasing, they will not be able to pull together enough
money to buy the freedom of all people on planet Earth. They may try...but, most people's
minds are not for sale.

Jim Fleming
2002:[IPv4]:000X:03DB:...IPv8 is closer than you think...IPv16 is even closer...
http://ipv8.dyndns.tv
http://ipv8.yi.org
http://ipv8.dyns.cx
http://ipv8.no-ip.com
http://ipv8.no-ip.org
http://ipv8.no-ip.biz
http://ipv8.no-ip.info
http://ipv8.myip.us
http://ipv8.dyn.ee
http://ipv8.community.net.au
http://www.iana.org/assignments/ipv4-address-space
http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt