Re: [Diffserv] Re: FlowId and FlowIdOrAny

Brian E Carpenter <brian@hursley.ibm.com> Tue, 21 January 2003 14:36 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01197 for <diffserv-archive@odin.ietf.org>; Tue, 21 Jan 2003 09:36:40 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0LEsGi21789 for diffserv-archive@odin.ietf.org; Tue, 21 Jan 2003 09:54:16 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LEk8J21336; Tue, 21 Jan 2003 09:46:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LEdjJ21102 for <diffserv@optimus.ietf.org>; Tue, 21 Jan 2003 09:39:45 -0500
Received: from d12lmsgate-4.de.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00971 for <diffserv@ietf.org>; Tue, 21 Jan 2003 09:21:39 -0500 (EST)
Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22]) by d12lmsgate-4.de.ibm.com (8.12.3/8.12.3) with ESMTP id h0LEOx9J031248; Tue, 21 Jan 2003 15:25:00 +0100
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d12relay01.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id h0LEIbm2207108; Tue, 21 Jan 2003 15:22:28 +0100
Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA48648 from <brian@hursley.ibm.com>; Tue, 21 Jan 2003 15:18:27 +0100
Message-Id: <3E2D5689.F92C3392@hursley.ibm.com>
Date: Tue, 21 Jan 2003 15:17:45 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Cc: bwijnen@lucent.com, rap@ops.ietf.org, diffserv@ietf.org
Subject: Re: [Diffserv] Re: FlowId and FlowIdOrAny
References: <7D5D48D2CAA3D84C813F5B154F43B155BADE65@nl0006exch001u.nl.lucent.com> <200301211239.h0LCdh8T029652@hansa.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-BeenThere: diffserv@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=unsubscribe>
List-Id: Diffserv Discussion List <diffserv.ietf.org>
List-Post: <mailto:diffserv@ietf.org>
List-Help: <mailto:diffserv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The flow label in IPv6 was 24 bits at one time. So that looks like
a minor obsolescence in the Intserv MIB.

    Brian

Juergen Schoenwaelder wrote:
> 
> >>>>> Wijnen, Bert (Bert) writes:
> 
> Bert> Now... if we do this, then this could still be used by the
> Bert> framework pib.  However, for the diffserv-mib it would mean they
> Bert> must deprecate a current object and create a new one (switching
> Bert> from Unsigned to Integer32 causes a change on the wire!).
> 
> Oops, I missed that part of the picture. So if there is concensus to
> change the range as a bug fix in the DIFFSERV0MIB without introducing
> a new object (which formally the SMIv2 would require to do), then
> using Unsigned32 makes some sense. Note that this will also most
> likely include the definition of a DEFVAL which is in fact the new
> value.  However, if we decided that it is safer to use deprecate the
> filter obejct and introduce a new one, I prefer to use Integer32.
> 
> BTW, this is what I found in the INTEGRATED-SERVICES-MIB:
> 
>     intSrvFlowFlowId OBJECT-TYPE
>         SYNTAX      INTEGER (0..16777215)
>         MAX-ACCESS  read-only
>         STATUS      current
>         DESCRIPTION
>            "The flow ID that  this  sender  is  using,  if
>            this  is  an IPv6 session."
>        ::= { intSrvFlowEntry 11 }
> 
> Note that this range is [0..2^24-1] while the other definitions under
> discussion use a range of [0..2^20-1]. Note that RFC 2460 says:
> 
> :    Flow Label           20-bit flow label.  See section 6.
> 
> /js
> 
> --
> Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>
_______________________________________________
diffserv mailing list
diffserv@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html