[Diffserv] FW: FW: FlowId and FlowIdOrAny

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 23 January 2003 02:14 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13964 for <diffserv-archive@odin.ietf.org>; Wed, 22 Jan 2003 21:14:22 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0N2WeM06432 for diffserv-archive@odin.ietf.org; Wed, 22 Jan 2003 21:32:40 -0500
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N2JUJ05817; Wed, 22 Jan 2003 21:19:30 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0N28fJ05543 for <diffserv@optimus.ietf.org>; Wed, 22 Jan 2003 21:08:41 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13639 for <Diffserv@ietf.org>; Wed, 22 Jan 2003 20:49:51 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com []) by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0N1rGU09527 for <Diffserv@ietf.org>; Wed, 22 Jan 2003 20:53:16 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <YJ268HNF>; Thu, 23 Jan 2003 02:53:15 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE372@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Rap-wg (E-mail)" <rap@ops.ietf.org>, Diffserv@ietf.org
Date: Thu, 23 Jan 2003 02:51:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Diffserv] FW: FW: 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 checked with authors and WG chair of SSPM MIB

I have a request outstanding to author(s) of ipsec-conf-mib


-----Original Message-----
From: Andy Bierman [mailto:abierman@cisco.com]
Sent: woensdag 22 januari 2003 23:15
To: Wijnen, Bert (Bert)
Cc: Dan Romascanu (E-mail); Carl Kalbfleisch (E-mail); Bob Cole (E-mail)
Subject: Re: FW: FlowId and FlowIdOrAny

At 04:31 PM 1/22/2003 +0100, Wijnen, Bert (Bert) wrote:
>Are you following RAP or DIFFSERV WG mailing lists?

I am on the diffserv list.
Thanks for bringing this to our attention.

To be consistent with previous decisions related to
the DSMON MIB, the RMONMIB WG would prefer it if the
WG owning IPv6 flow standards would publish a MIB
module containing the appropriate TCs, so we can import
them into the SSPM MIB.


>We are discussing a common set of TCs to be used by multiple
>MIB and PIB modules.
>If your not up to date, you may want to check the mailing lists 
>archives. Discussion was over teh last week or two.
>p.s. I know I have this doc in AD review.... but you may
>want to check this part of it yet
>-----Original Message-----
>From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
>Sent: woensdag 22 januari 2003 15:19
>To: rap@ops.ietf.org; diffserv@ietf.org
>Subject: Re: FlowId and FlowIdOrAny
>I found some more objects that seem to model a flow label. It turns
>out that MIB authors are really creative...
>  ihfIPv6FlowLabel OBJECT-TYPE
>      MAX-ACCESS  read-create
>      STATUS      current
>          "The IPv6 Flow Label that the packet must match against.
>          This object is only used if ipv6FlowLabel is set in ihfType."
>      ::= { ipHeaderFilterEntry 13 }
>  They obviously have another mechanism to control whether the
>  object participates in a match.
>   sspmSourceProfileFlowLabel OBJECT-TYPE
>       SYNTAX      Integer32 (0..1048575)     -- 20-bit range (0 to 0xfffff)
>       MAX-ACCESS  read-create
>       STATUS      current
>           "This object is  used to specify the Flow Label  in a IPv6
>            packet (RFC 2460) to force special handling by the IPv6 routers for
>            non-default quality-of-service.
>            This object is meaningful only when sspmSourceDestAddressType is
>            ipv6(2).  The value of this object defaults to zero if not
>            set."
>       DEFVAL { 0 }
>       ::= { sspmSourceProfileEntry 7 }
>  This object seems to actually control how the flow label looks like
>  in packets coming from a synthetic traffic source.
>Note that these objects are called flow label rather than flowid and
>hence I did not find them the first time...
>Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>
diffserv mailing list
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html