Re: Fuzzy-layering and its suggestion

"Jason Gao" <jag@kinet.com.cn> Mon, 09 September 2002 10:13 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27873 for <ietf-web-archive@odin.ietf.org>; Mon, 9 Sep 2002 06:13:04 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id GAA25500 for ietf-outbound.10@loki.ietf.org; Mon, 9 Sep 2002 06:14:01 -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 GAA25430 for <ietf-mainout@loki.ietf.org>; Mon, 9 Sep 2002 06:09:40 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA27800 for ietf-mainout@loki.ietf.org; Mon, 9 Sep 2002 06:08:01 -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 GAA27796 for <ietf@ietf.org>; Mon, 9 Sep 2002 06:07:56 -0400 (EDT)
Received: from fujitsu [61.149.4.102] by mail.gmmedia.net.cn with ESMTP (SMTPD32-7.04) id A044650052; Mon, 09 Sep 2002 17:56:20 +0800
Message-ID: <00e601c257e9$19aa68b0$5019e29f@fujitsu>
From: Jason Gao <jag@kinet.com.cn>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: ietf@ietf.org
References: <001f01c254dd$b30bdd40$5019e29f@fujitsu> <3D7B0CAD.C8339952@hursley.ibm.com>
Subject: Re: Fuzzy-layering and its suggestion
Date: Mon, 09 Sep 2002 18:10:18 +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 GAA27797
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

> Jason Gao wrote:
> ...
> > --- IPv6 flow label assignment
> > 
> > Transport layer may set a 'control' bit in the IPv6 Traffic Class octet of the initiating packet
> > during the setup phase of a connection.
> > 
> > 
> > 
> > The edge router inspects the control bit. If it is set, the edge router can further inspect the
> > packet, and reserve resource as required by the piggybacked resource reservation header in the
> > transport layer packet, allocate and/or assign a flow label to the expected connection, put the flow
> > label in the flow label field of the initiating acknowledgement packet.
> 
> No. There is no such usage of the traffic class octet. See RFC 2474.
> Also, only the source host of a packet may set the flow label.
> See draft-ietf-ipv6-flow-label-03.txt
> 
>    Brian
> 
Well, both the draft and RFC 2474 are not the final standard. And both the traffic class octet and the flow label field are subject to further discuss. So I didn't mean to prove fuzzy-layering by the fields in IPv6 but instead tried to make some suggestions for the development of IPv6 in the QoS domain, according to the fuzzy-layering practices.

Anyway, thanks for the comment!

Jason