[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Diffserv] Re: FlowId and FlowIdOrAny
[ post by non-subscriber. with the massive amount of spam, it is easy to miss
and therefore delete posts by non-subscribers. if you wish to regularly
post from an address that is not subscribed to this mailing list, send a
message to <listname>-owner@ops.ietf.org and ask to have the alternate
address added to the list of addresses from which submissions are
automatically accepted. ]
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/>