[Diffserv] RE: FlowId and FlowIdOrAny

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Tue, 21 January 2003 12:22 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26768 for <diffserv-archive@odin.ietf.org>; Tue, 21 Jan 2003 07:22:56 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0LCeSc12838 for diffserv-archive@odin.ietf.org; Tue, 21 Jan 2003 07:40:28 -0500
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LCWfJ11811; Tue, 21 Jan 2003 07:32:41 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0LCOdJ11549 for <diffserv@optimus.ietf.org>; Tue, 21 Jan 2003 07:24:39 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26567 for <diffserv@ietf.org>; Tue, 21 Jan 2003 07:06:36 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com []) by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LCA0T24473 for <diffserv@ietf.org>; Tue, 21 Jan 2003 07:10:01 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <YJ267BV9>; Tue, 21 Jan 2003 13:10:00 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BADE65@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>, bwijnen@lucent.com
Cc: rap@ops.ietf.org, diffserv@ietf.org
Date: Tue, 21 Jan 2003 13:09:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Diffserv] RE: FlowId and FlowIdOrAny
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>

Ok, good, cause I was surprised to see a -1 in an Unsigned32.

Now... if we do this, then this could still be used by the
framework pib. 
However, for the diffserv-mib it would mean they must 
deprecate a current object and create a new one (switching
from Unsigned to Integer32 causes a change on the wire!).

The solution presented earlier could be considered as a
bug fix and would not require the diffserv-MIB to
deprecate the existing object


> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
> Sent: dinsdag 21 januari 2003 11:24
> To: bwijnen@lucent.com
> Cc: rap@ops.ietf.org; diffserv@ietf.org
> Subject: FlowId and FlowIdOrAny
> I changed the subject line and fixed the proposed TC. So here is where
> I think we are. I have also reduced the CC list and I have added the
> diffserv mailing list since diffserv folks should be in the loop I
> think.
>       DISPLAY-HINT "d"
>       STATUS       current
> 	"The flow identifier in an IPv6 header that may be used to
> 	 discriminate traffic flows."
> 	"RFC 2460"
>       SYNTAX       Integer32 (0..1048575)
>       DISPLAY-HINT "d"
>       STATUS       current
> 	"The flow identifier in an IPv6 header that may be used to
> 	 discriminate traffic flows. The value of -1 is used to
> 	 indicate a wildcard, i.e. any value."
> 	"RFC 2460"
>       SYNTAX       Integer32 (-1 | 0..1048575)
> Open issues:
> - Is the flow identifier the same as the flow label? I guess so. If
>   this is true, then we should probably use the TC names FlowLabel
>   and FlowLableOrAny and also change the wordings in the description
>   clause.
> - The name of the MIB modules which will contain these definitions.
> - Since Fred kind of said that the diffServMultiFieldClfrFlowId
>   object should have had a wildcard, can we agree that this is 
>   actually a bug in RFC 3289 which will be fixed by using FlowIdOrAny
>   in the next revision of the DIFFSERV-MIB?
> /js
> -- 
> Juergen Schoenwaelder    

diffserv mailing list
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html