Fw: Fuzzy-layering... - Towards better QoS solution in the IPv6 network

"Jason Gao" <jag@kinet.com.cn> Wed, 11 September 2002 02:15 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02385 for <ietf-web-archive@odin.ietf.org>; Tue, 10 Sep 2002 22:15:11 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id WAA06637 for ietf-outbound.10@loki.ietf.org; Tue, 10 Sep 2002 22:14: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 WAA06611 for <ietf-mainout@loki.ietf.org>; Tue, 10 Sep 2002 22:12:40 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02342 for ietf-mainout@loki.ietf.org; Tue, 10 Sep 2002 22:10:59 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from mail.gmmedia.net.cn ([210.51.18.129]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02338 for <ietf@ietf.org>; Tue, 10 Sep 2002 22:10:54 -0400 (EDT)
Received: from fujitsu [61.149.1.238] by mail.gmmedia.net.cn with ESMTP (SMTPD32-7.04) id A37614006C; Wed, 11 Sep 2002 09:59:18 +0800
Message-ID: <027301c25938$c86f6760$5019e29f@fujitsu>
From: Jason Gao <jag@kinet.com.cn>
To: ietf@ietf.org
Subject: Fw: Fuzzy-layering... - Towards better QoS solution in the IPv6 network
Date: Wed, 11 Sep 2002 10:13:12 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id WAA02339
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

But, as far as I know, IPv8 doesn't give a solution for the QoS issue. IPv6 has the potential. I think the killer applications of IPv6, or whichever the next generation IP protocol, are very likely what demand high QoS and natively peer-to-peer, such as video interactive game. If an application doesn't demand high QoS it can somehow be implemented with the inexpensive NAT middleboxes and/or message relays with ripe experience.
> 
> Jason.
> 
> ----- Original Message ----- 
> From: "Jim Fleming" <JimFleming@ameritech.net>
> To: "Fred Baker" <fred@cisco.com>; "Jason Gao" <jag@kinet.com.cn>
> Cc: <steinle@smartvia.de>; "Richard J. Sexton" <richard@vrx.net>; <karl@cavebear.com>; "Joe Baptista" <baptista@dot-god.com>; <jefsey@jefsey.com>; <andy@ccc.de>; "@quasar Internet Solutions, Inc." <shore@quasar.net>; "Vittorio Bertola" <vb@vitaminic.net>; <sotiris@hermesnetwork.com>; "Richard Henderson" <richardhenderson@ntlworld.com>; <k@widgital.com>; <jwkckid1@ix.netcom.com>; "Judith Oppenheimer" <joppenheimer@icbtollfree.com>; "Joanna Lane" <jo-uk@rcn.com>; <eric@hi-tek.com>; <DannyYounger@cs.com>; "Bruce Young" <Bruce@barelyadequate.info>
> Sent: Tuesday, September 10, 2002 8:28 PM
> Subject: Re: Fuzzy-layering and its suggestion - Towards better QoS solution in the IPv6 network
> 
> 
> > ----- Original Message ----- 
> > From: "Jason Gao" <jag@kinet.com.cn>
> > To: "Fred Baker" <fred@cisco.com>
> > > > 
> > > > 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.
> > > 
> > 
> > Actually, it is just the opposite. 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.
> > 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
> > 
> > 
>