[Diffserv] FlowId and FlowIdOrAny

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Mon, 03 February 2003 17:08 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 MAA13496 for <diffserv-archive@odin.ietf.org>; Mon, 3 Feb 2003 12:08:42 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h13HDju05492 for diffserv-archive@odin.ietf.org; Mon, 3 Feb 2003 12:13:45 -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 h13H3DJ04012; Mon, 3 Feb 2003 12:03:13 -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 h13Gu2J03637 for <diffserv@optimus.ietf.org>; Mon, 3 Feb 2003 11:56:02 -0500
Received: from auemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12981 for <diffserv@ietf.org>; Mon, 3 Feb 2003 11:50:28 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h13Gs1i02855 for <diffserv@ietf.org>; Mon, 3 Feb 2003 11:54:02 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <DVZNQFY9>; Mon, 3 Feb 2003 17:53:55 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155D6C368@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: rap@ops.ietf.org, diffserv@ietf.org
Date: Mon, 3 Feb 2003 17:53:46 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Diffserv] 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>

I have posted an initial I-D for the two TCs to the
mibs@ops.ietf.org mailing list.
Mailing list info:
for generic MIB (Management Information Base) discussions: 

General Discussion: mibs@ops.ietf.org
To subscribe:       majordomo@ops.ietf.org
     in body:       subscribe mibs
     Archive:       ftp://ops.ietf.org/pub/lists/


Thanks,
Bert 

> -----Original Message-----
> From: Dan Grossman [mailto:dan@dma.isg.mot.com]
> Sent: dinsdag 21 januari 2003 17:34
> To: Juergen Schoenwaelder
> Cc: bwijnen@lucent.com; rap@ops.ietf.org; diffserv@ietf.org
> Subject: Re: [Diffserv] FlowId and FlowIdOrAny
> 
> 
> 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/curre
nt/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