Re: [Diffserv] FlowId and FlowIdOrAny

Dan Grossman <dan@dma.isg.mot.com> Tue, 21 January 2003 16:55 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 LAA05072 for <diffserv-archive@odin.ietf.org>; Tue, 21 Jan 2003 11:55:02 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0LHCdQ32673 for diffserv-archive@odin.ietf.org; Tue, 21 Jan 2003 12:12:39 -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 h0LH1eJ31005; Tue, 21 Jan 2003 12:01:40 -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 h0LGqBJ30617 for <diffserv@optimus.ietf.org>; Tue, 21 Jan 2003 11:52:11 -0500
Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04369 for <diffserv@ietf.org>; Tue, 21 Jan 2003 11:34:03 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h0LGbPOD024250; Tue, 21 Jan 2003 09:37:25 -0700 (MST)
Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id JAA15071; Tue, 21 Jan 2003 09:37:24 -0700 (MST)]
Received: from dma.isg.mot.com (ma07-0056.dma.isg.mot.com [150.21.30.201]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id LAA01833; Tue, 21 Jan 2003 11:34:14 -0500 (EST)
Message-ID: <3E2D7686.F5E7AC92@dma.isg.mot.com>
Date: Tue, 21 Jan 2003 11:34:14 -0500
From: Dan Grossman <dan@dma.isg.mot.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
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] FlowId and FlowIdOrAny
References: <7D5D48D2CAA3D84C813F5B154F43B155AA9B41@nl0006exch001u.nl.lucent.com> <200301211024.h0LAONtX026845@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

Um... since you're bringing the Diffserv folks into the middle of the conversation, would
it be possible to clue us in as to what we're talking about?
Thanks.

Juergen Schoenwaelder wrote:

> 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.
>
>   FlowId TECTUAL-CONVENTION
>       DISPLAY-HINT "d"
>       STATUS       current
>       DESCRIPTION
>         "The flow identifier in an IPv6 header that may be used to
>          discriminate traffic flows."
>       REFERENCE
>         "RFC 2460"
>       SYNTAX       Integer32 (0..1048575)
>
>   FlowIdOrAny TECTUAL-CONVENTION
>       DISPLAY-HINT "d"
>       STATUS       current
>       DESCRIPTION
>         "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."
>       REFERENCE
>         "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    <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

_______________________________________________
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