The MPLS WG Archive

[Soumen Sarkar <soumen@sasken.com>]

On Tue, 23 Jan 2001, Thomas D. Nadeau wrote:

>
>
> 	Hi,
>
> 	In addition to the 4 agreed upon changes from Joan
> and Shobhan, the co-authors of the MPLS-TE-MIB have three
> objects that we would like added/modified in the existing
> MPLS-TE-MIB and thought that we would post them to
> the mailing list prior to adding them. I understand
> that last call was finished last Friday, but I
> was too busy to send these out, so I apologize.
>
> 	HopTable:
>
> 	Add an object called mplsTunnelHopExcludeAddr whose
> purpose it is to denote whether or not this hop specifies
> an 'included' or 'excluded' hop. The default is 'include',
> so the DEFVAL is false(2).
>
> mplsTunnelHopIncludeExclude  OBJECT-TYPE
>     SYNTAX        TruthValue
>     MAX-ACCESS    read-create
>     STATUS        current
>     DESCRIPTION
>            "If this value is set to true(1), then this indicates that this
> hop MUST be included in the tunnel's path. If this value is set to
> false(2), then this hop MUST be avoided when calculating the path for this
> tunnel. The default value of this object is true(1), so that by default all
> indicated hops are included in the CSPF path computation."
>     ::= { mplsTunnelHopEntry xxx }
>
>
 Tom, I think the name mplsTunnelHopIncludeExclude is creating
 confusion since its type is TruthValue. Since the default value
 would be true(1), I suggest the name to be : mplsTunnelHopInclude
 It will be aligned with its semantic.
-regards,
Soumen