RE: [Diffserv] Re: FlowId and FlowIdOrAny

OK, so if I understand you correctly, then the newly proposed
TCs would also be useable for the Intserv MIB when they do
a revision, right? And again that can then be considered
a bug fix. 

So we now have a conflict in that if we make it Integer32, 
then diffserv MIB needs to deprecate and create a new object
If we make it Unsigned32, then Intserv MIB needs to deprecate
and create a new object.

It then seems to me that making it Integer32 as suggested by
Juergen then makes the most sense, since that seems to be
then more consistent with how we have done this at other
places (that is, used a -1 value to mean any).

Comments?

Thanks,
Bert 

> -----Original Message-----
> From: Brian E Carpenter [mailto:[email protected]]
> Sent: dinsdag 21 januari 2003 15:18
> To: Juergen Schoenwaelder
> Cc: [email protected]; [email protected]; [email protected]
> Subject: Re: [Diffserv] Re: FlowId and FlowIdOrAny
> 
> 
> 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/>
>