RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt

["Thomas D. Nadeau" <tnadeau@cisco.com>]

	I agree.

	--Tom


> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
> Sent: Tuesday, August 05, 2003 12:04 PM
> To: cheenu@alumni.princeton.edu; bwijnen@lucent.com; 
> dperkins@dsperkins.com
> Cc: tnadeau@cisco.com; arunv@force10networks.com; 
> zinin@psg.com; swallow@cisco.com; loa.andersson@utfors.se; 
> mreview@ops.ietf.org
> Subject: RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
> 
> 
> FYI, forwarded with permission. I think this is a 
> valid/useful suggestion by Dave.
> 
> Thanks,
> Bert 
> >> -----Original Message-----
> >> From: David T. Perkins [mailto:dperkins@dsperkins.com]
> >> Sent: maandag 4 augustus 2003 17:25
> >> To: Wijnen, Bert (Bert)
> >> Subject: RE: MIB Doctor review of: draft-ietf-mpls-ftn-mib-07.txt
> >> 
> >> 
> >> Bert,
> >> 
> >> I probably screwed up the first example, since I changed it pretty 
> >> late last night. Thanks for the catch.
> >> 
> >> If I was writing the MIB, I would not support 'createAndWait' or 
> >> 'notInService'. That is,
> >>    mplsFTNMapRowStatus OBJECT-TYPE 
> >>       SYNTAX RowStatus { active(1), createAndGo(4),destroy(6) }
> >>       ...
> >> 
> >> With the 'createAndWait' and 'notInService' the question 
> as to when 
> >> the side effect occurs becomes an issue. (Or you could say 
> that it is 
> >> up to the agent to determine, but that leads to more code on the 
> >> manager.)
> >> 
> >> Regards,
> >> /david t. perkins
> >> 
>